500 - Internal Server Error
by suporte＠logicworks.pt
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 years, 11 months
4.4 to 4.5, lost Gluster Mounts for data and engine
by Abe E
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 ~]#
2 years, 11 months
(no subject)
by Abe E
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 years, 11 months
Issue on Ovirt Node 4.4.10 installation by using DUD for MPTSAS driver update
by peter.yu＠guest-tek.com
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
2 years, 11 months
Async release for ovirt-engine-ui-extensions (1.3.3)
by Sandro Bonazzola
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.*
2 years, 11 months
Installing new self-hosted engine v4.5.0 on gluster 10
by Alessandro De Salvo
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
2 years, 11 months
How to renew CA cert after upgrading to ovirt 4.4
by noua.toukourou＠uni.lu
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 years, 11 months
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
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 years, 11 months
