#619 Need a statically reserved uid and gid for heketi
Closed: invalid 2 years ago Opened 3 years ago by lpabon.

According to RHEL guidelines, a user/group id must be reserved (See https://bugzilla.redhat.com/show_bug.cgi?id=1306914 )

I submitted https://bugzilla.redhat.com/show_bug.cgi?id=1323545 according to RHEL RPM guidelines.


RHEL guidelines doesn't require static uid reservation - as they basically follow Fedora Packaging Guidelines. Is this static id reservation necessary from technical point of view? Are there any consequences when using dynamic system ids for heketi?

I've put this on the agenda for the meeting tomorrow, but if you don't answer the questions from ovasik (or turn up) then we'll probably pass on it for a week or so.

Sorry I'm not sure what meeting you mean. Is there a link to the meeting infomrmation? Also, I still have no information. I'll try to determine if bz 13069154 should still be opened.

Replying to [comment:3 lpabon]:

Sorry I'm not sure what meeting you mean. Is there a link to the meeting infomrmation? Also, I still have no information. I'll try to determine if bz 13069154 should still be opened.

The FPC has a weekly meeting on Thursdays. There was not enough people for a meeting this week, so it will be on the agenda for the meeting next Thursday.

The exact time of the meeting can be found in the Fedora Calendar: https://apps.fedoraproject.org/calendar/packaging/2016/4/18/

We discussed this at this weeks meeting (http://meetbot.fedoraproject.org/fedora-meeting-1/2016-04-28/fpc.2016-04-28-16.00.txt):

  • 619 Need a statically reserved uid and gid for heketi (geppetto,


    16:12:47)

...basically nothing happened as we didn't know any info.

We discussed this at this weeks meeting (http://meetbot.fedoraproject.org/fedora-meeting-1/2016-05-05/fpc.2016-05-05-16.00.txt):

  • 619 Need a statically reserved uid and gid for heketi (geppetto,


    16:16:29)

...still need some reasoning, what you need the uid/gid for etc.

Metadata Update from @james:
- Issue assigned to james

2 years ago

It's been a very long time and nothing has happened, so I'm just going to go ahead and close this. Feel free to reopen it or to file another ticket if the uid/gid pair is still needed and you are willing to provide the information we've requested.

Metadata Update from @tibbs:
- Issue close_status updated to: invalid
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata