Bug 1449561 - [RFE] allow changing the gateway IP hosted-engine-ha checks use
Summary: [RFE] allow changing the gateway IP hosted-engine-ha checks use
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-hosted-engine-ha
Classification: oVirt
Component: RFEs
Version: 2.1.0.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.3.0
: ---
Assignee: Martin Sivák
QA Contact: Nikolai Sednev
URL:
Whiteboard:
Depends On: 1457357
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-10 09:22 UTC by Evgheni Dereveanchin
Modified: 2019-02-13 07:45 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-02-13 07:45:11 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-4.3?
mavital: testing_plan_complete?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)

Description Evgheni Dereveanchin 2017-05-10 09:22:25 UTC
Description of problem:

Hosted Engine HA utilizes a user-supplied router IP to check for network connectivity. There is no tooling to change this IP after installation which may be needed due to network reorganization or hardware replacement.

This RFE is to add support for changing the router IP on existing HE hosts as well as on the storage domain so that new hosts are configured properly. The router IP must be up to date since network connectivity has the highest weight in host score calculation.

Comment 1 Evgheni Dereveanchin 2017-05-10 10:39:10 UTC
Also, what would be the current manual process of changing the router IP?
Is it enough to edit /etc/ovirt-hosted-engine/hosted-engine.conf on hosts one by one and reboot them?

Comment 2 Doron Fediuck 2017-05-11 08:43:45 UTC
Jenny,
is this supported using the HE config utility?

Comment 3 Martin Sivák 2017-05-11 08:51:24 UTC
Actually the gateway address is host specific and is changeable manually in /etc/ovirt-hosted-engine/hosted-engine.conf.

Comment 4 Martin Sivák 2017-05-11 09:35:25 UTC
Lets use this bug to track an RFE of puting the gateway IP to the shared configuration.

Comment 5 Red Hat Bugzilla Rules Engine 2017-08-21 10:47:24 UTC
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 6 Yaniv Kaul 2018-02-28 16:37:31 UTC
(In reply to Martin Sivák from comment #4)
> Lets use this bug to track an RFE of puting the gateway IP to the shared
> configuration.

Or having an Ansible role to configure it locally across all hosts... (I wonder if ovirt hosts facts have the information who is a HE host...).

(BTW, if we move to DNS queries, we'll still need this - which address you are trying to resolve?)

Comment 7 Martin Sivák 2018-02-28 16:58:48 UTC
We know the hosts addresses from the metadata, but we do not have the credentials to ssh there. So ansible is out of the question unless the engine is up (it knows the hosts and it has ssh keys).

Comment 8 Martin Sivák 2018-04-18 13:45:58 UTC
This has been implemented in 4.2.2 as part of https://bugzilla.redhat.com/show_bug.cgi?id=1543988

Comment 9 Nikolai Sednev 2018-08-14 16:12:54 UTC
In short, I've got some explanations from Martin, this RFE is all about changing the pingable IP address from existing to another, by default pingable IP address that was set during deployment taken from default gateway, but it is not mandatory to be it, it can be any external pingable IP address.
 
Please provide me with documentation on how should "pingable" IP address be changed in order to verify this RFE.

# hosted-engine --set-shared-config --help
Usage: /usr/sbin/hosted-engine --set-shared-config key value [--type=<type>]
    Set shared storage configuration.
    Valid types are: he_local, he_shared, ha, broker.
    Available only after deployment has completed.

    New values for he_shared (hosted-engine.conf source on the shared storage)
    will be used by all hosts (re)deployed after the configuration change.
    Currently running hosts will still use the old values.
    New values for he_local will be set in the local instance of
    he configuration file on the local host.
[root@alma03 ~]# hosted-engine --set-shared-config --type=he_shared
You must specify a new value to set
[root@alma03 ~]# hosted-engine --set-shared-config --type=he_shared xx

Comment 10 Simone Tiraboschi 2018-12-06 09:20:02 UTC
Moving to ON_QA according to https://bugzilla.redhat.com/show_bug.cgi?id=1449561#c8

Comment 11 Nikolai Sednev 2018-12-13 17:09:39 UTC
Works for me on HE environment, which was deployed on FC storage domain.

puma18 ~]# hosted-engine --set-shared-config --help
Usage: /usr/sbin/hosted-engine --set-shared-config key value [--type=<type>]
    Set shared storage configuration.
    Valid types are: he_local, he_shared, ha, broker.
    Available only after deployment has completed.

    New values for he_shared (hosted-engine.conf source on the shared storage)
    will be used by all hosts (re)deployed after the configuration change.
    Currently running hosts will still use the old values.
    New values for he_local will be set in the local instance of
    he configuration file on the local host.
[root@puma18 ~]# hosted-engine --get-shared-config --help
Usage: /usr/sbin/hosted-engine --get-shared-config key [--type=<type>]
    Get shared storage configuration.
    Valid types are: he_local, he_shared, ha, broker.
    Available only after deployment has completed.

puma18 ~]# hosted-engine --get-shared-config gateway  --type=he_shared
gateway : 10.35.163.254, type : he_shared

puma18 ~]# hosted-engine --get-shared-config gateway  --type=he_local
gateway : 10.35.163.254, type : he_local

puma18 ~]# hosted-engine --set-shared-config gateway 8.8.8.8  --type=he_shared
[root@puma18 ~]# hosted-engine --get-shared-config gateway  --type=he_shared
gateway : 8.8.8.8, type : he_shared

puma18 ~]# hosted-engine --get-shared-config gateway  --type=he_local
gateway : 10.35.163.254, type : he_local

Tested on:
ovirt-hosted-engine-ha-2.3.0-0.2.master.20181212075523.gitde89e03.el7.noarch
ovirt-hosted-engine-setup-2.3.0-0.2.master.20181211213852.git82b1918.el7.noarch
ovirt-engine-appliance-4.3-20181211.1.el7.noarch
Linux 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 15 17:36:42 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.6 (Maipo)

Comment 12 Sandro Bonazzola 2019-02-13 07:45:11 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

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


Note You need to log in before you can comment on or make changes to this bug.