Bug 1489968

Summary: [RFE] [RHV] Add support to query illegal images in unlock_entity.sh
Product: Red Hat Enterprise Virtualization Manager Reporter: Bimal Chollera <bcholler>
Component: ovirt-engineAssignee: Bimal Chollera <bcholler>
Status: CLOSED ERRATA QA Contact: Jiri Belka <jbelka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.1.5CC: bcholler, dougsland, lsurette, lsvaty, mkalinin, mperina, pstehlik, rbalakri, Rhev-m-bugs, rhv-bugzilla-bot, srevivo, ykaul
Target Milestone: ovirt-4.2.3Keywords: FutureFeature
Target Release: ---Flags: jbelka: testing_plan_complete-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1566366 (view as bug list) Environment:
Last Closed: 2018-05-15 17:43:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 902971, 1520566, 1538360, 1566366    

Description Bimal Chollera 2017-09-08 20:27:12 UTC 
Description of problem:

Currently the /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh supports unlocking types vm, template, disk and snapshot but not if it's just the image (imagestatus=4).  The other entities of the VM are in correct status but if the image has imagestatus=4, then we need to update the RHV engine database.

Version-Release number of selected component (if applicable):
4.1.5

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 14 Martin Perina 2018-04-17 07:18:38 UTC 
The fix was delivered earlier than expected, so regargeting to RHV 4.2 GA instead of z-stream
Comment 15 Martin Perina 2018-04-17 07:18:59 UTC 
*** Bug 1566366 has been marked as a duplicate of this bug. ***
Comment 20 errata-xmlrpc 2018-05-15 17:43:37 UTC 
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/RHEA-2018:1488
Comment 21 Franta Kust 2019-05-16 13:04:47 UTC 
BZ<2>Jira Resync