[ovirt-users] Re: upgrade ovirt-engine 4.3 to 4.4. engine.ear problems?
Hi,
I can confirm that this was the postgresql-jdbc issue.
After doing a downgrade, I succeeded to continue the installation.
All my oVirt nodes are upgraded, VM’s, Cluster and Datacenter as well.
The reason for not upgrading directly to 4.5, was that it was not GA when we
started.
I will let it run for a moment before going to 4.5
Thanks for a quick response.
Regards, Ingvar
On 27 Apr 2022, at 18:20, Martin Perina
mailto:mper...@redhat.com>> wrote:
On Wed, Apr 27, 2022 at 8:52 AM Yedidyah Bar David
mailto:d...@redhat.com>> wrote:
On Wed, Apr 27, 2022 at 9:31 AM Martin Perina
mailto:mper...@redhat.com>> wrote:
>
> Hi Ingvar,
> according to the logs your 4.4 installation doesn't work because you hit
> postgresql-jdbc issue:
>
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SBCWNXLFLJBKTA3TFJARE7QCYZQ6QMMH/
Thanks, Martin. Can you please clarify how you understand this, and
more importantly, add relevant possible errors/warnings/whatever to
the bug, so that people will find it when searching for them? Thanks.
It was just a guess from below error:
2022-04-26 13:52:42,220+02 ERROR [org.jboss.msc.service.fail] (ServerService
Thread Pool -- 51) MSC01: Failed to start service
jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START:
org.jboss.msc.service.StartException in service
jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START:
java.lang.IllegalStateException: WFLYEE0042: Failed to construct component
instance
2022-04-26 13:52:42,231+02 ERROR [org.jboss.as.controller.management-operation]
(Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address:
([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0080: Failed
services" => {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar
and a fact that they tried to upgrade to 4.4 now when there is this
postgresql-jdbc issue.
Also, while we are working on fixing this, perhaps we can temporarily
make the engine require an older version?
E.g.: https://github.com/oVirt/ovirt-engine/pull/316
Didn't test it.
We are still investigating the issue, once we have a complete picture we will
address it
Best regards,
--
Didi
--
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/F2NCRAKZFMU4HIVV4UHGZKAK2YOUT54W/
[ovirt-users] Re: upgrade ovirt-engine 4.3 to 4.4. engine.ear problems?
On Wed, Apr 27, 2022 at 8:52 AM Yedidyah Bar David wrote:
> On Wed, Apr 27, 2022 at 9:31 AM Martin Perina wrote:
> >
> > Hi Ingvar,
> > according to the logs your 4.4 installation doesn't work because you hit
> postgresql-jdbc issue:
> >
> >
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/SBCWNXLFLJBKTA3TFJARE7QCYZQ6QMMH/
>
> Thanks, Martin. Can you please clarify how you understand this, and
> more importantly, add relevant possible errors/warnings/whatever to
> the bug, so that people will find it when searching for them? Thanks.
>
It was just a guess from below error:
2022-04-26 13:52:42,220+02 ERROR [org.jboss.msc.service.fail]
(ServerService Thread Pool -- 51) MSC01: Failed to start service
jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START:
org.jboss.msc.service.StartException in service
jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START:
java.lang.IllegalStateException: WFLYEE0042: Failed to construct component
instance
2022-04-26 13:52:42,231+02 ERROR
[org.jboss.as.controller.management-operation] (Controller Boot Thread)
WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
"engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" =>
{"jboss.deployment.subunit.\"engine.ear\".\"bll.jar
and a fact that they tried to upgrade to 4.4 now when there is this
postgresql-jdbc issue.
>
> Also, while we are working on fixing this, perhaps we can temporarily
> make the engine require an older version?
>
> E.g.: https://github.com/oVirt/ovirt-engine/pull/316
>
> Didn't test it.
>
We are still investigating the issue, once we have a complete picture we
will address it
> Best regards,
> --
> Didi
>
>
--
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/JYYVGLDCDREJQY7COYFQKQBF2754AB2J/
[ovirt-users] Re: upgrade ovirt-engine 4.3 to 4.4. engine.ear problems?
On Wed, Apr 27, 2022 at 9:31 AM Martin Perina wrote: > > Hi Ingvar, > according to the logs your 4.4 installation doesn't work because you hit > postgresql-jdbc issue: > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/SBCWNXLFLJBKTA3TFJARE7QCYZQ6QMMH/ Thanks, Martin. Can you please clarify how you understand this, and more importantly, add relevant possible errors/warnings/whatever to the bug, so that people will find it when searching for them? Thanks. Also, while we are working on fixing this, perhaps we can temporarily make the engine require an older version? E.g.: https://github.com/oVirt/ovirt-engine/pull/316 Didn't test it. Best regards, -- Didi ___ 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/KJ2E73JTDDNANSPBQO77FJWCQAGGZ5TI/
[ovirt-users] Re: upgrade ovirt-engine 4.3 to 4.4. engine.ear problems?
Hi Ingvar,
according to the logs your 4.4 installation doesn't work because you hit
postgresql-jdbc issue:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/SBCWNXLFLJBKTA3TFJARE7QCYZQ6QMMH/
Regards,
Martin
On Wed, Apr 27, 2022 at 8:09 AM Yedidyah Bar David wrote:
> Hi,
>
> On Wed, Apr 27, 2022 at 8:38 AM ingvar.jungenas--- via Users
> wrote:
> >
> > - having a 4,3 ovirt-engine up and running on centos 7
> > - Create a new engine machine with centos 8 stream, latests updates
> > - installing packages, restoring ovirt-engine backup from previous host
> and running ovirt-setup,
>
> I suppose you mean you used engine-backup for backup/restore.
> Otherwise, please provide more details.
>
> Also, which exact 4.3 version did you have?
>
> > - When started, no access to the admin console at
> > https:///ovirt-engine.
> The web proxy will return: 500 Internal error""
> > - I can access the Grafana login
> >
> > - ovirt-engine.service is started without any systemd errors
> >
> > Any Ideas how to proceed?
> >
> > Log files:
> > /var/log/ovirt-engine/boot.log # No Errors
> > /var/log/ovirt-engine/engine.log # No Errors
> > /var/log/ovirt-engine/server.log# Errors found
> > If I just grep for "ERROR" in server.log
> >
> > 2022-04-26 13:52:42,220+02 ERROR [org.jboss.msc.service.fail]
> (ServerService Thread Pool -- 51) MSC01: Failed to start service
> jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START:
> org.jboss.msc.service.StartException in service
> jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START:
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct component
> instance
> > 2022-04-26 13:52:42,231+02 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
> "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" =>
> {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START"
> => "java.lang.IllegalStateException: WFLYEE0042: Failed to construct
> component instance
> > 2022-04-26 13:52:42,568+02 ERROR [org.jboss.as] (Controller Boot
> Thread) WFLYSRV0026: WildFly Full 23.0.2.Final (WildFly Core 15.0.1.Final)
> started (with errors) in 24096ms - Started 1668 of 1888 services (6
> services failed or missing dependencies, 393 services are lazy, passive or
> on-demand)
> >
> > The complete starting sequence from server.log
> >
> > 2022-04-26 13:52:23,322+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-4) WFLYSRV0027: Starting deployment of "restapi.war"
> (runtime-name: "restapi.war")
> > 2022-04-26 13:52:24,074+02 INFO [org.jboss.as.remoting] (MSC service
> thread 1-2) WFLYRMT0001: Listening on 127.0.0.1:8707
> > 2022-04-26 13:52:24,247+02 INFO
> [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2)
> WFLYJCA0098: Bound non-transactional data source:
> java:/ENGINEDataSourceNoJTA
> > 2022-04-26 13:52:24,901+02 INFO [org.jboss.as.ejb3] (MSC service thread
> 1-4) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
> > 2022-04-26 13:52:25,194+02 INFO
> [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4)
> WFLYJCA0001: Bound data source [java:/ENGINEDataSource]
> > 2022-04-26 13:52:25,195+02 INFO
> [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4)
> WFLYJCA0001: Bound data source [java:/DWHDataSource]
> > 2022-04-26 13:52:25,530+02 INFO [org.wildfly.security] (MSC service
> thread 1-3) ELY1: WildFly Elytron version 1.15.3.Final
> > 2022-04-26 13:52:25,741+02 INFO [org.jboss.weld.deployer] (MSC service
> thread 1-2) WFLYWELD0003: Processing weld deployment restapi.war
> > 2022-04-26 13:52:25,999+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "services.war")
> > 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "root.war")
> > 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "docs.war")
> > 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "welcome.war")
> > 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "bll.jar")
> > 2022-04-26 13:52:26,001+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "enginesso.war")
> > 2022-04-26 13:52:26,001+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "webadmin.war")
> > 2022-04-26 13:52:26,368+02 INFO
> [org.hibernate.validator.internal.util.Version] (MSC service thread
[ovirt-users] Re: upgrade ovirt-engine 4.3 to 4.4. engine.ear problems?
Hi,
On Wed, Apr 27, 2022 at 8:38 AM ingvar.jungenas--- via Users
wrote:
>
> - having a 4,3 ovirt-engine up and running on centos 7
> - Create a new engine machine with centos 8 stream, latests updates
> - installing packages, restoring ovirt-engine backup from previous host and
> running ovirt-setup,
I suppose you mean you used engine-backup for backup/restore.
Otherwise, please provide more details.
Also, which exact 4.3 version did you have?
> - When started, no access to the admin console at
> https:///ovirt-engine. The web proxy will return: 500 Internal error""
> - I can access the Grafana login
>
> - ovirt-engine.service is started without any systemd errors
>
> Any Ideas how to proceed?
>
> Log files:
> /var/log/ovirt-engine/boot.log # No Errors
> /var/log/ovirt-engine/engine.log # No Errors
> /var/log/ovirt-engine/server.log# Errors found
> If I just grep for "ERROR" in server.log
>
> 2022-04-26 13:52:42,220+02 ERROR [org.jboss.msc.service.fail] (ServerService
> Thread Pool -- 51) MSC01: Failed to start service
> jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START:
> org.jboss.msc.service.StartException in service
> jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START:
> java.lang.IllegalStateException: WFLYEE0042: Failed to construct component
> instance
> 2022-04-26 13:52:42,231+02 ERROR
> [org.jboss.as.controller.management-operation] (Controller Boot Thread)
> WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
> "engine.ear")]) - failure description: {"WFLYCTL0080: Failed services" =>
> {"jboss.deployment.subunit.\"engine.ear\".\"bll.jar\".component.Backend.START"
> => "java.lang.IllegalStateException: WFLYEE0042: Failed to construct
> component instance
> 2022-04-26 13:52:42,568+02 ERROR [org.jboss.as] (Controller Boot Thread)
> WFLYSRV0026: WildFly Full 23.0.2.Final (WildFly Core 15.0.1.Final) started
> (with errors) in 24096ms - Started 1668 of 1888 services (6 services failed
> or missing dependencies, 393 services are lazy, passive or on-demand)
>
> The complete starting sequence from server.log
>
> 2022-04-26 13:52:23,322+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-4) WFLYSRV0027: Starting deployment of "restapi.war"
> (runtime-name: "restapi.war")
> 2022-04-26 13:52:24,074+02 INFO [org.jboss.as.remoting] (MSC service thread
> 1-2) WFLYRMT0001: Listening on 127.0.0.1:8707
> 2022-04-26 13:52:24,247+02 INFO
> [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2)
> WFLYJCA0098: Bound non-transactional data source: java:/ENGINEDataSourceNoJTA
> 2022-04-26 13:52:24,901+02 INFO [org.jboss.as.ejb3] (MSC service thread 1-4)
> WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
> 2022-04-26 13:52:25,194+02 INFO
> [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4)
> WFLYJCA0001: Bound data source [java:/ENGINEDataSource]
> 2022-04-26 13:52:25,195+02 INFO
> [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4)
> WFLYJCA0001: Bound data source [java:/DWHDataSource]
> 2022-04-26 13:52:25,530+02 INFO [org.wildfly.security] (MSC service thread
> 1-3) ELY1: WildFly Elytron version 1.15.3.Final
> 2022-04-26 13:52:25,741+02 INFO [org.jboss.weld.deployer] (MSC service
> thread 1-2) WFLYWELD0003: Processing weld deployment restapi.war
> 2022-04-26 13:52:25,999+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "services.war")
> 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "root.war")
> 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "docs.war")
> 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "welcome.war")
> 2022-04-26 13:52:26,000+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "bll.jar")
> 2022-04-26 13:52:26,001+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "enginesso.war")
> 2022-04-26 13:52:26,001+02 INFO [org.jboss.as.server.deployment] (MSC
> service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name:
> "webadmin.war")
> 2022-04-26 13:52:26,368+02 INFO
> [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2)
> HV01: Hibernate Validator 6.0.22.Final
> 2022-04-26 13:52:26,752+02 INFO [org.wildfly.extension.undertow]
> (ServerService Thread Pool -- 40) WFLYUT0021: Registered web context:
> '/ovirt-engine/apidoc' for server 'default-server'
> 2022-04-26 13:52:26,751+02 INFO [org.wildfly.extension.undertow]
> (ServerService
