yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #76167
[Bug 1530860] Re: Nova service restart disconnects Quobyte volumes on systemd systems
** Changed in: nova
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1530860
Title:
Nova service restart disconnects Quobyte volumes on systemd systems
Status in OpenStack Compute (nova):
Fix Released
Bug description:
When running an instance from an image in a Cinder Quobyte volume
issues arise when the corresponding Nova service (openstack-nova-
compute) is restarted or stopped while the instance is active. systemd
sigterms the whole cgroup, this includes the Quobyte client(s)
handling the instances mount point(s), which effectively removes the
image from under the VM(s).
Possible immediate Mitigation steps:
- Do _NOT_ restart/stop a Nova service that has running instances using images in Cinder Quobyte volumes
- Reconfigure sytemd.kill to use killmode=process or killmode=none instead of killmode=control-group (which is the default).
- Migrate instances off the host prior to restarting/stopping the Nova service.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1530860/+subscriptions
References