Bug 1192413
| Summary: | Reserve static gid/uid for jboss user (all MW & OpenShift layers impact) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vaclav Tunka <vtunka> |
| Component: | setup | Assignee: | Ondrej Vasik <ovasik> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | emajorsi, jscotka |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | setup-2.8.71-6.el7 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the Red Hat® JBoss® middleware and OpenShift products reserved the user ID and group ID pair 185:185 for the JBoss Application Server user called jboss-as. As this user is now going to be used more widely, a more generic name, jboss, has been chosen for it. With this update, the reservation of the user ID and group ID pair has been changed to jboss in the setup package, mentioning former reservations for jboss-as and wildfly.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-12 07:48:21 UTC | Type: | Bug |
| 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: | |||
| Bug Blocks: | 1192088 | ||
Vasku, jboss-as is reserved as 185/185 in RHEL 6 and RHEL 7. They are now discussing how to rename it properly. So I believe this is just confusion (and definitely not a blocker ;). Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-1599.html |
Description of problem: Currently then the EAP product is being installed in the RPM version a jboss user and jboss group is being created, although it does not use static uid/gids: JBOSS_SHELL=/sbin/nologin %{_sbindir}/groupadd -r jboss 2>/dev/null || : %{_sbindir}/useradd -c JBossAS -r -s $JBOSS_SHELL -d %{_localstatedir}/lib/jbossas -g jboss jboss 2>/dev/null || : This is a problem, because the generated uid can conflict with some services. A static user and group id should be used. Additionally, in the Cloud Enablement team we are preparing initial Docker images for JBoss products. Every product will be used launched as a regular jboss user. We need to base on a registered uid/gid to not choose an ID that could possibly conflict with some other service. Using static uid/gid in Docker is crucial, because the system administrator need to know upfront the id's to set up the volumes permissions for the selected user. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: