Here still encounter SystemError error when setting password in TUI, the detail error is not completely same as original error, but still can not update and save password successful. Test version: # cat /etc/redhat-release Red Hat Enterprise Virtualization Hypervisor release 6.7 (20150728.0.el6ev) # rpm -qa ovirt-node ovirt-node-3.2.3-14.el6.noarch Test Steps: 1. TUI installation RHEV-H 6.7 successful. 2. Login RHEV-H 3. Set password in Security TUI, the first time set password, there is no error display, the password can be updated and set successful. 4. Reboot RHEV-H 5. Set password in Security TUI, the second time to set password here, then you may 50% can reproduce this SystemError. 6. if don't encounter this error, then Reboot RHEV-H 7. Set password in Security TUI, the third time to set password here, then you probably 90% can reproduce this SystemError. 8. if don't encounter this error, then Reboot RHEV-H 8. Set password in Security TUI, the fourth time to set password, then 99.99% can reproduce this SystemError. 2015-07-29 03:50:58,414 INFO An exception during the transaction: Error replacing `/etc/shadow': Device or resource busy Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/ovirt/node/ui/__init__.py", line 949, in __run_transaction File "/usr/lib/python2.6/site-packages/ovirt/node/plugins.py", line 188, in dry_or File "/usr/lib/python2.6/site-packages/ovirt/node/ui/__init__.py", line 949, in <lambda> File "/usr/lib/python2.6/site-packages/ovirt/node/setup/core/security_page.py", line 124, in commit File "/usr/lib/python2.6/site-packages/ovirt/node/utils/security.py", line 99, in set_password File "/usr/lib/python2.6/site-packages/ovirtnode/password.py", line 44, in set_password SystemError: Error replacing `/etc/shadow': Device or resource busy 2015-07-29 03:50:58,425 INFO Changes were merged successfully #./ovirt-config-password ... Changing password for user 'admin'. New password: Retype new Password: [WARNING] You have provided a weak password! Strong passwords contain a mix of uppercase, lowercase, numeric and punctuation characters. They are six or more characters long and do not contain dictionary words. Reason: it is based on a dictionary word Traceback (most recent call last): File "/usr/lib64/python2.6/runpy.py", line 122, in _run_module_as_main File "/usr/lib64/python2.6/runpy.py", line 34, in _run_code File "/usr/lib/python2.6/site-packages/ovirt/node/tools/password.py", line 179, in <module> File "/usr/lib64/python2.6/cmd.py", line 142, in cmdloop File "/usr/lib64/python2.6/cmd.py", line 219, in onecmd File "/usr/lib/python2.6/site-packages/ovirt/node/tools/password.py", line 92, in do_admin File "/usr/lib/python2.6/site-packages/ovirt/node/tools/password.py", line 106, in do_set_admin_password File "/usr/lib/python2.6/site-packages/ovirt/node/tools/password.py", line 157, in __ask_and_set_user_pasword File "/usr/lib/python2.6/site-packages/ovirt/node/utils/security.py", line 99, in set_password File "/usr/lib/python2.6/site-packages/ovirtnode/password.py", line 44, in set_password SystemError: Error replacing `/etc/shadow': Device or resource busy Additional info 1. In RHEVM TUI to set password, we also can reproduce this issue. 2. In CIM TUI to set password, we also can reproduce this issue.
This is yet another regression which I did not expect. Despite that I'd suggest that we limit this bug to the initial password reset, because that bug was important to fix the automation. The regression should be moved to a new bug, and even if bad, IMO we can defer that fix to our next update.
(In reply to Fabian Deutsch from comment #5) > This is yet another regression which I did not expect. > > Despite that I'd suggest that we limit this bug to the initial password > reset, because that bug was important to fix the automation. > > The regression should be moved to a new bug, and even if bad, IMO we can > defer that fix to our next update. split new bug here. https://bugzilla.redhat.com/show_bug.cgi?id=1248371
The original bug issue is gone on build rhevh 6.7 (20150728.0.el6ev). According to comment 4 and comment 5, let's trace new error in new bug 1248371, so verified this bug.
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/RHBA-2015-1733.html