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.
I'm not entirely persuaded that this is a regression. The code that does the pool+vol translation is in place for a rather long time.
Anyways, we should not attempt to do the translation when reconnecting. The storage pool may even be redefined to a new source. We should store the original config of the source in private data.
(In reply to Meina Li from comment #2)
> There's a same bug before and has already been fixed.
> Bug 1685151 - Guest will be destroyed if autostarted pool is destroyed and
> libvirtd restarted
So this should be a regression bug.
It can still be reproduced with libvirt-8.5.0-5.el9.x86_64 and qemu-kvm-7.0.0-10.el9.x86_64.
So according to the comment 1, I change the "Stale date" to avoid the 30-day auto-close.
It can still be reproduced with libvirt-9.0.0-9.el9_2.x86_64 and qemu-kvm-7.2.0-14.el9_2.x86_64.
Comment 11RHEL Program Management
2023-09-22 16:18:36 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 12RHEL Program Management
2023-09-22 16:19:54 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Description of problem: Guest will be destroyed if iscsi pool is destroyed and libvirtd restart Version-Release number of selected component (if applicable): libvirt-7.0.0-8.module+el8.4.0+10233+8b7fd9eb.x86_64 qemu-kvm-5.2.0-10.module+el8.4.0+10217+cbdd2152.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start a storage Regres pool with iscsi backend storage. # cat iscsi-pool.xml <pool type='iscsi'> <name>iscsi</name> <uuid>37219096-5307-4e8f-af91-c22c45420563</uuid> <capacity unit='bytes'>21474836480</capacity> <allocation unit='bytes'>21474836480</allocation> <available unit='bytes'>0</available> <source> <host name='**IP**' port='3260'/> <device path='iqn.2021-01.com.redhat:test'/> </source> <target> <path>/dev/disk/by-path</path> <permissions> <mode>0755</mode> <owner>-1</owner> <group>-1</group> </permissions> </target> </pool> # virsh pool-define iscsi-pool.xml Pool iscsi defined from iscsi-pool.xml # virsh pool-start iscsi Pool iscsi started # virsh pool-list --all Name State Autostart --------------------------------- default active yes iscsi active no 2. Start a domain with a disk from that storage pool # virsh dumpxml lmn | grep /disk -B10 ... <disk type='volume' device='disk'> <driver name='qemu' type='raw'/> <source pool='iscsi' volume='unit:0:0:0' mode='host' index='1'/> <backingStore/> <target dev='vdc' bus='virtio'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </disk> # virsh list --all Id Name State --------------------------------- 1 lmn running 3. Set the pool as autostart # virsh pool-autostart iscsi Pool iscsi marked as autostarted 4. Destroy the pool and restart libvirtd # virsh pool-destroy iscsi Pool iscsi destroyed # systemctl restart libvirtd 5. Check the guest status. # virsh list --all Id Name State --------------------------------- - lmn shut off Actual results: Guest will be destroyed Expected results: Guest is still in running Additional info: 1. Same with iscsi-direct pool. 2. libvirtd.log: 2021-03-09 09:45:33.230+0000: 324447: debug : virGetConnectGeneric:156 : Opened new storage connection 0x7f3c58015190 2021-03-09 09:45:33.230+0000: 324447: debug : virStoragePoolLookupByName:367 : conn=0x7f3c58015190, name=iscsi 2021-03-09 09:45:33.230+0000: 324447: debug : virAccessManagerCheckStoragePool:359 : manager=0x559816feedf0(name=stack) driver=storage pool=0x7f3c5810e8d0 perm=0 2021-03-09 09:45:33.230+0000: 324447: debug : virAccessManagerCheckStoragePool:359 : manager=0x559816feee50(name=none) driver=storage pool=0x7f3c5810e8d0 perm=0 2021-03-09 09:45:33.230+0000: 324447: debug : virStoragePoolIsActive:2187 : pool=0x7f3c580205f0 2021-03-09 09:45:33.230+0000: 324447: debug : virAccessManagerCheckStoragePool:359 : manager=0x559816feedf0(name=stack) driver=storage pool=0x7f3c5810e8d0 perm=1 2021-03-09 09:45:33.230+0000: 324447: debug : virAccessManagerCheckStoragePool:359 : manager=0x559816feee50(name=none) driver=storage pool=0x7f3c5810e8d0 perm=1 2021-03-09 09:45:33.230+0000: 324447: error : virDomainStorageSourceTranslateSourcePool:31401 : unsupported configuration: storage pool 'iscsi' containing volume 'unit:0:0:0' is not active 2021-03-09 09:45:33.230+0000: 324447: debug : virStoragePoolDispose:601 : release pool 0x7f3c580205f0 iscsi 37219096-5307-4e8f-af91-c22c45420563 2021-03-09 09:45:33.230+0000: 324447: debug : qemuProcessStop:7590 : Shutting down vm=0x5598170216a0 name=lmn id=2 pid=324291, reason=daemon, asyncJob=none, flags=0x0 2021-03-09 09:45:33.230+0000: 324447: debug : qemuDomainLogAppendMessage:6605 : Append log message (vm='lmn' message='2021-03-09 09:45:33.230+0000: shutting down, reason=daemon ) stdioLogD=1 2021-03-09 09:45:33.230+0000: 324447: debug : virNetSocketNewConnectUNIX:683 : path=/run/libvirt/virtlogd-sock spawnDaemon=0 binary=<null> 2021-03-09 09:45:33.230+0000: 324447: debug : virNetSocketNewConnectUNIX:739 : connect() succeeded 2021-03-09 09:45:33.230+0000: 324447: debug : virNetSocketNew:245 : localAddr=0x7f3c43ffe540 remoteAddr=0x7f3c43ffe5d0 fd=34 errfd=-1 pid=0 2021-03-09 09:45:33.230+0000: 324447: info : virNetSocketNew:301 : RPC_SOCKET_NEW: sock=0x5598170848b0 fd=34 errfd=-1 pid=0 localAddr=127.0.0.1;0, remoteAddr=127.0.0.1;0