This bug was initially created as a copy of Bug #1923887 I am copying this bug because: It required documentation updates to go with it. Description of problem: In https://bugzilla.redhat.com/show_bug.cgi?id=1923887 we finally close the loop on some issues which arose with regards to repository management when deploying the overcloud. We can now remove the previously implemented workarounds, including: The upgrades-environment.yaml file in 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-upgrades-environment-file-overcloud-leapp is now optional and is only useful when any of the upgrade parameters needs to be customised. There may be other places where repo manipulation was done via parameters or playbook which is no longer needed. With the above-mentioned bug fix the overcloud's container-tools & virt streams are configured by the product, and the right repositories are passed to leapp.
The changes are now published on the Customer Portal: 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-upgrades-environment-file-overcloud-leapp Thank you