Description of problem: vSphere IPI was dropped from 4.4, therefore we don't want the controller to run in this release. We'll enable it back once master opens for 4.5 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Still seeing machine-api-controller pods [miyadav@miyadav bug1800425]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.4.0-0.nightly-2020-03-08-235004 True False 132m Cluster version is 4.4.0-0.nightly-2020-03-08-235004 [miyadav@miyadav bug1800425]$ Steps : oc get pods -n openshift-machine-api NAME READY STATUS RESTARTS AGE cluster-autoscaler-operator-7dd5b454f7-bdgkq 2/2 Running 0 136m machine-api-controllers-6bbd74ddd-6lr8r 4/4 Running 4 144m machine-api-operator-7969bfb45f-8sblt 2/2 Running 2 165m Actual : machine-api-controllers running Expected : machine-api-controller pods should not be deployed for this version
As it was expected that controller should run on 4.5 we are seeing that [miyadav@miyadav ManualRun]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-03-22-211241 True False 22m Cluster version is 4.5.0-0.nightly-2020-03-22-211241 Steps : run oc get pods -n openshift-machine-api NAME READY STATUS RESTARTS AGE cluster-autoscaler-operator-74c6c6dbf8-f7wrt 2/2 Running 0 34m machine-api-controllers-6f9968fcf5-r82ck 4/4 Running 0 35m machine-api-operator-56bdfb8474-ll2ll 2/2 Running 0 35m Actual - Machine controller pod is running Expected : Machine controller pod is running