Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
If rpc is in a tree on Atomic, then it won't start, because it seems that it is directly (not indirectly through libs) checking that the rpc user exists in /etc/passwd.
But as users are in /usr/lib/passwd on Atomic, rpcbind refuses to start:
Logs:
Aug 31 08:46:38 atomic01.example.org systemd[1]: Starting RPC bind service...
Aug 31 08:46:38 atomic01.example.org systemd[1]: Started RPC bind service.
Aug 31 08:46:38 atomic01.example.org rpcbind[776]: cannot get uid of 'rpc': Success
Aug 31 08:46:38 atomic01.example.org systemd[1]: rpcbind.service: main process exited, code=exited, status=1/FAILURE
Aug 31 08:46:38 atomic01.example.org systemd[1]: Unit rpcbind.service entered failed state.
Version-Release number of selected component (if applicable):
# rpm -q rpcbind
rpcbind-0.2.0-26.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
To make it work:
# cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
centos:x:1000:1000:Cloud User:/home/centos:/bin/bash
# grep rpc /usr/lib/passwd >> /etc/passwd
# service rpcbind restart
Redirecting to /bin/systemctl restart rpcbind.service
# systemctl status rpcbind
rpcbind.service - RPC bind service
Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; static)
Active: active (running) since Fr 2015-09-04 07:56:14 UTC; 4s ago
Process: 13656 ExecStart=/sbin/rpcbind -w ${RPCBIND_ARGS} (code=exited, status=0/SUCCESS)
Main PID: 13657 (rpcbind)
CGroup: /system.slice/rpcbind.service
└─13657 /sbin/rpcbind -w
Description of problem: If rpc is in a tree on Atomic, then it won't start, because it seems that it is directly (not indirectly through libs) checking that the rpc user exists in /etc/passwd. But as users are in /usr/lib/passwd on Atomic, rpcbind refuses to start: Logs: Aug 31 08:46:38 atomic01.example.org systemd[1]: Starting RPC bind service... Aug 31 08:46:38 atomic01.example.org systemd[1]: Started RPC bind service. Aug 31 08:46:38 atomic01.example.org rpcbind[776]: cannot get uid of 'rpc': Success Aug 31 08:46:38 atomic01.example.org systemd[1]: rpcbind.service: main process exited, code=exited, status=1/FAILURE Aug 31 08:46:38 atomic01.example.org systemd[1]: Unit rpcbind.service entered failed state. Version-Release number of selected component (if applicable): # rpm -q rpcbind rpcbind-0.2.0-26.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: To make it work: # cat /etc/passwd root:x:0:0:root:/root:/bin/bash centos:x:1000:1000:Cloud User:/home/centos:/bin/bash # grep rpc /usr/lib/passwd >> /etc/passwd # service rpcbind restart Redirecting to /bin/systemctl restart rpcbind.service # systemctl status rpcbind rpcbind.service - RPC bind service Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; static) Active: active (running) since Fr 2015-09-04 07:56:14 UTC; 4s ago Process: 13656 ExecStart=/sbin/rpcbind -w ${RPCBIND_ARGS} (code=exited, status=0/SUCCESS) Main PID: 13657 (rpcbind) CGroup: /system.slice/rpcbind.service └─13657 /sbin/rpcbind -w