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:
Active mpath type pool is changed to inactive status after libvirtd restarted. The same issue would be met in logical and disk type pool
Produce version
libvirt-1.1.1-29.el7_0.1.x86_64
How producible
100%
Steps:
1. Define/Start a mpath type pool with the following xml
[root@dell-pet105-04 yy]# virsh pool-define pool-mpath
Pool mpath-test defined from pool-mpath
[root@dell-pet105-04 yy]# virsh pool-start mpath-test
Pool mpath-test started
[root@dell-pet105-04 yy]# cat pool-mpath
<pool type="mpath">
<name>mpath-test</name>
<target>
<path>/dev/mapper</path>
</target>
</pool>
2. Check the pool status
[root@dell-pet105-04 yy]# virsh pool-list --all
Name State Autostart
-----------------------------------------
default active yes
mpath-test active no
3. Restart libvirtd
[root@dell-pet105-04 yy]# service libvirtd restart
Stopping libvirtd daemon: [ OK ]
Starting libvirtd daemon: [ OK ]
4. Re-check the pool status
[root@dell-pet105-04 yy]# virsh pool-list --all
Name State Autostart
-----------------------------------------
default active yes
mpath-test inactive no
Actual Results:
Pool mpath_test is inactivated after libvirtd restarted
Expected Results:
Pool mpath_test should remain active
Additional Info:
The issue was also met in logical and disk type pool
The issue was also met in RHEL6. Is the issue worth to fix in RHEL6 ?
Description: Active mpath type pool is changed to inactive status after libvirtd restarted. The same issue would be met in logical and disk type pool Produce version libvirt-1.1.1-29.el7_0.1.x86_64 How producible 100% Steps: 1. Define/Start a mpath type pool with the following xml [root@dell-pet105-04 yy]# virsh pool-define pool-mpath Pool mpath-test defined from pool-mpath [root@dell-pet105-04 yy]# virsh pool-start mpath-test Pool mpath-test started [root@dell-pet105-04 yy]# cat pool-mpath <pool type="mpath"> <name>mpath-test</name> <target> <path>/dev/mapper</path> </target> </pool> 2. Check the pool status [root@dell-pet105-04 yy]# virsh pool-list --all Name State Autostart ----------------------------------------- default active yes mpath-test active no 3. Restart libvirtd [root@dell-pet105-04 yy]# service libvirtd restart Stopping libvirtd daemon: [ OK ] Starting libvirtd daemon: [ OK ] 4. Re-check the pool status [root@dell-pet105-04 yy]# virsh pool-list --all Name State Autostart ----------------------------------------- default active yes mpath-test inactive no Actual Results: Pool mpath_test is inactivated after libvirtd restarted Expected Results: Pool mpath_test should remain active Additional Info: The issue was also met in logical and disk type pool The issue was also met in RHEL6. Is the issue worth to fix in RHEL6 ?