Bug 1756949 - vgchange can't activate VG with autobackup disabled
Summary: vgchange can't activate VG with autobackup disabled
Keywords:
Status: POST
Alias: None
Product: LVM and device-mapper
Classification: Community
Component: lvm2
Version: 2.02.180
Hardware: All
OS: Linux
medium
unspecified
Target Milestone: ---
: ---
Assignee: David Teigland
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-30 09:25 UTC by Max Halldén
Modified: 2023-08-10 15:40 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:
pm-rhel: lvm-technical-solution?
pm-rhel: lvm-test-coverage?


Attachments (Terms of Use)

Description Max Halldén 2019-09-30 09:25:48 UTC
Description of problem:
When trying to activate a volume group without autobackup enabled, it fails because "-A option not necessary with -a option".

Version-Release number of selected component (if applicable):
vgchange --version
  LVM version:     2.02.180(2) (2018-07-19)
  Library version: 1.02.149 (2018-07-19)
  Driver version:  4.39.0

How reproducible:
Every time

Steps to Reproduce:
1. vgchange -A n -a y my_vg

Actual results:

root@(none):~# vgchange -A n -a y my_vg
  -A option not necessary with -a option
  Run `vgchange --help' for more information.

Expected results:
Command succeeds

Additional info:

Comment 1 David Teigland 2019-10-21 18:34:27 UTC
more option detritus remaining in vgchange, but pushed one off fix to master
https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=967e2decd22cee4aa4426cfda5732860e1a085b3


Note You need to log in before you can comment on or make changes to this bug.