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.
Description of problem:
Trying to use blivet to manage lvmvdo - installed the following components:
['Installed: lsof-4.94.0-1.el9.x86_64',
'Installed: libaio-0.3.111-12.el9.x86_64',
'Installed: lvm2-9:2.03.12-3.el9.x86_64',
'Installed: lvm2-libs-9:2.03.12-3.el9.x86_64',
'Installed: mdadm-4.1-8.el9.x86_64',
'Installed: libblockdev-2.25-6.el9.x86_64',
'Installed: libblockdev-crypto-2.25-6.el9.x86_64',
'Installed: libblockdev-dm-2.25-6.el9.x86_64',
'Installed: libblockdev-fs-2.25-6.el9.x86_64',
'Installed: libblockdev-kbd-2.25-6.el9.x86_64',
'Installed: ndctl-71.1-3.el9.x86_64',
'Installed: libblockdev-loop-2.25-6.el9.x86_64',
'Installed: ndctl-libs-71.1-3.el9.x86_64',
'Installed: libblockdev-lvm-2.25-6.el9.x86_64',
'Installed: python3-pyudev-0.22.0-5.el9.noarch',
'Installed: libblockdev-mdraid-2.25-6.el9.x86_64',
'Installed: libblockdev-mpath-2.25-6.el9.x86_64',
'Installed: libblockdev-nvdimm-2.25-6.el9.x86_64',
'Installed: libblockdev-part-2.25-6.el9.x86_64',
'Installed: libblockdev-swap-2.25-6.el9.x86_64',
'Installed: userspace-rcu-0.12.1-5.el9.x86_64',
'Installed: libblockdev-utils-2.25-6.el9.x86_64',
'Installed: vdo-8.1.0.264-1.el9.x86_64',
'Installed: libbytesize-2.5-2.el9.x86_64',
'Installed: python3-pyparted-1:3.11.7-3.el9.x86_64',
'Installed: python3-blivet-1:3.4.0-2.el9.noarch',
'Installed: blivet-data-1:3.4.0-2.el9.noarch',
'Installed: daxctl-libs-71.1-3.el9.x86_64',
'Installed: volume_key-libs-0.3.12-12.el9.x86_64',
'Installed: nspr-4.31.0-5.el9.x86_64',
'Installed: device-mapper-event-9:1.02.177-3.el9.x86_64',
'Installed: nss-3.67.0-8.el9.x86_64',
'Installed: device-mapper-event-libs-9:1.02.177-3.el9.x86_64',
'Installed: kmod-kvdo-8.1.0.264-1.el9.x86_64',
'Installed: device-mapper-multipath-0.8.6-6.el9.x86_64',
'Installed: gdisk-1.0.7-2.el9.x86_64',
'Installed: nss-softokn-3.67.0-8.el9.x86_64',
'Installed: device-mapper-multipath-libs-0.8.6-6.el9.x86_64',
'Installed: device-mapper-persistent-data-0.9.0-9.el9.x86_64',
'Installed: nss-softokn-freebl-3.67.0-8.el9.x86_64',
'Installed: nss-sysinit-3.67.0-8.el9.x86_64',
'Installed: python3-blockdev-2.25-6.el9.x86_64',
'Installed: nss-util-3.67.0-8.el9.x86_64',
'Installed: python3-bytesize-2.5-2.el9.x86_64']
modprobe of kvdo works:
TASK [Check if kvdo is loadable] ***********************************************
task path: /tmp/tmpp9xlrbl_/tests/tests_create_lvmvdo_then_remove.yml:27
ok: [/cache/rhel-x.qcow2] => {"changed": false, "cmd": ["modprobe", "--dry-run", "kvdo"], "delta": "0:00:00.004953", "end": "2021-08-06 17:31:48.323615", "rc": 0, "start": "2021-08-06 17:31:48.318662", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}
But blivet fails because it is looking for a kmod named "dm-vdo":
Failed to commit changes to disk: Process reported exit code 3: modprobe: FATAL: Module dm-vdo not found in directory /lib/modules/5.14.0-0.rc4.35.el9.x86_64
/usr/sbin/modprobe failed: 1
vdo: Required device-mapper target(s) not detected in your kernel.
Run `lvcreate --help' for more information.
I just want to know how I can either reliably test vdo functionality in the storage role, or skip the test if vdo is not available.
I have already added the "Check if kvdo is loadable"
Is dm-vdo also required? Is it always required? Should I also add
Full logfile is here: https://fedorapeople.org/groups/linuxsystemroles/logs/linux-system-roles-storage-pull-linux-system-roles_storage-220-d4ce3e8-rhel-x-20210806-204425/artifacts/ansible.log
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 5guazhang@redhat.com
2021-08-11 13:40:50 UTC
Hi
rhel-system-roles-1.7.5-99.el9.noarch
test pass with tests_create_lvmvdo_then_remove.yml
TASK [Check if kvdo is loadable] ***********************************************
task path: /usr/share/ansible/roles/rhel-system-roles.storage/tests/tests_create_lvmvdo_then_remove.yml:27
fatal: [localhost]: FAILED! => {"changed": false, "cmd": "set -euo pipefail\nmodprobe --dry-run kvdo && modprobe --dry-run dm-vdo\n", "delta": "0:00:00.004066", "end": "2021-08-11 09:02:00.303107", "msg": "non-zero return code", "rc": 1, "start": "2021-08-11 09:02:00.299041", "stderr": "modprobe: FATAL: Module dm-vdo not found in directory /lib/modules/5.14.0-0.rc4.35.el9.x86_64", "stderr_lines": ["modprobe: FATAL: Module dm-vdo not found in directory /lib/modules/5.14.0-0.rc4.35.el9.x86_64"], "stdout": "", "stdout_lines": []}
...ignoring
PLAY RECAP *********************************************************************
localhost : ok=22 changed=0 unreachable=0 failed=0 skipped=22 rescued=0 ignored=1
Description of problem: Trying to use blivet to manage lvmvdo - installed the following components: ['Installed: lsof-4.94.0-1.el9.x86_64', 'Installed: libaio-0.3.111-12.el9.x86_64', 'Installed: lvm2-9:2.03.12-3.el9.x86_64', 'Installed: lvm2-libs-9:2.03.12-3.el9.x86_64', 'Installed: mdadm-4.1-8.el9.x86_64', 'Installed: libblockdev-2.25-6.el9.x86_64', 'Installed: libblockdev-crypto-2.25-6.el9.x86_64', 'Installed: libblockdev-dm-2.25-6.el9.x86_64', 'Installed: libblockdev-fs-2.25-6.el9.x86_64', 'Installed: libblockdev-kbd-2.25-6.el9.x86_64', 'Installed: ndctl-71.1-3.el9.x86_64', 'Installed: libblockdev-loop-2.25-6.el9.x86_64', 'Installed: ndctl-libs-71.1-3.el9.x86_64', 'Installed: libblockdev-lvm-2.25-6.el9.x86_64', 'Installed: python3-pyudev-0.22.0-5.el9.noarch', 'Installed: libblockdev-mdraid-2.25-6.el9.x86_64', 'Installed: libblockdev-mpath-2.25-6.el9.x86_64', 'Installed: libblockdev-nvdimm-2.25-6.el9.x86_64', 'Installed: libblockdev-part-2.25-6.el9.x86_64', 'Installed: libblockdev-swap-2.25-6.el9.x86_64', 'Installed: userspace-rcu-0.12.1-5.el9.x86_64', 'Installed: libblockdev-utils-2.25-6.el9.x86_64', 'Installed: vdo-8.1.0.264-1.el9.x86_64', 'Installed: libbytesize-2.5-2.el9.x86_64', 'Installed: python3-pyparted-1:3.11.7-3.el9.x86_64', 'Installed: python3-blivet-1:3.4.0-2.el9.noarch', 'Installed: blivet-data-1:3.4.0-2.el9.noarch', 'Installed: daxctl-libs-71.1-3.el9.x86_64', 'Installed: volume_key-libs-0.3.12-12.el9.x86_64', 'Installed: nspr-4.31.0-5.el9.x86_64', 'Installed: device-mapper-event-9:1.02.177-3.el9.x86_64', 'Installed: nss-3.67.0-8.el9.x86_64', 'Installed: device-mapper-event-libs-9:1.02.177-3.el9.x86_64', 'Installed: kmod-kvdo-8.1.0.264-1.el9.x86_64', 'Installed: device-mapper-multipath-0.8.6-6.el9.x86_64', 'Installed: gdisk-1.0.7-2.el9.x86_64', 'Installed: nss-softokn-3.67.0-8.el9.x86_64', 'Installed: device-mapper-multipath-libs-0.8.6-6.el9.x86_64', 'Installed: device-mapper-persistent-data-0.9.0-9.el9.x86_64', 'Installed: nss-softokn-freebl-3.67.0-8.el9.x86_64', 'Installed: nss-sysinit-3.67.0-8.el9.x86_64', 'Installed: python3-blockdev-2.25-6.el9.x86_64', 'Installed: nss-util-3.67.0-8.el9.x86_64', 'Installed: python3-bytesize-2.5-2.el9.x86_64'] modprobe of kvdo works: TASK [Check if kvdo is loadable] *********************************************** task path: /tmp/tmpp9xlrbl_/tests/tests_create_lvmvdo_then_remove.yml:27 ok: [/cache/rhel-x.qcow2] => {"changed": false, "cmd": ["modprobe", "--dry-run", "kvdo"], "delta": "0:00:00.004953", "end": "2021-08-06 17:31:48.323615", "rc": 0, "start": "2021-08-06 17:31:48.318662", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} But blivet fails because it is looking for a kmod named "dm-vdo": Failed to commit changes to disk: Process reported exit code 3: modprobe: FATAL: Module dm-vdo not found in directory /lib/modules/5.14.0-0.rc4.35.el9.x86_64 /usr/sbin/modprobe failed: 1 vdo: Required device-mapper target(s) not detected in your kernel. Run `lvcreate --help' for more information. I just want to know how I can either reliably test vdo functionality in the storage role, or skip the test if vdo is not available. I have already added the "Check if kvdo is loadable" Is dm-vdo also required? Is it always required? Should I also add Full logfile is here: https://fedorapeople.org/groups/linuxsystemroles/logs/linux-system-roles-storage-pull-linux-system-roles_storage-220-d4ce3e8-rhel-x-20210806-204425/artifacts/ansible.log Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: