When useradd is choosing an UID for a system account (what about other tools, and GIDs?), it first tries to use (min(existing_system_uid)-1), and only if that ID is outside of the SYS_UID_* range, it tries to use other values in "holes". This can lead to using surprisingly low values, potentially conflicting with static ID allocation. See bug 924501 comment 9 for a real-world scenario. Would it make sense to use the highest free UID in the SYS_UID_* range instead?
I suppose the reasoning behind the current algorithm is that if accounts get deleted, using the holes could assign UID of previously existing account to the new account. If there were strain files/directories of the old account bad things could potentially happen. Perhaps we could add some kind of heuristic such as choosing an UID from the first gap larger than X (how big the X should be though?) looking from the top of the SYS_UID range.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This BZ has been evaluated and we assessed that it is a valuable request to keep in the backlog and address it at some point in future. Currently we have no capacity nor will have in the foreseeable future to work on it. In such a situation keeping it in the backlog is misleading and setting the wrong expectation that we will be able to address it. Unfortunately we will not. To reflect this we are closing this BZ. If you disagree with the decision please reopen or create a new BZ. However this does not guarantee that the request will not be closed during the triage as we are currently applying much more rigor to what we actually can accomplish in the foreseeable future. Contributions and collaboration in the upstream community and CentOS Stream is always welcome! Thank you for understanding Red Hat Enterprise Linux Identity Management Team