Bug 1519194

Summary: ovirt-engine-rename should change ImageProxyAddress if hosted on same host as engine
Product: [oVirt] ovirt-engine Reporter: Jiri Belka <jbelka>
Component: Tools.RenameAssignee: Gal Zaidman <gzaidman>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: medium Docs Contact:
Priority: medium    
Version: arachman, bugs, fgarciad, gzaidman, lsvaty, pmatyas
Target Milestone: ovirt-4.3.1Flags: rule-engine: ovirt-4.3+
lsvaty: testing_ack+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: v1.5.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-13 16:39:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jiri Belka 2017-11-30 11:13:45 UTC
Description of problem:

When IP/FQDN of engine is changed we use ovirt-engine-rename. But it does not change ImageProxyAddress even it is hosted on same engine host:

# select * from vdc_options where option_name ilike 'Image%' and option_value like '%example.com%';
 option_id |    option_name    |                  option_value                   | version 
       439 | ImageProxyAddress | 10-37-138-187.example.com:54323 | general
(1 row)

This still points to old IP.

# grep FQDN /etc/ovirt-engine/engine.conf.d/10-setup-protocols.conf

rename tool or setup (??) should check if imageio-proxy is on same host as engine and if so, something should change ImageProxyAddress in engine's DB to same fqdn as engine's one.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. engine with imageio-proxy on same host (default setup anyway)
2. change fqdn of the host
3. ovirt-engine-rename + engine-setup

Actual results:
check ImageProxyAddress in the engine db

Expected results:
ImageProxyAddress has old value

Additional info:

Comment 1 Sandro Bonazzola 2019-01-16 09:21:52 UTC
Gal, can you please check what's missing for closing this?

Comment 2 Petr Matyáš 2019-03-07 15:36:19 UTC
Verified on ovirt-engine-4.3.0-0.4.master.20190102130922.gitef7445b.el7.noarch

Comment 3 Sandro Bonazzola 2019-03-13 16:39:28 UTC
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

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