- Users - oVirt List Archives

Re: [Ext.] Re: convert disk image to thin-provisioned - Ovirt 4.1
by Arik Hadas 28 Apr '22

28 Apr '22

On Thu, Apr 28, 2022 at 11:11 AM Mohamed Roushdy <mohamedroushdy(a)peopleintouch.com> wrote: > > Thanks for responding. > > So, this feature isn't available in 4.4.10 as we are intending to move to that version? It's not available in 4.4.10 See https://bugzilla.redhat.com/show_bug.cgi?id=977778 (introduced in 4.5) > Storage used for that VM is NFS. > > Thanks, > > -----Original Message----- > From: Nir Soffer <nsoffer(a)redhat.com> > Sent: Wednesday, April 27, 2022 10:53 PM > To: Mohamed Roushdy <mohamedroushdy(a)peopleintouch.com> > Cc: users(a)ovirt.org; Benny Zlotnik <bzlotnik(a)redhat.com> > Subject: [Ext.] Re: [ovirt-users] convert disk image to thin-provisioned - Ovirt 4.1 > > [CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe] > > On Wed, Apr 27, 2022 at 1:02 PM Mohamed Roushdy <mohamedroushdy(a)peopleintouch.com> wrote: > > > > Hello, > > > > I’ve researched a bit on how to convert a disk image from pre-allocated to thin in Ovirt 4.1, but nothing worked. Is there a way to achieve this please? > > Yes! > > 1. Install ovirt 4.5.0 > 2. Use the new convert disk feature > > With oVirt 4.1 you can do this manually. What kind storage are you using? > (NFS, iSCSI?) > > Nir > > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)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/KNYUTOLPAUZOX…

1 0

Re: convert disk image to thin-provisioned - Ovirt 4.1
by Nir Soffer 28 Apr '22

28 Apr '22

On Wed, Apr 27, 2022 at 1:02 PM Mohamed Roushdy <mohamedroushdy(a)peopleintouch.com> wrote: > > Hello, > > I’ve researched a bit on how to convert a disk image from pre-allocated to thin in Ovirt 4.1, but nothing worked. Is there a way to achieve this please? Yes! 1. Install ovirt 4.5.0 2. Use the new convert disk feature With oVirt 4.1 you can do this manually. What kind storage are you using? (NFS, iSCSI?) Nir

2 1

Zanata user request
by Temuri Doghonadze 27 Apr '22

27 Apr '22

Hello, My name is Temuri and I'd like to ask for account for Zanata to help with translation of ovirt to Georgian. I've done translation of zoiper, FreeCAD, part of gitlab, protonmail, parts of gnome and KDE, etc etc etc. In case of questions feel free to ask. BR, Temuri

4 12

upgrade ovirt-engine 4.3 to 4.4. engine.ear problems?
by ingvar.jungenas＠zebware.com 27 Apr '22

27 Apr '22

- 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, - When started, no access to the admin console at https://<fqdn>/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) MSC000001: 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) ELY00001: 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) HV000001: 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 Thread Pool -- 41) WFLYUT0021: Registered web context: '/ovirt-engine/web-ui' for server 'default-server' 2022-04-26 13:52:26,983+02 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 3.1.6 (Final) 2022-04-26 13:52:28,596+02 WARN [org.jboss.as.dependency.deprecated] (MSC service thread 1-1) WFLYSRV0221: Deployment "deployment.engine.ear.bll.jar" is using a deprecated module ("sun.jdk") which may be removed in future versions without notice. 2022-04-26 13:52:28,604+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment engine.ear 2022-04-26 13:52:28,713+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment root.war 2022-04-26 13:52:28,747+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment docs.war 2022-04-26 13:52:28,863+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment enginesso.war 2022-04-26 13:52:28,929+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Processing weld deployment services.war 2022-04-26 13:52:28,978+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment webadmin.war 2022-04-26 13:52:29,007+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment welcome.war 2022-04-26 13:52:29,042+02 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment bll.jar 2022-04-26 13:52:29,067+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'LockManager' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:29,067+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'Backend' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:29,067+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'OvirtGlusterSchedulingService' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:29,067+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'InitBackendServicesOnStartupBean' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:29,068+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'ManagedBlockStorageDiskUtil' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:29,068+02 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'MacPoolPerCluster' in deployment unit 'subdeployment "bll.jar" of deployment "engine.ear"' are as follows: 2022-04-26 13:52:30,878+02 INFO [org.infinispan.CONTAINER] (ServerService Thread Pool -- 51) ISPN000128: Infinispan version: Infinispan 'Corona Extra' 11.0.9.Final 2022-04-26 13:52:31,074+02 INFO [org.infinispan.PERSISTENCE] (ServerService Thread Pool -- 41) ISPN000556: Starting user marshaller 'org.wildfly.clustering.infinispan.marshalling.jboss.JBossMarshaller' 2022-04-26 13:52:31,462+02 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0002: Started dashboard cache from ovirt-engine container 2022-04-26 13:52:31,465+02 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51) WFLYCLINF0002: Started inventory cache from ovirt-engine container 2022-04-26 13:52:35,426+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,436+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.JsonExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,436+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002220: Adding singleton resource org.ovirt.engine.api.restapi.resource.BackendApiResource from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,436+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.MappingExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,436+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.IOExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,436+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.MalformedIdExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,437+02 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (ServerService Thread Pool -- 45) RESTEASY002210: Adding provider singleton org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper from Application class org.ovirt.engine.api.restapi.BackendApplication 2022-04-26 13:52:35,615+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 45) WFLYUT0021: Registered web context: '/ovirt-engine/api' for server 'default-server' 2022-04-26 13:52:40,024+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type org.codehaus.jackson.map.deser.std.StdScalarDeserializer<java.lang.Enum<?>> ignored on [EnhancedAnnotatedTypeImpl] public class org.ovirt.engine.core.utils.serialization.json.JsonEnumDeserializer 2022-04-26 13:52:40,031+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type class org.codehaus.jackson.map.JsonDeserializer<java.lang.Enum<?>> ignored on [EnhancedAnnotatedTypeImpl] public class org.ovirt.engine.core.utils.serialization.json.JsonEnumDeserializer 2022-04-26 13:52:40,031+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 1) WELD-001125: Illegal bean type class org.codehaus.jackson.map.deser.std.StdDeserializer<java.lang.Enum<?>> ignored on [EnhancedAnnotatedTypeImpl] public class org.ovirt.engine.core.utils.serialization.json.JsonEnumDeserializer 2022-04-26 13:52:40,350+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.DefaultGenericDao<org.ovirt.engine.core.common.businessentities.Provider<?>, org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,351+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type class org.ovirt.engine.core.dao.DefaultReadDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,351+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type interface org.ovirt.engine.core.dao.ModificationDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,351+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.SearchDao<org.ovirt.engine.core.common.businessentities.Provider<?>> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,351+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type interface org.ovirt.engine.core.dao.ReadDao<org.ovirt.engine.core.common.businessentities.Provider<?>,class org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,352+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type org.ovirt.engine.core.dao.GenericDao<org.ovirt.engine.core.common.businessentities.Provider<?>, org.ovirt.engine.core.compat.Guid> ignored on [EnhancedAnnotatedTypeImpl] public @Named @Singleton class org.ovirt.engine.core.dao.provider.ProviderDaoImpl 2022-04-26 13:52:40,424+02 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-001125: Illegal bean type org.springframework.jdbc.core.RowMapper<org.ovirt.engine.core.common.businessentities.Provider<?>> ignored on [EnhancedAnnotatedTypeImpl] private static class org.ovirt.engine.core.dao.provider.ProviderDaoImpl$ProviderRowMapper 2022-04-26 13:52:41,564+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Registered web context: '/' for server 'default-server' 2022-04-26 13:52:41,603+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 51) WFLYUT0021: Registered web context: '/ovirt-engine/docs' for server 'default-server' 2022-04-26 13:52:41,659+02 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 47) IJ000407: No lazy enlistment available for ENGINEDataSource 2022-04-26 13:52:41,673+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Registered web context: '/ovirt-engine/services' for server 'default-server' 2022-04-26 13:52:41,687+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 56) WFLYUT0021: Registered web context: '/ovirt-engine' for server 'default-server' 2022-04-26 13:52:41,825+02 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (ServerService Thread Pool -- 51) Loading XML bean definitions from class path resource [org/springframework/jdbc/support/sql-error-codes.xml] 2022-04-26 13:52:41,889+02 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 47) IJ000407: No lazy enlistment available for DWHDataSource 2022-04-26 13:52:41,934+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) WFLYUT0021: Registered web context: '/ovirt-engine/webadmin' for server 'default-server' 2022-04-26 13:52:41,938+02 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 44) WFLYUT0021: Registered web context: '/ovirt-engine/sso' for server 'default-server' 2022-04-26 13:52:42,093+02 INFO [org.springframework.jdbc.support.SQLErrorCodesFactory] (ServerService Thread Pool -- 51) SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase, Hana] 2022-04-26 13:52:42,220+02 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 51) MSC000001: 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,240+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2022-04-26 13:52:42,241+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2022-04-26 13:52:42,241+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2022-04-26 13:52:42,241+02 INFO [org.jboss.as.server] (ServerService Thread Pool -- 25) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2022-04-26 13:52:42,254+02 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report 2022-04-26 13:52:42,564+02 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 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) 2022-04-26 13:52:42,574+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2022-04-26 13:52:42,575+02 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706

4 5

500 - Internal Server Error
by suporte＠logicworks.pt 27 Apr '22

27 Apr '22

When upgrading from 4.5 to 4.5.0.5 have this 500 - Internal Server Error Engine service is running, postgresql service is running. Maybe wrong postgresql version? # rpm -qa |grep postgr* postgresql-contrib-12.9-3.module_el8.6.0+1043+60b632d3.x86_64 postgresql-server-12.9-3.module_el8.6.0+1043+60b632d3.x86_64 postgresql-jdbc-42.2.14-1.el8.noarch postgresql-12.9-3.module_el8.6.0+1043+60b632d3.x86_64 collectd-postgresql-5.12.0-7.el8s.x86_64 Found this error on /var/log/ovirt-engine/server.log 2022-04-27 11:20:16,003+01 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (ServerService Thread Pool -- 47) Loading XML bean definitions from class path resource [org/springframework/jdbc/support/sql-error-codes.xml] 2022-04-27 11:20:16,078+01 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService Thread Pool -- 58) IJ000407: No lazy enlistment available for DWHDataSource 2022-04-27 11:20:16,103+01 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Registered web context: '/ovirt-engine/webadmin' for server 'default-server' 2022-04-27 11:20:16,302+01 INFO [org.springframework.jdbc.support.SQLErrorCodesFactory] (ServerService Thread Pool -- 47) SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase, Hana] 2022-04-27 11:20:16,418+01 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 57) WFLYUT0021: Registered web context: '/ovirt-engine/sso' for server 'default-server' 2022-04-27 11:20:16,479+01 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 47) MSC000001: 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 at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.base/java.lang.Thread.run(Thread.java:829) at org.jboss.threads@2.4.0.Final//org.jboss.threads.JBossThread.run(JBossThread.java:513) Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:170) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:141) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.createInstance(BasicComponent.java:88) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.SingletonComponent.getComponentInstance(SingletonComponent.java:127) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.SingletonComponent.start(SingletonComponent.java:141) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54) ... 8 more Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@c153250 at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:239) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.supports(CMTTxInterceptor.java:446) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:70) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInjectionContextInterceptor.processInvocation(WeldInjectionContextInterceptor.java:43) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.component.singleton.StartupCountDownInterceptor.processInvocation(StartupCountDownInterceptor.java:25) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.BasicComponent.constructComponentInstance(BasicComponent.java:168) ... 13 more Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@c153250 at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:85) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:66) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:122) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:174) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.contexts.AbstractContext.get(AbstractContext.java:96) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:140) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:694) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:794) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:92) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.util.Beans.injectBoundFields(Beans.java:345) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:356) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.DefaultInjector$1.proceed(DefaultInjector.java:71) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.DefaultInjector.inject(DefaultInjector.java:73) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.module.ejb.DynamicInjectionPointInjector.inject(DynamicInjectionPointInjector.java:61) at org.jboss.weld.core@3.1.7.SP1//org.jboss.weld.module.ejb.SessionBeanInjectionTarget.inject(SessionBeanInjectionTarget.java:138) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInjectionContext.inject(WeldInjectionContext.java:39) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:51) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.ComponentInstantiatorInterceptor.processInvocation(ComponentInstantiatorInterceptor.java:74) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.weld@24.0.1.Final//org.jboss.as.weld.interceptors.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:111) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ee@24.0.1.Final//org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation@1.6.0.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) at org.jboss.as.ejb3@24.0.1.Final//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:232) ... 28 more Caused by: java.lang.reflect.InvocationTargetException 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.weld.core@3.1.7.SP1//org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:83) ... 59 more Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id' at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.processProcedureColumns(GenericCallMetaDataProvider.java:362) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.metadata.GenericCallMetaDataProvider.initializeWithProcedureColumnMetaData(GenericCallMetaDataProvider.java:114) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory.lambda$createMetaDataProvider$0(CallMetaDataProviderFactory.java:127) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:324) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.metadata.CallMetaDataProviderFactory.createMetaDataProvider(CallMetaDataProviderFactory.java:70) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.metadata.CallMetaDataContext.initializeMetaData(CallMetaDataContext.java:252) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.simple.AbstractJdbcCall.compileInternal(AbstractJdbcCall.java:313) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dal.dbbroker.PostgresDbEngineDialect$PostgresSimpleJdbcCall.compileInternal(PostgresDbEngineDialect.java:106) at org.springframework@5.0.4.RELEASE//org.springframework.jdbc.core.simple.AbstractJdbcCall.compile(AbstractJdbcCall.java:296) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.getCall(SimpleJdbcCallsHandler.java:157) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeImpl(SimpleJdbcCallsHandler.java:134) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dal.dbbroker.SimpleJdbcCallsHandler.executeReadList(SimpleJdbcCallsHandler.java:105) at org.ovirt.engine.core.dal//org.ovirt.engine.core.dao.TagDaoImpl.getAllForParent(TagDaoImpl.java:82) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.TagsDirector.addChildren(TagsDirector.java:116) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.TagsDirector.init(TagsDirector.java:75) ... 64 more 2022-04-27 11:20:16,506+01 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 Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@c153250 Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke protected void org.ovirt.engine.core.bll.TagsDirector.init() on org.ovirt.engine.core.bll.TagsDirector@c153250 Caused by: java.lang.reflect.InvocationTargetException Caused by: org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id'"}} 2022-04-27 11:20:16,545+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "ovirt-web-ui.war" (runtime-name : "ovirt-web-ui.war") 2022-04-27 11:20:16,545+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "apidoc.war" (runtime-name : "apidoc.war") 2022-04-27 11:20:16,546+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "restapi.war" (runtime-name : "restapi.war") 2022-04-27 11:20:16,546+01 INFO [org.jboss.as.server] (ServerService Thread Pool -- 27) WFLYSRV0010: Deployed "engine.ear" (runtime-name : "engine.ear") 2022-04-27 11:20:16,571+01 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance WFLYCTL0448: 2 additional services are down due to their dependencies being missing or failed 2022-04-27 11:20:16,785+01 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server 2022-04-27 11:20:16,794+01 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 24.0.1.Final (WildFly Core 16.0.1.Final) started (with errors) in 35078ms - Started 1670 of 1890 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) 2022-04-27 11:20:16,798+01 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:8706/management 2022-04-27 11:20:16,798+01 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:8706 -- Jose Ferradeira http://www.logicworks.pt

2 2

convert disk image to thin-provisioned - Ovirt 4.1
by Mohamed Roushdy 27 Apr '22

27 Apr '22

Hello, I’ve researched a bit on how to convert a disk image from pre-allocated to thin in Ovirt 4.1, but nothing worked. Is there a way to achieve this please? Thank you,

1 0

4.4 to 4.5, lost Gluster Mounts for data and engine
by Abe E 27 Apr '22

27 Apr '22

Seems the Gluster Node that booted from 4.5 into emergency mode was due to not finding the mounts for gluster_bricks data and engine, its as if it cant see them any more. Once i removed the mounts from /etc/fstab it lets me in, I could boot up. This is node 3 of the Gluster, Arbiter. [root@ovirt-3 ~]# mount -a mount: /gluster_bricks/engine: can't find UUID=45349e37-7a97-4a64-81eb-5fac3fec6477. mount: /gluster_bricks/data: can't find UUID=c0fa1111-0db2-4e08-bb79-be677530aeaa. SDA4 is where the Data and Engine glusters are, although If I try to make a new volumegroup for the gluster, I get this serror If I try try to make a new vgroup I get the following error, it almost sounds as if the partition is corrupted or something, basically i was trying to get it a new UUID. Physical volume '/dev/sda4' is already in volume group 'gluster_vg_sda4' Unable to add physical volume '/dev/sda4' to volume group 'gluster_vg_sda4' /dev/sda4: physical volume not initialized. [root@ovirt-3 ~]# dnf -q list installed centos-release\* ovirt-release\* ovirt-engine Installed Packages centos-release-advanced-virtualization.noarch 1.0-4.el8 @@commandline centos-release-ceph-pacific.noarch 1.0-2.el8 @System centos-release-gluster10.noarch 1.0-1.el8s @System centos-release-messaging.noarch 1-3.el8 @@commandline centos-release-nfv-common.noarch 1-3.el8 @System centos-release-nfv-openvswitch.noarch 1-3.el8 @System centos-release-openstack-xena.noarch 1-1.el8 @@commandline centos-release-opstools.noarch 1-12.el8 @System centos-release-ovirt45.noarch 8.6-1.el8 @@commandline centos-release-rabbitmq-38.noarch 1-3.el8 @@commandline centos-release-storage-common.noarch 2-2.el8 @System centos-release-virt-common.noarch 1-2.el8 @System ovirt-release-host-node.x86_64 4.5.0.1-1.el8 @System [root@ovirt-3 ~]# rpm -qa | grep gluster glusterfs-server-10.1-1.el8s.x86_64 glusterfs-selinux-2.0.1-1.el8s.noarch glusterfs-client-xlators-10.1-1.el8s.x86_64 qemu-kvm-block-gluster-6.2.0-5.module_el8.6.0+1087+b42c8331.x86_64 vdsm-gluster-4.50.0.13-1.el8.x86_64 gluster-ansible-maintenance-1.0.1-12.el8.noarch centos-release-gluster10-1.0-1.el8s.noarch libvirt-daemon-driver-storage-gluster-8.0.0-2.module_el8.6.0+1087+b42c8331.x86_64 python3-gluster-10.1-1.el8s.x86_64 glusterfs-geo-replication-10.1-1.el8s.x86_64 gluster-ansible-cluster-1.0-4.el8.noarch gluster-ansible-repositories-1.0.1-5.el8.noarch libglusterfs0-10.1-1.el8s.x86_64 glusterfs-fuse-10.1-1.el8s.x86_64 glusterfs-events-10.1-1.el8s.x86_64 gluster-ansible-features-1.0.5-12.el8.noarch gluster-ansible-roles-1.0.5-26.el8.noarch glusterfs-10.1-1.el8s.x86_64 libglusterd0-10.1-1.el8s.x86_64 gluster-ansible-infra-1.0.4-20.el8.noarch glusterfs-cli-10.1-1.el8s.x86_64 [root@ovirt-3 ~]#

1 0

(no subject)
by Abe E 27 Apr '22

27 Apr '22

Seems the Gluster Node that booted from 4.5 into emergency mode was due to not finding the mounts for gluster_bricks data and engine, its as if it cant see them any more. Once i removed the mounts from /etc/fstab it lets me in, I could boot up to the node past emergency mode but odd issue. One of the errors: dependency failed for /gluster_bricks/data Subject: Unit gluster_bricks-data.mount has failed This is node 3 of the Gluster, Arbiter. [root@ovirt-3 ~]# mount -a mount: /gluster_bricks/engine: can't find UUID=45349e37-7a97-4a64-81eb-5fac3fec6477. mount: /gluster_bricks/data: can't find UUID=c0fa1111-0db2-4e08-bb79-be677530aeaa.

2 4

Issue on Ovirt Node 4.4.10 installation by using DUD for MPTSAS driver update
by peter.yu＠guest-tek.com 27 Apr '22

27 Apr '22

Hello, I'm trying to install Ovirt Node 4.4.10 to my server and it gets an error when I'm trying to install iso for my MPT SAS driver by using DUD. In the boot menu, I pressed tab to enter Kernel and added "inst,dd". After that I got a screen shows a list of disk devices and selected USB that has iso file for MPT SAS : "Device : sda1 / Type : Vfat / Label : OEMDRV / UUDI : 6837-8481" Then, I selected drivers to install : "/media/DD-2/rpms/x86_64/kmod-mptsas-3.04.20-6.e18_5.elrepo.x86_64.rpm" And I pressed "C" to continue and gets an error message below : "modprobe : ERROR : could not insert 'mptsas' : invalid argument" Could you please help me what's the next step I can try to fix the issue? Thank you

3 4

Async release for ovirt-engine-ui-extensions (1.3.3)
by Sandro Bonazzola 27 Apr '22

27 Apr '22

The oVirt Team has just released a new version of ovirt-engine-ui-extensions package (1.3.3) that fixes a few important bugs: - Bug 2073005 <https://bugzilla.redhat.com/show_bug.cgi?id=2073005> - ui-extensions dialogs are flashing when they are rendered on a chrome browser ChangeLog: - Fix a bug for minimizing CSS flashing of all ui-extensions dialogs - vGPU dialog: small code refactorings - vGPU dialog: show widgets even if the cluster doesn't contain any vGPU hosts - CPU pinning dialog: fix message's trailing zero in case of no CPU topology was found - I18n: update translations (fetch from Zanata, remove outdated translations) - I18n: add support for Georgian language as a community translation The update is already available mirror.centos.org and should land on oVirt mirrors within 24 hours. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Async release for ovirt-engine (4.5.0.5) is now available
by Sandro Bonazzola 26 Apr '22

26 Apr '22

The oVirt Team has just released a new version of ovirt-engine package (4.5.0.5) that fixes a few important bugs: - Bug 2075486 <https://bugzilla.redhat.com/show_bug.cgi?id=2075486> - VM with Q35 UEFI and 64 CPUs is running but without boot screen, console and network. - Bug 1988496 <https://bugzilla.redhat.com/show_bug.cgi?id=1988496> - vmconsole-proxy-helper.cer is not renewed when running engine-setup - Bug 2074916 <https://bugzilla.redhat.com/show_bug.cgi?id=2074916> - Failed to upload OVA as template via upload_ova_as_vm_or_template.py - Bug 2075435 <https://bugzilla.redhat.com/show_bug.cgi?id=2075435> - Hybrid Backup - backup href has changed and causing backups to get stuck in finalizing stage - Bug 2077387 <https://bugzilla.redhat.com/show_bug.cgi?id=2077387> - Update to 4.5 failed due to failed database schema refresh - Bug 2071468 <https://bugzilla.redhat.com/show_bug.cgi?id=2071468> - Engine fenced host that was already reconnected and set to Up status. The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Installing new self-hosted engine v4.5.0 on gluster 10
by Alessandro De Salvo 26 Apr '22

26 Apr '22

Hi, I'm trying to install a new self-hosted engine 4.5.0 on an upgraded gluster v10.1, but the deployment fails at the domain activation stage, with this error: [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Activate storage domain] [ ERROR ] ovirtsdk4.Error: Fault reason is "Operation Failed". Fault detail is "[]". HTTP response code is 400. Looking at the server.log in the engine I see the follwing error: 2022-04-25 00:55:58,266+02 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-1) 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.BackendAttachedStorageDomainResource.get(BackendAttachedStorageDomainResource.java:35) at org.ovirt.engine.api.restapi-definition//org.ovirt.engine.api.resource.AttachedStorageDomainResource.doGet(AttachedStorageDomainResource.java:81) 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) The gluster volume itself is working fine and has the storage uid/gid set to 36 as it should be, and if I use a server with gluster 8 the installation works, while it fails with gluster 10 servers. Any help is appreciated, thanks, Alessandro

3 7

How to renew CA cert after upgrading to ovirt 4.4
by noua.toukourou＠uni.lu 26 Apr '22

26 Apr '22

Hi, I successfully migrated from 4.3 to 4.4 and ran ovirt-engine-rename. Now I would also like to renew the self-signed CA cert since it still has the CN of the former engine. Any idea how to do this ? Thanks,

2 1

I want to use the SSO function with some modifications. So, I have two questions about the SSO feature of oVirt VM.
by whoisjmh＠gmail.com 26 Apr '22

26 Apr '22

I'm in a situation where a small company is adopting oVirt and is trying to support the use of VMs using SSO functionality. I'm going to ask you two questions. First, I wonder how oVirt will support SSO to VMs without ovirt-guest-agent going forward. Already the guest-agent project seems to be excluded from oVirt. However, you can still use the SSO function through installation in the VM and setting on the admin page. Is this supported through an agent other than guest-agent? Second, I want to know the logic that supports VM SSO in oVirt. I looked up the documentation (https://www.ovirt.org/develop/release-management/features/infra/sso.html) but is it implemented as it is here? Or I'd like to know if it's being supported in a different direction than this. If anyone is familiar with SSO function support, please let me know. Thanks.

2 1

[ANN] oVirt Node 4.5.0.1 Async update
by Sandro Bonazzola 26 Apr '22

26 Apr '22

oVirt Node 4.5.0.1 Async update On April 26th 2022 the oVirt project released an async update of oVirt Node (4.5.0.1) delivering important impact security fixes, several bug fixes and enhancements. The update is already available on resources.ovirt.org and should land on oVirt mirrors within 24 hours. Security fixes included in oVirt Node NG 4.5.0 Async1 compared to latest oVirt 4.5.0 GA: - CVE-2022-1015 <https://bugzilla.redhat.com/show_bug.cgi?id=2065323> - important - kernel: arbitrary code execution in linux/net/netfilter/nf_tables_api.c - CVE-2022-0435 <https://bugzilla.redhat.com/show_bug.cgi?id=2048738> - important - kernel: remote stack overflow via kernel panic on systems using TIPC may lead to DoS - CVE-2022-25636 <https://bugzilla.redhat.com/show_bug.cgi?id=2056830> - important - kernel: heap out of bounds write in nf_dup_netdev.c - CVE-2021-4028 <https://bugzilla.redhat.com/show_bug.cgi?id=2027201> - important - kernel: use-after-free in RDMA listen() - CVE-2022-1016 <https://bugzilla.redhat.com/show_bug.cgi?id=2066614> - moderate - kernel: uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM oVirt Node has been updated, including: - Ansible Core 2.12.3: https://github.com/ansible/ansible/blob/stable-2.12/changelogs/CHANGELOG-v2… - CentOS Stream 8 latest updates - Full list of changes compared to oVirt Node 4.5.0 GA: 4.5.0 GA 4.5.0 Async #1 ansible-core 2.12.2-2.el8 2.12.3-1.el8 binutils 2.30-113.el8 2.30-114.el8 fribidi 1.0.4-8.el8 1.0.4-9.el8 ipa-client 4.9.8-2.module_el8.6.0+1054+cdb51b28 4.9.8-6.module_el8.6.0+1104+ba556574 ipa-client-common 4.9.8-2.module_el8.6.0+1054+cdb51b28 4.9.8-6.module_el8.6.0+1104+ba556574 ipa-common 4.9.8-2.module_el8.6.0+1054+cdb51b28 4.9.8-6.module_el8.6.0+1104+ba556574 ipa-selinux 4.9.8-2.module_el8.6.0+1054+cdb51b28 4.9.8-6.module_el8.6.0+1104+ba556574 ipxe-roms-qemu 20181214-8.git133f4c47.el8 20181214-9.git133f4c47.el8 kernel 4.18.0-373.el8 4.18.0-383.el8 kernel-core 4.18.0-373.el8 4.18.0-383.el8 kernel-modules 4.18.0-373.el8 4.18.0-383.el8 kernel-tools 4.18.0-373.el8 4.18.0-383.el8 kernel-tools-libs 4.18.0-373.el8 4.18.0-383.el8 krb5-libs 1.18.2-14.el8 1.18.2-17.el8 krb5-workstation 1.18.2-14.el8 1.18.2-17.el8 libestr 0.1.10-1.el8 0.1.10-3.el8 libkadm5 1.18.2-14.el8 1.18.2-17.el8 nmstate 1.2.1-1.el8 1.3.0-0.alpha.20220407.el8 nmstate-plugin-ovsdb 1.2.1-1.el8 1.3.0-0.alpha.20220407.el8 openvswitch2.15 2.15.0-81.el8s 2.15.0-88.el8s openvswitch2.15-ipsec 2.15.0-81.el8s 2.15.0-88.el8s ovirt-node-ng-image-update-placeholder 4.5.0-4.el8 4.5.0.1-1.el8 ovirt-release-host-node 4.5.0-4.el8 4.5.0.1-1.el8 python3-ipaclient 4.9.8-2.module_el8.6.0+1054+cdb51b28 4.9.8-6.module_el8.6.0+1104+ba556574 python3-ipalib 4.9.8-2.module_el8.6.0+1054+cdb51b28 4.9.8-6.module_el8.6.0+1104+ba556574 python3-libnmstate 1.2.1-1.el8 1.3.0-0.alpha.20220407.el8 python3-openvswitch2.15 2.15.0-81.el8s 2.15.0-88.el8s python3-perf 4.18.0-373.el8 4.18.0-383.el8 python3-sanlock 3.8.4-1.el8 3.8.4-3.el8 rsyslog 8.2102.0-7.el8 8.2102.0-9.el8 rsyslog-elasticsearch 8.2102.0-7.el8 8.2102.0-9.el8 rsyslog-mmjsonparse 8.2102.0-7.el8 8.2102.0-9.el8 rsyslog-mmnormalize 8.2102.0-7.el8 8.2102.0-9.el8 rsyslog-openssl 8.2102.0-7.el8 8.2102.0-9.el8 sanlock 3.8.4-1.el8 3.8.4-3.el8 sanlock-lib 3.8.4-1.el8 3.8.4-3.el8 virt-install 3.2.0-3.el8 3.2.0-4.el8 virt-manager-common 3.2.0-3.el8 3.2.0-4.el8 virt-what 1.18-13.el8 1.18-14.el8 Additional resources: - Read more about the oVirt 4.5.0 release highlights: https://www.ovirt.org/release/4.5.0/ - Get more oVirt project updates on Twitter: https://twitter.com/ovirt - Check out the latest project news on the oVirt blog: https://blogs.ovirt.org/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

AMD Ryzen 5600G unsupported?
by Gilboa Davara 26 Apr '22

26 Apr '22

Hello all, I'm building adding a Ryzen 5 5600G workstation to an existing AMD Threadripper cluster (The existing machine use the 3960X CPU) and the cluster rejects the new host as it fails to recognize the host CPU as either "Secure AMD Epyc" or "AMD Epyc". All hosts are using a fully updated CentOS 8 Streams. I assume the 5XXX family has yet to be supported by oVirt. Can I somehow force oVirt / HE to recognize the new host? - Gilboa

2 5

Error 500 on Hosted Engine admin portal!!!
by Patrick Lomakin 25 Apr '22

25 Apr '22

Hi everyone! Did the oVirt team check the 4.5 update before release? I've update my production latest 4.4.10 version and get Error 500 on admin page. Clean installation on another bare-metal node using Ovirt Node 4.5 and hosted-engine console setup (installing through the web installer several versions of Ovirt traditionally makes the connection break and disconnects access to the host by means of the IP address) get an error 500 after healthcheck. What I will do in this situation? Httpd log: [Sat Apr 23 15:54:59.826076 2022] [core:notice] [pid 1526:tid 140201844767040] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND' [Sat Apr 23 15:55:05.685872 2022] [proxy:error] [pid 2125:tid 140201102243584] (111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 (127.0.0.1) failed [Sat Apr 23 15:55:05.685924 2022] [proxy_ajp:error] [pid 2125:tid 140201102243584] [client 192.168.0.14:43194] AH00896: failed to make connection to backend: 127.0.0.1 [Sat Apr 23 15:55:15.831754 2022] [proxy:error] [pid 2125:tid 140201110636288] (111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 (127.0.0.1) failed [Sat Apr 23 15:55:15.831811 2022] [proxy_ajp:error] [pid 2125:tid 140201110636288] [client 192.168.0.14:43196] AH00896: failed to make connection to backend: 127.0.0.1 [Sat Apr 23 16:21:57.720678 2022] [proxy:error] [pid 7761:tid 140200894203648] (111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 (127.0.0.1) failed [Sat Apr 23 16:21:57.720745 2022] [proxy_ajp:error] [pid 7761:tid 140200894203648] [client 192.168.0.14:43516] AH00896: failed to make connection to backend: 127.0.0.1 [Sat Apr 23 16:30:57.738971 2022] [proxy:error] [pid 7761:tid 140200877418240] (111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 (127.0.0.1) failed [Sat Apr 23 16:30:57.739043 2022] [proxy_ajp:error] [pid 7761:tid 140200877418240] [client 192.168.0.14:43640] AH00896: failed to make connection to backend: 127.0.0.1 [Sat Apr 23 16:32:27.838795 2022] [proxy:error] [pid 7761:tid 140200978130688] (111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 (127.0.0.1) failed [Sat Apr 23 16:32:27.838881 2022] [proxy_ajp:error] [pid 7761:tid 140200978130688] [client 192.168.0.14:43658] AH00896: failed to make connection to backend: 127.0.0.1 [Sat Apr 23 16:37:49.357585 2022] [core:notice] [pid 1497:tid 139855753558336] SELinux policy enabled; httpd running as context system_u:system_r:httpd_t:s0 [Sat Apr 23 16:37:49.361573 2022] [suexec:notice] [pid 1497:tid 139855753558336] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Sat Apr 23 16:37:49.388188 2022] [so:warn] [pid 1497:tid 139855753558336] AH01574: module proxy_module is already loaded, skipping [Sat Apr 23 16:37:49.391763 2022] [lbmethod_heartbeat:notice] [pid 1497:tid 139855753558336] AH02282: No slotmem from mod_heartmonitor [Sat Apr 23 16:37:49.399281 2022] [mpm_event:notice] [pid 1497:tid 139855753558336] AH00489: Apache/2.4.37 (centos) OpenSSL/1.1.1k mod_auth_gssapi/1.6.1 mod_wsgi/4.6.4 Python/3.6 configured -- resuming normal operations [Sat Apr 23 16:37:49.399320 2022] [core:notice] [pid 1497:tid 139855753558336] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND' [Sat Apr 23 23:20:37.254289 2022] [proxy:error] [pid 6183:tid 139854109198080] (111)Connection refused: AH00957: AJP: attempt to connect to 127.0.0.1:8702 (127.0.0.1) failed [Sat Apr 23 23:20:37.254354 2022] [proxy_ajp:error] [pid 6183:tid 139854109198080] [client 192.168.0.13:52982] AH00896: failed to make connection to backend: 127.0.0.1 server.log: 2022-04-23 16:38:20,655+03 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-23 16:38:20,752+03 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 24.0.1.Final (WildFly Core 16.0.1.Final) started (with errors) in 22155ms - Started 1670 of 1890 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand) 2022-04-23 23:20:50,622+03 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 47) MSC000001: 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-23 23:20:50,630+03 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-23 23:20:50,706+03 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 24.0.1.Final (WildFly Core 16.0.1.Final) started (with errors) in 15267ms - Started 1670 of 1890 services (6 services failed or missing dependencies, 393 services are lazy, passive or on-demand)

7 6

Cannot remove geo-replication session
by simon＠justconnect.ie 25 Apr '22

25 Apr '22

On CentOS 8 - 4.4.5 I removed a geo-replication session from a volume from the command line but ovirt manager 'volume' is still showing the geo-replication session. I cannot remove this session as it says it doesn't exist (which is correct). Geo Rep session deletion failed: rc=30800 out=() err=['Geo-replication session between data01 and bdtovirthci01-strg::pgs_data01 does not exist_']

1 1

Windows VMs randomly wont boot after compatibility change
by David Sekne 25 Apr '22

25 Apr '22

Hello, I have noticed that some of our Windows VM's (2012 - 2022) randomly won't boot when reboot is initiated from guest OS. As far as I can tell this started happening after we raised the cluster compatibility from 4.4 to 4.5 (it's 4.6 now). To fix it a VM needs to be stopped and started. We are running oVirt 4.4.10. I cannot really see much from the logs if grepping for a specific VM that had these issues. Example VM ID is: daf33e97-a76f-4b82-b4f2-20fa4891c88b Im attaching logs: - Initial hypervisor where VM was running on (reboot is initiated at 4:06:38 AM): vdsm-1.log - Second hypervisor where VM was started after it was stopped and started back (this was done 7:45:43 AM): vdsm-2.log - Engine log: engine.log Has someone noticed any similar issues and can provide some feedback / help? Regards, David

2 4

How to configure oVirt for OKD 4.10
by marcellus major 24 Apr '22

24 Apr '22

Recently, I watched a video made by Gal Zadman detailing how to install OKD on oVirt Is there any documentation detailing how Gal configured the oVirt environment prior to installation of OKD? Thanks

3 2

oVirt Node 4.5 - Installing gluster single node stops immediately
by Patrick Lomakin 23 Apr '22

23 Apr '22

Hi guys! I've tried to deploy ovirt single node with gluster via GUI but have a problem immediately. A log file that shows after installation was empty. But in journalctl I found that: Apr 23 20:06:45 host1 cockpit-ws[22948]: ERROR! couldn't resolve module/action 'vdo'. This often indicates a misspelling, missing collection, or incorrect module path. Apr 23 20:06:45 host1 cockpit-ws[22948]: The error appears to be in '/etc/ansible/roles/gluster.infra/roles/backend_setup/tasks/vdo_create.yml': line 53, column 3, but may Apr 23 20:06:45 host1 cockpit-ws[22948]: be elsewhere in the file depending on the exact syntax problem. Apr 23 20:06:45 host1 cockpit-ws[22948]: The offending line appears to be: Apr 23 20:06:45 host1 cockpit-ws[22948]: - name: Create VDO with specified size Apr 23 20:06:45 host1 cockpit-ws[22948]: ^ here

1 1

Command line management and ansible error
by fs3000＠pm.me 23 Apr '22

23 Apr '22

Hello guys, So i read in the documentation that managing VMs is not done with ovirt-shell anymore, ansible should be used instead. Ansible can manage VMs via modules, connecting to the Manager VM. However, how can i start the Manager VM itself, if it stopped? (it just happened to me) Catch 22 problem :) Anyway, i tried using the ovirt_vm_info modulei in ansible, but it resulted in an error, because the web interface is running with a self signed certificate, configured by the engine setup: " An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ovirtsdk4.Error: Error while sending HTTP request: (60, 'SSL certificate problem: self signed certificate in certificate chain') fatal: [192.168.0.200]: FAILED! => {"changed": false, "msg": "Error while sending HTTP request: (60, 'SSL certificate problem: self signed certificate in certificate chain')"} " I know this is a curl error. In the shell, the option -k or --insecure can be used. How to use that option in the ansible module? Thanks in advance for any pointers on this!

3 5

ovirt 4.5.0 - template Issue
by Winfried de Heiden 22 Apr '22

22 Apr '22

Hi all, For some reason, I am not able to create or import tempates. Creating a template from an existing VM (using the UI) will result in the ui.log: 2022-04-22 10:45:30,273+02 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-13) [] Permutation name: 1EBF700FBD4B5CDF0BCDABD7F03C4FA9 2022-04-22 10:45:30,273+02 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-13) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : Cannot read properties of undefined (reading 'a') Trying to import a template will result in ui.log: 2022-04-22 12:17:02,383+02 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-20) [] Permutation name: 45A889347BD114EA48B9B9409FF70ADC 2022-04-22 12:17:02,383+02 ERROR [org.ovirt.engine.ui.frontend.server.gwt.OvirtRemoteLoggingService] (default task-20) [] Uncaught exception: com.google.gwt.core.client.JavaScriptException: (TypeError) : e is null New bug? Anyone? Winfried

2 1

Re: engine.rar
by Sandro Bonazzola 22 Apr '22

22 Apr '22

Il giorno ven 22 apr 2022 alle ore 11:54 Nazeem Durgahee < nazeem.durgahee(a)harelmallac.com> ha scritto: > Hi Sandro, > > > > This what I am getting while trying to upgrade. > > > > Complete! > > [root@fscdrs-ovirt-001 ~]# dnf install -y centos-release-ovirt45 > > Last metadata expiration check: 0:02:50 ago on Fri 22 Apr 2022 01:51:06 PM > +04. > > No match for argument: centos-release-ovirt45 > > Error: Unable to find a match: centos-release-ovirt45 > I assume you are on Oracle Linux for hosts as well, not using oVirt Node, right? In such case, you need Oracle Linux 8.6 Beta as a first step. I never used Oracle Linux but I guess it means enabling this beta repo https://yum.oracle.com/repo/OracleLinux/OL8/beta/x86_64/ Perhaps @Simon Coter <simon.coter(a)oracle.com> , @Marcos Sungaila <marcos.sungaila(a)oracle.com> or someone else from Oracle can assist you with this. Then, you'll need to follow https://ovirt.org/download/install_on_rhel.html for adding CentOS Stream extras repositories before trying to install centos-release-ovirt45. Perhaps you or someone else using Oracle Linux can help updating https://ovirt.org/download/install_on_rhel.html for the Oracle Linux case once you succeed installing there? > > > *From:* Sandro Bonazzola <sbonazzo(a)redhat.com> > *Sent:* Thursday, April 21, 2022 12:17 PM > *To:* Nazeem Durgahee <nazeem.durgahee(a)harelmallac.com> > *Cc:* Veeroo Dowlut <Veeroo.Dowlut(a)harelmallac.com>; Govind Mooroogen < > govind.mooroogen(a)harelmallac.com>; users(a)ovirt.org > *Subject:* Re: [ovirt-users] engine.rar > > > > > > > > Il giorno gio 21 apr 2022 alle ore 10:13 Nazeem Durgahee < > nazeem.durgahee(a)harelmallac.com> ha scritto: > > > HI, > > We have ovirt 4.4.10 running on oracle linux 8 but we are having issues > with netbackup whereby it is not removing the snapshot after VM backup. > > Kindly find attached engine log. > > > > Can you please upgrade to 4.5.0 and try to reproduce? > > More info: > > * https://blogs.ovirt.org/2022/04/ovirt-4-5-0-is-now-generally-available/ > > * https://blogs.ovirt.org/2022/04/ovirt-4-4-end-of-life/ > > > > -- > > *Sandro Bonazzola* > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbonazzo(a)redhat.com > > <https://www.redhat.com/> > > *Red Hat respects your work life balance. Therefore there is no need to > answer this email out of your office hours.* > > > -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

Re: engine.rar
by Sandro Bonazzola 22 Apr '22

22 Apr '22

Il giorno gio 21 apr 2022 alle ore 10:13 Nazeem Durgahee < nazeem.durgahee(a)harelmallac.com> ha scritto: > > HI, > > We have ovirt 4.4.10 running on oracle linux 8 but we are having issues > with netbackup whereby it is not removing the snapshot after VM backup. > > Kindly find attached engine log. > Can you please upgrade to 4.5.0 and try to reproduce? More info: * https://blogs.ovirt.org/2022/04/ovirt-4-5-0-is-now-generally-available/ * https://blogs.ovirt.org/2022/04/ovirt-4-4-end-of-life/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 1