Description of problem: ERROR message was shown in vdsm.log on host when suspend by RHEVM. Version-Release number of selected component (if applicable): libvirt-0.10.2-37.el6.x86_64 rhevm-3.3.3-0.52.el6ev.noarch qemu-kvm-rhev-0.12.1.2-2.427.el6.x86_64 vdsm-4.13.2-0.17.el6ev.x86_64 How reproducible: 100% Steps to Reproduce: 1. prepare an RHEVM server. 2. create date center,cluster,host. 3. create vm on host. notes: not install os. 4. chick suspend button. 5. check vdsm.log on host. #tail -f vdsm.log | grep ERROR Actual results: 16:09:49,485::vmChannels::53::vds::(_handle_event) Received 00000019 on fileno 7 Expected results: should not show ERROR message. Additional info: storage type:NFS,ISCSI.
this is normal during VM life transitions. since it's widespread enough I'd consider lesser importance (warn)
Merged to u/s master LOGLEVEL is now INFO - For these issues it does not even make sense to WARN or report an ERROR. INFO is good enough when we need to investigate anything related.
Are we too late for 3.5?
(In reply to Dave Sullivan from comment #4) > Are we too late for 3.5? IMHO 3.5 RHEV should be still possible if it is important enough. It's not like that it is breaking anything.
this bug was moved to MODIFIED before vt4 build date thus moving to ON_QA. if you belive this bug isn't in vt4, please report to rhev-integ
This patch is not yet in the 3.5 branch. It has been moved from 3.6 to 3.5. The patch is still pending!
Verified using: vdsm-4.16.7-1.el6ev.x86_64 libvirt-0.10.2-46.el6.x86_64 sanlock-2.8-1.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64
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-0159.html