Bug 1510405

Summary:	vdo create --indexMem=0 is not accepted anymore
Product:	Red Hat Enterprise Linux 7	Reporter:	Jakub Krysl <jkrysl>
Component:	vdo	Assignee:	bjohnsto
Status:	CLOSED ERRATA	QA Contact:	Jakub Krysl <jkrysl>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	awalsh, bjohnsto, limershe
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	6.1.0.39	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 15:47:46 UTC	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 Jakub Krysl 2017-11-07 10:36:47 UTC

Description of problem:
According to help/manpage, --indexMem=0 should request default index memory size. 
 This value was accepted in vdo 6.1.0.0-6, but in vdo 6.1.0.34-8 this fails with:
vdo: error: option --indexMem: must be an index memory value

Version-Release number of selected component (if applicable):
vdo 6.1.0.34-8

How reproducible:
100%

Steps to Reproduce:
1.vdo create --device=DEVICE --name=NAME --indexMem=0

Actual results:
vdo: error: option --indexMem: must be an index memory value

Expected results:
vdo created with default index memory value

Additional info:

Comment 3 bjohnsto 2017-11-08 23:18:52 UTC

Have update help and man page to remove the reference to 0. Change should be available in VDO version 38 and greater.

Comment 5 Jakub Krysl 2017-11-14 15:00:50 UTC

Tested with vdo-6.1.0.46-9, both man vdo and vdo --help no longer mention possibility of --indexMem 0.

Comment 8 errata-xmlrpc 2018-04-10 15:47:46 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0871