Description of problem: change root's passwd in setup report "/etc/shadow" device busy. Version-Release number of selected component (if applicable): 5.8-20111028.0 How reproducible: 50%. Steps to Reproduce: 1. install RHEV-H manually. 2. after installation is finished, reboot. 3. login with root. 4. change root's passwd in setup. Actual results: change passwd in setup report "/etc/shadow" device busy. Expected results: It should not report "/etc/shadow" device busy.
Created attachment 530912 [details] screenshot
Verified on 5.8-20111121.0, no this message show anymore.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Attempts to change the root user's password would result in a "device busy" error caused by multipathd keeping the file busy. A multipathd restart in the password setting script solves this problem.
Re-open this bug, because it's reproduced on 5.8-20120202: Red Hat Enterprise Virtualization Hypervisor release 5.8 (20120202.0) Virtualization hardware is unavailable. (No virtualization hardware was detected on this system) Hypervisor Configuration Menu 1) Configure authentication 5) Configure the host for RHEV 2) Set the hostname 6) View logs 3) Networking setup 7) Exit Hypervisor Configuration Menu 4) Register Host to RHN Choose an option to configure: 1 SSH password authentication is currently enabled. 1) Set the administrator password 3) Return to menu 2) Toggle SSH password authentication Choose an option: 1 Configure passwords Set the system administrator's (root) password: Stopping multipathd daemon: [ OK ] Starting multipathd daemon: [ OK ] cp: cannot remove `/etc/shadow': Device or resource busy New UNIX password:
it's odd, I tested this on another machine, cannot reproduce it. lower the priority.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Attempts to change the root user's password would result in a "device busy" error caused by multipathd keeping the file busy. A multipathd restart in the password setting script solves this problem.+Attempts to change the root user's password would result in a "device busy" error on the "/etc/shadow/" file. This occurred because multipathd held a lock on the file. The script that changes the password now restarts multipathd to release the lock, avoiding the "device busy" error.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Attempts to change the root user's password would result in a "device busy" error on the "/etc/shadow/" file. This occurred because multipathd held a lock on the file. The script that changes the password now restarts multipathd to release the lock, avoiding the "device busy" error.+Previously attempts to change the root user's password resulted in a "device busy" error on the "/etc/shadow/" file. This occurred because multipathd held a lock on the file. The script that changes the password now restarts multipathd to release the lock, avoiding the "device busy" error.
Test version: rhev-hypervisor5-5.9-20120808.0.el5 ovirt-node-1.0-86.el5 test steps: 1. install RHEV-H manually. 2. after installation is finished, reboot. 3. login with root. 4. change root's passwd in setup. Test result: 1) Set the administrator password 3) Return to menu 2) Toggle SSH password authentication Choose an option: 1 Configure passwords Set the system administrator's (root) password: New UNIX password: BAD PASSWORD: it is WAY too short Retype new UNIX password: Changing password for user root. passwd: all authentication tokens updated successfully. File persisted Successfully persisted /etc/shadow 1. RHEV-H will not report "/etc/shadow" device busy. 2. Login RHEV-H with the new password can successful. So the bug is fixed, change bug status to VERIFIED.
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. http://rhn.redhat.com/errata/RHBA-2013-0143.html