Description of problem:
The clusterlogging operator couldn't be find after installed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install clusterlogging from operator hub using global-operators group
2. Check the clusterlogging in the installed Operators
3. check pod under openshift-operators namespaces
2. The clusterlogging operator can't be found.
3. There isn't any pod under
The clusterlogging operator are installed in openshift-operators namespace
This bug needs more info on your side. Please check for a subscription, csv, installplan, or any OLM resources created and their status.
Requesting more info. See previous comment.
The CSV couldn't be created.
$ oc get csv --all-namespaces
NAMESPACE NAME DISPLAY VERSION REPLACES PHASE
openshift-operator-lifecycle-manager packageserver.v0.8.1 Package Server 0.8.1 Succeeded
$ oc get subscription --all-namespaces
NAMESPACE NAME PACKAGE SOURCE CHANNEL
openshift-operator-lifecycle-manager packageserver packageserver olm-operators alpha
openshift-operators cluster-logging cluster-logging installed-community-global-operators preview
$ oc get installplan --all-namespaces
NAMESPACE NAME CSV SOURCE APPROVAL APPROVED
openshift-operator-lifecycle-manager install-rkvj7 packageserver.v0.8.1 Automatic true
openshift-operators install-5sc2z clusterlogging.v0.0.1 Automatic true
Created attachment 1535989 [details]
The pod logs in openshift-marketplace
So the pod logs are for the catalog. It looks like an installplan was generated for the cluster-logging subscription which means that there (probably) wasn't an issue resolving the CSV or its dependencies. I need the pod logs from olm-operator and catalog-operator in openshift-operator-lifecycle-manager as well as the status of the installplan generated for clusterlogging in openshift-operators.
Created attachment 1536465 [details]
CLM pod logs and install plan
catalog-operator pod log
olm-operator pod log
We've resolves some issues on the OLM side that should allow CLO to install now. Please try again with the latest release.
@Evan, The logging can be deployed now. Could you move to on_qa?
Verified in 4.0.0-0.nightly-2019-02-25-194625, the CLO and EO can be deployed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.