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.
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?
What about the cockpit settings? Any progress?
Rename works fine now. verified in ovirt-engine-4.2.3-0.1.el7.noarch BZ 1567936 should solve cockpit changes.
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.