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

MCO Provide Coordination for Reboot by Other Operators

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • None
    • mco-reset-coordination
    • False
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined
    • 0
    • 0

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Provide a mechanism for other agents to request a single node reboot
      • Have an initial implementation used by the SRIOV Operator to reboot nodes after changing SR-IOV configuration

      Why is this important?

      • Currently 2 Bugs are recorded for 4.7: 19161696 (MCO) and 1921321 (SRIOV)
      • These uncovered a race condition between SRIOV and MCO.  Both sides require a fix.

      Scenarios

      1. An MCO managed change and an SRIOV managed change happening simultaneously is coordinated correctly, and neither operator breaks the other.
      2. A user must be able to add a server to a machine configuration pool which includes MCO and SRIOV configuration.

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • A user can configure SRIOV and MCO simultaneously
      • A server can be added to a machine config pool with contains SRIOV and MCO changes.

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. An initial workaround for 1921321 (SRIOV) has been proposed.  This likely will be fixed in 4.7.

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              Unassigned Unassigned
              kenyis Ken Young
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: