Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This can be done with a very small shell script:
[root@rhel75test-20171023 ~]# vdo list
vdo2
vdo1
[root@rhel75test-20171023 ~]# for j in 1 2; do echo $j; vdo remove --name=vdo$j; done
1
Removing VDO vdo1
Stopping VDO vdo1
2
Removing VDO vdo2
Stopping VDO vdo2
Description of problem: Certainly not a priority initially, but this would be nice eventually. [root@harding-02 ~]# vdo list PV1 PV3 PV2 PV5 PV4 PV7 PV6 PV8 [root@harding-02 ~]# vdo remove --name PV[12345678] Usage: vdo --name=<volume>|--all [<option>...] activate|deactivate|create|remove| start|stop|status|list|modify| changeWritePolicy|enableDeduplication| disableDeduplication|enableCompression| disableCompression|growLogical|growPhysical| printConfigFile vdo: error: option --name: VDO device names may only contain characters in 'A-Za-z0-9#+.:@_-': bad value 'PV[12345678]' [root@harding-02 ~]# vdo remove --name PV* Usage: vdo --name=<volume>|--all [<option>...] activate|deactivate|create|remove| start|stop|status|list|modify| changeWritePolicy|enableDeduplication| disableDeduplication|enableCompression| disableCompression|growLogical|growPhysical| printConfigFile vdo: error: option --name: VDO device names may only contain characters in 'A-Za-z0-9#+.:@_-': bad value 'PV*' [root@harding-02 ~]# vdo remove --name PV1 PV2 PV3 vdo: ERROR - Must specify exactly one command Usage: vdo --name=<volume>|--all [<option>...] activate|deactivate|create|remove| start|stop|status|list|modify| changeWritePolicy|enableDeduplication| disableDeduplication|enableCompression| disableCompression|growLogical|growPhysical| printConfigFile [root@harding-02 ~]# vdo remove --name PV1 Removing VDO PV1 Stopping VDO PV1 [root@harding-02 ~]# vdo remove --name PV{12345678} Usage: vdo --name=<volume>|--all [<option>...] activate|deactivate|create|remove| start|stop|status|list|modify| changeWritePolicy|enableDeduplication| disableDeduplication|enableCompression| disableCompression|growLogical|growPhysical| printConfigFile vdo: error: option --name: VDO device names may only contain characters in 'A-Za-z0-9#+.:@_-': bad value 'PV{12345678}' Version-Release number of selected component (if applicable): vdo-6.1.0.34-8 BUILT: Fri Nov 3 06:58:45 CDT 2017 kmod-kvdo-6.1.0.34-7.el7 BUILT: Fri Nov 3 06:44:06 CDT 2017