* Previously, if a cluster had multiple custom resources with the same name, the resource would get selected alphabetically when not fully qualified with the API group. As a result, if you installed both Red Hat’s OpenShift Elasticsearch Operator alongside the OpenShift Elasticsearch Operator, you would see failures when collected data via a must-gather report. The current release fixes this issue by ensuring must-gathers now use the full API group when gathering information about the cluster's custom resources. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1897731[*BZ#1897731*])
Description of problem:
In case there is a duplicate CR of the same name, it gets selected alphabetically when not fully qualified.
-- Gather Elasticsearch CR
Error from server (NotFound): elasticsearches.elasticsearch.k8s.elastic.co "elasticsearch" not found
-- Gather Kibana CR
Error from server (NotFound): kibanas.kibana.k8s.elastic.co "kibana" not found
./must-gather/collection-scripts/gather_install_resources:oc get -n ${NAMESPACE} subscription -o yaml > "$install_folder/subscription"
./must-gather/collection-scripts/gather_install_resources:oc get -n ${NAMESPACE} installplan -o yaml > "$install_folder/install_plan"
./must-gather/collection-scripts/gather_logstore_resources: oc get -n $NAMESPACE elasticsearch elasticsearch -o yaml > $es_folder/cr
./must-gather/collection-scripts/gather_visualization_resources: oc get -n ${NAMESPACE} kibana -o yaml > $kibana_folder/cr
Version-Release number of selected component (if applicable):
master
How reproducible:
100%
Steps to Reproduce:
1. Install logging and the elastic operator
2.
3.
Actual results:
m-g fails to collect the CR
Expected results:
collects the CR
Additional info:
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 (Errata Advisory for Openshift Logging 5.0.0), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:0652
Description of problem: In case there is a duplicate CR of the same name, it gets selected alphabetically when not fully qualified. -- Gather Elasticsearch CR Error from server (NotFound): elasticsearches.elasticsearch.k8s.elastic.co "elasticsearch" not found -- Gather Kibana CR Error from server (NotFound): kibanas.kibana.k8s.elastic.co "kibana" not found ./must-gather/collection-scripts/gather_install_resources:oc get -n ${NAMESPACE} subscription -o yaml > "$install_folder/subscription" ./must-gather/collection-scripts/gather_install_resources:oc get -n ${NAMESPACE} installplan -o yaml > "$install_folder/install_plan" ./must-gather/collection-scripts/gather_logstore_resources: oc get -n $NAMESPACE elasticsearch elasticsearch -o yaml > $es_folder/cr ./must-gather/collection-scripts/gather_visualization_resources: oc get -n ${NAMESPACE} kibana -o yaml > $kibana_folder/cr Version-Release number of selected component (if applicable): master How reproducible: 100% Steps to Reproduce: 1. Install logging and the elastic operator 2. 3. Actual results: m-g fails to collect the CR Expected results: collects the CR Additional info: