Bug 1473392 - "lvs" exits with status 0 after failing
Summary: "lvs" exits with status 0 after failing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-20 17:06 UTC by Jonathan Kamens
Modified: 2017-07-20 17:16 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-20 17:16:53 UTC
Embargoed:
rule-engine: lvm-technical-solution?
rule-engine: lvm-test-coverage?

Attachments (Terms of Use)

Description Jonathan Kamens 2017-07-20 17:06:34 UTC 
$ sudo lvs /tmp
[sudo] password for jik:
  "/tmp": Invalid path for Logical Volume.
$ echo $?
0
$

Clearly that exit status should not be 0.
Comment 1 Alasdair Kergon 2017-07-20 17:16:53 UTC 
Already fixed upstream a few releases ago IIRC.

# lvm lvs /tmp
  "/tmp": Invalid path for Logical Volume.
# echo $?
5
Note You need to log in before you can comment on or make changes to this bug.