Bug 1516557
| Summary: | Set disable:true for oci-machine-register | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Angus Thomas <athomas> |
| Component: | puppet-tripleo | Assignee: | RHOS Maint <rhos-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Omri Hochman <ohochman> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 12.0 (Pike) | CC: | achernet, chjones, dprince, jjoyce, jschluet, mburns, michele, sgordon, slinaber, tvignaud |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | 12.0 (Pike) | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | puppet-tripleo-7.4.3-9.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-13 22:22:16 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
Angus Thomas
2017-11-22 22:32:35 UTC
@Omri: I believe that as well as a hard reboot, you also need a container that's failing and being restarted, to properly trigger this issue. Verified with puppet-tripleo-7.4.3-10.el7ost.noarch
unable to reproduce the race issue by running overcloud reboot loop while one of the containers is in "Restarting" status .
steps:
(1) caused horizon container to be stuck in 'restarting status'
[root@overcloud-controller-1 ~]# docker ps | grep horizon
6047011009b6 192.168.0.1:8787/rhosp12/openstack-horizon-docker:12.0-20171128.1 "kolla_start" 29 minutes ago Restarting (2) About a min
horizon
(changed the docker start command pointing to different ports )
(2) ran "Killer Reboot test case" - 5 X reboot , wait 5 minutes sleep after each reboot.
results : docker is still up and running on the OC nodes. while the horizon container is still stuck in restarting.
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/RHEA-2017:3462 |