-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Update pre-merge testing of edpm-ansible content in a upstream
-
False
-
-
False
-
Not Selected
-
?
-
?
-
To Do
-
?
-
rhos-ops-day1day2-upgrades
-
?
-
-
-
Goal:
- As a developer I want to be able to test my edpm-ansible pull request in update scenario following full end-to-end update workflow.
Acceptance Criteria:
- Minor update pre-merge job with github (upstream) content (from current stable content -> latest/PR)
- Job uses catalog index mechanism for instrumenting update to test update end-to-end(operators update first and later Openstack minor update)
Catalog index:
https://quay.io/repository/openstack-k8s-operators/openstack-operator-index-upgrade?tab=tags
https://issues.redhat.com/browse/OSPRH-14819
- Edpm-ansible pull request is used to build ansiblee container, but the container is only injected into update phase. For deployment phase stable ansiblee container is used. This to guarantee that we are testing how changes in pull request impacts update, not deployment.
Open questions:
- We need to measure time the job takes to complete and based on that make it opt-in instead of running it always on all pull request.
- relates to
-
OSPRH-14819 Create an upstream OLM catalog/index which supports update/upgrade testing
-
- Closed
-
- links to