Description of problem: Octavia deployment fails during overcloud install (step5). Version-Release number of selected component (if applicable): RHOS-17.1-RHEL-9-20230525.n.1 How reproducible: Deploy an overcloud with Octavia, and OctaviaManageNovaFlavor set to True (default). Actual results: Flavor in Nova, but not in Octavia. The deployment returns: END return value: 2"], "stdout": "openstack: 'loadbalancer flavorprofile create --name octavia_amphora-mvcpu-ha_profile --provider amphora --flavor-data {\"loadbalancer_topology\": \"ACTIVE_STANDBY\", \"compute_flavor\": \"amphora-mvcpu-ha\"}' is not an openstack command. See 'openstack --help'.\nDid you mean one of these?\n container create\n container delete\n container list\n container save\n container set\n container show\n container unset", "stdout_lines": ["openstack: 'loadbalancer flavorprofile create --name octavia_amphora-mvcpu-ha_profile --provider amphora --flavor-data {\"loadbalancer_topology\": \"ACTIVE_STANDBY\", \"compute_flavor\": \"amphora-mvcpu-ha\"}' is not an openstack command. See 'openstack --help'.", "Did you mean one of these?", " container create", " container delete", " container list", " container save", " container set", " container show", " container unset"]} Expected results: The flavor is successfuly created.
The issue seems reproducible only on pre-provisioned servers. the python3-octaviaclient RPM is missing, thus the "openstack loadbalancer" command fails. In our CI jobs, the directory images already include octaviaclient.
Raising severity due to the Regression keyword
After running the following on a host with puddle RHOS-17.1-RHEL-9-20230607.n.0: ~ > cat virt/flavors.yml parameter_defaults: OctaviaManageNovaFlavor: True ~ > cat overcloud_deploy.sh | grep flavor -e /home/stack/virt/flavors.yaml \ I re-deployed the overcloud successfully: 2023-06-09 10:05:29.491228 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ End Summary Information ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2023-06-09 10:05:30.728 418717 INFO tripleoclient.utils.utils [-] Temporary directory [ /tmp/tripleo2j49aa4j ] cleaned up 2023-06-09 10:05:30.729 418717 INFO tripleoclient.utils.utils [-] Ansible execution success. playbook: /home/stack/overcloud-deploy/overcloud/config-download/overcloud/deploy_steps_playbook.yaml Overcloud configuration completed for stack: overcloud 2023-06-09 10:05:30.732 418717 INFO tripleoclient.v1.overcloud_deploy.DeployOvercloud [-] Overcloud configuration completed for stack: overcloud 2023-06-09 10:05:30.784 418717 WARNING tripleoclient.utils.safe_write [-] The output file /home/stack/overcloud-deploy/overcloud/overcloud-deployment_status.yaml will be overriden Overcloud Endpoint: http://10.0.0.119:5000 Overcloud Horizon Dashboard URL: http://10.0.0.119:80/dashboard Overcloud rc file: /home/stack/overcloud-deploy/overcloud/overcloudrc and /home/stack/overcloudrc Overcloud Deployed successfully 2023-06-09 10:05:31.192 418717 INFO tripleoclient.v1.overcloud_deploy.DeployOvercloud [-] Stopping ephemeral heat. 2023-06-09 10:05:31.280 418717 INFO tripleoclient.heat_launcher [-] Pod does not exist: ephemeral-heat 2023-06-09 10:05:33.784 418717 INFO osc_lib.shell [-] END return value: None This BZ looks good to me and I am moving the BZ status to VERIFIED. Please let me know if there are any additional verification actions I missed.
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 (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), 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-2023:4577