Red Hat Bugzilla – Bug 1416834
Gracefully fails if user is still using old hiera mechanism.
Last modified: 2017-05-17 15:43:48 EDT
Hi, as described there[1], the new hiera hook is a breaking change in in ocata. As there hasn't been a deprecation period, we have to make any error very user friendly. Currently the template deployment are just stuck. This bug should make sure that we have such mechanism in place. Steve Hardy suggested that 99-refresh-completed could be a good candidate to signal the error. A strong documentation should go with this change. [1] http://lists.openstack.org/pipermail/openstack-dev/2017-January/110922.html
AFAICS we still need to cherrypick this to ocata, as I can't see it in [3] and my just upgraded OSP11 undercloud with openstack-heat-agents-1.0.0-2.el7ost.noarch doesn't have the fix. I just posted the cherrypick at https://review.openstack.org/#/c/450195/ As discussed on the openstack-dev mailing list at [1] we remove any existing data during the newton to ocata upgrade with [2] so the remaining cherrypick is just for deployments starting at ocata thanks
(In reply to marios from comment #2) > AFAICS we still need to cherrypick this to ocata, as I can't see it in [3] > and my just upgraded OSP11 undercloud with > openstack-heat-agents-1.0.0-2.el7ost.noarch doesn't have the fix. I just > posted the cherrypick at https://review.openstack.org/#/c/450195/ > > As discussed on the openstack-dev mailing list at [1] we remove any existing > data during the newton to ocata upgrade with [2] so the remaining cherrypick > is just for deployments starting at ocata > > thanks woops sorry, [1] http://lists.openstack.org/pipermail/openstack-dev/2017-January/110922.html we [2] https://github.com/openstack/tripleo-heat-templates/blob/stable/ocata/environments/major-upgrade-composable-steps.yaml#L10-L15 [3] https://github.com/openstack/heat-agents/blob/stable/ocata/heat-config-hiera/install.d/hook-hiera.py
Nearly merged in stable/ocata.
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:1245