Bug 1473392 - "lvs" exits with status 0 after failing
"lvs" exits with status 0 after failing
Status: CLOSED CURRENTRELEASE
Product: LVM and device-mapper
Classification: Community
Component: lvm2 (Show other bugs)
unspecified
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: LVM and device-mapper development team
cluster-qe@redhat.com
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-20 13:06 EDT by Jonathan Kamens
Modified: 2017-07-20 13:16 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-20 13:16:53 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: lvm‑technical‑solution?
rule-engine: lvm‑test‑coverage?


Attachments (Terms of Use)

  None (edit)
Description Jonathan Kamens 2017-07-20 13:06:34 EDT
$ 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 13:16:53 EDT
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.