|Summary:||Setting host to 'maintenance' will be blocked when there are image transfers with status different then 'paused'|
|Product:||[oVirt] ovirt-engine||Reporter:||Eyal Shenitzky <eshenitz>|
|Component:||BLL.Storage||Assignee:||Eyal Shenitzky <eshenitz>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Amit Sharir <asharir>|
|Version:||4.4.7||CC:||aefrat, asharir, bugs, dfodor, eshames, lsvaty, nsoffer, tashkena|
|Target Milestone:||ovirt-4.4.8||Keywords:||Regression, ZStream|
|Fixed In Version:||Doc Type:||Bug Fix|
Cause: A host will not be able to set to maintenance if there are image finished transfers (finished/failed status). Fix: A host can now be set to maintenance if the image transfers ended.
|Last Closed:||2021-08-19 06:23:08 UTC||Type:||Bug|
|oVirt Team:||Storage||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Eyal Shenitzky 2021-07-29 12:51:55 UTC
Description of problem: When trying to set a host to maintenance and the system contains image transfer entities that weren't clear yet, it fails even if the image transfer is already done (successfully or with failure). The host managed to set to maintenance when the image transfer cleared from the DB. Version-Release number of selected component (if applicable): 4.4.7 How reproducible: 100% Steps to Reproduce: 1. Create a VM with a disk 2. Start a full backup for the VM and download the disk 3. After backup ended and the disk is downloaded, try to set the host that was used for the transfer to maintenance. Actual results: Setting host to maintenance is not allowed. Expected results: The host should be able to set to maintenance if all transfers are done or idle. Additional info:
Comment 1 Avihai 2021-08-01 08:51:43 UTC
(In reply to Eyal Shenitzky from comment #0) > Description of problem: > > When trying to set a host to maintenance and the system contains image > transfer entities that weren't clear yet, it fails even if the image > transfer is already done (successfully or with failure). > > > The host managed to set to maintenance when the image transfer cleared from > the DB. > > Version-Release number of selected component (if applicable): > 4.4.7 > > How reproducible: > 100% > > Steps to Reproduce: > 1. Create a VM with a disk > 2. Start a full backup for the VM and download the disk > 3. After backup ended and the disk is downloaded, try to set the host that > was used for the transfer to maintenance. > > Actual results: > Setting host to maintenance is not allowed. this is just for the 15minutes until DB entree is cleared, right? After that(15 min), you can move the host to maintenance? > > Expected results: > The host should be able to set to maintenance if all transfers are done or > idle. > > Additional info:
Comment 2 Eyal Shenitzky 2021-08-01 08:55:25 UTC
(In reply to Avihai from comment #1) > this is just for the 15minutes until DB entree is cleared, right? > After that(15 min), you can move the host to maintenance? Right
Comment 3 RHEL Program Management 2021-08-02 11:36:34 UTC
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 6 Nir Soffer 2021-08-03 19:41:34 UTC
*** Bug 1989718 has been marked as a duplicate of this bug. ***
Comment 7 Amit Sharir 2021-08-08 11:56:44 UTC
Version: vdsm-22.214.171.124-1.el8ev.x86_64 ovirt-engine-126.96.36.199-0.10.el8ev.noarch Verification conclusions: The total flow mentioned was done with no errors/unexpected logs. After the full backup for the VM and the download of the disk, I was able to put the host that was used for the transfer into maintenance via the UI (in less than 15 min). Bug verified.
Comment 8 Sandro Bonazzola 2021-08-19 06:23:08 UTC
This bugzilla is included in oVirt 4.4.8 release, published on August 19th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.8 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.