[federation] Fix RHSSO OperatorGroup conflict with RHOSO operators#4028
Conversation
|
Skipping CI for Draft Pull Request. |
|
Build failed (check pipeline). Post ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 19m 08s |
The federation role was deploying the RHSSO OperatorGroup into openstack-operators, which already has an OperatorGroup from the OpenStack operator. OLM enforces one OperatorGroup per namespace, so the second one triggered TooManyOperatorGroups and blocked InstallPlan creation for the RHSSO subscription. Change the default cifmw_federation_operator_namespace from openstack-operators to keycloak-operators, and add a task to create that namespace before applying the OLM manifest. Signed-off-by: Samuel Rac <srac@redhat.com>
srac0
force-pushed
the
fix/RHOSS-OperatorGroup-conflict
branch
from
4c82bed to
b51bec2
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Valkyrie00 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
Bot
merged commit 5bd0c82
into
openstack-k8s-operators:main
3 participants
The federation role was deploying the RHSSO OperatorGroup into openstack-operators, which already has an OperatorGroup from the OpenStack operator. OLM enforces one OperatorGroup per namespace, so the second one triggered TooManyOperatorGroups and blocked InstallPlan creation for the RHSSO subscription.
Change the default cifmw_federation_operator_namespace from openstack-operators to keycloak-operators, and add a task to create that namespace before applying the OLM manifest.