Hi, We have 2 hosts, upgarded to 4.4.5. Engine and one of the hosts was successfull But, of of the hosts stucked and doesnt upgrade. successful one has these kernels # vmlinuz-4.18.0-240.1.1.el8_3.x86_64 # vmlinuz-4.18.0-240.15.1.el8_3.x86_64 Unsuccessful one has; # vmlinuz-4.18.0-193.28.1.el8_2.x86_64 # vmlinuz-4.18.0-240.1.1.el8_3.x86_64 Unsuccessful one has "/usr/share/ovirt-node-ng-image-update/" directory and image but we dont make it upgrade This is the some part of the log file from engine; FAILED! => {"changed": true, "cmd": ["vdsm-tool", "configure", "--force"], "delta": "0:00:10.773484", "end": "2021-03-23 09:00:08.285785", "msg": "non-zero return code", "rc": 1, "start": "2021-03-23 08:59:57.512301", "stderr": "Error: ServiceOperationError: _systemctlStop failed\nb'Job for vdsmd.service canceled.\\n' ", "stderr_lines": ["Error: ServiceOperationError: _systemctlStop failed", "b'Job for vdsmd.service canceled.\\n' "], "stdout": "\nChecking configuration status...\n\nlibvirt is already configured for vdsm\nSUCCESS: ssl configured to true. No conflicts\nsanlock is configured for vdsm\nlvm is configured for vdsm\nCurrent revision of multipath.conf detected, preserving\nabrt is already configured for vdsm\nManaged volume database is already configured", "stdout_lines": ["", "Checking configuration status...", "", "libvirt is already configured for vdsm", "SUCCESS: ssl configured to true. No conflicts", "sanlock is configured for vdsm", "lvm is configured for vdsm", "Cur rent revision of multipath.conf detected, preserving", "abrt is already configured for vdsm", "Managed volume database is already configured"]} when we triggered the dnf update/upgrade it says "there is no upgrade" both engine web page and cli Is there any suggestion for upgrading the host, it's stucked on "NonOperational" mode