mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[GH-ISSUE #346] Error create first account #88
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#88
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 @Gskill75 on GitHub (Oct 26, 2022).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/346
Hello,
when I would like create my first account I have this message.
Do you have an idea to debug this problem ?
For information I realized my installation with the puppet module.
Thank you in advance for your answer.
os facts:
NAME="AlmaLinux"
VERSION="8.6 (Sky Tiger)"
ID="almalinux"
ID_LIKE="rhel centos fedora"
@speed47 commented on GitHub (Oct 27, 2022):
Hello,
AlmaLinux is not officially supported, so minor alterations from CentOS (on which it seems to be based on) might get in the way.
Just tried on in a docker sandbox, a tiny change needs to be done on the script responsible for installing the prerequisites (system packages), as AlmaLinux doesn't name its repositories exactly the same. Namely, the "powertools" repo was not auto-enabled properly. You didn't seem to have encountered this issue, which might be because you already enabled it before. I'll still add a patch for this case (even if AlmaLinux is unsupported, the patch is minimal, so it's OK).
However I couldn't reproduce your problem. The Puppet module is known to work correctly under Debian, which has a lot of differences from RedHat/CentOS-derivatives, so it might also be part of the problem.
Can you enable debug mode and try again? This should give more details:
sed -i -re 's/"debug": .+/"debug": true,/' /etc/bastion/bastion.confThe failing command is
usermod, underneath, more preciselyusermod -a -G bastion-users toto, can you try to run that manually and see if your system outputs an error?@Gskill75 commented on GitHub (Oct 27, 2022):
Hello,
when I use the manual command I have this message :
usermod: group 'bastion-users' does not exist@Gskill75 commented on GitHub (Oct 27, 2022):
for more details on my installation :
class { 'thebastion': install_packages => true, bastion_name => 'xx.prod.bast-01', allowed_networks => ['10.0.0.0/24', '10.0.10.0/24'], default_login => 'xx', admin_accounts => ['xx_a', 'xx_a'], password_allowed => false, super_owner_accounts => ['xxx-bast'], http_proxy_enabled => true, }@speed47 commented on GitHub (Oct 28, 2022):
OK, so something went wrong with the install script when it tried to create the
bastion-usersgroup.Can you run this command:
/opt/bastion/bin/admin/install --managed-upgrade, it'll attempt to create it again if it doesn't exist, and you might have an error message there that should give us a hint as to why it failed, should it fail again@Gskill75 commented on GitHub (Oct 28, 2022):
Hello,
log-bastion-install.log
You will find attached the output in the order indicated.
I think indeed that there was a problem.
Thanks again for your time
@speed47 commented on GitHub (Oct 28, 2022):
The installation worked properly this time, so it seems that the script had not been launched previously, which is odd.
For good measure, can you also run this:
/opt/bastion/bin/admin/install-ttyrec.sh -a, this'll installovh-ttyrecas it appears to be missing also.I'll have to try to reproduce your problem with Puppet and your distro.