Bug 1603538
Summary: | [OSP13] starting nova_compute docker on a new compute node makes guest disks on nfs share read-only | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Martin Schuppert <mschuppe> |
Component: | openstack-tripleo-heat-templates | Assignee: | Martin Schuppert <mschuppe> |
Status: | CLOSED ERRATA | QA Contact: | Archit Modi <amodi> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 13.0 (Queens) | CC: | berrange, dasmith, dbecker, dwalsh, ealcaniz, eglynn, ipetrova, jhakimra, joflynn, jschluet, kchamart, lmiccini, mbooth, mburns, morazi, mschuppe, ojanas, owalsh, roxenham, sbauza, sferdjao, sgordon, srevivo, svmichel, vgoyal, vromanso |
Target Milestone: | z2 | Keywords: | Triaged, ZStream |
Target Release: | 13.0 (Queens) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-8.0.4-9.el7ost | Doc Type: | Bug Fix |
Doc Text: |
With shared storage for /var/lib/nova/instances, like nfs, restarting nova_compute on any compute resulted in owner/group change of the instances virtual ephemeral disks and console.log. As a result, instances lost access to their virtual ephemeral disks and stopped working.
The scripts to modify the ownership of the instance files in /var/lib/nova/instances have been improved.
There is now no loss in access to the instance files during restart of nova compute.
|
Story Points: | --- |
Clone Of: | 1594261 | Environment: | |
Last Closed: | 2018-08-29 16:38:50 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: | |||
Bug Depends On: | 1594261 | ||
Bug Blocks: | 1598396 |
Comment 17
Joanne O'Flynn
2018-08-15 08:06:26 UTC
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/RHBA-2018:2574 |