Don't create any additional OperatorGroup during installation of OpenShift Logging in ROSA
Environment
- Red Hat OpenShift Service on AWS
- 4.x
- OpenShift Logging
Issue
- Even though you've done all procedures according to our docs, Installing the logging subsystem for Red Hat OpenShift, the OpenShift Logging could not be deployed in ROSA.
Resolution
- Please don't create any additional OperatorGroup during installation of OpenShift Logging in ROSA. Because the openshift-logging namespace was created in adavance, and the OperatorGroup was also created as "openshift-logging" name there.
- An install plan considers an Operator group invalid in the following scenarios, refer Troubleshooting Operator groups - Membership for more details.
* No Operator groups exist in the install plan’s namespace.
* Multiple Operator groups exist in the install plan’s namespace.
* An incorrect or non-existent service account name is specified in the Operator group.
Root Cause
- A step about creating OperatorGroup for openshift-logging namespace in our docs can cause an initial installation failure in ROSA case.
Diagnostic Steps
- Please check if there is any existing OperatorGroup in openshift-logging as follows. And if there are TWO operatorgroup, please remove one you added, then reinstall the OpenShift Logging.
$ oc get operatorgroup -n openshift-logging
NAME AGE
openshift-logging 18d
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments