Bug 1686069

Summary: After successfully deploying metrics-store Kibana and Elasticsearch have no external IPs
Product: [oVirt] ovirt-engine-metrics Reporter: Ivana Saranova <isaranov>
Component: GenericAssignee: Shirly Radco <sradco>
Status: CLOSED CURRENTRELEASE QA Contact: Ivana Saranova <isaranov>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: bugs, lleistne
Target Milestone: ovirt-4.3.3Flags: sradco: ovirt-4.3?
lleistne: testing_ack+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-16 13:58:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Metrics RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1631193    

Description Ivana Saranova 2019-03-06 16:19:23 UTC
Description of problem:
When installing metrics-store according to README in this patch: https://gerrit.ovirt.org/#/c/97643/ 
In services Kibana and Elasticsearch don't have external IPs.

Version-Release number of selected component (if applicable):
ovirt-engine-metrics-1.2.1-0.0.master.20190305121733.el7.noarch
ovirt-engine-4.2.8.3-0.1.el7ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install metrics-store
2. See services: oc get svc
3. Check if they have external IPs

Actual results:
[root@master0 ~]# oc get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE logging-es ClusterIP 172.30.146.56 <none> 9200/TCP 4m logging-es-cluster ClusterIP None <none> 9300/TCP 4m logging-es-prometheus ClusterIP 172.30.60.177 <none> 443/TCP 4m logging-kibana ClusterIP 172.30.17.199 <none> 443/TCP 4m logging-mux ClusterIP 172.30.119.204 mux_ip 24284/TCP 3m

Expected results:
Elasticsearch and Kibana have external IPs

Additional info:

Comment 2 Ivana Saranova 2019-04-04 09:25:11 UTC
Steps to Reproduce:
1. Install metrics-store
2. See services: oc get svc
3. Check if they have external IPs

Results:
Kibana doesn't have external IP, but according to Shirly, this is supported and already removed from the documentation (https://bugzilla.redhat.com/show_bug.cgi?id=1695100), Elasticsearch service has an external IP.

Verified in: 
ovirt-engine-4.2.8.5-0.1.el7ev.noarch
ovirt-engine-metrics-1.2.1.3-1.el7ev.noarch

Also verified in:
ovirt-engine-4.3.3.1-0.1.el7.noarch
ovirt-engine-metrics-1.2.1.3-1.el7ev.noarch

Comment 3 Sandro Bonazzola 2019-04-16 13:58:26 UTC
This bugzilla is included in oVirt 4.3.3 release, published on April 16th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.