Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1545559

Summary:	[RFE] Assign externalIP to the Elasticsearch Service
Product:	[oVirt] ovirt-engine-metrics	Reporter:	Shirly Radco <sradco>
Component:	RFEs	Assignee:	Shirly Radco <sradco>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lukas Svaty <lsvaty>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0.7	CC:	apinnick, bugs, eheftman, lsvaty, lveyde, rmeggins, sradco, ylavi
Target Milestone:	ovirt-4.2.2	Keywords:	FutureFeature
Target Release:	---	Flags:	sradco: ovirt-4.2? rule-engine: planning_ack? rule-engine: devel_ack+ rule-engine: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-metrics-1.1.3.1	Doc Type:	Enhancement
Doc Text:	In this release, the oVirt metrics configuration script automatically assigns an external IP to the Elasticsearch service.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-29 11:18:39 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:	1547123

Description Shirly Radco 2018-02-15 09:48:02 UTC

Description of problem:
Assign an IP Address to the Elasticsearch Service on the metrics store machine, so that we can configure the metrics and logs index curation parameter and make it configurable.

Currently user need to do this manually.

Comment 1 Rich Megginson 2018-02-15 14:59:42 UTC

I don't understand - Elasticsearch already has an IP address?

Comment 2 Shirly Radco 2018-02-18 07:58:38 UTC

This bug sets the "externalIP" for Elasticsearch service.

Comment 3 Lukas Svaty 2018-03-07 14:13:04 UTC

verified in ovirt-engine-metrics-1.1.3.2-1.el7ev.noarch

Comment 4 Sandro Bonazzola 2018-03-29 11:18:39 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.