Bug 2017843

Summary:	Extend vdoPrepareForLVM utility to support RHEL8.6+ tp RHEL9.0 upgrade
Product:	Red Hat Enterprise Linux 8	Reporter:	Joe Shimkus <jshimkus>
Component:	vdo	Assignee:	Joe Shimkus <jshimkus>
Status:	CLOSED ERRATA	QA Contact:	Filip Suba <fsuba>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	awalsh, cwei, fsuba
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.6
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	vdo-6.2.6.7-14.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-10 15:21:06 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 Joe Shimkus 2021-10-27 14:17:12 UTC

Description of problem:
To support LEAPP validation that a RHEL 8.6+ system is/isn't in a state for upgrade to RHEL 9.0 vdoPrepareForLVM will be augmented with an option to indicate if a specified block device is one of:
  - not a VDO device
  - a pre-conversion VDO device
  - a post-conversion VDO device

This augmentation does not impact default behavior of vdoPrepareForLVM.

Comment 1 Joe Shimkus 2021-10-27 14:32:07 UTC

Filip, please add qa_ack+ approval.

Comment 5 Andy Walsh 2021-11-15 19:03:33 UTC

There is a follow-up fix for this posted to Github.

https://github.com/dm-vdo/vdo/releases/tag/6.2.6.7

Comment 6 Andy Walsh 2021-11-15 19:44:01 UTC

The fix for this BZ is available in build vdo-6.2.6.7-14.el8.

Comment 7 Filip Suba 2021-12-06 13:25:03 UTC

Verified with vdo-6.2.6.7-14.el8.

Comment 9 errata-xmlrpc 2022-05-10 15:21:06 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 (vdo bug fix and enhancement update), 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/RHBA-2022:2028