[ovirt-users] Re: Deployment suddenly fails at engine check
I'm not doing a oVirt update, I'm just deploying a fresh. I just ssh to the engine via the ip in /etc/hosts. And then use the downgrade command after wizard has run upgrade. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/YQMC4MQE56PABXN6VQ7XBPXQ4NKYCWMK/
[ovirt-users] Re: Deployment suddenly fails at engine check
Unfortunately, for a clean install with 4.4.10, the trick downgrading
postgresql-jdbc doesn't seem to work (or I'm missing something.)
Here's the server.log after the engine copied it to the hypervisor host: (I
picked it up when I was trying to login to the web UI, the other restarts
were in there too.)
2022-05-02 15:20:21,205-05 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "enginesso.war")
2022-05-02 15:20:21,234-05 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "root.war")
2022-05-02 15:20:21,235-05 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-6) WFLYSRV0207: Starting subdeployment (runtime-name: "webadmin.war")
2022-05-02 15:20:21,209-05 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-2) WFLYSRV0207: Starting subdeployment (runtime-name: "services.war")
2022-05-02 15:20:21,209-05 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "bll.jar")
2022-05-02 15:20:21,207-05 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "welcome.war")
2022-05-02 15:20:21,206-05 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: "docs.war")
2022-05-02 15:20:22,988-05 INFO [org.wildfly.security] (MSC service thread
1-6) ELY1: WildFly Elytron version 1.15.3.Final
2022-05-02 15:20:23,177-05 INFO [org.jboss.weld.deployer] (MSC service thread
1-5) WFLYWELD0003: Processing weld deployment restapi.war
2022-05-02 15:20:23,558-05 WARN [org.jboss.as.dependency.deprecated] (MSC
service thread 1-3) WFLYSRV0221: Deployment "deployment.engine.ear.bll.jar" is
using a deprecated module ("sun.jdk") which may be removed in future versions
without notice.
2022-05-02 15:20:23,772-05 INFO [org.jboss.weld.deployer] (MSC service thread
1-3) WFLYWELD0003: Processing weld deployment engine.ear
2022-05-02 15:20:24,204-05 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 44) WFLYUT0021: Registered web context:
'/ovirt-engine/apidoc' for server 'default-server'
2022-05-02 15:20:24,208-05 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 43) WFLYUT0021: Registered web context:
'/ovirt-engine/web-ui' for server 'default-server'
2022-05-02 15:20:24,422-05 INFO
[org.hibernate.validator.internal.util.Version] (MSC service thread 1-5)
HV01: Hibernate Validator 6.0.22.Final
2022-05-02 15:20:24,976-05 INFO [org.jboss.weld.deployer] (MSC service thread
1-3) WFLYWELD0003: Processing weld deployment docs.war
2022-05-02 15:20:24,977-05 INFO [org.jboss.weld.deployer] (MSC service thread
1-4) WFLYWELD0003: Processing weld deployment root.war
2022-05-02 15:20:24,985-05 INFO [org.jboss.weld.deployer] (MSC service thread
1-1) WFLYWELD0003: Processing weld deployment welcome.war
2022-05-02 15:20:25,041-05 INFO [org.jboss.weld.deployer] (MSC service thread
1-2) WFLYWELD0003: Processing weld deployment services.war
2022-05-02 15:20:25,080-05 INFO [org.jboss.weld.Version] (MSC service thread
1-5) WELD-000900: 3.1.6 (Final)
2022-05-02 15:20:25,255-05 INFO [org.jboss.weld.deployer] (MSC service thread
1-8) WFLYWELD0003: Processing weld deployment enginesso.war
2022-05-02 15:20:25,256-05 INFO [org.jboss.weld.deployer] (MSC service thread
1-7) WFLYWELD0003: Processing weld deployment webadmin.war
2022-05-02 15:20:25,416-05 INFO [org.jboss.weld.deployer] (MSC service thread
1-6) WFLYWELD0003: Processing weld deployment bll.jar
2022-05-02 15:20:25,427-05 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'LockManager' in
deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as
follows:
java:global/engine/bll/LockManager!org.ovirt.engine.core.utils.lock.LockManager
java:app/bll/LockManager!org.ovirt.engine.core.utils.lock.LockManager
java:module/LockManager!org.ovirt.engine.core.utils.lock.LockManager
java:global/engine/bll/LockManager
java:app/bll/LockManager
java:module/LockManager
2022-05-02 15:20:25,428-05 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-6) WFLYEJB0473: JNDI bindings for session bean named 'Backend' in
deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as
follows:
java:global/engine/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler
java:app/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler
java:module/Backend!org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler
java:global/engine/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal
java:app/bll/Backend!org.ovirt.engine.core.bll.interfaces.BackendInternal
[ovirt-users] Re: Deployment suddenly fails at engine check
Harry O, Are you updating 4.4 to 4.5? I just tried clean installing 4.4.10 again using the same instructions, and it broke down (see my next msg about the wildfly startup). It didn't matter if I downgraded early (just after the VM started) or late (as soon as it was waiting for the health check URL.). I didn't try 4.5 (because I had 4.4 working before), that's next. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RLETXM3NRKZ5443VSV3QMK4PXRVCSJSP/
[ovirt-users] Re: Deployment suddenly fails at engine check
Martin, I ran into this same issue, and tried to prevent the postgresql-jdbc upgrade by jumping into the local VM as soon as it would respond to ssh and putting a exclude=postgresql-jdbc in /etc/dnf/dnf.conf. (basically, don't let it upgrade postgresql-jdbc past the instal The installation finished successfully with the health check url passing, but once the engine is online, I'm seeing different issues during what looks like page loads (after trying to login to the admin portal) Is there a point before that initial wildfly load that it *needs* the 4.2.14 version? The engine appears to load, but after I go to the portal, and attempt to login, the page hangs like it's trying to retrieve info from various APIs. I'm worried I redirected the process too early and should have allowed it to upgrade ===ddd Here are the most recent errors that appear just after 'restart ovirt-engine', and trying to login to the ui. ... 2022-05-02 11:29:11,765-05 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 23.0.2.Final (WildFly Core 15.0.1.Final) started in 41377ms - Started 1674 of 1888 services (393 services are lazy, passive or on-demand) 2022-05-02 11:29:11,768-05 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2022-05-02 11:29:11,768-05 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 2022-05-02 11:29:51,723-05 WARNING [javax.persistence.spi] (default task-2) javax.persistence.spi::No valid providers found. 2022-05-02 11:29:52,055-05 WARN [org.jboss.as.weld] (default task-2) WFLYWELD0052: Using deployment classloader to load proxy classes for module org.ovirt.engine.core.utils. Package-private access will not work. To fix this the module sh ould declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi, org.jboss.weld.api] 2022-05-02 11:29:52,321-05 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-2) RESTEASY002010: Failed to execute: javax.ws.rs.WebApplicationException: HTTP 404 Not Found at org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BaseBackendResource.handleError(BaseBackendResource.java:236) at org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BackendResource.getEntity(BackendResource.java:119) at org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BackendResource.getEntity(BackendResource.java:99) at org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.AbstractBackendSubResource.performGet(AbstractBackendSubResource.java:34) at org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.AbstractBackendSubResource.performGet(AbstractBackendSubResource.java:30) at org.ovirt.engine.api.restapi-jaxrs//org.ovirt.engine.api.restapi.resource.BackendVmResource.get(BackendVmResource.java:124) at org.ovirt.engine.api.restapi-definition//org.ovirt.engine.api.resource.VmResource.doGet(VmResource.java:208) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jboss.resteasy.resteasy-jaxrs@3.15.1.Final//org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:138) at org.jboss.resteasy.resteasy-jaxrs@3.15.1.Final//org.jboss.resteasy.core.ResourceMethodInvoker.internalInvokeOnTarget(ResourceMethodInvoker.java:546) at org.jboss.resteasy.resteasy-jaxrs@3.15.1.Final//org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTargetAfterFilter(ResourceMethodInvoker.java:435) at org.jboss.resteasy.resteasy-jaxrs@3.15.1.Final//org.jboss.resteasy.core.ResourceMethodInvoker.lambda$invokeOnTarget$0(ResourceMethodInvoker.java:396) at org.jboss.resteasy.resteasy-jaxrs@3.15.1.Final//org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:358) at org.jboss.resteasy.resteasy-jaxrs@3.15.1.Final//org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:398) at org.jboss.resteasy.resteasy-jaxrs@3.15.1.Final//org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:365) at org.jboss.resteasy.resteasy-jaxrs@3.15.1.Final//org.jboss.resteasy.core.ResourceLocatorInvoker.invokeOnTargetObject(ResourceLocatorInvoker.java:150) at org.jboss.resteasy.resteasy-jaxrs@3.15.1.Final//org.jboss.resteasy.core.ResourceLocatorInvoker.invoke(ResourceLocatorInvoker.java:110) at
[ovirt-users] Re: Deployment suddenly fails at engine check
When I time the postgresql-jdbc downgrade right with the engine deployment, it runs perfect - thanks again. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/AF6HKJP2E23KVBN7WDUN3QN5QGZC46WF/
[ovirt-users] Re: Deployment suddenly fails at engine check
Hi Martin, Thanks for your reply, Here is some output from the process: [root@hej ~]# dnf downgrade postgresql-jdbc Last metadata expiration check: 0:37:09 ago on Sat 30 Apr 2022 09:42:39 AM CEST. Dependencies resolved. === Package Architecture Version Repository Size === Downgrading: postgresql-jdbc noarch 42.2.3-3.el8_2 appstream 710 k Transaction Summary === Downgrade 1 Package Total download size: 710 k Is this ok [y/N]: y Downloading Packages: postgresql-jdbc-42.2.3-3.el8_2.noarch.rpm 795 kB/s | 710 kB 00:00 --- Total 710 kB/s | 710 kB 00:00 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing: 1/1 Downgrading : postgresql-jdbc-42.2.3-3.el8_2.noarch 1/2 Cleanup : postgresql-jdbc-42.2.14-1.el8.noarch 2/2 Verifying: postgresql-jdbc-42.2.3-3.el8_2.noarch 1/2 Verifying: postgresql-jdbc-42.2.14-1.el8.noarch 2/2 Downgraded: postgresql-jdbc-42.2.3-3.el8_2.noarch Complete! [root@hej ~]# systemctl restart ovirt-engine [root@hej ~]# [root@hej ~]# curl http://127.0.0.1:8706/management Error401 - Unauthorized[root@hej ~]# [root@hej ~]# [root@hej ~]# curl http://127.0.0.1:8706 [root@hej ~]# [root@hej ~]# systemctl status ovirt-engine ● ovirt-engine.service - oVirt Engine Loaded: loaded (/usr/lib/systemd/system/ovirt-engine.service; enabled; vendor preset: disabled) Active: active (running) since
[ovirt-users] Re: Deployment suddenly fails at engine check
Hi,
Could you please check if you are not hit by the new postgresql-jdbc
package issue?
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SBCWNXLFLJBKTA3TFJARE7QCYZQ6QMMH/
Thanks,
Martin
On Fri, Apr 22, 2022 at 7:38 PM Harry O wrote:
> Hi,
> After the new update, my deployment fails at engine check.
> What can I do to debug?
>
> [ INFO ] skipping: [localhost]
> [ INFO ] TASK [ovirt.ovirt.engine_setup : Check if Engine health page is
> up]
> [ ERROR ] fatal: [localhost -> 192.168.222.12]: FAILED! => {"attempts":
> 30, "changed": false, "connection": "close", "content":
> "Error500 - Internal Server
> Error", "content_encoding": "identity", "content_length":
> "86", "content_type": "text/html; charset=UTF-8", "date": "Fri, 22 Apr 2022
> 16:02:04 GMT", "elapsed": 0, "msg": "Status code was 500 and not [200]:
> HTTP Error 500: Internal Server Error", "redirected": false, "server":
> "Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1 mod_wsgi/4.6.4
> Python/3.6", "status": 500, "url": "
> http://localhost/ovirt-engine/services/health"}
> [ INFO ] TASK [ovirt.ovirt.engine_setup : Clean temporary files]
> [ INFO ] changed: [localhost -> 192.168.222.12]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Sync on engine machine]
> [ INFO ] changed: [localhost -> 192.168.222.12]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set destination directory
> path]
> [ INFO ] ok: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Create destination
> directory]
> [ INFO ] changed: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : include_tasks]
> [ INFO ] ok: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Find the local appliance
> image]
> [ INFO ] ok: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Set local_vm_disk_path]
> [ INFO ] ok: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Give the vm time to flush
> dirty buffers]
> [ INFO ] ok: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Copy engine logs]
> [ INFO ] changed: [localhost]
> [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Notify the user about a
> failure]
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "There
> was a failure deploying the engine on the local engine VM. The system may
> not be provisioned according to the playbook results: please check the logs
> for the issue, fix accordingly or re-deploy from scratch.\n"}
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/MDMO5CPVXFBXJPQYIL3FFNB4FVNSCLYJ/
>
--
Martin Perina
Manager, Software Engineering
Red Hat Czech s.r.o.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2DFJKFRTU2DXOXDBUM32KLQJEXGQQ6EZ/
