The original pre-requisites for adoption were RHOSP 17.1.4 which included (1). Some time later some additional changes made to the deployment tooling to ensure that the systemd-container package was installed and machined was running on the host. These changes were finalised in 17.1.6.

Current documentation expresses that the source environment must be on 17.1.latest which is a bit heavy handed and impacts customers who are already planning their upgrades based on 17.1.4. We need to hold the minimum at 17.1.4 and providing guidance for any additional requirements beyond that release. We should only be shifting that minimum if there is a critical problem uncovered that cannot be worked around.

So, for example, (2) can be changed to state that it is only required to be done if systemd-container is not installed and machined is not already running. It can also include steps to identify whether that is the case.

Also, (3) has two sections which say that RHOSP must be at the latest minor release. One is 'Perform a minor update to the latest RHOSP version' and the other is 'The RHOSP 17.1 cloud is updated to the latest minor version of the 17.1 release'. These can be consolidated into simply saying that 17.1.4 is a pre-requisite.

I also suggest that in (3) 'Install the systemd-container package on your Compute hosts' is changed to something that expresses that the package and service must be running, and then point to the procedure for how to verify and remedy that as it currently does.

(1) https://bugzilla.redhat.com/show_bug.cgi?id=2247302 

(2) https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/adopting_a_red_hat_openstack_platform_17.1_deployment/rhoso-180-adoption-overview_assembly#installing-the-systemd-container-package-on-compute-hosts_planning 

(3) https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/adopting_a_red_hat_openstack_platform_17.1_deployment/rhoso-180-adoption-overview_assembly#adoption-prerequisites_planning