[ovirt-users] Re: unable to upgrade engine to 4.4.10 from 4.4.8

[Patrick Hibbs]

Redownload the latest 4.4 release rpm and install it on the hosts. That
should fix your mirrorlists.

Do be aware that there is an ongoing issue with postgresql-jdbc and
that you'll need to exclude it from the upgrade process with "dnf
update -x postgresql-jdbc" otherwise the engine will fail to start.
You'll also need to exclude ansible-core if you are running centos-
stream.

Also, "oVirt 4.4.x is EOL. Please upgrade to oVirt 4.5 as soon as
practical."

-Patrick Hibbs

On Wed, 2022-04-27 at 22:24 +, Diggy Mc wrote:
> ovirt-
> 4.4  
>  Latest oVirt 4.4 Release

___
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/337MGHVGMRHP7PTMT53NE6MLBN3Q5MSB/

[ovirt-users] Re: Q: Non-Operational Node Hosts - Ghost Network Problem

[Patrick Hibbs]

Your logs suggest that VDSM hasn't detected the removal of the network
yet. Did you try clicking on the "Sync Host Networks" button on the
non-operational hosts?

If you've changed the network config, VDSM may have failed to set up
the host properly. What does the output of "ip addr show" on these
hosts?

Manually removing the network from the hosts is only a temporary fix.
VDSM will attempt to recreate the network on restart if VDSM's config
isn't sync'd with the engine.

-Patrick Hibbs

On Wed, 2022-04-27 at 12:36 +0300, Andrei Verovski wrote:
> Hi,
> 
> 
> I run into nasty and unexpected problem (oVirt 4.4.7.6-1.el8 ) and 2
> non-operational node hosts, which seem relate to ghost network
> glitch.
> Everything worked fine for a very long time until I did the
> following.
> 
> 1) Made a backup of several VMs which have network “CloudLink-ISP2”.
> 2) Moved VM disks into another node hosts, which don’t have link
> “CloudLink-ISP2”, and forgot (preliminary to move) to re-configure
> network interface (remove link to “CloudLink-ISP2”) as I did before..
> 3) Now I have 2 hosts in non-operational mode which is a really big
> problem - there are only 3 nodes total in a cluster.
> 
> I tried to fix this by adding 3rd network “CloudLink-ISP2” to each
> non-operational hosts, and connected ethernet interfaces to a switch.
> Unfortunately, it didn’t helped either because for whatever reason
> link did not go up.
> 
> How I can remove any reference to “CloudLink-ISP2” from node11 and
> node14? They don’t have any VMs needed that “CloudLink-ISP2”. I
> edited even inactive VMs and removed “CloudLink-ISP2”.
> May be there is an option to ignore missing or downed links whn
> activating node hosts?
> 
> Thanks in advance for any help.
> 
> 
> ——
> 
> Logs:
> 
> 2022-04-27 11:16:59,769+03 ERROR
> [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-
> ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51)
> [5ab20328] Host 'node14' is set to Non-Operational, it is missing the
> following networks: 'CloudLink-ISP2'
> 2022-04-27 11:16:59,790+03 WARN 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector
> ] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-
> Thread-51) [5ab20328] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519),
> Host node14 does not comply with the cluster ClusterRiga11 networks,
> the following networks are missing on host: 'CloudLink-ISP2'
> 2022-04-27 11:16:59,884+03 INFO 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector
> ] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-
> Thread-51) [55610e1e] EVENT_ID: VDS_DETECTED(13), Status of host
> node14 was set to NonOperational.
> 2022-04-27 11:16:59,907+03 INFO 
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-
> ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51)
> [5d6ef791] Host 'node14'(aa871d44-94e2-4fdb-aeb3-ca0ae8dc568f) is
> already in NonOperational status for reason 'NETWORK_UNREACHABLE'.
> SetNonOperationalVds command is skipped.
> 
> 2022-04-27 11:12:26,050+03 ERROR
> [org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] (EE-
> ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19)
> [5400352e] Host 'node11' is set to Non-Operational, it is missing the
> following networks: 'CloudLink-ISP2'
> 2022-04-27 11:12:26,070+03 WARN 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector
> ] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-
> Thread-19) [5400352e] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519),
> Host node11 does not comply with the cluster ClusterRiga11 networks,
> the following networks are missing on host: 'CloudLink-ISP2'
> 2022-04-27 11:12:26,192+03 INFO 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector
> ] (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-
> Thread-19) [57d79e54] EVENT_ID: VDS_DETECTED(13), Status of host
> node11 was set to NonOperational.
> 2022-04-27 11:12:26,214+03 INFO 
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-
> ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19)
> [151821e3] Host 'node11'(3c854f9c-2cdd-423e-bca0-37964ba76702) is
> already in NonOperational status for reason 'NETWORK_UNREACHABLE'.
> SetNonOperationalVds command is skipped.
> 
> 2022-04-27 11:51:10,539+03 INFO 
> [org.ovirt.engine.core.vdsbroker.VdsManager] (EE-
> ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62)
> [] Clearing domains data for host node14
> 2022-04-27 11:51:10,539+03 INFO 
> [org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] (EE-
> ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62)
> [] Host 'node14' moved to Non-Operational state because interface/s
> which are down are needed by required network/s in the current
> cluster: 'eno3 (CloudLink-ISP2)'
> 2022-04-27 11:51:10,569+03 WARN 
> 

[ovirt-users] unable to upgrade engine to 4.4.10 from 4.4.8

[Diggy Mc]

I am unable to upgrade my hosted engine from version 4.4.8 to 4.4.10.  I 
suspect the problem is because of the obsolescence of CentOS Linux 8.
DNF gives me the following error:

CentOS Linux 8 - AppStream
Error: Failed to download metadata for repo 'appstream': Cannot prepare 
internal mirrorlist: No URLs in mirrorlist

This is the list of repositories on my engine:

appstream   
CentOS Linux 8 - AppStream
baseos  
CentOS Linux 8 - BaseOS
extras  
CentOS Linux 8 - Extras
ovirt-4.4   
Latest oVirt 4.4 Release
ovirt-4.4-advanced-virtualization   
Advanced Virtualization packages for x86_64
ovirt-4.4-centos-ceph-pacific   
Ceph packages for x86_64
ovirt-4.4-centos-gluster8   
CentOS-8 - Gluster 8
ovirt-4.4-centos-nfv-openvswitch
CentOS-8 - NFV OpenvSwitch
ovirt-4.4-centos-opstools   
CentOS-8 - OpsTools - collectd
ovirt-4.4-centos-ovirt44
CentOS-8 - oVirt 4.4
ovirt-4.4-copr:copr.fedorainfracloud.org:sac:gluster-ansible
Copr repo for gluster-ansible owned by sac
ovirt-4.4-copr:copr.fedorainfracloud.org:sbonazzo:EL8_collection
Copr repo for EL8_collection owned by sbonazzo
ovirt-4.4-epel  
Extra Packages for Enterprise Linux 8 - x86_64
ovirt-4.4-openstack-victoria
OpenStack Victoria Repository
ovirt-4.4-virtio-win-latest 
virtio-win builds roughly matching what will be shipped in upcoming 
RHEL
powertools  
CentOS Linux 8 - PowerTools

Your guidance on how to proceed is much appreciated.  Thanks.
___
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/I6K2P6Y2XRXYHOF2BDXUAPBOWDNAGDUU/

[ovirt-users] Re: Zanata user request

[Scott Dickerson]

Hi Temuri,

The compile requirements aren't that steep with the right build command
options.

Since there are a few challenges in getting the translations pulled and
deployed through to rpms, I went ahead and created a copr project to make
the whole thing easier.  The copr project builds ovirt-engine,
ovirt-engine-ui-extensions and ovirt-web-ui from my github forks.  As of
this afternoon, they're exactly the same and their master branches plus
your translations.  You should be able to enable my repo on your
ovirt-engine and install the rpms with your translations without much
trouble.

The copr repo: https://copr.fedorainfracloud.org/coprs/sdickers/enUS_kaGE/

I can refresh the builds by updating my forks.  Only takes a few minutes to
do so.  Just drop me an email and I can do that.  Or you can fork the copr
project and repos to do it yourself (if you're comfortable with the forks,
configs, git pushing etc).

Good luck,
Scott

On Tue, Apr 26, 2022 at 12:47 PM Temuri Doghonadze <
temuri.doghona...@gmail.com> wrote:

> Thanks for suggestion.
> Seems like ovirt-engine needs more than 32GB RAM to be compile.
> Will it take long to get it merged? I'd just wait, if it doesn't.
>
> On Tue, Apr 26, 2022 at 6:42 PM Scott Dickerson 
> wrote:
>
>>
>>
>> On Tue, Apr 19, 2022 at 4:03 PM Temuri Doghonadze <
>> temuri.doghona...@gmail.com> wrote:
>>
>>> Hello,
>>> No problem with that, I already got ovirt master installed through copr.
>>> Downloaded everything, found spec files, downloaded translations from
>>> zanata..
>>>
>>> Where to put translations? I see no "po" or "intl" or anything familiar.
>>> Also, there are no translations in src.rpms I see on copr. Any specific way
>>> to get them into source?
>>>
>>
>> For Admin Portal (ovirt-engine), translations need to be compiled in for
>> about half of the files.  For VM Portal, po and pot files are only used to
>> communicate with zanta.  There are build and processing scripts to manage
>> the various translation files in the relevant projects.
>>
>> Really the best way is to grab the source, pull and apply the
>> translations and build the rpms.  It is a pain, but it is the only safe way
>> to do it.
>>
>>
>>>
>>> Regards, Temuri
>>>
>>> On Tue, Apr 19, 2022 at 9:24 PM Scott Dickerson 
>>> wrote:
>>>
 Hi Temuri,

 I created a BZ to track adding of Georgian on the various parts of the
 project.  See https://bugzilla.redhat.com/show_bug.cgi?id=2075188.

 To test your translations it can get a bit tricky.  The patches linked
 in the BZ enable Georgian but do not actually include your current set of
 translations.  To get a set of rpms with translations applied can require a
 bit of work:

- clone the git repos for the projects (ovirt-engine,
ovirt-engine-ui-extensions, ovirt-web-ui)
- apply the appropriate PR from BZ2075188 if it has not been merged
yet
- pull the translations from zanata to your local copy
- build the rpm from your local copy
- install the new rpm to your ovirt instance
- select Georgina on the main landing/welcome page

 I can probably help get some rpms with translations installed for you
 via a custom copr repo (linked to you or me, either could work).  Let me
 know if that would be easier for you.

 Regards,
 Scott

 On Mon, Mar 28, 2022 at 2:54 AM Temuri Doghonadze <
 temuri.doghona...@gmail.com> wrote:

> Hello,
> Thanks for fixing it, It's almost done, error messages are too boring
> :)
> Another question is, when/how will I be able to test/see translation?
> I got access to 4.4 version of ovirt and translations can be copied
> forward (no access to 4.5 branch) I guess/hope.
> Anyways, is there any way for me to see what I just did?. I'd even
> recompile whole ovirt, if needed.
> BR, Temuri
>
> On Wed, Mar 23, 2022 at 12:54 PM Sharon Gratch 
> wrote:
>
>> Hi,
>>
>> On Wed, Mar 23, 2022 at 11:54 AM Temuri Doghonadze <
>> temuri.doghona...@gmail.com> wrote:
>>
>>> Hello again,
>>> Translation of 2 modules you gave access me to is completed.
>>> But I've noticed 2 additional modules I didn't have access to.
>>> Could you please tell me if they're not neccessary?
>>>
>>
>> Thanks for translating web-ui and ovirt-engine-ui-extensions
>> projects.
>> Regarding the ovirt-engine project, please check now since for some
>> reason the Georgian language was disabled. I enabled it so it should be 
>> ok
>> now.
>> The 4th project rhvm-branding is a downstream project so no need to
>> translate it.
>>
>>
>>
>>> Also, virt-manager translation is still unavailable.
>>>
>>> On Tue, Mar 22, 2022 at 1:02 PM Temuri Doghonadze <
>>> temuri.doghona...@gmail.com> wrote:
>>>
 Hello,
 Got it, thank you.
 All's ok, I'm in. Only thing I might 

[ovirt-users] Re: convert disk image to thin-provisioned - Ovirt 4.1

[Nir Soffer]

On Wed, Apr 27, 2022 at 1:02 PM Mohamed Roushdy
 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@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/M4RXWOKSUGKWHUQBRX7MF4ANPMASDCJB/

[ovirt-users] Re: upgrade ovirt-engine 4.3 to 4.4. engine.ear problems?

[Martin Perina]

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: Host cannot connect to storage domains

[José Ferradeira via Users]

It did not work 

Thanks 


De: "Abe E"  
Para: users@ovirt.org 
Enviadas: Quarta-feira, 27 De Abril de 2022 15:58:01 
Assunto: [ovirt-users] Re: Host cannot connect to storage domains 

I think you're running into that bug, someone mentioned the following which 
seemed to work for my nodes that complained of not being able to connect to the 
storage pool. 

The following fix worked for me, i.e. replacing the following line in 
/usr/lib/python3.6/site-packages/vdsm/gluster/cli.y 


Replace: value['stripeCount'] =el.find('stripeCount').text 

With: if (el.find('stripeCount')): value['stripeCount'] = 
el.find('stripeCount').text 

Restart VSMD and SuperVSMD and then your host should be able to connect if you 
have the same issue 
___ 
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/TWTFZ4VHKSEABMEZYMDUJI2PUYA24XMU/
 
___
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/22NF5BKNFPDVS3OGITBIM3XVFZJVCO2H/

[ovirt-users] Re: Host cannot connect to storage domains

[Abe E]

I think you're running into that bug, someone mentioned the following which 
seemed to work for my nodes that complained of not being able to connect to the 
storage pool.

The following fix worked for me, i.e. replacing the following line in
/usr/lib/python3.6/site-packages/vdsm/gluster/cli.y


Replace: value['stripeCount'] =el.find('stripeCount').text

With: if (el.find('stripeCount')): value['stripeCount'] = 
el.find('stripeCount').text

Restart VSMD and SuperVSMD and then your host should be able to connect if you 
have the same issue
___
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/TWTFZ4VHKSEABMEZYMDUJI2PUYA24XMU/

[ovirt-users] Re: Host cannot connect to storage domains

[Nir Soffer]

On Wed, Apr 27, 2022 at 3:54 PM José Ferradeira via Users
 wrote:
>
> After upgrade to 4.5 host cannot be activated because cannot connect to data 
> domain.
>
> I have a data domain in NFS (master) and a GlusterFS. It complains about the 
> Gluster domain:
> The error message for connection node1-teste.acloud.pt:/data1 returned by 
> VDSM was: XML error
>
> # rpm -qa|grep glusterfs*
> glusterfs-10.1-1.el8s.x86_64
> glusterfs-selinux-2.0.1-1.el8s.noarch
> glusterfs-client-xlators-10.1-1.el8s.x86_64
> glusterfs-events-10.1-1.el8s.x86_64
> libglusterfs0-10.1-1.el8s.x86_64
> glusterfs-fuse-10.1-1.el8s.x86_64
> glusterfs-server-10.1-1.el8s.x86_64
> glusterfs-cli-10.1-1.el8s.x86_64
> glusterfs-geo-replication-10.1-1.el8s.x86_64
>
>
> engine log:
>
> 2022-04-27 13:35:16,118+01 ERROR 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) [e
> be79c6] EVENT_ID: VDS_STORAGES_CONNECTION_FAILED(188), Failed to connect Host 
> NODE1 to the Storage Domains DATA1.
> 2022-04-27 13:35:16,169+01 ERROR 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) [e
> be79c6] EVENT_ID: STORAGE_DOMAIN_ERROR(996), The error message for connection 
> node1-teste.acloud.pt:/data1 returned by VDSM was: XML error
> 2022-04-27 13:35:16,170+01 ERROR 
> [org.ovirt.engine.core.bll.storage.connection.FileStorageHelper] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) 
> [ebe79c6
> ] The connection with details 'node1-teste.acloud.pt:/data1' failed because 
> of error code '4106' and error message is: xml error
>
>
>
> vdsm log:
> 2022-04-27 13:40:07,125+0100 ERROR (jsonrpc/4) [storage.storageServer] Could 
> not connect to storage server (storageServer:92)
> Traceback (most recent call last):
>  File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 
> 90, in connect_all
>con.connect()
>  File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 
> 233, in connect
>self.validate()
>  File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 
> 365, in validate
>if not self.volinfo:
>  File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 
> 352, in volinfo
>self._volinfo = self._get_gluster_volinfo()
>  File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 
> 405, in _get_gluster_volinfo
>self._volfileserver)
>  File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 56, 
> in __call__
>return callMethod()
>  File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 54, 
> in 
>**kwargs)
>  File "", line 2, in glusterVolumeInfo
>  File "/usr/lib64/python3.6/multiprocessing/managers.py", line 772, in 
> _callmethod
>raise convert_to_error(kind, result)
> vdsm.gluster.exception.GlusterXmlErrorException: XML error: rc=0 out=() 
> err=[b'\n  0\n  0\n   />\n  \n\
> n  \ndata1\n
> d7eb2c38-2707-4774-9873-a7303d024669\n1\n   
>  Started\n apshotCount>0\n2\n
> 2\n1\n
> 0
> \n0\n
> 0\n0\n
> Distribute\n0 sport>\n\n   uuid="08c7ba5f-9aca-49c5-abfd-8a3e42dd8c0b">node1-teste.acloud.pt:/home/brick1node1-teste.acloud.pt:/home/brick10
> 8c7ba5f-9aca-49c5-abfd-8a3e42dd8c0b0\n
>uuid="08c7ba5f-9aca-49c5-abfd-8a3e42dd8c0b">node1-teste.acloud.pt:/brick2nod
> e1-teste.acloud.pt:/brick208c7ba5f-9aca-49c5-abfd-8a3e42dd8c0b0\n
> \n23\n
> \n  \nnfs.disable\n 
>on\n  \n  \n   
>  transport.addre
> ss-family\ninet\n  \n  
> \nstorage.fips-mode-rchecksum\n  
>   on\n
>\n  \n
> storage.owner-uid\n36\n  
> \n  \nstorag
> e.owner-gid\n36\n  \n  
> \ncluster.min-free-disk\n
> 5%\n
>  \n  \n
> performance.quick-read\noff\n 
>  \n  \nperfor
> mance.read-ahead\noff\n  
> \n  \n
> performance.io-cache\noff\n
>\n  \n
> performance.low-prio-threads\n32\n
>   \n  \n<
> name>network.remote-dio\nenable\n  
> \n  \ncluster.eager-lock\n  
>   enable<
> /value>\n  \n  \n
> cluster.quorum-type\nauto\n  
> \n  \n
>   cluster.server-quorum-type\n
> server\n  \n  \n
> cluster.data-self-heal-algorithm\n
>full\n  \n  \n 
>cluster.locking-scheme\n
> granular\n  

[ovirt-users] Host cannot connect to storage domains

[José Ferradeira via Users]

After upgrade to 4.5 host cannot be activated because cannot connect to data 
domain. 

I have a data domain in NFS (master) and a GlusterFS. It complains about the 
Gluster domain: 
The error message for connection node1-teste.acloud.pt:/data1 returned by VDSM 
was: XML error 

# rpm -qa|grep glusterfs* 
glusterfs-10.1-1.el8s.x86_64 
glusterfs-selinux-2.0.1-1.el8s.noarch 
glusterfs-client-xlators-10.1-1.el8s.x86_64 
glusterfs-events-10.1-1.el8s.x86_64 
libglusterfs0-10.1-1.el8s.x86_64 
glusterfs-fuse-10.1-1.el8s.x86_64 
glusterfs-server-10.1-1.el8s.x86_64 
glusterfs-cli-10.1-1.el8s.x86_64 
glusterfs-geo-replication-10.1-1.el8s.x86_64 


engine log: 

2022-04-27 13:35:16,118+01 ERR OR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) [e 
be79c6] EVENT_ID: VDS_STORAGES_CONNECTION_FAILED(188), Failed to connect Host 
NODE1 to the Storage Domains DATA1. 
2022-04-27 13:35:16,169+01 ERR OR 
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) [e 
be79c6] EVENT_ID: STORAGE_DOMAIN_ ERR OR(996), The error message for connection 
node1-teste.acloud.pt:/data1 returned by VDSM was: XML error 
2022-04-27 13:35:16,170+01 ERR OR 
[org.ovirt.engine.core.bll.storage.connection.FileStorageHelper] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-66) 
[ebe79c6 
] The connection with details 'node1-teste.acloud.pt:/data1' failed because of 
error code '4106' and error message is: xml error 



vdsm log: 
2022-04-27 13:40:07,125+0100 ERROR (jsonrpc/4) [storage.storageServer] Could 
not connect to storage server (storageServer:92) 
Traceback (most recent call last): 
File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 90, 
in connect_all 
con.connect() 
File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 
233, in connect 
self.validate() 
File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 
365, in validate 
if not self.volinfo: 
File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 
352, in volinfo 
self._volinfo = self._get_gluster_volinfo() 
File "/usr/lib/python3.6/site-packages/vdsm/storage/storageServer.py", line 
405, in _get_gluster_volinfo 
self._volfileserver) 
File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 56, in 
__call__ 
return callMethod() 
File "/usr/lib/python3.6/site-packages/vdsm/common/supervdsm.py", line 54, in 
 
**kwargs) 
File "", line 2, in glusterVolumeInfo 
File "/usr/lib64/python3.6/multiprocessing/managers.py", line 772, in 
_callmethod 
raise convert_to_error(kind, result) 
vdsm.gluster.exception.GlusterXmlErrorException: XML error: rc=0 out=() 
err=[b'\n 0\n 0\n \n 
\n \ 
n \n data1\n 
d7eb2c38-2707-4774-9873-a7303d024669\n 1\n 
Started\n 0\n 2\n 
2\n 1\n 
0 
\n 0\n 0\n 
0\n Distribute\n 0\n \n node1-teste.acloud.pt:/home/brick1node1-teste.acloud.pt:/home/brick10
 
8c7ba5f-9aca-49c5-abfd-8a3e42dd8c0b0\n
 node1-teste.acloud.pt:/brick2nod
 
e1-teste.acloud.pt:/brick208c7ba5f-9aca-49c5-abfd-8a3e42dd8c0b0\n
 \n 23\n 
\n \n nfs.disable\n on\n 
\n \n transport.addre 
ss-family\n inet\n \n \n 
storage.fips-mode-rchecksum\n on\n 
\n \n storage.owner-uid\n 36\n 
\n \n storag 
e.owner-gid\n 36\n \n \n 
cluster.min-free-disk\n 5%\n 
\n \n performance.quick-read\n 
off\n \n \n perfor 
mance.read-ahead\n off\n \n \n 
performance.io-cache\n off\n 
\n \n performance.low-prio-threads\n 
32\n \n \n < 
name>network.remote-dio\n enable\n \n \n 
cluster.eager-lock\n enable< 
/value>\n \n \n cluster.quorum-type\n 
auto\n \n \n 
cluster.server-quorum-type\n server\n \n 
\n cluster.data-self-heal-algorithm\n 
full\n \n \n 
cluster.locking-scheme\n granular\n  
\n \n cluster.shd-wait-qlength\n 1\n 
\n \n features.shar 
d\n off\n \n \n user.cifs\n 
off\n \n 
\n cluster.choose-local\n off\n \n 
\n client.event-threads\ 
n 4\n \n \n server.event-threads\n 
4\n \n 
\n performance.client-io-threads\n on\n 
\n \n \n 1\ 
n \n \n'] 
2022-04-27 13:40:07,125+0100 INFO (jsonrpc/4) [storage.storagedomaincache] 
Invalidating storage domain cache (sdc:74) 
2022-04-27 13:40:07,125+0100 INFO (jsonrpc/4) [vdsm.api] FINISH 
connectStorageServer return={'statuslist': [{'id': 
'dede3145-651a-4b01-b8d2-82bff8670696', 'status': 4106}]} from= 
:::192.168.5.165,42132, flow_id=4c170005, 
task_id=cec6f36f-46a4-462c-9d0a-feb8d814b465 (api:54) 
2022-04-27 13:40:07,410+0100 INFO (jsonrpc/5) [api.host] START getAllVmStats() 
from=:::192.168.5.165,42132 (api:48) 
2022-04-27 13:40:07,411+0100 INFO (jsonrpc/5) [api.host] FINISH getAllVmStats 
return={'status': {'code': 0, 'message': 'Done'}, 'statsList': (suppressed)} 
from=:::192.168.5.1 
65,42132 (api:54) 
2022-04-27 13:40:07,785+0100 INFO (jsonrpc/7) [api.host] START getStats() 
from=:::192.168.5.165,42132 (api:48) 
2022-04-27 13:40:07,797+0100 INFO 

[ovirt-users] Re: 500 - Internal Server Error

[José Ferradeira via Users]

It worked, thanks 


De: "John"  
Para: users@ovirt.org 
Enviadas: Quarta-feira, 27 De Abril de 2022 12:11:19 
Assunto: [ovirt-users] Re: 500 - Internal Server Error 



downgrade postgresql-jdbc package 

dnf downgrade postgresql-jdbc 

That should fix the problem 
On 27/04/2022 11:36, José Ferradeira via Users wrote: 



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) 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 
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-49: 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 

[ovirt-users] Re: 500 - Internal Server Error

[John]

downgrade postgresql-jdbc package

dnf downgrade postgresql-jdbc

That should fix the problem

On 27/04/2022 11:36, José Ferradeira via Users wrote:

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) 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
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-49: 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 

[ovirt-users] 500 - Internal Server Error

[José Ferradeira via Users]

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) 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 
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-49: 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 

[ovirt-users] convert disk image to thin-provisioned - Ovirt 4.1

[Mohamed Roushdy]

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,
___
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/N34YGZDKQV5P42EAUYVPIDRFEAZUMG4C/

[ovirt-users] Q: Non-Operational Node Hosts - Ghost Network Problem

[Andrei Verovski]

Hi,


I run into nasty and unexpected problem (oVirt 4.4.7.6-1.el8 ) and 2 
non-operational node hosts, which seem relate to ghost network glitch.
Everything worked fine for a very long time until I did the following.

1) Made a backup of several VMs which have network “CloudLink-ISP2”.
2) Moved VM disks into another node hosts, which don’t have link 
“CloudLink-ISP2”, and forgot (preliminary to move) to re-configure network 
interface (remove link to “CloudLink-ISP2”) as I did before..
3) Now I have 2 hosts in non-operational mode which is a really big problem - 
there are only 3 nodes total in a cluster.

I tried to fix this by adding 3rd network “CloudLink-ISP2” to each 
non-operational hosts, and connected ethernet interfaces to a switch.
Unfortunately, it didn’t helped either because for whatever reason link did not 
go up.

How I can remove any reference to “CloudLink-ISP2” from node11 and node14? They 
don’t have any VMs needed that “CloudLink-ISP2”. I edited even inactive VMs and 
removed “CloudLink-ISP2”.
May be there is an option to ignore missing or downed links whn activating node 
hosts?

Thanks in advance for any help.


——

Logs:

2022-04-27 11:16:59,769+03 ERROR 
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) 
[5ab20328] Host 'node14' is set to Non-Operational, it is missing the following 
networks: 'CloudLink-ISP2'
2022-04-27 11:16:59,790+03 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) 
[5ab20328] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host node14 does not 
comply with the cluster ClusterRiga11 networks, the following networks are 
missing on host: 'CloudLink-ISP2'
2022-04-27 11:16:59,884+03 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) 
[55610e1e] EVENT_ID: VDS_DETECTED(13), Status of host node14 was set to 
NonOperational.
2022-04-27 11:16:59,907+03 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-51) 
[5d6ef791] Host 'node14'(aa871d44-94e2-4fdb-aeb3-ca0ae8dc568f) is already in 
NonOperational status for reason 'NETWORK_UNREACHABLE'. SetNonOperationalVds 
command is skipped.

2022-04-27 11:12:26,050+03 ERROR 
[org.ovirt.engine.core.bll.SetNonOperationalVdsCommand] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) 
[5400352e] Host 'node11' is set to Non-Operational, it is missing the following 
networks: 'CloudLink-ISP2'
2022-04-27 11:12:26,070+03 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) 
[5400352e] EVENT_ID: VDS_SET_NONOPERATIONAL_NETWORK(519), Host node11 does not 
comply with the cluster ClusterRiga11 networks, the following networks are 
missing on host: 'CloudLink-ISP2'
2022-04-27 11:12:26,192+03 INFO  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) 
[57d79e54] EVENT_ID: VDS_DETECTED(13), Status of host node11 was set to 
NonOperational.
2022-04-27 11:12:26,214+03 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-19) 
[151821e3] Host 'node11'(3c854f9c-2cdd-423e-bca0-37964ba76702) is already in 
NonOperational status for reason 'NETWORK_UNREACHABLE'. SetNonOperationalVds 
command is skipped.

2022-04-27 11:51:10,539+03 INFO  [org.ovirt.engine.core.vdsbroker.VdsManager] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] 
Clearing domains data for host node14
2022-04-27 11:51:10,539+03 INFO  
[org.ovirt.engine.core.vdsbroker.monitoring.HostMonitoring] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] 
Host 'node14' moved to Non-Operational state because interface/s which are down 
are needed by required network/s in the current cluster: 'eno3 (CloudLink-ISP2)'
2022-04-27 11:51:10,569+03 WARN  
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
(EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-62) [] 
EVENT_ID: VDS_SET_NONOPERATIONAL_IFACE_DOWN(603), Host node14 moved to 
Non-Operational state because interfaces which are down are needed by required 
networks in the current cluster: 'eno3 (CloudLink-ISP2)'.

___
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: 

[ovirt-users] 4.4 to 4.5, lost Gluster Mounts for data and engine

[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=c0fa-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 ~]#
___
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/5IQE3GNBZ4UZ2KAM5YLKETLUNXBJIJXD/

[ovirt-users] Re: (no subject)

[Abe E]

Will do, thanks anyways
___
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/LBN3HABXAWXUPCW5N6VTYVNM42GLUFGH/

[ovirt-users] Re: Issue on Ovirt Node 4.4.10 installation by using DUD for MPTSAS driver update

[Sandro Bonazzola]

Il giorno mer 27 apr 2022 alle ore 09:17  ha
scritto:

> Thank you for the information.
> Could I ask you again if you know any sites I can find a correct DUD for
> MPT SAS?
> This is the link I used below :
> https://elrepo.org/linux/dud/el8/x86_64/
>
> I have tried these files but none of them worked :
>
> dd-mptsas-3.04.20-1.el8_0.elrepo.iso
> dd-mptsas-3.04.20-1.el8_1.elrepo.iso
> dd-mptsas-3.04.20-1.el8_2.elrepo.iso
> dd-mptsas-3.04.20-1.el8_3.elrepo.iso
> dd-mptsas-3.04.20-1.el8_4.elrepo.iso
> dd-mptsas-3.04.20-1.el8_5.elrepo.iso
>
>
elrepo is not working on CentOS Stream, elrepo is at RHEL 8.5 and CentOS
Stream is between 8.6 and 8.7.
I would recommend in this case to go with RHEL 8.5 or clone and oVirt
4.4.10 until 8.6 is out and then upgrade to oVirt 4.5.0.
DUD does not really work fine with oVirt Node.



> Thank you again!
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/PIGDXCGD222VGKWBIEWJKKLLCGWISI7Q/
>


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/YYGSUQA3FTTMU3PAPWRFLMGIUZHYGJN2/

[ovirt-users] Async release for ovirt-engine-ui-extensions (1.3.3)

[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 
- 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 RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
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/GQT42G74E57SUNOIWBXQ2QEJC4VILL4Z/

[ovirt-users] Re: Issue on Ovirt Node 4.4.10 installation by using DUD for MPTSAS driver update

[peter . yu]

Thank you for the information. 
Could I ask you again if you know any sites I can find a correct DUD for MPT 
SAS? 
This is the link I used below :
https://elrepo.org/linux/dud/el8/x86_64/

I have tried these files but none of them worked : 

dd-mptsas-3.04.20-1.el8_0.elrepo.iso
dd-mptsas-3.04.20-1.el8_1.elrepo.iso
dd-mptsas-3.04.20-1.el8_2.elrepo.iso
dd-mptsas-3.04.20-1.el8_3.elrepo.iso
dd-mptsas-3.04.20-1.el8_4.elrepo.iso
dd-mptsas-3.04.20-1.el8_5.elrepo.iso

Thank you again!
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/PIGDXCGD222VGKWBIEWJKKLLCGWISI7Q/

[ovirt-users] Re: (no subject)

[Yedidyah Bar David]

On Wed, Apr 27, 2022 at 9:55 AM Abe E  wrote:
>
> I ran the following: dnf -q list installed centos-release\* ovirt-release\* 
> ovirt-engine
>  and it shows I do have gluster10 which comes with 4.5.
>
> I have checked other threads already but didnt find anything that matched my 
> issue. Can you link what you're referring to?

Nothing special, just what you already did.

> 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.

Sorry, no idea. I suggest to start a new thread with a better subject,
that will help people that might know the answer what it's about.
Thanks.

>
>
> [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

On the new thread, perhaps also list 'rpm -qa | grep gluster'.

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/ZSQ4WHLCXWDSESQEL3RGRKC2SEMMRQC3/

[ovirt-users] Re: upgrade ovirt-engine 4.3 to 4.4. engine.ear problems?

[Yedidyah Bar David]

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: (no subject)

[Abe E]

I ran the following: dnf -q list installed centos-release\* ovirt-release\* 
ovirt-engine
 and it shows I do have gluster10 which comes with 4.5. 

I have checked other threads already but didnt find anything that matched my 
issue. Can you link what you're referring to?
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
___
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/6J7QRFRPL6GMMDA7BHNPE3UMA3MQSDPD/

[ovirt-users] Re: upgrade ovirt-engine 4.3 to 4.4. engine.ear problems?

[Martin Perina]

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?

[Yedidyah Bar David]

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