Currently, installing OSP17.1.4 as a greenfield, and also updating it from OSP17.x, require a compute node reboot in order to apply the delayed installation of the systemd-container package. See the background story for "why it does" in bz2247302.

This situation is OK for the OSP17 lifecycle. However, it became a blocker for the adoption of workloads from OSP17 to RHOSO18. We should not require a greenfiled 17.1.4 deployment reboot all hypervisors and live migrate VMs, before the adoption can be started (and it cannot be started w/o systemd-container installed, to not interrupt running workloads during adoption).

Note that the reboot-before-adoption requirement still applies to all OSP17.1.4 deployments updated from OSP17.x. There is NO such a requirement for FFU from OSP16.2.