Bug 698240
| Summary: | IPA is allowing multiple groups to contain the same gidNumber value | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jenny Severance <jgalipea> |
| Component: | doc-Identity_Management_Guide | Assignee: | Deon Ballard <dlackey> |
| Status: | CLOSED DUPLICATE | QA Contact: | ecs-bugs |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1 | CC: | dpal, jgalipea, mkosek, rcritten, tim |
| Target Milestone: | rc | Keywords: | Documentation |
| Target Release: | 6.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 697887 | Environment: | |
| Last Closed: | 2011-07-14 22:33:30 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 697887, 698671 | ||
| Bug Blocks: | 710235 | ||
|
Description
Jenny Severance
2011-04-20 14:04:10 UTC
Do I read this correctly that there will be no proper technical solution preventing this from happening but to hide it in some footnote or box in the documentation? Nobody is hiding anything. There is really no technical way to prevent all sorts of different misconfigurations with UID & GID if you decide to override them manually. IPA will do the right thing if you let if deal with UID and GID but if you have to set it up the way you want IPA should not prevent you from doing it. There are a lot of use cases where for compatibility people would want to mess with GID and UID. We would let them do it but explain the implications and potential problems in the documentation that that they are aware about the problems that their actions might cause. It is the best solution we can offer. Do you still disagree? I would rather like the tool to check if the UID/GID exists, and if it does throw an error. A "force" flag would then allow the admin to override this if he knows what it is doing. What this does it that it catches a behavior which I presume is most often undesired and unexpected, but still allows it if the admin know what he is doing. Much better than having this in the documentation, which -- let's be honest -- you hardly read from start to end. If the RHEL documentation is similar to the Fedora Guide I admit that it is excellent and helpful documentation, but I tend to read the least amount of documentation as possible and expect tools to help me, to give relevant and useful run-time information, and to prevent typical pitfalls. Makes sense? The default behavior of IPA is to let it assign UID/GID so we give the benefit of the doubt if the user provides it. I opened an RFE ticket to do the enforcement and provide a --force override. https://fedorahosted.org/freeipa/ticket/1231 Blocking the IPA 2.1 tracker bug. *** This bug has been marked as a duplicate of bug 693483 *** |