> vdsm.log in the node side, will help here too.
https://www.dropbox.com/s/zvnttmylmrd0hyx/vdsm.log.gz?dl=0. This log
contains only the messages at and after when a host was become
unresponsive due to storage issues.
> # rpm -qa | grep -i vdsm
> might help too.
vdsm-cli-4.16.14-0.el7.noarch
vdsm-reg-4.16.14-0.el7.noarch
ovirt-node-plugin-vdsm-0.2.2-5.el7.noarch
vdsm-python-zombiereaper-4.16.14-0.el7.noarch
vdsm-xmlrpc-4.16.14-0.el7.noarch
vdsm-yajsonrpc-4.16.14-0.el7.noarch
vdsm-4.16.14-0.el7.x86_64
vdsm-gluster-4.16.14-0.el7.noarch
vdsm-hook-ethtool-options-4.16.14-0.el7.noarch
vdsm-python-4.16.14-0.el7.noarch
vdsm-jsonrpc-4.16.14-0.el7.noarch
Hey Chris,
please open a bug [1] for this, then we can track it and we can help to
identify the issue.
I will do so.