RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 971037 - Allocate 'foreman' and 'foreman-proxy' usernames
Summary: Allocate 'foreman' and 'foreman-proxy' usernames
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: setup
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ondrej Vasik
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-05 14:00 UTC by Jordan OMara
Modified: 2014-11-09 22:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-05 21:59:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jordan OMara 2013-06-05 14:00:22 UTC 
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

ruby193-foreman and
ruby193-foreman-proxy

respectively.


homedir:  ${scl_root}/usr/share/foreman
          ${scl_root}/usr/share/foreman-proxy

eg
/opt/rh/ruby193/root/usr/share/foreman-proxy/
/opt/rh/ruby193/root/usr/share/foreman

package that creates it:  ruby193-foreman ruby193-foreman-proxy
Comment 1 Dominic Cleal 2013-06-05 14:09:32 UTC 
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:

foreman and
foreman-proxy

homedir:  /usr/share/foreman
          /usr/share/foreman-proxy
Comment 3 Ondrej Vasik 2013-06-05 15:35:08 UTC 
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.
Comment 4 Dominic Cleal 2013-06-05 15:39:52 UTC 
(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?
Comment 5 Ondrej Vasik 2013-06-05 15:45:45 UTC 
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.
Comment 6 Dominic Cleal 2013-06-05 21:59:25 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.