#6252 sudo access on bodhi stg and permissions for the ansible playbooks
Closed: Fixed 6 years ago Opened 6 years ago by jcline.

I need sudo access on the bodhi staging hosts (bodhi01.stg and bodhi-backend01.stg), and I also need permissions to run the bodhi Ansible playbooks.

Thanks!


I have sponsored you into the sysadmin-bodhi group, which @kevin informed me will give you access to adminstering Bodhi systems.

It doesn't seem that I have permissions to close this issue, but I believe it can be considered resolved now.

[jcline@bodhi01 ~][STG]$ sudo ls

We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

Password+Token: 
jcline is not in the sudoers file.  This incident will be reported.
[jcline@bodhi01 ~][STG]$ exit
 jcline  ~  devel  fedora-infra  ssh bodhi-backend01.phx2.fedoraproject.org 
Permission denied (publickey).
Killed by signal 1.

It seems like I still don't have any access :(

a few things to check:

  • are you using a stage token?
  • passwords in stage are typically older passwords since they don't get synced (try your password from 1 or 2 password changes ago)

stg fas is completely seperate from prod.... so if you sponsored him in prod it will not affect staging at all. Until we either:

1) sync prod->stg

or

2) you also sponsor him into the group in staging fas

If you want me to do a sync just let me know.

@kevin ah yes, I completely forgot about that. Sorry for the confusion. I'll go sponsor him there as well.

@jcline I have now sponsored you into the sysadmin-bodhi group in staging as well. I assume there's some time required for that to sync out, but I'm not sure how long that is. So "soon" you should be able to sudo there.

Metadata Update from @bowlofeggs:
- Issue assigned to bowlofeggs

6 years ago

I have become more powerful than you can possibly imagine (I can now close this ticket, thanks to @nb).

Metadata Update from @bowlofeggs:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Log in to comment on this ticket.

Metadata