As noted in https://bugzilla.redhat.com/show_bug.cgi?id=1953540, leapp has included some new data files which were previously not accounted for in tripleo-heat-templates.

Any customer using subscription-manager and with hosts connected to the internet will be fine because all the data files will install when the leapp packages install.

However, any customer in a disconnected environment (no internet access) or using Satellite (and who uses the new version) will end up with a failed upgrade because they will be missing all the data files.

The new version will attempt to download the data files directly from cloud.redhat. If that’s not available, then the operator has to get the files the old way and copy them as they had to before.

As such, we need to include a workaround in https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/framework_for_upgrades_13_to_16.1/index#copying-the-leapp-data-to-the-overcloud-nodes something like the following:

Each overcloud node requires the Leapp data files. Copy the `leapp-data` files from the undercloud to each overcloud.

Procedure:

1. Log in to the undercloud as the stack user.
2. Source the stackrc file.

$ source ~/stackrc

3. Create a static inventory file of all nodes:

$ tripleo-ansible-inventory --static-yaml-inventory ~/inventory.yaml --stack STACK_NAME

If you are not using the default overcloud stack name, set your stack name with the --stack STACK NAME option replacing STACK NAME with the name of your stack.

### note - the above is the same content as https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/framework_for_upgrades_13_to_16.1/index#creating-an-overcloud-inventory-file-initial-steps

4. Run the following ansible command to synchronize the leapp data folder to the overcloud hosts:

$ ansible -i ~/inventory.yaml --become -m synchronize -a "src=/etc/leapp/files dest=/etc/leapp/" overcloud