Bug 2132043
| Summary: | After removing autoscalers pod events still show "pod didn't trigger scale-up" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Online | Reporter: | Luca <lgiorgi> | ||||||
| Component: | Unknown | Assignee: | Abhishek Gupta <abhgupta> | ||||||
| Status: | NEW --- | QA Contact: | Xiaoli Tian <xtian> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.x | ||||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | --- | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1915982 [details]
correct scale up event behaviour
|
Created attachment 1915981 [details] scale up event without description of error Description of problem: In an OSD cluster running OCP v. 4.10.33, after having removed all MachineAutoscalers (by deleting all machine pools with autoscaling enabled), trying to schedule a pod for which there's not enough resources available on the cluster will still trigger a "pod didn't trigger scale-up" event. This event does not have a reason for why the scale up was possible, like it usually would have. Version-Release number of selected component (if applicable): OCP v. 4.10.33 How reproducible: Always Steps to Reproduce: 1.Try to schedule a pod that requests too many resources, confirm that you *don't* see "pod didn't trigger scale-up" in the events 1. Create MachineAutoscaler / Machine Pool with autoscaling enabled in OCP cluster 2. Try to schedule a pod that requests too many resources, confirm that you see "pod didn't trigger scale-up" in the events 3. Remove MachineAutoscaler/machine pool from cluster 4. Try to schedule a pod that requests too many resources, confirm that you *still* see "pod didn't trigger scale-up" in the events, although without any explicit error Actual results: scale up event is always shown after having had an autoscaling machine pool defined in the cluster, even after the pool is removed Expected results: Scale up event should not be shown since there are no MachineAutoscalers in the cluster. The even is misleading. Additional info: