Bug 1551517 - after renaming engine, logout takes very long time and error with engine's old fqdn appears in log
Summary: after renaming engine, logout takes very long time and error with engine's ol...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 4.2.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.3
: ---
Assignee: Ravi Nori
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-05 10:27 UTC by Lucie Leistnerova
Modified: 2018-05-10 06:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-10 06:34:07 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 89826 0 master MERGED tools : engine rename should update the notification callback 2018-04-17 07:08:17 UTC
oVirt gerrit 90023 0 ovirt-engine-4.2 MERGED tools : engine rename should update the notification callback 2018-04-17 08:00:21 UTC

Description Lucie Leistnerova 2018-03-05 10:27:07 UTC
Description of problem:
I renamed engine with /usr/share/ovirt-engine/setup/bin/ovirt-engine-rename. All seemed ok, engine is running. But log out takes very long time and server.log contains errors with old engine's fqdn.

Version-Release number of selected component (if applicable):
ovirt-engine-tools-4.2.2.1-0.1.el7.noarch
ovirt-engine-4.2.2.1-0.1.el7.noarch

How reproducible: always


Steps to Reproduce:
1. have running engine
2. change its' mac address and get new fqdn from dns server
3. rename engine to new fqdn via
/usr/share/ovirt-engine/setup/bin/ovirt-engine-rename
4. log to webamin portal
5. log out

Actual results: log out takes long time (around 10s), errors in server.log
2018-03-05 10:57:43,892+01 INFO  [org.apache.http.impl.execchain.RetryExec] (default task-1) I/O exception (java.net.NoRouteToHostException) caught when processing request to {s}->https://<old fqdn>:443: No route to host (Host unreachable)
2018-03-05 10:57:43,893+01 INFO  [org.apache.http.impl.execchain.RetryExec] (default task-1) Retrying request to {s}->https://<old fqdn>:443



Expected results: log out is immediate and no error


Additional info:
I found old engine's name in:
/usr/share/ovirt-cockpit-sso/config/cockpit/cockpit.conf:XXUrl = https://<old fqdn>/ovirt-engine/path/to/redirect
/usr/share/ovirt-cockpit-sso/config/cockpit/cockpit.conf:Url = https://<old fqdn>/ovirt-engine/ovirt-engine/
But it doesn't seem that it's the main problem. I changed it there, rebooted the server and the problem is still there.

Configuration in /etc/ovirt* have new fqdn, old is only in backups or example.

Comment 2 Sandro Bonazzola 2018-03-12 08:24:04 UTC
Moving to infra for further investigation since the configuration here seems to be completed for the engine side. Marek, can you check the cockpit-ovirt-sso part and eventually work with didi on a separate bug for fixing it if needed?

Comment 5 Lucie Leistnerova 2018-03-29 06:25:58 UTC
What about the cockpit settings? Any progress?

Comment 8 Lucie Leistnerova 2018-04-19 07:48:19 UTC
Rename works fine now.

verified in ovirt-engine-4.2.3-0.1.el7.noarch

BZ 1567936 should solve cockpit changes.

Comment 9 Sandro Bonazzola 2018-05-10 06:34:07 UTC
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

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


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