-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
builds-1.2
-
None
-
1
-
False
-
-
False
-
-
-
Builds Sprint #23, Builds Sprint #24
-
2
-
Customer Reported
Description of problem:
Workaround
Prerequisites (if any, like setup, operators/versions): OCP 4.16.24
Steps to Reproduce
# Install OpenShift Pipeline Operator 1.16.1
- Install OpenShift Build Operator 1.2.0
Everything is working
- Uninstall completely OpenShift Build:
- Delete the OpenShiftBuild CR
- Delete the namespace openshift-builds (which delete the Subscription at the same time)
- Uninstall completely OpenShift Pipelines:
- Delete the openshift-pipelines namespace
- Delete the openshift-peipleines-operator-rh subscription on openshift-operators namespace
- Reinstall OpenShift Pipelines Operator
The pipelines operator installation work
- Reinstall OpenShift Builds Operator
The Operator deploy a new OpenShift Pipeline Operator instance on openshift-builds namespace which is clashing with the existing OpenShift Pipelines reinstallation
Actual results:
Expected results: The Build Operator should not try to install OpenShift Pipelines if already existing
Reproducibility (Always/Intermittent/Only Once): Always
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):
Slack Conversation: https://redhat-internal.slack.com/archives/C014MHHKUSF/p1733402157090789
*
- impacts account
-
BUILD-1531 Builds Operator is creating a conflicting Pipelines Operator
-
- Closed
-