Bug 1393692 - [dmsetup] --version has wrong return code
Summary: [dmsetup] --version has wrong return code
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Heinz Mauelshagen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 07:46 UTC by Vojtech Trefny
Modified: 2016-12-14 08:22 UTC (History)
12 users (show)

Fixed In Version: lvm2-2.02.168-1.fc26
Clone Of:
Environment:
Last Closed: 2016-12-01 08:12:44 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1395398 0 unspecified CLOSED gi.overrides.BlockDev.BlockDevNotImplementedError: The function 'bd_dm_map_exists' called, but not implemented! 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1404416 0 unspecified CLOSED 'bd_dm_map_exists' called, but not implemented! 2021-02-22 00:41:40 UTC

Internal Links: 1395398 1404416

Description Vojtech Trefny 2016-11-10 07:46:44 UTC 
Description of problem:

"dmsetup --version" returns "1" instead of "0".

# dmsetup --version
Library version:   1.02.136 (2016-11-05)
Driver version:    4.35.0

# echo $?
1

Works as expected with older versions
# dmsetup --version
Library version:   1.02.134 (2016-09-07)
Driver version:    4.35.0

# echo $?
0
Comment 1 Heinz Mauelshagen 2016-11-10 15:42:50 UTC 
Same for "dmsetup --help".
Comment 2 Heinz Mauelshagen 2016-11-10 16:04:15 UTC 
Upstream commit 0b1c79642061
Comment 3 Heinz Mauelshagen 2016-11-10 17:13:12 UTC 
Leveraged in upstream commit b11f4f93d70d to return 0
on "dmsetup SubCommand --{help|version}"
Comment 4 Vratislav Podzimek 2016-12-14 07:19:09 UTC 
This now appears on F25.
Comment 5 Peter Rajnoha 2016-12-14 08:22:40 UTC 
(In reply to Vratislav Podzimek from comment #4)
> This now appears on F25.

Should be fixed with latest lvm2-2.02.167-3.fc25.
Note You need to log in before you can comment on or make changes to this bug.