Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1866901

Summary:	Deployment strategy for BMO allows multiple pods to run at the same time
Product:	OpenShift Container Platform	Reporter:	Doug Hellmann <dhellmann>
Component:	Bare Metal Hardware Provisioning	Assignee:	Zane Bitter <zbitter>
Bare Metal Hardware Provisioning sub component:	baremetal-operator	QA Contact:	Sasha Smolyak <ssmolyak>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	high	CC:	afasano, beth.white, rbartal, sdasu
Version:	4.6	Keywords:	Triaged
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-24 15:15:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Doug Hellmann 2020-08-06 18:33:45 UTC

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:

Comment 4 Sasha Smolyak 2020-12-14 15:13:21 UTC

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

Comment 7 errata-xmlrpc 2021-02-24 15:15:21 UTC

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