Bug 1936826
Summary: | Guest will be destroyed if iscsi pool is destroyed and libvirtd restart | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Meina Li <meili> |
Component: | libvirt | Assignee: | Virtualization Maintenance <virt-maint> |
libvirt sub component: | Storage | QA Contact: | Meina Li <meili> |
Status: | CLOSED MIGRATED | Docs Contact: | |
Severity: | unspecified | ||
Priority: | low | CC: | lmen, pkrempa, vgoyal, virt-maint, xuzhang, yalzhang |
Version: | 9.0 | Keywords: | MigratedToJIRA, Regression, Triaged |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-09-22 16:19:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Meina Li
2021-03-09 09:56:24 UTC
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. 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 (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. Bulk update: Move RHEL-AV bugs to RHEL9. If necessary to resolve in RHEL8, then clone to the current RHEL8 release. 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. 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. 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. |