I'd like to request a new tracking group called: yggdrasil
yggdrasil
This group will be used to share the maintenance of COPRs for packages related to client tools used for registering Red Hat systems to Red Hat (e.g. subscription-manager, rhc, the yggdrasil stack).
subscription-manager
rhc
Please add to the new group the following accounts, enabling them as sponsors (so they can add more people in the future): - @csnyder - @jhnidek - @linkdupont - @mhorky - @ptoscano (myself)
No specific date.
Metadata Update from @zlopez: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-trouble, medium-gain, ops
Unfortunately I couldn't create the group. I got error that the group already exists, but I only found the user with username yggdrasil not any group. The user is somewhat strange it doesn't show up in FAS, just in IPA.
@kevin @abompard Any idea what to do here?
The yggdrasil user hasn't been touched since it was imported from the old FAS, it does not have the fasuser objectclass which makes it invisible in FAS. I can easily add it if needed. There is a group called yggdrasil that was created as the primary group of the yggdrasil user. There again it does not have the fasgroup objectclass.
fasuser
fasgroup
Adding the object classes is easy, but if the user has always been a bot user, we may want to remove it and create the group instead.
@kevin I would like your view on this as well.
In this case I am ok with just deleting the existing non fas user. Their email address is @fedoraproject.org so I have no idea the history there, but I don't think it could have been actually used for anything.
Because of what @kevin said, would it be possible to move forward by dropping the old bits and creating the new group?
Metadata Update from @zlopez: - Issue assigned to zlopez
I removed the user yggdrasil, created the yggdrasil group and added requested sponsors.
Metadata Update from @zlopez: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.