-
Epic
-
Resolution: Obsolete
-
Major
-
None
-
None
-
cnv-epic-template
-
To Do
-
100% To Do, 0% In Progress, 0% Done
Goal
The idea is to be able to replicate the disconnected job for hypershift with kubevirt with our internal infrastructure.
Value: we can manually trigger it from our jenkins interface choosing a specific CNV candidate build.
Concern: this is going to duplicate an on-going periodic job from openshift-ci, can we simply trust that result?
User Stories
- High-Level goal-based user story, with context.
"As a QE engineer, I want ensure OCP conformance tests that are appropriate for disconnected environment runs successfully on disconnected hypershift environment, so that <Some Reason/Context>." - another user story
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
Notes
- This is a follow up epic needed to ensure adequate test coverage in disconnected scenario for hypershift (https://issues.redhat.com/browse/CNV-30914)
- relates to
-
CNV-37749 [GA] HCP/KubeVirt disconnected clusters
- Closed
-
HOSTEDCP-1260 [Automation Testing] HyperShift deploy on BM by Agent
- Closed
-
CNV-30671 Hypershift/KubeVirt procedure for disconnected clusters
- Closed