Bug 1475293

Summary:	thin_metadata_size -V returns 1 after success
Product:	Red Hat Enterprise Linux 7	Reporter:	Jakub Krysl <jkrysl>
Component:	device-mapper-persistent-data	Assignee:	Joe Thornber <thornber>
Status:	CLOSED ERRATA	QA Contact:	Jakub Krysl <jkrysl>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	agk, heinzm, jbrassow, lvm-team, mcsontos, msnitzer, thornber
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	device-mapper-persistent-data-0.7.2-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 13:17:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jakub Krysl 2017-07-26 12:05:26 UTC

Description of problem:
Running command "thin_metadata_size -V" shows the correct version, but return value is 1 instead of 0. Other tools in device-mapper-persistent-data return the same correct version of device-mapper-persistent-data and their return value is 0.

Version-Release number of selected component (if applicable):
0.7.0-0.1.rc6.el7

How reproducible:
100%

Steps to Reproduce:
1.thin_metadata_size -V
2.echo $?

Actual results:
1

Expected results:
0

Additional info:

Comment 2 Joe Thornber 2017-09-19 10:30:56 UTC

https://github.com/jthornber/thin-provisioning-tools/commit/313716028e6e19d7694cc194daa83a73c7264f5b

Above commit fixes.

Release to follow.

Comment 4 Jakub Krysl 2017-09-22 11:53:48 UTC

'thin_metadata_size -V' retcode is 0 on success in device-mapper-persistent-data-0.7.2-1.el7

Comment 7 errata-xmlrpc 2018-04-10 13:17:29 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:0776