Description of problem: ----------------------- Upgrade from RHOS-8 to RHOS-9 fails due to stack being stuck during AODH installation. openstack overcloud deploy --force-postconfig \ --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.yaml \ -e /home/stack/virt/network/network-environment.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 /usr/share/openstack-tripleo-heat-templates/environments/major-upgrade-aodh.yaml \ -e /home/stack/virt/ceph-client-key.yml Version-Release number of selected component (if applicable): ------------------------------------------------------------- openstack-heat-api-cloudwatch-6.1.0-4.el7ost.noarch openstack-heat-api-cfn-6.1.0-4.el7ost.noarch openstack-heat-common-6.1.0-4.el7ost.noarch openstack-heat-engine-6.1.0-4.el7ost.noarch openstack-heat-templates-0-0.3.96a0b0bgit.el7ost.noarch openstack-heat-api-6.1.0-4.el7ost.noarch Steps to Reproduce: ------------------- 1. Upgrade UC from RHOS-8 to RHOS-9 2. Prepare env according docs 3. Start upgrade with AODH installation Actual results: --------------- Upgrade is stuck Expected results: ----------------- Upgrade to RHOS-9 succeeds Additional info: ---------------- Virtual env: 3controllers + 2computes +3ceph
*** Bug 1623492 has been marked as a duplicate of this bug. ***
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:2853