Description of problem: The Deployment created by the MAO for the BMO does a rolling update when it is changed, which means there may be 2 pods running at once. We never want more than 1 pod running, so we should look at the settings available to control that behavior. https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#recreate-deployment Version-Release number of selected component (if applicable): 4.6 How reproducible: mostly comes up when working with the MAO but may occur in other scenarios Steps to Reproduce: 1. Modify the metal3 Deployment 2. Watch a second pod launch before the existing one is deleted 3. Actual results: Expected results: Additional info:
In openshift-machine-api namespace observed the pods, found one metal3 pod. Found cluster-baremetal-operator deploy, observed it, modified it, verified that the deploy has been modified. After modification observed the pods, the same single metal3 pod remained
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633