Bug 1725865
Summary: | openstack overcloud upgrade prepare fails to update heat templates | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Sergii Golovatiuk <sgolovat> |
Component: | openstack-heat | Assignee: | Rabi Mishra <ramishra> |
Status: | CLOSED ERRATA | QA Contact: | Sasha Smolyak <ssmolyak> |
Severity: | high | Docs Contact: | |
Priority: | urgent | ||
Version: | 15.0 (Stein) | CC: | apevec, cjeanner, emacchi, jstransk, lhh, mburns, ramishra, rrasouli, sbaker, shardy, ssmolyak |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 15.0 (Stein) | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-heat-12.0.1-0.20190704050403.bf16acc.el8ost | Doc Type: | No Doc Update |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-09-21 11:23:46 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
Sergii Golovatiuk
2019-07-01 15:22:48 UTC
This is probably due to removal of the attribute from templates, but not from the stack. We have already hit similar issues several times in Heat, though previously mainly w/r/t resource registry, e.g. i was just able to dig up this: https://bugs.launchpad.net/tripleo/+bug/1758014 We probably need a revert or at least a partial revert (put back the referenced attribute). Or we need to fix Heat if it's possible. This could be removed in a 2 stage process. First remove the reference from overcloud.j2 and set the attribute in role.role.j2 to empty value, and in next release remove the attribute from role.role.j2 completely. That's very similar to how we "fixed" the resource registry issues earlier. The process is working based on process: https://gitlab.cee.redhat.com/osp15/osp-upgrade-el8 The upgrade job passed. Verified 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-2019:2811 |