Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Hi, I dont see a reason for targeting to 4.3 as it's already verified on 4.2.4. Please close as duplicate of "Bug 1576329" or move to 4.2.4 so I can verify.
Bug 1576329 was closed as duplicate Bug 1575081.
Verified on: 4.3.0-0.0.master.20181001172150.git99e1298.el7 vdsm-4.30.0-608.gitd67b80d.el7.x86_64 libvirt-3.9.0-14.el7_5.8.x86_64
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.7 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.
Closed by mistake, moving back to qa -> verified
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.0 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.