Bug 1759613 - libvirt+socket activation will re-autostart domains/networks/ etc
Summary: libvirt+socket activation will re-autostart domains/networks/ etc
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-08 16:50 UTC by Cole Robinson
Modified: 2019-11-16 00:23 UTC (History)
10 users (show)

Fixed In Version: libvirt-5.6.0-5.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-16 00:23:24 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Cole Robinson 2019-10-08 16:50:51 UTC 
With libvirt socket activation in Fedora 31, libvirtd may be started and stopped transparently many times while a host is running. domain/network/storage autostart is tied to daemon startup, so objects may be repeatedly started even after the user has manually shut them down.

Fixed upstream, we should backport this to F31: https://www.redhat.com/archives/libvir-list/2019-October/msg00214.html
Comment 1 Fedora Update System 2019-11-11 20:50:10 UTC 
FEDORA-2019-8a6d24ceec has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-8a6d24ceec
Comment 2 Fedora Update System 2019-11-13 04:56:53 UTC 
libvirt-5.6.0-5.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-8a6d24ceec
Comment 3 Fedora Update System 2019-11-16 00:23:24 UTC 
libvirt-5.6.0-5.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.