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.

Description of problem:

For the upcoming system engine product, we need a reserved user and group of 'katello' for the service we are running. 


homedir:  /usr/share/katello
package that creates it:  katello-common


referenced bug 803740

Do you really need this static id reservation? Rpmdiff failure is only indicator - static id is required for network facing/communicating system accounts and daemons handling sensitive data - is it the case of this system account? If not, rpmdiff failure could be waived (static id range is limited).

Hey Ondrej,


"Rpmdiff failure is only indicator - static id is required for network
facing/communicating system accounts and daemons handling sensitive data"

I believe this is the case.  This is a network service that is holding user and
system information, so I would consider that 'sensitive data'.

I don't know that this is Z-stream worthy either.  As long as a UID is picked,
we can use that UID knowing it will be reserved in the future.  

Thanks,

-Justin

Thanks, I'll reserve 182:182 for katello. Removing z-stream request...

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0778.html