Bug 1822118
| Summary: | [IPI RHV] Autoscaler failed to scale up | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | sunzhaohua <zhsun> |
| Component: | Cloud Compute | Assignee: | Roy Golan <rgolan> |
| Cloud Compute sub component: | oVirt Provider | QA Contact: | sunzhaohua <zhsun> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | dougsland, vpagar |
| Version: | 4.4 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-27 15:57:47 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
sunzhaohua
2020-04-08 10:07:36 UTC
Almost all the autoscaler cases are blocked by this. due to capacity constraints we will be revisiting this bug in the upcoming sprint Once we got a RHV env, we will test this. Verify
clusterversion: 4.6.0-0.nightly-2020-08-12-062953
1. Create clusterautoscaler and machineautoscaler
---
apiVersion: "autoscaling.openshift.io/v1"
kind: "ClusterAutoscaler"
metadata:
name: "default"
spec:
scaleDown:
enabled: true
delayAfterAdd: 10s
delayAfterDelete: 10s
delayAfterFailure: 10s
unneededTime: 10s
$ oc get machineautoscaler
NAME REF KIND REF NAME MIN MAX AGE
worker-c MachineSet primary-zbpb5-worker-1 1 3 4h9m
2. Create workload to scale up the cluster
3. Check machine status, csrs, autoscale logs
I0817 06:24:58.795113 1 scale_up.go:456] Best option to resize: openshift-machine-api/primary-zbpb5-worker-1
I0817 06:24:58.795140 1 scale_up.go:460] Estimated 3 nodes needed in openshift-machine-api/primary-zbpb5-worker-1
I0817 06:24:58.997943 1 scale_up.go:574] Final scale-up plan: [{openshift-machine-api/primary-zbpb5-worker-1 1->3 (max: 3)}]
I0817 06:24:58.998168 1 scale_up.go:663] Scale-up: setting group openshift-machine-api/primary-zbpb5-worker-1 size to 3
$ oc get machine
NAME PHASE TYPE REGION ZONE AGE
primary-zbpb5-master-0 Running 4d23h
primary-zbpb5-master-1 Running 4d23h
primary-zbpb5-master-2 Running 4d23h
primary-zbpb5-worker-0-ctv4b Running 4d22h
primary-zbpb5-worker-0-f9dht Running 4d22h
primary-zbpb5-worker-0-mcl94 Running 4d22h
primary-zbpb5-worker-1-fzfdf Running 16m
primary-zbpb5-worker-1-nvm77 Running 16m
primary-zbpb5-worker-1-v4s9p Running 50m
$ oc get node
NAME STATUS ROLES AGE VERSION
primary-zbpb5-master-0 Ready master 4d22h v1.19.0-rc.2+edbf229-dirty
primary-zbpb5-master-1 Ready master 4d22h v1.19.0-rc.2+edbf229-dirty
primary-zbpb5-master-2 Ready master 4d22h v1.19.0-rc.2+edbf229-dirty
primary-zbpb5-worker-0-ctv4b Ready worker 4d22h v1.19.0-rc.2+edbf229-dirty
primary-zbpb5-worker-0-f9dht Ready worker 4d22h v1.19.0-rc.2+edbf229-dirty
primary-zbpb5-worker-0-mcl94 Ready worker 4d22h v1.19.0-rc.2+edbf229-dirty
primary-zbpb5-worker-1-fzfdf Ready worker 4m57s v1.19.0-rc.2+edbf229-dirty
primary-zbpb5-worker-1-nvm77 Ready worker 2m53s v1.19.0-rc.2+edbf229-dirty
primary-zbpb5-worker-1-v4s9p Ready worker 34m v1.19.0-rc.2+edbf229-dirty
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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196 |