It will be possible to cut the branch off yourself, by run: koji --principal=@REALM revoke-permission admin This can then only fixed by an SQL edit until you have an second account with admin rights.
PR 3684
Metadata Update from @jcupova: - Custom field Size adjusted to None
Metadata Update from @jcupova: - Issue set to the milestone: 1.33
I'm not sure if we want to limit this action. We expect that "admin" is somebody who can also touch the db, so in case of fatal error, it still could be fixed. On the other hand - process of admin editing the policy accordingly and downgrading its permissions, then dropping admin permission altogether is also valid usecase. Asking @mikem for opinion.
I'm not sure if we want to limit this action
I agree. This is not a bug. With great power comes great responsibility.
Metadata Update from @tkopecek: - Issue set to the milestone: None (was: 1.33)
Metadata Update from @tkopecek: - Issue close_status updated to: Dropped - Issue status updated to: Closed (was: Open)
This issue has been migrated to Fedora Forge: https://forge.fedoraproject.org/koji/koji/issues/3681
Please continue any further discussion there.