Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-1716

[Regression Test 3/5] Validate MCN properties for node with on-cluster image mode enabled

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • MCO Sprint 279
    • 0

      With the API changes made in MCO-1675, new properties were added in the MachineConfigNode (MCN) Spec and Status to hold the values of the `machineconfiguration.openshift.io/desiredImage` and `machineconfiguration.openshift.io/currentImage` node annotations. This test should ensure that the MCN properties, both new and pre-existing, are set as expected when on cluster image mode is enabled and disabled.

      This test will be similar to the test created in MCO-1595. However, it needs to validate the new MCN properties added in MCO-1675 both when on-cluster image mode is enabled on a node and when it is not.

      At a high-level, the sequence of this test will likely be something like:

      1. Validate starting properties of the MCN.
      2. Create a custom MachineConfigPool (MCP) & add a node to it.
      3. Validate the properties of the MCN.
      4. Enable on cluster image mode by applying a MachineOSConfig.
      5. Validate the properties of the MCN.
      6. Disable on cluster image mode by deleting the applied MachineOSConfig.
      7. Validate the properties of the MCN.

      Done when:

      References:

      • Information for creating and apply MCs can be found here.
      • On-cluster image mode docs can be found here.

      Depends on:

      • This test will probably need to be tagged as `Disruptive` since it will result in node reboots. Thus, completing this story depends on the MCO team having a test suite where running disruptive tests is allowed (see MCO-1679MCO-1652).
      • Creating this test will be much simpler and straightforward once the framework for on-cluster image mode tests in the MCO is established (see MCO-1609).
      • These tests should contribute to the StatusReporting feature gate’s component readiness score. Therefore, this test should be created after the StatusReporting feature gate exists (see MCO-1681).
      • This test depends on on-cluster image mode tests statuses existing in the MCN API & the associated functionality being implemented in the MCO (see MCO-1675, and MCO-1713).

              rh-ee-ijanssen Isabella Janssen
              rh-ee-ijanssen Isabella Janssen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: