Bug 923858 - uid/gid is inconsistent for openstack heat with rest of openstack projects
Summary: uid/gid is inconsistent for openstack heat with rest of openstack projects
Alias: None
Product: Fedora
Classification: Fedora
Component: setup
Version: 19
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-03-20 15:20 UTC by Steven Dake
Modified: 2016-04-26 21:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-03-20 17:44:52 UTC
Type: Bug

Attachments (Terms of Use)

Description Steven Dake 2013-03-20 15:20:34 UTC
Description of problem:
In bug #:

I requested a uid/gid openstack-heat.  Unfortunately the rest of the OpenStack packaging uses a uid/gid without the openstack- prefix.  We would prefer things be consistent as possible between openstack projects.  Any chance you would change this?

The goal would be to change the first field of the uidgid in setup to just "heat".

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

Comment 1 Ondrej Vasik 2013-03-20 16:57:43 UTC
I can change the ID reservation, but I can't handle the account name change. Is that a problem or you can handle it yourself? I mean - you should be able to handle the situation when you have a system with openstack-heat already created with the reserved ID.

Comment 2 Steven Dake 2013-03-20 17:24:58 UTC
I'm guessing you mean in the upgrade case from F18->F19.  The F18 package is in obsoletes because the package has been renamed.  So the upgrade case should work properly on an F18->F19 upgrade, but YMMV.

If you meant a different use case, let me know.


Comment 3 Ondrej Vasik 2013-03-20 17:39:17 UTC
I'll change the entry to the:
heat	187	187	/var/lib/heat		/sbin/nologin	heat

Comment 4 Ondrej Vasik 2013-03-20 17:44:52 UTC
Built as setup-2.8.67-1.fc20 - as it is cosmetic change, I don't plan to do that in F19 and older.

Note You need to log in before you can comment on or make changes to this bug.