Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-27597

Revert configuration done through NodeNetworkConfigurationPolicies

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • None
    • CNV Network
    •  cnv-epic-template
    • To Do

      Goal

      Allow users to request a revert of configuration done through a previously applied NodeNetworkConfigurationPolicy.

      User Stories

      • As a Console user, I expect to have a "delete" option available on the NodeNetworkConfigurationPolicies I created.
      • <another user story>

      Non-Requirements

      • <List of things not included in this epic, to alleviate any doubt raised during the grooming process.>

      Notes

      • Investigate whether setting "absent" on everything is good enough or if it is insufficient.
      • The revert does not have to cover 100% of situations, but we should be able to define a clear set of scenarios where it is useful.

      Done Checklist

      Who What Reference
      DEV Upstream roadmap issue (or individual upstream PRs) <link to GitHub Issue>
      DEV Upstream documentation merged <link to meaningful PR>
      DEV gap doc updated <name sheet and cell>
      DEV Upgrade consideration <link to upgrade-related test or design doc>
      DEV CEE/PX summary presentation label epic with cee-training and add a <link to your support-facingĀ preso>
      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>

            phoracek@redhat.com Petr Horacek
            phoracek@redhat.com Petr Horacek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: