Bug 1489334 - unlock_entity.sh -q reports duplicate records.
Summary: unlock_entity.sh -q reports duplicate records.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 4.1.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.0
: ---
Assignee: Miroslava Voglova
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-07 08:49 UTC by Roman Hodain
Modified: 2017-12-20 11:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1489328
Environment:
Last Closed: 2017-12-20 11:26:18 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 82810 0 master MERGED dbutils: unlock_entity: removed duplicate records 2017-10-29 10:53:15 UTC

Description Roman Hodain 2017-09-07 08:49:07 UTC
Description of problem:
/usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh reports duplicate records when more than one volume in the image chain is locked.

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

How reproducible:
100%

Steps to Reproduce:
1. lock two volumes of the same disk. ( a snapshot needs to be created )
2. ./unlock_entity.sh -u engine -t disk -q
3.

Actual results:
    The following command returns two same lines:

    # ./unlock_entity.sh -u engine -t disk -q
     6b324a40-6699-454c-8033-6e4070823e92 | 2a3fd3a2-f627-467b-bda0-06dc01e1c982
     6b324a40-6699-454c-8033-6e4070823e92 | 2a3fd3a2-f627-467b-bda0-06dc01e1c982


Expected results:
    
    Only one line is reported.

Comment 1 Petr Matyáš 2017-10-31 12:18:19 UTC
Verified on ovirt-engine-4.2.0-0.0.master.20171030093856.gitc4dc9af.el7.centos.noarch

Comment 2 Sandro Bonazzola 2017-12-20 11:26:18 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.