Run running FFWD update from 13 to 16, after running `openstack overcloud upgrade prepare` (and a few other commands) the customer runs `openstack overcloud upgrade run --limit overcloud-controller-0`. However, if leapp is not installed on that overcloud node, then this step will fail. Before the customer runs the upgrade, director should have a process to install leap for the customer.
Just as a note, this BZ would requires doc_text change, to state the existence of the new LeappRepoInitCommand and LeappInitCommand Heat parameters, as well as removing the need to pass UpgradeLeappCommandOptions if the repos are the default "--enablerepo rhel-8-for-x86_64-baseos-eus-rpms --enablerepo rhel-8-for-x86_64-appstream-eus-rpms --enablerepo rhel-8-for-x86_64-highavailability-eus-rpms --enablerepo advanced-virt-for-rhel-8-x86_64-rpms --enablerepo ansible-2.9-for-rhel-8-x86_64-rpms --enablerepo fast-datapath-for-rhel-8-x86_64-rpms". I set the requires_doc_text (I can't + it) in the BZ.
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 (Red Hat OpenStack Platform 16.1 director bug fix advisory), 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/RHBA-2020:3542