mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[GH-ISSUE #459] Upgrade errors: [ERR.] <x> doesn't seem to be a valid bastion group #118
Labels
No labels
answered
bug
documentation
enhancement
enhancement
feature
feature
kept-open-for-info
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/the-bastion#118
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KarlAustin on GitHub (Mar 26, 2024).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/459
When upgrading we're running into an issue where the upgrade script regenerates group sudoers files:
*** Regenerating all groups sudoers files from templates -> [ERR.] key<X> doesn't seem to be a valid bastion group -> [ERR.] key<Y> doesn't seem to be a valid bastion group ... -> [ERR.] Failed generating 13 sudoersWe hadn't up until now wanted to use SFTP or SCP wrappers, so on the basis of "it's working, don't break it" we're on v3.11.01. The error happens even when trying to go to 3.11.02.
OS: Ubuntu 22.04 LTS
Any help to fix without tearing it all down would be appreciated.
Thanks,
Karl
@KarlAustin commented on GitHub (Mar 26, 2024):
Fix: I had a moment, the server had been rebooted and I didn't mount the encrypted home. I'm going to go sit in the corner and give myself a talking to.