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 652287 - RHEVM User and Group ID reservation request
Summary: RHEVM User and Group ID reservation request
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: setup
Version: 6.0
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: rc
: ---
Assignee: Ondrej Vasik
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-11 14:53 UTC by Doron Fediuck
Modified: 2011-05-19 11:54 UTC (History)
3 users (show)

Fixed In Version: setup-2.8.14-11.el6
Doc Type: Bug Fix
Doc Text:
The vdsm-reg package creates a user ID (UID) pair and group ID (GID) pair, both with the name "rhevm" and number "109". This user and group are used as a virtualization agent for Red Hat Enterprise Virtualization Manager. Previously, this UID/GID pair were not reserved during setup and other packages or administrators could accidentally assign those values to other users and groups. The setup package now reserves these UID and GID names and numbers. Accidental clashes with other users and groups are therefore avoided.
Clone Of:
Environment:
Last Closed: 2011-05-19 11:54:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0524 0 normal SHIPPED_LIVE setup bug fix and enhancement update 2011-05-18 17:44:56 UTC

Description Doron Fediuck 2010-11-11 14:53:38 UTC 
Description of problem:
As a part of RHEV-M development, we need a specific user and group
in RHEL in order to setup the RHEV agent properly.

Expected results:
1. user / group name: rhevm / rhevm
2. home directory: /home/rhevm
Comment 2 Ondrej Vasik 2010-11-11 15:06:22 UTC 
If you really need it, home directory in /home/rhevm is possible, however /var/<something> is in bigger use in the case of system accounts. 
As the other virt-related accounts are on 107:107 and 108:108 , I think the best would be to reserve 109:109 for rhevm.

Could you please add which package should own/create this account?
Comment 3 Doron Fediuck 2010-11-11 16:38:49 UTC 
(In reply to comment #2)
> If you really need it, home directory in /home/rhevm is possible, however
> /var/<something> is in bigger use in the case of system accounts. 
You are correct, but rhevm will follow the vdsm user (36), and therefore
I need a similar home.

> As the other virt-related accounts are on 107:107 and 108:108 , I think the
> best would be to reserve 109:109 for rhevm.
Very well- you're the master :)
> 
> Could you please add which package should own/create this account?
vdsm-reg

Thanks again!
Comment 4 Ondrej Vasik 2010-11-11 20:25:04 UTC 
Ok, will reserve 109:109 in Fedora Rawhide in next build...
Comment 5 Ondrej Vasik 2010-11-12 12:58:08 UTC 
Reserved in Fedora Rawhide - setup-2.28-1.fc15 ...
Comment 6 Doron Fediuck 2010-11-15 07:20:26 UTC 
(In reply to comment #5)
> Reserved in Fedora Rawhide - setup-2.28-1.fc15 ...

Thanks!
What about RHEL ?
Comment 7 Ondrej Vasik 2010-11-15 12:52:50 UTC 
It needs 3 acks for commit into RHEL-6 trees ... qa_ack is missing ... but feel free to use that uidgid pair.
Comment 8 Ondrej Vasik 2010-11-15 12:53:53 UTC 
At least in RHEL-6 - in RHEL-5 I can't guarantee it (as the threshold for uidgid reservation in RHEL-5 and older is only 100 - and I don't have free uidgid pairs there).
Comment 12 Florian Nadge 2011-03-02 18:20:14 UTC 
Please be so kind and add a few key words to the technical note of this
bugzilla entry using the following structure:

Cause:

Consequence:

Fix:

Result:


For details, see:
https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks
Comment 13 Florian Nadge 2011-03-02 18:20:33 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause
    What actions or circumstances induced the feature request.
Consequence
    What action was inhibited by the feature’s absence.
Change
    What was done to implement the feature.
    Note: backported from upstream is not an explanation.
Result
    What now happens when the actions or circumstances above occur.
    Note: this is not the same as the feature request was fulfilled.
Comment 14 Ondrej Vasik 2011-03-03 09:15:39 UTC 
These are already present in errata description text ... but ok, adding to
technotes field.
Comment 15 Ondrej Vasik 2011-03-03 09:15:39 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,10 +1 @@
-Cause
+This updated setup package reserves the new "rhevm" user ID and group ID, and the userid (UID) and groupid (GID) numbers (109:109), which should prevent accidental usage of that UID/GID pair by other packages and administrators. The "rhevm" user and group IDs are created by vdsm-reg package and used as virtualization agent for RHEV-M.-    What actions or circumstances induced the feature request.
-Consequence
-    What action was inhibited by the feature’s absence.
-Change
-    What was done to implement the feature.
-    Note: backported from upstream is not an explanation.
-Result
-    What now happens when the actions or circumstances above occur.
-    Note: this is not the same as the feature request was fulfilled.
Comment 16 Ryan Lerch 2011-04-19 04:12:14 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-This updated setup package reserves the new "rhevm" user ID and group ID, and the userid (UID) and groupid (GID) numbers (109:109), which should prevent accidental usage of that UID/GID pair by other packages and administrators. The "rhevm" user and group IDs are created by vdsm-reg package and used as virtualization agent for RHEV-M.+The vdsm-reg package creates a user ID (UID) pair and group ID (GID) pair, both with the name "rhevm" and number "109". This user and group are used as a virtualization agent for Red Hat Enterprise Virtualization Manager. Previously, this UID/GID pair were not reserved during setup and other packages or administrators could accidentally assign those values to other users and groups. The setup package now reserves these UID and GID names and numbers. Accidental clashes with other users and groups are therefore avoided.
Comment 19 errata-xmlrpc 2011-05-19 11:54:35 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0524.html
Note You need to log in before you can comment on or make changes to this bug.