Re: Unable to log into Administration Portal
Zachary, The version lock is used by oVirt devs to prevent the system to update too far ahead of the oVirt level. Don't remove that next time. You should access the engine only by https://FQDN .IP should not be used. If you have some kind of snapshot (for example gluster) - you can consider reverting. Even consider restore from backup. I'm pretty sure that almost every failiure is recorded somewhere there ... (I am still new to advise location). Bet Regards, Strahil Nikolov On Jun 23, 2019 04:41, zachary.winter@witsconsult.com wrote:
I suppose I just keep striking out on recent oVirt updates. Today (22 June 2019, all previous updates have been installed successfully) I saw that an update was available for my Enterprise Linux Host (main oVirt engine, CentOS 7 x64), and I attempted to update it. The update failed, which had never happened before. I logged in via SSH and saw that the updates had been halted due to "yum versionlock." I cleared versionlock and proceeded with the update, which appeared to work successfully. I rebooted the system, which came up a-ok. However, I can no longer reach the Administration Portal page. The browser only hangs. I see the following:
- type in the IP address to the server and get the https://<ip address>/ovirt-engine/sso/oauth/authorize page, which tells me:
"The FQDN used to access the system is not a valid engine FQDN. You must access the system using the engine FQDN or one of the engine alternate FQDNs. Click here to continue."
When I click the provided link, I get the same hanging behavior and it never loads the login page.
- I was able to connect via Cockpit to https://<IP Address>:9090 and log in successfully as root after SSH'ing in and restarting the engine. There are no major issues displayed, and I was able to create a Diagnostic Report. Under Hostname > oVirt Machines, it will actually redirect me to the login page at https://fqdn/ovirt-engine/sso/login.html. The page will actually load after the redirect, but when I enter my admin@internal credentials it just hangs and spins.
When I return to "Virtual Machines" in Cockpit, I have Host/Cluster/Templates/VDSM options, I see "oVirt login in progress" with a continually spinning circle, never actually able to authenticate.
In /var/log/ovirt-engine/ui.log, I see:
2019-06-22 19:08:02,533-04 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-4) [] Permutation name: C92E6928986552EDD0E1C99CDC0CC8AB 2019-06-22 19:08:02,533-04 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-4) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read property 'kh' of null at org.ovirt.engine.ui.uicommonweb.dataprovider.AsyncDataProvider.$lambda$4(AsyncDataProvider.java:387) at org.ovirt.engine.ui.uicommonweb.dataprovider.AsyncDataProvider$lambda$4$Type.executed(AsyncDataProvider.java:387) at org.ovirt.engine.ui.frontend.Frontend$2.$onFailure(Frontend.java:329) [frontend.jar:] at org.ovirt.engine.ui.frontend.Frontend$2.onFailure(Frontend.java:329) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.$onFailure(OperationProcessor.java:184) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.onFailure(OperationProcessor.java:184) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider.$handleMultipleQueriesFailure(GWTRPCCommunicationProvider.java:305) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.onFailure(GWTRPCCommunicationProvider.java:263) [frontend.jar:] at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:198) [gwt-servlet.jar:] at com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:233) [gwt-servlet.jar:] at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409) [gwt-servlet.jar:] at Unknown.eval(webadmin-0.js) at com.google.gwt.core.client.impl.Impl.apply(Impl.java:236) [gwt-servlet.jar:] at com.google.gwt.cor
On Sun, Jun 23, 2019 at 7:51 AM Strahil <hunter86_bg@yahoo.com> wrote:
Zachary,
The version lock is used by oVirt devs to prevent the system to update too far ahead of the oVirt level. Don't remove that next time.
Indeed. The engine is not working well with a database that is not 100% matching it (both schema and actual content). So we have engine-setup that handles upgrades (clears versionlock, updates the database and the packages, versionlocks again). It's not very nice but that's how it goes...
You should access the engine only by https://FQDN .IP should not be used.
If you have some kind of snapshot (for example gluster) - you can consider reverting.
You can also try 'yum history undo $ID' (after 'yum history' and one or more 'yum history info $ID' to find the correct one). That said, in principle the new engine could even have corrupted the database, so even that does not guarantee success.
Even consider restore from backup.
I'm pretty sure that almost every failiure is recorded somewhere there ... (I am still new to advise location).
Perhaps new, but very helpful. Thanks :-) Good luck and best regards,
Bet Regards, Strahil Nikolov On Jun 23, 2019 04:41, zachary.winter@witsconsult.com wrote:
I suppose I just keep striking out on recent oVirt updates. Today (22 June 2019, all previous updates have been installed successfully) I saw that an update was available for my Enterprise Linux Host (main oVirt engine, CentOS 7 x64), and I attempted to update it. The update failed, which had never happened before. I logged in via SSH and saw that the updates had been halted due to "yum versionlock." I cleared versionlock and proceeded with the update, which appeared to work successfully. I rebooted the system, which came up a-ok. However, I can no longer reach the Administration Portal page. The browser only hangs. I see the following:
- type in the IP address to the server and get the https://<ip address>/ovirt-engine/sso/oauth/authorize page, which tells me:
"The FQDN used to access the system is not a valid engine FQDN. You must access the system using the engine FQDN or one of the engine alternate FQDNs. Click here to continue."
When I click the provided link, I get the same hanging behavior and it never loads the login page.
- I was able to connect via Cockpit to https://<IP Address>:9090 and log in successfully as root after SSH'ing in and restarting the engine. There are no major issues displayed, and I was able to create a Diagnostic Report. Under Hostname > oVirt Machines, it will actually redirect me to the login page at https://fqdn/ovirt-engine/sso/login.html. The page will actually load after the redirect, but when I enter my admin@internal credentials it just hangs and spins.
When I return to "Virtual Machines" in Cockpit, I have Host/Cluster/Templates/VDSM options, I see "oVirt login in progress" with a continually spinning circle, never actually able to authenticate.
In /var/log/ovirt-engine/ui.log, I see:
2019-06-22 19:08:02,533-04 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-4) [] Permutation name: C92E6928986552EDD0E1C99CDC0CC8AB 2019-06-22 19:08:02,533-04 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-4) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read property 'kh' of null at org.ovirt.engine.ui.uicommonweb.dataprovider.AsyncDataProvider.$lambda$4(AsyncDataProvider.java:387) at org.ovirt.engine.ui.uicommonweb.dataprovider.AsyncDataProvider$lambda$4$Type.executed(AsyncDataProvider.java:387) at org.ovirt.engine.ui.frontend.Frontend$2.$onFailure(Frontend.java:329) [frontend.jar:] at org.ovirt.engine.ui.frontend.Frontend$2.onFailure(Frontend.java:329) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.$onFailure(OperationProcessor.java:184) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.OperationProcessor$2.onFailure(OperationProcessor.java:184) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider.$handleMultipleQueriesFailure(GWTRPCCommunicationProvider.java:305) [frontend.jar:] at org.ovirt.engine.ui.frontend.communication.GWTRPCCommunicationProvider$5$1.onFailure(GWTRPCCommunicationProvider.java:263) [frontend.jar:] at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:198) [gwt-servlet.jar:] at com.google.gwt.http.client.Request.$fireOnResponseReceived(Request.java:233) [gwt-servlet.jar:] at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:409) [gwt-servlet.jar:] at Unknown.eval(webadmin-0.js) at com.google.gwt.core.client.impl.Impl.apply(Impl.java:236) [gwt-servlet.jar:] at com.google.gwt.cor
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/R5G27V32W5DOZG...
-- Didi
participants (2)
-
Strahil -
Yedidyah Bar David