Description of problem: /usr/share/ovirt-engine/setup/dbutils/unlock_entity.sh does not return human readable output. There is no way for the user to figure out what the returned data is. Version-Release number of selected component (if applicable): 4.1.5 How reproducible: 100% Steps to Reproduce: 1. lock a disk 2. run # ./unlock_entity.sh -u engine -t disk -q 3. Actual results: Not header is displayed # ./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: The result is presented in a way that the it is possible to figure out what the result is, but still keeps ability to be easily parsed.
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [No relevant external trackers attached] For more info please contact: infra
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Tag 'ovirt-engine-4.2.0_beta1' doesn't contain patch 'https://gerrit.ovirt.org/82812'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.2.0_beta1 For more info please contact: infra
unlock_entity.sh got -c option (documented in help) that shows header with column names verified in ovirt-engine-4.2.1.2-0.1.el7.noarch
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.