Bug 1835873 - cluster autoscaler end-to-end tests do not validate removal of deletion annotations
Summary: cluster autoscaler end-to-end tests do not validate removal of deletion annot...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.0
Assignee: Michael McCune
QA Contact: sunzhaohua
URL:
Whiteboard:
Depends On: 1820410
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-14 16:24 UTC by Michael McCune
Modified: 2020-06-19 13:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1820410
Environment:
Last Closed: 2020-06-19 13:49:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-api-actuator-pkg pull 150 0 None open add a test for deletion annotations after scale down 2020-06-19 13:02:38 UTC
Red Hat Bugzilla 1820410 0 medium CLOSED [autoscaler]Sometimes the only machine of a machineset gets a delete annotation by autoscaler 2021-02-22 00:41:40 UTC

Comment 1 Michael McCune 2020-05-14 20:53:39 UTC
i am changing the target release version to 4.6.0 as i think these tests are going to take some time to write correctly. i originally created a test that seemed sufficient, but it now looks like deeper investigation is required.

Comment 2 Alberto 2020-05-29 11:10:40 UTC
We are waiting for master to open for 4.6 to merge this.

Comment 3 Michael McCune 2020-06-19 13:40:00 UTC
the test for this has just merged, see the PR attached above

Comment 4 Michael McCune 2020-06-19 13:49:46 UTC
this bug was originally opened during the 4.5 code freeze to reflect an incoming change to the testing repository. given that this bug is linked to one that was closed in 4.5, and that this is only related to that bug in terms of providing testing coverage, i am closing this issue.


Note You need to log in before you can comment on or make changes to this bug.