Hide Forgot
Description of problem: OSP11 -> OSP12 upgrade: upgrade-non-controller.sh script silently fails and compute node doesn't get upgraded Version-Release number of selected component (if applicable): (undercloud) [stack@undercloud-0 ~]$ rpm -qa | grep tripleo-heat-templates openstack-tripleo-heat-templates-7.0.3-0.20171019091938.el7ost.noarch (undercloud) [stack@undercloud-0 ~]$ rpm -qa | grep tripleo-common openstack-tripleo-common-7.6.3-0.20171010234828.el7ost.noarch openstack-tripleo-common-containers-7.6.3-0.20171010234828.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy OSP11 2. Upgrade to OSP12 3. Run the upgrade-non-controller.sh script to upgrade a compute node Actual results: The command fails(rc 1) without any error message: (undercloud) [stack@undercloud-0 ~]$ upgrade-non-controller.sh --upgrade compute-r00-00 Sat Oct 21 11:55:19 EDT 2017 upgrade-non-controller.sh Logging to upgrade-non-controller.sh-compute-r00-00 Sat Oct 21 11:55:25 EDT 2017 upgrade-non-controller.sh nova node compute-r00-00 found with IP 192.168.0.27 Sat Oct 21 11:55:25 EDT 2017 upgrade-non-controller.sh Executing /root/tripleo_upgrade_node.sh on 192.168.0.27 Warning: Permanently added '192.168.0.27' (ECDSA) to the list of known hosts. "nova_compute", Sat Oct 21 15:55:26 UTC 2017 528dc68b-53fe-482c-919c-957d0743efb4 tripleo-upgrade compute-r00-00 /root/tripleo_upgrade_node.sh has completed - moving onto ansible playbooks Sat Oct 21 11:55:26 EDT 2017 upgrade-non-controller.sh Clearing any existing dir compute-r00-00 and downloading config compute-r00-00/tripleo-HdrjM9-config (undercloud) [stack@undercloud-0 ~]$ echo $? 1 Expected results: Upgrade socceeds Additional info:
openstack overcloud config download --config-dir returns exit code 1: (undercloud) [stack@undercloud-0 ~]$ openstack overcloud config download --config-dir test; echo $? test/tripleo-aVtbPQ-config 1
removing master review since stable/pike patch is landed.
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