Description of problem: Unexpected error during SmartState Analysis of a RHEL-OSP Image Version-Release number of selected component (if applicable): 5.4.3.0.20151001120745_d11cf59 How reproducible: 100% for specific VMs Steps to Reproduce: 1. Define OpenStack Cloud Provider 2. Run SmartState Analysis on Images 3. Actual results: Unknown QCOW Version 3 for /tmp/vm_name-string Expected results: No error Additional info: In QcowDisk.rb, error occurs at line 621. The logic for https://bugzilla.redhat.com/show_bug.cgi?id=1192223 didn't appear to cover the csize_shift
It looks like the case statement in `csize_shift` needs to accept version 3 as valid.
PR 5024 submitted https://github.com/ManageIQ/manageiq/pull/5024
Detected commit referencing this ticket while ticket status is POST.
New commit detected on cfme/5.4.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=61ae74acfbb80e0b1ea55213904eb0e9b88d08c6 commit 61ae74acfbb80e0b1ea55213904eb0e9b88d08c6 Author: Mo Morsi <mmorsi> AuthorDate: Wed Oct 21 16:43:39 2015 -0400 Commit: Mo Morsi <mmorsi> CommitDate: Wed Oct 21 16:43:39 2015 -0400 Add missing check needed for qcow3 compressed images https://bugzilla.redhat.com/show_bug.cgi?id=1271332 gems/pending/disk/modules/QcowDisk.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/61ae74acfbb80e0b1ea55213904eb0e9b88d08c6 commit 61ae74acfbb80e0b1ea55213904eb0e9b88d08c6 Author: Mo Morsi <mmorsi> AuthorDate: Wed Oct 21 16:43:39 2015 -0400 Commit: Mo Morsi <mmorsi> CommitDate: Wed Oct 21 16:43:39 2015 -0400 Add missing check needed for qcow3 compressed images https://bugzilla.redhat.com/show_bug.cgi?id=1271332 gems/pending/disk/modules/QcowDisk.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
https://github.com/ManageIQ/manageiq/pull/5053
Verified on 5.5.0.11 against 5.4.3.0. The image that triggers this problem is the f22-qcow on our rhos5 provider.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:2551