--stack-only --no-config-download are broken

Bug #1880577 reported by John Fulton
2
Affects Status Importance Assigned to Milestone
tripleo
Invalid
Undecided
Unassigned

Bug Description

Ever since config-download was introduced [1] we've had the option to manually run config-downlaod like this:

 openstack overcloud deploy --stack-only ...

However the above, or --no-config-download, are no longer working as documented [2].

The options are still in the client [3] but aren't producing the desired results, e.g. I deployed with --stack-only using an undercloud built on 24 May 2020 and when heat finished my deployment raced ahead as if I hadn't passed --stack-only with the functional equivalent of 'openstack overcloud config download' and then 'ansible-playbook-3 ... ~/config-download/config-download-latestdeploy_steps_playbook.yaml'.

[1] https://github.com/openstack/python-tripleoclient/commit/c68f54a45881a9aeff9cdf197240e2
[2] https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deployment/ansible_config_download.html#config-download-related-cli-arguments
[3] https://opendev.org/openstack/python-tripleoclient/src/branch/master/tripleoclient/v1/overcloud_deploy.py#L892-L894

Revision history for this message
John Fulton (jfulton-org) wrote :

I'm using a virtual undercloud deployed by tripleo-operator-ansible (tripleo-lab) with:

 tripleo_repos_version: tripleo-ci-testing

which I built yesterday and deploying as described in:

https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/provisioning/baremetal_provision.html

I'm not using the standalone

description: updated
Revision history for this message
Emilien Macchi (emilienm) wrote :

Hey John, I couldn't reproduce.

Here is what I did on a fresh undercloud (master):

source ~/stackrc
openstack overcloud deploy \
  --templates /usr/share/openstack-tripleo-heat-templates/ \
  --stack overcloud-0 --stack-only \
  -n /home/stack/oc0-network-data.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/net-multiple-nics.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/network-environment.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/disable-telemetry.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/low-memory-usage.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/enable-swap.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \
    -e /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovn-ha.yaml \
  -e /home/stack/domain.yaml \
  -e /home/stack/containers-prepare-parameter.yaml \
  -e /home/stack/generated-container-prepare.yaml \
  --environment-directory ~/overcloud-0-yml \
  --ntp-server pool.ntp.org --libvirt-type qemu

At this point, it just created the stack:

        +--------------------------------------+-------------+----------------------------------+-----------------+----------------------+--------------+
        | ID | Stack Name | Project | Stack Status | Creation Time | Updated Time |
        +--------------------------------------+-------------+----------------------------------+-----------------+----------------------+--------------+
        | 7efd5bca-69b6-4336-8aca-442825026d8c | overcloud-0 | c71b654a777c4c7b9aa51c07a38b408d | CREATE_COMPLETE | 2020-05-25T17:54:25Z | None |
        +--------------------------------------+-------------+----------------------------------+-----------------+----------------------+--------------+

Then I ran:

tripleo-config-download --stack-name overcloud-0 --output-dir oc0-config-download
tripleo-ansible-inventory --ansible_ssh_user heat-admin --static-yaml-inventory oc0-inventory.yaml --stack overcloud-0

I could see deployment running:
+-------------+-------------------+
| Plan Name | Deployment Status |
+-------------+-------------------+
| overcloud-0 | DEPLOYING |
+-------------+-------------------+

I'll report back when the deployment is finished to deploy.
Note that I didn't deploy Ceph.

Revision history for this message
Emilien Macchi (emilienm) wrote :

My deployment finished successfully, I can't reproduce the issue. Can you please try again with latest rpms?

Revision history for this message
Emilien Macchi (emilienm) wrote :
Revision history for this message
John Fulton (jfulton-org) wrote :

Apologies. This was user error on my part. I had a typo in my deployment command. When I fixed the typo --no-config-download works correctly. I've updated the flags on the bug so that it shouldn't show up as a valid bug any more.

Changed in tripleo:
importance: Critical → Undecided
status: Triaged → Invalid
milestone: ussuri-rc3 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.