Bug 1794119
Summary: | [OSP13] Docker containers stuck in restarting. Error is OSError: [Errno 30] Read-only file system: '/etc/pki/ca-trust/extracted' | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | ggrimaux |
Component: | openstack-tripleo-heat-templates | Assignee: | Alex Schultz <aschultz> |
Status: | CLOSED ERRATA | QA Contact: | Sasha Smolyak <ssmolyak> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 13.0 (Queens) | CC: | akaris, aschultz, asonmez, dhill, dhruv, dwojewod, emacchi, ipetrova, jhajyahy, jmelvin, jraju, mariel, mburns, mgarciac, slinaber |
Target Milestone: | --- | Keywords: | Triaged, ZStream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-8.4.1-52.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Before this update, files that were mounted as read-only on the host were incorrectly collected during container configuration generation. This caused the containers to remain in a `restarting` state and generated a `read-only file system` error.
With this update, read-only files are no longer collected during container configuration generation, and the containers restart correctly. If the error still occurs, you must manually clean up the old files before re-deploying. For more information, see: https://access.redhat.com/solutions/5048941
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-06-24 11:33:20 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
ggrimaux
2020-01-22 17:16:44 UTC
The hotfix does not remove the files. Once a customer hits the problem, they need to clean it up per the KCS and deploy with the hotfix to ensure it does not occur again. 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-2020:2718 *** Bug 1847507 has been marked as a duplicate of this bug. *** |