Bug 1756949

Summary:	vgchange can't activate VG with autobackup disabled
Product:	[Community] LVM and device-mapper	Reporter:	Max Halldén <max.hallden>
Component:	lvm2	Assignee:	David Teigland <teigland>
lvm2 sub component:	Command-line tools	QA Contact:	cluster-qe <cluster-qe>
Status:	POST ---	Docs Contact:
Severity:	unspecified
Priority:	medium	CC:	agk, heinzm, jbrassow, msnitzer, prajnoha, thornber, zkabelac
Version:	2.02.180	Flags:	pm-rhel: lvm-technical-solution? pm-rhel: lvm-test-coverage?
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 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