Comment 3 for bug 1884246

Here's the history and an explanation of what I ran into with this bug report:

A. When export was introduced it defaulted to /var/lib/mistral/<stack> [1]

B. I am running config-download manually [2] so I run the following to do an export:

   openstack overcloud config download --name $STACK --config-dir config-download
   openstack overcloud export --stack $STACK --config-download-dir config-download

C. The above worked prior to the mistral removal and will reproduce what I'm reporting

B. Export was updated during the migration from mistral to use the new default location
   so '/var/lib/mistral/<stack>' became '$HOME/config-download/<stack>' [3]

So the command in step B used to work and now it doesn't. I'm not sure if that's a bug
though. Is there a variation of the command in step B I can run which doesn't have this
issue and which doesn't require to do the workaround from comment #1?

I think the next step is to determine if people encounter this issue when not running
config-download manually. If the automatic config-download which happens when you do
not pass --stack-only fails export in the same way, then I think this is a bug for DCN
users. I'll test that next.

[1] https://github.com/openstack/python-tripleoclient/commit/975f7717029b56c7a2e6113d82e166e7c63fcba2#diff-f65025c157b1193fd86c95a092eb1000R54

[2] https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deployment/ansible_config_download.html#manual-config-download

[3] https://github.com/openstack/python-tripleoclient/commit/191438f7435aa19e9656a2052bbb6fa5ce7b6b32#diff-f65025c157b1193fd86c95a092eb1000