Bug 1817564

Summary:	Limits not updated
Product:	OpenShift Container Platform	Reporter:	Sergio <sregidor>
Component:	Migration Tooling	Assignee:	John Matthews <jmatthew>
Status:	CLOSED WONTFIX	QA Contact:	Xin jiang <xjiang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.3.z	CC:	chezhang, jmatthew, rpattath, whu, xjiang
Target Milestone:	---
Target Release:	4.3.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1817559	Environment:
Last Closed:	2020-03-30 14:52:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1817559
Bug Blocks:

Description Sergio 2020-03-26 15:13:37 UTC

+++ This bug was initially created as a clone of Bug #1817559 +++

Description of problem:
When migrationcontroller resource is edited to redefine the configured limits, the new configured limits are ignored.

Version-Release number of selected component (if applicable):
CAM 1.1.2
OCP 4.2

How reproducible:
Always

Steps to Reproduce:
1. Install CAM using this limit value in the migration controller

mig_namespace_limit: "2"

2. Run a migration of 3 clusters. The migration should be show a Critical Condition preventing the execution.
3. Edit the migrationcontroller limit and use: 

$ oc edit migrationcontroller migration-controller -n openshift-migration
....
mig_namespace_limit: "4"


Actual results:
After setting the new limit to "4" the migration continues blocked with the critical condition.

Expected results:
The new limit should be used, and migrations with 3 namespaces should be allowed.


Additional info:
Whenever we change the limits in migrationcontroller resource, the controller should be redeployed to take the new values. This redeployment is not happening.

Comment 1 John Matthews 2020-03-30 14:52:42 UTC

After reviewing this issue we have decided it's best to fix this in our CAM 1.2.0 release and not introduce possible regressions into CAM 1.1.2 with this change.
As such I am marking this BZ as CLOSED WONTFIX since we have the original BZ https://bugzilla.redhat.com/show_bug.cgi?id=1817559 already aligned to our CAM 1.2.0.