Description of problem: ----------------------- Upgrade from RHOS-9 to RHOS-10 failed during convergence stage: openstack overcloud deploy \ --timeout 100 \ --templates /usr/share/openstack-tripleo-heat-templates \ --stack overcloud \ --libvirt-type kvm \ --ntp-server clock.redhat.com \ --control-scale 3 \ --control-flavor controller \ --compute-scale 2 \ --compute-flavor compute \ --ceph-storage-scale 3 \ --ceph-storage-flavor ceph \ -e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml \ -e /home/stack/virt/internal.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation-v6.yaml \ -e /home/stack/virt/network/network-environment-v6.yaml \ -e /home/stack/virt/enable-tls.yaml \ -e /home/stack/virt/inject-trust-anchor.yaml \ -e /home/stack/virt/hostnames.yml \ -e /home/stack/virt/debug.yaml \ -e /home/stack/virt/public_vip.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/tls-endpoints-public-ip.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/major-upgrade-pacemaker-converge.yaml ... 2018-05-16 23:39:35Z [AllNodesDeploySteps.CephStorageDeployment_Step3.0]: CREATE_COMPLETE state changed 2018-05-16 23:39:35Z [AllNodesDeploySteps.CephStorageDeployment_Step3]: CREATE_COMPLETE Stack CREATE completed successfully 2018-05-16 23:39:35Z [AllNodesDeploySteps.ComputeDeployment_Step3.0]: CREATE_FAILED Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 1 2018-05-16 23:39:35Z [AllNodesDeploySteps.CephStorageDeployment_Step3.0]: SIGNAL_IN_PROGRESS Signal: deployment a22510c9-b69d-460b-8bde-4961690b0a56 succeeded 2018-05-16 23:39:35Z [AllNodesDeploySteps.ComputeDeployment_Step3]: CREATE_FAILED Resource CREATE failed: Error: resources[1]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 1 2018-05-16 23:39:36Z [AllNodesDeploySteps.CephStorageDeployment_Step3]: CREATE_COMPLETE state changed 2018-05-16 23:39:36Z [AllNodesDeploySteps.ComputeDeployment_Step3]: CREATE_FAILED Error: resources.ComputeDeployment_Step3.resources[1]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1 2018-05-16 23:39:36Z [AllNodesDeploySteps.ControllerDeployment_Step3]: CREATE_FAILED CREATE aborted 2018-05-16 23:39:36Z [AllNodesDeploySteps]: CREATE_FAILED Resource CREATE failed: Error: resources.ComputeDeployment_Step3.resources[1]: Deployment to serveHeat Stack update failed. r failed: deploy_status_code: Deployment exited with non-zero status code: 1 2018-05-16 23:39:37Z [AllNodesDeploySteps]: CREATE_FAILED Error: resources.AllNodesDeploySteps.resources.ComputeDeployment_Step3.resources[1]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1 2018-05-16 23:39:37Z [overcloud]: UPDATE_FAILED Error: resources.AllNodesDeploySteps.resources.ComputeDeployment_Step3.resources[1]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1 Stack overcloud UPDATE_FAILED Checking logs on compute: ------------------------- ... Error: We couldn't get the live value of the neutron agent, please contact support. at /etc/puppet/modules/tripleo/manifests/profile/base/neutron.pp:77 on node compute-0.localdomain\u001b[0m\n", "deploy_status_code": 1} Version-Release number of selected component (if applicable): ------------------------------------------------------------- puppet-tripleo.noarch 5.6.8-6.el7ost openstack-tripleo-heat-templates.noarch 5.3.10-1.el7ost Steps to Reproduce: ------------------- 1. Upgrade RHOS-9 to RHOS-10
*** Bug 1582284 has been marked as a duplicate of this bug. ***
*** Bug 1581075 has been marked as a duplicate of this bug. ***
*** Bug 1593422 has been marked as a duplicate of this bug. ***
Hello, Which nodes should the hotfix be installed? undercloud or controller compute ? all overcloud nodes?
All overcloud nodes in my experience needed that patch
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/RHBA-2018:2101