Bug 749192

Summary: Ovirt User and Group ID reservation request
Product: [Retired] oVirt Reporter: Perry Myers <pmyers>
Component: ovirt-nodeAssignee: Mike Burns <mburns>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, apevec, leiwang, mburns, moli, ovasik, ovirt-bugs, ovirt-maint, pknirsch, ranglust, ycui
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 749154 Environment:
Last Closed: 2011-12-04 00:09:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 749154    
Bug Blocks:    

Description Perry Myers 2011-10-26 12:56:01 UTC
This bug is for creation of the ovirt user account on oVirt Node images.

+++ This bug was initially created as a clone of Bug #749154 +++

Description of problem:
As a part of ovirt-engine development, we need a specific user and group
in Fedora in order to setup the ovirt-engine agent properly.

Expected results:
1. user / group name: ovirt / ovirt
2. home directory: /home/ovirt

Comment 1 Alan Pevec 2011-10-29 15:25:55 UTC
(In reply to comment #0)
> This bug is for creation of the ovirt user account on oVirt Node images.

What would that account be used for on node, we don't run ovirt-engine?

Comment 2 Perry Myers 2011-10-29 15:35:33 UTC
I thought that by ovirt-engine agent they meant the agent that would run on the Nodes.  (i.e. vdsm)

Besides, we need to get rid of 'root' user usage on oVirt Node anyhow, so a user name like 'ovirt' would make sense for that.

Comment 3 Ondrej Vasik 2011-10-29 17:14:22 UTC
ovirt user and group id is already reserved in setup because of #513261 (by package libvirt ... but I don't see that user used there. Probably they decided to use only vdsm user...) Anyway - the id for ovirt user/group 108:108 is reserved, so if you use it safely (e.g.
getent group ovirt > /dev/null || /usr/sbin/groupadd -g 108 -r ovirt
getent passwd ovirt > /dev/null || /usr/sbin/useradd -r -u 108 -g ovirt \
       -c "ovirt user" -d / -s /sbin/nologin ovirt
) then I see no problem. (the ovirt id 108:108 is reserved even in RHEL-6).

Comment 4 Mike Burns 2011-12-02 15:41:39 UTC
ovirt-node doesn't specifically use the ovirt user, so I don't think there is a need for additional changes here.  

Ayal,

Is vdsm going to switch to using an ovirt user?  And if so, is the vdsm rpm going to handle creating it if it doesn't exist? Or do you expect it to already be there?

Comment 5 Ayal Baron 2011-12-03 22:47:52 UTC
(In reply to comment #4)
> ovirt-node doesn't specifically use the ovirt user, so I don't think there is a
> need for additional changes here.  
> 
> Ayal,
> 
> Is vdsm going to switch to using an ovirt user?  And if so, is the vdsm rpm
> going to handle creating it if it doesn't exist? Or do you expect it to already
> be there?

vdsm today and in current plans for future uses only user vdsm:kvm (36:36)

Comment 6 Mike Burns 2011-12-04 00:09:02 UTC
Closing as this does not apply to ovirt-node