
Htis issue can be resolve by downgrading of the packages: Installing : vdsm-api-4.30.32-1.el7.noarch 1/26 Installing : vdsm-common-4.30.32-1.el7.noarch 2/26 Installing : vdsm-yajsonrpc-4.30.32-1.el7.noarch 3/26 Installing : vdsm-network-4.30.32-1.el7.x86_64 4/26 Installing : vdsm-python-4.30.32-1.el7.noarch 5/26 Installing : vdsm-jsonrpc-4.30.32-1.el7.noarch 6/26 Installing : vdsm-http-4.30.32-1.el7.noarch 7/26 Installing : vdsm-hook-vmfex-dev-4.30.32-1.el7.noarch 8/26 Installing : vdsm-4.30.32-1.el7.x86_64 9/26 Installing : vdsm-gluster-4.30.32-1.el7.x86_64 10/26 Installing : vdsm-hook-ethtool-options-4.30.32-1.el7.noarch 11/26 Installing : vdsm-hook-fcoe-4.30.32-1.el7.noarch 12/26 Installing : vdsm-client-4.30.32-1.el7.noarch 13/26 Cleanup : vdsm-client-4.30.33-1.el7.noarch 14/26 Cleanup : vdsm-hook-ethtool-options-4.30.33-1.el7.noarch 15/26 Cleanup : vdsm-gluster-4.30.33-1.el7.x86_64 16/26 Cleanup : vdsm-hook-fcoe-4.30.33-1.el7.noarch 17/26 Cleanup : vdsm-hook-vmfex-dev-4.30.33-1.el7.noarch 18/26 Cleanup : vdsm-4.30.33-1.el7.x86_64 19/26 Cleanup : vdsm-jsonrpc-4.30.33-1.el7.noarch 20/26 Cleanup : vdsm-http-4.30.33-1.el7.noarch 21/26 Cleanup : vdsm-python-4.30.33-1.el7.noarch 22/26 Cleanup : vdsm-network-4.30.33-1.el7.x86_64 23/26 Cleanup : vdsm-common-4.30.33-1.el7.noarch 24/26 Cleanup : vdsm-api-4.30.33-1.el7.noarch 25/26 Cleanup : vdsm-yajsonrpc-4.30.33-1.el7.noarch 26/26 In other words, something happened after the version 4.30.32-1. With 4.30.33-1 all working fine, after installing 4.30.33-1 - i see this issue.