Red Hat Bugzilla – Bug 1353049
[RFE] failed update and/or upgrade attempt should return non 0 value.
Last modified: 2017-06-14 11:16:45 EDT
rhel-osp-director: [RFE] failed update and/or upgrade attempt should return non 0 value. Currently , once the update or upgrade fails: IN_PROGRESS FAILED update finished with status FAILED The exit value is 0, so we can't test result based on it. Expected: The exit value should be 0 only when the update/upgrade succeeded.
Brad - Can you see if this is a reasonably quick fix to include in 9?
What command(s) is this referring to? openstack overcloud deploy? openstack overcloud update?
openstack overcloud update stack overcloud -i with arguments.
Upstream bug: https://bugs.launchpad.net/tripleo/+bug/1599872
Can you please update the BZ, please? Seems that upstream bug was merged back.
Sasha, did you notice if this is included in OSP10 while testing upgrades?
[stack@instack ~]$ openstack overcloud update stack overcloud -i --templates -e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e network-environment.yaml starting package update on stack overcloud <urlopen error [Errno 2] No such file or directory: '/usr/share/openstack-tripleo-heat-templates/overcloud-without-mergepy.yaml'> [stack@instack ~]$ echo $? 1
Thank you, Sasha. Adding as an RFE for 11.
Brad, this still seems not working, could you have a look, please?
fix was merged upstream in stable/newton on Sep 20. Moving to Modified
See comment#11
Updating NVR and component. Target release is set to 11 so, even though the fix was backported I'm setting "Fixed in version" according to the 11 puddle.
Verified for puddle 2017-04-06.
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