Red Hat Bugzilla – Bug 594155
wrong users and groups creation in spec file
Last modified: 2013-07-02 23:28:58 EDT
Description of problem:
Please fix user/group creation in your spec file. There were problems when
(UID != GID) && (UID<200) . For example:
Problem was caused by change/fix of shadow-utis behaviour. useradd does not
create group with same GID as user's UID for IDs < 200 (static/reserved) unless
it's done this way:
getent group qemu >/dev/null || groupadd -g 107 -r qemu
getent passwd qemu >/dev/null || \
useradd -r -u 107 -g qemu -G kvm -d / -s /sbin/nologin \
-c "qemu user" qemu
This issue should be fixed as soon as possible. Note, it can't be resolved by
any update once we have RHEL6 GA. Please fix it in Fedora too. thnx.
Hm, isn't the consensus in bug #593683 that useradd should be fixed to preserve the old behavior?
I agree that it wouldn't be a bad idea to modify the mysql spec file to make the group ID be specified explicitly, but I hardly think this is a blocker.
BTW, are you satisfied with the way the postgresql spec file does the same thing?
Yes the consensus was to fix useradd. Nevertheless, I recommend fixing spec files too.
Since useradd is already fixed this doesn't need to be blocker.
I think postgresql does user/group creation correctly.
mysql-5.1.47-1.fc12 has been submitted as an update for Fedora 12.
mysql-5.1.47-1.fc13 has been submitted as an update for Fedora 13.
mysql-5.1.47-1.fc11 has been submitted as an update for Fedora 11.
mysql-5.1.47-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
mysql-5.1.47-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
mysql-5.1.47-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.