Red Hat Bugzilla – Bug 865628
ovirt landing page links break when hostname changes
Last modified: 2015-02-01 18:28:28 EST
Description of problem:
I installed Ovirt onto an EBS backed EC2 node. Got it all setup, logged in everything was great. I then stopped the instance and left it down for a couple of weeks.
I came back and started the instance up again (this gave the node a new public DNS entry). Since it had been a couple of weeks I had forgotten what context root and port I should go to get the admin UI (that URL is also not mentioned here: http://www.ovirt.org/get-ovirt/), so I just hit port 80 and the root context. Everything worked great, I got the landing page...
Welcome to Open Virtualization Manager.
Now here is the problem. I click on the Administrator Portal link, it sits for a while spinning then I get a 404. It turns out (after an annoying amount of investigation) that the link is using the *old* public DNS entry that was correct when I first installed ovirt but is now no longer correct. I'm sure this is the entry I typed when installing ovirt, so you could just blame this on user error, but it still leaves a bad impression in this common usage scenario: the main landing page loads fine, but its links are broken. Perhaps the solution is just to use relative links on that main landing page?
Version-Release number of selected component (if applicable):
oVirt Engine Version: 3.1.0-2.fc17
juan - any thoughts on this one?
If you try one of the latest builds you will see that that file is no longer used, and that the links are relative.
However, this is not the only problem you will find when changing the host name. Expect other harder to solve issues, like invalid certificates.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.