RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2005004 - what's the plan if a script or user fails to answer "y" to the vdoimport "convert vdovg/vdolvol_vpool" question? [rhel-8.6.0]
Summary: what's the plan if a script or user fails to answer "y" to the vdoimport "con...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.5
Hardware: x86_64
OS: Linux
urgent
medium
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 1988504
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-16 14:31 UTC by RHEL Program Management Team
Modified: 2022-05-10 16:37 UTC (History)
9 users (show)

Fixed In Version: lvm2-2.03.14-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1988504
Environment:
Last Closed: 2022-05-10 15:22:14 UTC
Type: ---
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-5156 0 None None None 2022-01-13 01:01:47 UTC
Red Hat Issue Tracker CLUSTERQE-5504 0 None None None 2022-03-15 23:01:12 UTC
Red Hat Issue Tracker RHELPLAN-97552 0 None None None 2021-09-18 10:20:11 UTC
Red Hat Product Errata RHBA-2022:2038 0 None None None 2022-05-10 15:22:30 UTC

Comment 1 Zdenek Kabelac 2021-09-22 14:34:57 UTC 
Fixed upstream 2.03.14
Comment 3 Corey Marthaler 2021-11-03 03:49:18 UTC 
Marking Verifed:Tested in the latest rpms.

kernel-4.18.0-348.4.el8.kpq0    BUILT: Wed Oct 27 15:00:32 CDT 2021
lvm2-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
lvm2-libs-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
lvm2-dbusd-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:48 CDT 2021



SCENARIO - [attempt_no_flag_answer_to_lvm_import_vdo_convert]
Test the proceedure for answering no to the lvm_import_vdo conversion question midway through the process (1988504)
vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 500G --device /dev/sdd1
Creating VDO lvm_import_vdo_sanity
      The VDO volume can address 928 GB in 464 data slabs, each 2 GB.
      It can grow to address at most 16 TB of physical storage in 8192 slabs.
      If a larger maximum size might be needed, use bigger slabs.
Starting VDO lvm_import_vdo_sanity
Starting compression on VDO lvm_import_vdo_sanity
VDO instance 154 volume is ready at /dev/mapper/lvm_import_vdo_sanity

echo n | lvm_import_vdo /dev/disk/by-id/scsi-36d094660650d1e0022bd29f31e631f3e-part1
Convert VDO device "/dev/disk/by-id/scsi-36d094660650d1e0022bd29f31e631f3e-part1" to VDO LV "vdovg/vdolvol"? [y|N]: No
lvm_import_vdo properly did not complete (and errored non zero) when answering no

vdo remove --name lvm_import_vdo_sanity
Removing VDO lvm_import_vdo_sanity
Stopping VDO lvm_import_vdo_sanity
Comment 7 Corey Marthaler 2021-11-16 18:27:23 UTC 
Marking Verified in the latest rpms.

kernel-4.18.0-348.4.el8.kpq0    BUILT: Wed Oct 27 15:00:32 CDT 2021
lvm2-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021
lvm2-libs-2.03.14-1.el8    BUILT: Wed Oct 20 10:18:17 CDT 2021


SCENARIO - attempt_no_flag_answer_to_lvm_import_vdo_convert:  Test the proceedure for answering no to the lvm_import_vdo conversion question midway through the process (1988504) 
vdo create --force --name lvm_import_vdo_sanity --vdoLogicalSize 500G --device /dev/sdd1
Creating VDO lvm_import_vdo_sanity
      The VDO volume can address 1 TB in 929 data slabs, each 2 GB.
      It can grow to address at most 16 TB of physical storage in 8192 slabs.
      If a larger maximum size might be needed, use bigger slabs.
Starting VDO lvm_import_vdo_sanity
Starting compression on VDO lvm_import_vdo_sanity
VDO instance 5 volume is ready at /dev/mapper/lvm_import_vdo_sanity

echo n | lvm_import_vdo /dev/disk/by-id/scsi-36d094660575ece002291ba5c230d16c6-part1
Convert VDO device "/dev/disk/by-id/scsi-36d094660575ece002291ba5c230d16c6-part1" to VDO LV "vdovg/vdolvol"? [y|N]: No
lvm_import_vdo properly did not complete (and errored non zero) when answering no
vdo remove --name lvm_import_vdo_sanity
Removing VDO lvm_import_vdo_sanity
Stopping VDO lvm_import_vdo_sanity
Comment 9 errata-xmlrpc 2022-05-10 15:22:14 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 (lvm2 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:2038
Note You need to log in before you can comment on or make changes to this bug.