-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Enable upstream ovn-k e2e tests downstream
-
False
-
None
-
False
-
To Do
-
44% To Do, 33% In Progress, 22% Done
-
---
-
0
-
0
Template:
Networking Definition of Planned
Epic Template descriptions and documentation
Epic Goal
Ensure we run e2es downstream with OCP cluster.
Why is this important?
It should help us ensure correct behaviour with CNO-deployed clusters and backports
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement
details and documents.
...
Dependencies (internal and external)
1.
...
Previous Work (Optional):
1. …
Open questions::
1. …
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>