#9222 Grant root access on batcave
Closed: Fixed 3 years ago by kevin. Opened 3 years ago by humaton.

Describe what you would like us to do:

Hi, I need root access to perform mass branching tasks.
This phase[1] of the mass branching requires me to ssh to pkgs01 and for that, I need root access.
fas: humaton

When do you need this to be done by? (YYYY/MM/DD)

ASAP

[1] - https://docs.pagure.org/releng/sop_mass_branching.html#dist-git


Well, it's not that I don't trust you, but we have a process for granting sysadmin-main access... and a rush to do a task is not part of it. :)

So, can you get @mohanboddu to do this part? or perhaps we could just do a tmux share and get you in that way and watch things?

This also relates to a bug with pkgs01/src.fedoraproject.org that it doesn't allow user logins anymore. ;(

@kevin yeah, @mohanboddu is running it.
I am opening this issue for future requirements.

Metadata Update from @mobrien:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, medium-gain, medium-trouble

3 years ago

I was wondering if we should consider having an ansible script to do this step. It seems pretty straight forward except for the question: how to give it (the script) access to the input file listing all the repos to branch?

I was wondering if we should consider having an ansible script to do this step. It seems pretty straight forward except for the question: how to give it (the script) access to the input file listing all the repos to branch?

Could the input file just be a file in the ansible repo that can be updated before running each time?

So, lets close this for now...

First, we may well add @humaton to sysadmin-main, but we usually do that before flock and there's a process.

Next, we want to make branching a ansible-playbook, if we did that we could just automate this away.

We can revisit this next branching if we haven't solved it by then.

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

3 years ago

Hi,
I am reopening this issue, we had another 2 branching events since this was reported.
Another thing is that I would like to also be able to delete dist-git branches since that kind of issue is landing in releng tracker.
Also during the processing of scm-requests, I have created some branches that should not have been created.

Can I get the access pretty please?

Metadata Update from @humaton:
- Issue status updated to: Open (was: Closed)

3 years ago

Hey @humaton we have added you to sysadmin-main now. Congrats. :)

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

3 years ago

Login to comment on this ticket.

Metadata