Bug 1555329
Summary: | FFU: os-collect-config is stopped on the overcloud nodes after deploy_steps_playbook.yaml | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> |
Component: | openstack-tripleo-heat-templates | Assignee: | Lukas Bezdicka <lbezdick> |
Status: | CLOSED ERRATA | QA Contact: | Marius Cornea <mcornea> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 13.0 (Queens) | CC: | dbecker, jschluet, lbezdick, mandreou, mbracho, mbultel, mburns, mcornea, morazi, rhel-osp-director-maint |
Target Milestone: | beta | Keywords: | Triaged |
Target Release: | 13.0 (Queens) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-8.0.0-0.20180326192239.e59fd2c.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-27 13:36:14 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
Marius Cornea
2018-03-14 13:41:02 UTC
took this one for triage last week - first pass, can't see something that is explicitly stopping os-collect-config, except in FFU stopping @ [1] and starting at [2] any idea what is stopping it mcornea and whether it was indeed started OK after the ffu playbook? Alternatively the controller logs (journal?) so we can try and work out what happened [1] https://github.com/openstack/tripleo-heat-templates/blob/97664cb9fe8d930c01cbbf6026d0dcefce378599/common/deploy-steps.j2#L592 [2] https://github.com/openstack/tripleo-heat-templates/blob/97664cb9fe8d930c01cbbf6026d0dcefce378599/common/deploy-steps.j2#L629 This is done in ffu role steps and there is already fix, still causing issues though. Investigating. Resolved as part of: https://review.openstack.org/#/q/I649afc6fa384ae21edc5bc917f8bb586350e5d47 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-2018:2086 |