Last Modified: Oct 04, 2021
Opened: Jun 29, 2021
In automated testing, following partition upgrade, deployment of a tenant immediately after the upgrade may restart one or two times before the tenant comes up. In confd, if you catch it at the right time, the BIG-IP tenant may appear to be stuck with an Error "Waiting for real qemu" ... but this is transient and the system recovers.
In the worst case, tenant bringup is delayed for a few minutes. The system recovers on its own and the tenant finally comes up after 1 or 2 tries.
Kubernetes, Openshift, and kubevirt may have been started or restarted due to a system upgrade.