Description of problem: messages log flooded with 'Failed to reset devices.list on /machine.slice: Invalid argument'. Version-Release number of selected component (if applicable): Linux 3.10.0-229.14.1.el7.x86_64 rpm -qa | grep systemd systemd-208-20.el7_1.6.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Can you please provide the RHEV-H version and sosreport (run sos on the console) from the host?
RHEV Hypervisor - 7.1 - 20151015.0.el7ev RHEV Manager - 3.5.5-0.1.el6ev
This is likely a dupe of bug 1178848.
Hiding comment 4 to protect some sensitive informations.
Ying, can you reproduce this issue?
(In reply to Fabian Deutsch from comment #6) > Ying, can you reproduce this issue? Test version: rhev-hypervisor7-7.1-20151015.0 + ovirt-node-3.2.3-23.el7.noarch + systemd-208-20.el7_1.6.x86_64 rhev-hypervisor7-7.2-20151123.0 + ovirt-node-3.2.3-29.el7.noarch + systemd-219-19.el7.x86_64 Test steps: 1. Install RHEV-H. 2. Login hypervisor, configure network with bond. 3. Check /var/log/messages (grep "Failed to reset devices.list" /var/log/messages) 4. Reboot host repeatedly. 5. Check /var/log/messages again. Test result: # grep "Failed to reset devices.list" /var/log/messages # We can't reproduce this issue on our test env.
Hi Max, Can you please provide the detail reproduce steps? or could you help us to verify this bug? Thanks!
Hi Chen, Can you please add any VM on hypervisor(from template or install)? On our's empty hypervisors there are no errors in messages file.
(In reply to Max from comment #9) > Hi Chen, > > Can you please add any VM on hypervisor(from template or install)? On our's > empty hypervisors there are no errors in messages file. Hi Max, Thanks for your advice, I can reproduce this issue now. Test version: RHEV Hypervisor-7.1-20151015.0.el7ev ovirt-node-3.2.3-23.el7.noarch Test steps: 1. Install RHEV-H. 2. Login hypervisor, configure network 3. Register to RHEV-M 4. Create VM. 5. Check /var/log/messages (grep "Failed to reset devices.list" /var/log/messages) 6. Reboot host repeatedly. 7. Check /var/log/messages again. Test result: # grep "Failed to reset devices.list" /var/log/messages Nov 27 02:36:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:37:56 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:38:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:40:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:40:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:40:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:40:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:42:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:44:02 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:46:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:48:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:50:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:50:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Nov 27 02:50:01 localhost systemd: Failed to reset devices.list on /machine.slice: Invalid argument Hi ycui, Please give qa_ack. Thanks!
Test version: rhev-hypervisor7-7.2-20151210.1 ovirt-node-3.6.0-0.24.20151209gitc0fa931.el7ev.noarch Test steps: 1. Install RHEV-H. 2. Login hypervisor, configure network 3. Register to RHEV-M 4. Create VM. 5. Check /var/log/messages (grep "Failed to reset devices.list" /var/log/messages) 6. Reboot host repeatedly. 7. Check /var/log/messages again. Test result: Above messages log was gone. 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. https://rhn.redhat.com/errata/RHSA-2016-0379.html