origin e2e tests have a small amount of tests around the machine-api. Just scale up one machine, then scale down, make sure that machine joined the cluster. This runs towards the end of the tests so as to not disrupt other tests.
Unlike our more comprehensive e2e tests for our own repos, this test does not create a new machineset. Default machineset options cause us to delete a random machine on scale down, which is probably not what we want.
We should use the annotation to specify which machine we want to remove on scale down to be least disruptive.
Talking about this tests specifically: https://github.com/openshift/origin/blob/f749b790af49f66b558b04f4ffd2799dd4a1e165/test/extended/machines/scale.go#L121
@MGugino are you happy to handle this during the next sprint? This definitely isn't a release blocker but is high priority as it affects testing across many components
Do you think it best to annotate the machine to be removed or should we instead create a new MachineSet for this test?
We intend to refactor these tests generally by making our specific tests 'steps' that other test suites can run limited parts of. We are planning on doing that in the near future.
A recent change to the test configuration (migrating everything to steps) means that this is now unblocked, we can take a look at this next sprint
the PRs associated with this issue are under review
This isn't really considered an urgent issue, we are looking into solving this issue but it will take a longer time to come up with a good solution for this
Using the test-grid - https://testgrid.k8s.io/redhat-openshift-ocp-release-4.10-informing#periodic-ci-openshift-release-master-nightly-4.10-e2e-vsphere-serial
I was able to confirm the newest machine is now getting deleted , attached events.json from the test in private comments
Moved to Verified.
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 (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.