-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
As explained in MCO-1860, each MCO regression tests should run in only one suite. Further, the preference should be having the tests live in the default `conformance/serial` and `conformance/parallel` test suites when possible. So, only tests disruptive in nature need to run in the new MCO team's disruptive suite.
This story involves updating the MCO regression tests defined in o/origin to run in the most appropriate suite.
Remove from disruptive suite:
| Feature Gate | Test Name | Correct suite |
|---|---|---|
| MachineConfigNode | Should properly block MCN updates from a MCD that is not the associated one | Default parallel |
| MachineConfigNode | Should properly block MCN updates by impersonation of the MCD SA | Default parallel |
| MachineConfigNode | Should have MCN properties matching associated node properties for nodes in default MCPs | Default parallel |
| MachineConfigNode | Should properly transition through MCN conditions on rebootless node update | Default serial |
| MachineConfigNode | Should properly update the MCN from the associated MCD | Default serial |
| MachineConfigNode | Should have MCN properties matching associated node properties for nodes in custom MCPs | Default serial |
| ManagedBootImages | Should update boot images only on MachineSets that are opted in | Default serial |
| ManagedBootImages | Should not update boot images on any MachineSet when not configured | Default serial |
| ManagedBootImages | Should stamp coreos-bootimages configmap with current MCO hash and release version | Default serial |
| ManagedBootImages | Should update boot images on all MachineSets when configured | Default serial |
| ManagedBootImagesAWS | Should not update boot images on any MachineSet when not configured | Default serial |
| ManagedBootImagesAWS | Should update boot images on all MachineSets when configured | Default serial |
| ManagedBootImagesAWS | Should update boot images only on MachineSets that are opted in | Default serial |
| ManagedBootImagesAWS | Should stamp coreos-bootimages configmap with current MCO hash and release version | Default serial |
Remove from default serial suite:
| Feature Gate | Test Name | Correct suite |
|---|---|---|
| PinnedImages | All Nodes in a Custom Pool should have the PinnedImages in PIS | MCO disruptive |
| PinnedImages | Invalid PIS leads to degraded MCN in a custom Pool | MCO disruptive |
| PinnedImages | Invalid PIS leads to degraded MCN in a standard Pool | MCO disruptive |
| PinnedImages | All Nodes in a standard Pool should have the PinnedImages PIS | MCO disruptive |
| PinnedImages | All Nodes in a custom Pool should have the PinnedImages even after Garbage Collection | MCO disruptive |
Done when:
- All MCO regression tests implemented in o/origin are running in only one test suite (`conformance/serial`, `conformance/parallel`, or mco disrutive)
- Note that this story does not include making any updates to the `ManagedBootImagesvSphere` or `ManagedBootImagesAzure` test since those are newly implemented and should be evaluated at a later time.
- depends on
-
MCO-1860 Determine correct test suite for each MCO regression test
-
- Closed
-
- links to