+++ 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.
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.