Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1168109

Summary: [RFE] Create neutron group with explicit GID
Product: Red Hat OpenStack Reporter: Eduard Barrera <ebarrera>
Component: openstack-neutronAssignee: John Schwarz <jschwarz>
Status: CLOSED WONTFIX QA Contact: Ofer Blaut <oblaut>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: apevec, calba, chrisw, ebarrera, felipe.alfaro, ihrachys, jlibosva, lpeer, majopela, nyechiel, tvvcox, yeylon
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-16 17:05:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eduard Barrera 2014-11-26 07:30:03 UTC 
Description of problem:

I am working on automatizing some of the tasks of the Openstack installation and while working on the LDAP data required for our setup I have found the following inconsistency:

While the rest of modules that create users/group give an explicit GID, neutron does not. This makes portability across environments more complicated.

The line under the package is the result of doing 

rpm -q --scripts $PACKAGE | grep group

openstack-ceilometer-common-2013.2.3-2.el6ost.noarch
getent group ceilometer >/dev/null || groupadd -r ceilometer --gid 166
openstack-cinder-2013.2.3-3.el6ost.noarch
getent group cinder >/dev/null || groupadd -r cinder --gid 165
openstack-glance-2013.2.3-3.el6ost.noarch
getent group glance >/dev/null || groupadd -r glance -g 161
openstack-heat-common-2013.2.3-2.el6ost.noarch
getent group heat >/dev/null || groupadd -r --gid 187 heat
openstack-keystone-2013.2.3-8.el6ost.noarch
getent group keystone >/dev/null || groupadd -r --gid 163 keystone
openstack-neutron-2013.2.3-16.el6ost.noarch
getent group neutron >/dev/null || groupadd -r neutron     <==============
openstack-nova-common-2013.2.3-12.el6ost.noarch
getent group nova >/dev/null || groupadd -r nova --gid 162


Version-Release number of selected component (if applicable):

I checked it in openstack-neutron-2013.2.3-14.el6ost.noarch and the problem is present

# rpm -q --scripts openstack-neutron-2013.2.3-14.el6ost.noarch | grep group
getent group neutron >/dev/null || groupadd -r neutron


How reproducible:

Install neutron package
Comment 9 Ihar Hrachyshka 2015-03-05 09:57:54 UTC 
Quoting http://fedoraproject.org/wiki/Packaging:UsersAndGroups

"To allocate a UID and/or GID, file a ticket for the FPC to evaluate. If the FPC finds that your package needs a soft static UID or GID, they will assign you one and add an entry documenting it to the /usr/share/doc/setup-*/uidgid file in the setup package. Because the number of UIDs and GIDs is limited, you need to justify your package's need for a soft static uid in the FPC ticket. Explain how the uids and gids are being shared between computers. If applicable, also explain why the program can't be adapted to use symbolic names (username and groupname) instead. If a specific UID or GID should be used, please mention it and why (for instance, it is the one used by upstream or the one used by other distributions). We will try to accommodate on a first-come-first serve basis if the UID/GID is available from within the Fedora system UID/GID range."

So neutron should allocate Fedora GID/UID and only then use it.
Comment 14 Lon Hohberger 2015-04-08 20:19:42 UTC 
Note that non-static UID/GID I think might have been intentional.

https://fedoraproject.org/wiki/Packaging:UsersAndGroups#Allocation_Strategies
Comment 15 Lon Hohberger 2015-04-08 20:20:45 UTC 
That is, I think that Dynamic Allocation strategy was chosen for neutron.
Comment 18 lpeer 2015-04-12 12:15:39 UTC 
Eduard,
After some investigation on this bug we realized that we do not meet the criteria for getting a static UID/GID allocated to the Neutron project.

Other projects who have static GID got it according to the old packaging guidelines, other projects like Neutron, Trove, Ironic do not have it and are not eligible for it.

We recommend the customer to pre-allocate a static GID before installing the openstack packages in case he has dependencies on such allocation.

Could you please communicate that to the customer?

Thanks, Livnat
Comment 20 RHEL Program Management 2015-04-16 17:05:38 UTC 
Product Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Comment 21 Red Hat Bugzilla 2023-09-14 02:51:29 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days