Bug 1812912
Summary: | In IPv6 bare metal deployment elasticsearch binds on IPv4 loopback address instead of the cluster IPv6 address | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jeff Cantrill <jcantril> | |
Component: | Logging | Assignee: | Jeff Cantrill <jcantril> | |
Status: | CLOSED ERRATA | QA Contact: | Raviv Bar-Tal <rbartal> | |
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 4.4 | CC: | anli, aos-bugs, augol, periklis, rbartal, smiron | |
Target Milestone: | --- | Keywords: | TestBlocker | |
Target Release: | 4.5.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | No Doc Update | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | 1811867 | |||
: | 1812913 (view as bug list) | Environment: | ||
Last Closed: | 2020-08-04 18:05:06 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1811867 | |||
Bug Blocks: | 1771572, 1812913 |
Description
Jeff Cantrill
2020-03-12 13:51:44 UTC
I'm getting this error when trying to follow the deployment cluster-logging procedure, in OCP 4.5 disconnected env: $ oc create -f clo-instance.yaml error: unable to recognize "clo-instance.yaml": no matches for kind "ClusterLogging" in version "logging.openshift.io/v1" Also, there are no operators installed when running: $ oc get csv --all-namespaces NAMESPACE NAME DISPLAY VERSION REPLACES PHASE ---------- -------- -------- -------- -------- ------ openshift-operator-lifecycle-manager packageserver Package Server 0.14.2 Succeeded Might you be running into [1]? The fact that you don't have this type means there is no CRD so the operator installation must have failed. I don't see how this failure relates to this specific BZ unless you are attempting to verify IPV6 for 4.5 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1817592https://bugzilla.redhat.com/show_bug.cgi?id=1817592 Verified on 4.5. Already on project "openshift-logging" on server "https://api.ocp-edge08-0.qe.lab.redhat.com:6443". + echo '-->1. check Elasticsearch Cluster Status --< ' -->1. check Elasticsearch Cluster Status --< + oc exec -c elasticsearch elasticsearch-cdm-2cegfoxd-1-6667b86ffc-2ggcp -- es_cluster_health { "cluster_name" : "elasticsearch", "status" : "green", "timed_out" : false, "number_of_nodes" : 3, "number_of_data_nodes" : 3, "active_primary_shards" : 2, "active_shards" : 4, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 0, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 0, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 0, "active_shards_percent_as_number" : 100.0 } + echo '-->2. List Shards status' -->2. List Shards status + es_run _cat/shards + es_run_util _cat/shards + oc exec -c elasticsearch elasticsearch-cdm-2cegfoxd-1-6667b86ffc-2ggcp -- es_util --query=_cat/shards .kibana_1 0 r STARTED 0 230b fd01::1:f42c:a6ff:fe00:9b elasticsearch-cdm-2cegfoxd-2 .kibana_1 0 p STARTED 0 230b fd01::3:f42c:a6ff:fe00:9c elasticsearch-cdm-2cegfoxd-3 .security 0 p STARTED 5 30.5kb fd01::1:f42c:a6ff:fe00:9b elasticsearch-cdm-2cegfoxd-2 .security 0 r STARTED 5 30.5kb fd01::2:f42c:a6ff:fe00:83 elasticsearch-cdm-2cegfoxd-1 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 (OpenShift Container Platform 4.5 image release 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. https://access.redhat.com/errata/RHBA-2020:2409 |