Red Hat Bugzilla – Bug 971037
Allocate 'foreman' and 'foreman-proxy' usernames
Last modified: 2014-11-09 17:56:41 EST
Description of problem:
For the upcoming satellite 6 product and the RHOS 3.0 openstack foreman installer tech preview, we need a reserved user and group of 'foreman' and 'foreman-proxy' for the service we are running.
Both of these packages are inside the ruby193 SCL and are provided by
package that creates it: ruby193-foreman ruby193-foreman-proxy
Hmm, the package names and home directories are different between Satellite and RHOS currently. In Sat6 (probably more the canonical home for Foreman), package names are:
Unfortunately, I no longer can do the reservations that easily. Fedora Packaging Committee decided to change the guidelines for the reservations and all requests have to go through their review. See https://fedoraproject.org/wiki/Packaging:UsersAndGroups for details.
Please file a ticket at https://fedorahosted.org/fpc/newticket and put me to cc so I will know about their decision. Based on it, I can add the reservation to setup Rawhide package and then to RHEL-6.5.
(In reply to Ondrej Vasik from comment #3)
> Unfortunately, I no longer can do the reservations that easily. Fedora
> Packaging Committee decided to change the guidelines for the reservations
> and all requests have to go through their review. See
> https://fedoraproject.org/wiki/Packaging:UsersAndGroups for details.
Jordan, the criteria listed here seem to focus mainly on NFS or sharing of UIDs between computers, which isn't applicable to Foreman. Perhaps this is sufficient rationale to waive rpmdiff issue you encountered?
I know rpmdiff is suggesting the static reservations everywhere - but they should be used only where useful. On other places, dynamic allocation should be fine and you could probably waive this, but I'll wait for Jordan's opinion.
I don't think a static allocation would qualify as useful, nor would it satisfy the Fedora criteria from my understanding of them. There aren't any places in Foreman where I can see that UIDs across hosts would matter, and there's no NFS use. Closing this bug, thanks Ondrej.