Hide Forgot
Description of problem: After scale down, the cluster autoscaler log continue to output "Removing unregistered node" which is related to the down group Version-Release number of selected component (if applicable): $ bin/openshift-install version bin/openshift-install v0.5.0-master-2-g78e2c8b144352b1bef854501d3760a9daaaa2eb0 Terraform v0.11.8 How reproducible: always Steps to Reproduce: 1. Create clusterautoscaler machineautoscaler resources 2. Scale up and down the cluster 3. Check logs Actual results: After scale down, the cluster autoscaler log continue output "Removing unregistered node" which is related to the down group $ oc logs -f cluster-autoscaler-default-77f884d74b-527bq I1205 05:27:42.269095 1 utils.go:388] Removing unregistered node ip-10-0-133-103.us-east-2.compute.internal W1205 05:27:42.269141 1 utils.go:404] Failed to remove node ip-10-0-133-103.us-east-2.compute.internal: node group min size reached, skipping unregistered node removal I1205 05:27:52.288702 1 utils.go:388] Removing unregistered node ip-10-0-133-103.us-east-2.compute.internal W1205 05:27:52.288746 1 utils.go:404] Failed to remove node ip-10-0-133-103.us-east-2.compute.internal: node group min size reached, skipping unregistered node removal Expected results: No such info Additional info:
In the new version this bug doesn't exist. $ bin/openshift-install version bin/openshift-install v0.8.0-master-2-g5e7b36d6351c9cc773f1dadc64abf9d7041151b1 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.alpha-2018-12-25-225820 True False 34m Cluster version is 4.0.0-0.alpha-2018-12-25-225820 Scale up then scale down, the autoscaler logs: $ oc logs -f cluster-autoscaler-default-7c88c947bc-mnnrj I1226 02:59:42.867768 1 scale_up.go:584] Scale-up: setting group openshift-cluster-api/zhsun-worker-us-east-2a size to 3 I1226 02:59:53.003637 1 scale_up.go:584] Scale-up: setting group openshift-cluster-api/zhsun-worker-us-east-2c size to 3 I1226 03:02:43.750096 1 scale_down.go:791] Scale-down: removing empty node ip-10-0-130-211.us-east-2.compute.internal I1226 03:02:53.828581 1 scale_down.go:791] Scale-down: removing empty node ip-10-0-161-246.us-east-2.compute.internal I1226 03:02:53.828644 1 scale_down.go:791] Scale-down: removing empty node ip-10-0-168-125.us-east-2.compute.internal I1226 03:03:14.261237 1 scale_down.go:791] Scale-down: removing empty node ip-10-0-168-125.us-east-2.compute.internal I1226 03:03:34.403414 1 scale_down.go:791] Scale-down: removing empty node ip-10-0-134-117.us-east-2.compute.internal
Andrew, can you double check and close if it is no longer an issue?
Verified. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-9 True False 17h Cluster version is 4.0.0-9 Scale up then scale down, the autoscaler logs: I0111 08:25:03.996513 1 scale_up.go:584] Scale-up: setting group openshift-cluster-api/zhsun-worker-us-east-2c size to 5 I0111 08:31:37.324344 1 scale_down.go:791] Scale-down: removing empty node ip-10-0-163-132.us-east-2.compute.internal I0111 08:31:37.324993 1 scale_down.go:791] Scale-down: removing empty node ip-10-0-172-163.us-east-2.compute.internal I0111 08:31:37.325187 1 scale_down.go:791] Scale-down: removing empty node ip-10-0-170-149.us-east-2.compute.internal I0111 08:31:37.325267 1 scale_down.go:791] Scale-down: removing empty node ip-10-0-174-211.us-east-2.compute.internal
(In reply to Jan Chaloupka from comment #2) > Andrew, can you double check and close if it is no longer an issue? I no longer see this issue either.