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.
DescriptionMichal Privoznik
2019-03-04 13:53:39 UTC
+++ This bug was initially created as a clone of Bug #1658504 +++
While working on a fix for this bug ^^^ I've came across another one:
1) start a storage libvirt pool (e.g. type of iscsi)
2) start a domain with a disk from that storage pool, e.g.:
<disk type='volume' device='disk'>
<driver name='qemu' type='raw'/>
<source pool='iscsi-secret-pool' volume='unit:0:0:1'/>
<target dev='vdc' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</disk>
3) make sure the pool is autostarted (virsh pool-autostart)
4) destroy the pool
5) restart libvirtd
6) observe domain being killed
This is introduced by:
cefb97fb81 virStateDriver - Separate AutoStart from Initialize
e4a969092b Separate out StateAutoStart from StateInitialize
Alternatively, when bug 1658504 is fixed then all that is needed to reproduce this bug is to use a volume from iscsi-direct pool since iscsi-direct pools don't keep their state through libvirtd restarts. Then no pool-destroy is ineeded.
I've just pushed patches upstream:
07a9c8bae8 Revert "Separate out StateAutoStart from StateInitialize"
fc380c2e01 Revert "virStateDriver - Separate AutoStart from Initialize"
31c3c35c94 bhyve: Move autostarting of domains into bhyveStateInitialize
c6266ddb02 daemon: Register secret driver before storage driver
v5.1.0-80-g07a9c8bae8
Additional verify:
Also test iscsi-direct pool for the clone Bug #1658504
<disk type='volume' device='disk'>
<driver name='qemu' type='raw'/>
<source pool='iscsi-direct' volume='unit:0:0:0'/>
<target dev='vdb' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
</disk>
and do the same work as comment7 ,all works well.
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, 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/RHSA-2019:3345