[ovirt-users] Re: Setting Up oVirt + NFS Storage Issues

[Arden Shackelford]

Just for reference in case anyone else comes across this, I opted to take the 
path of using GlusterFS in place of the NFS storage server that I've got to 
avoid having to make changes to the NFS server.

The glusterfs was setup on the same node, which is actually my preferred way to 
go for this.

Anyway, with the switch to gluster I'm up and running! Very excited to start 
playing with oVirt!

Thanks for the responses here to help me get a better understanding of how this 
stuff works!
___
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/ZQGJ6S4CEYT3L7QTSOQQHNMTDHAHWAQM/

[ovirt-users] Re: 4.2.8 and yum update

[carl langlois]

HI again,

I found out that the vdsm-gluster was not installed on the host I had just
upgraded.. probably a bad manipulation i did g. I will need to be more
careful with the other host
everything seems to be back to normal..
Thanks for your help..
Carl

On Thu, Aug 6, 2020 at 4:49 PM carl langlois  wrote:

> Hi ,
>
> I was able to update to ovirt 4.2.8 on one of my host using 7.6 centos
> repo like Alex suggested. But now when i try to activate it i get this
> error in the engine log
>
> 020-08-06 16:43:44,903-04 INFO
>  [org.ovirt.engine.core.vdsbroker.gluster.ManageGlusterServiceVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-97)
> [51530ac3-6864-47fd-8910-9c1a2a825da8] START,
> ManageGlusterServiceVDSCommand(HostName = ovhost3,
> GlusterServiceVDSParameters:{hostId='c85cd64e-94ff-4b0f-a9a0-c888d348b1aa'}),
> log id: 5677f568
> 2020-08-06 16:43:44,970-04
> * ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-97)
> [51530ac3-6864-47fd-8910-9c1a2a825da8] EVENT_ID:
> VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovhost3 command
> ManageGlusterServiceVDS failed: The method does not exist or is not
> available: {'method': u'GlusterService.action'}2020-08-06 16:43:44,970-04
> ERROR
> [org.ovirt.engine.core.vdsbroker.gluster.ManageGlusterServiceVDSCommand]
> (EE-ManagedThreadFactory-engine-Thread-97)
> [51530ac3-6864-47fd-8910-9c1a2a825da8] Command
> 'ManageGlusterServiceVDSCommand(HostName = ovhost3,
> GlusterServiceVDSParameters:{hostId='c85cd64e-94ff-4b0f-a9a0-c888d348b1aa'})'
> execution failed: VDSGenericException: VDSErrorException: Failed to
> ManageGlusterServiceVDS, error = The method does not exist or is not
> available: {'method': u'GlusterService.action'}, code = -32601*
> 2020-08-06 16:43:44,970-04 INFO
>  [org.ovirt.engine.core.bll.ActivateVdsCommand]
> (EE-ManagedThreadFactory-engine-Thread-97)
> [51530ac3-6864-47fd-8910-9c1a2a825da8] Activate host finished. Lock
> released. Monitoring can run now for host 'ovhost3' from data-center
> 'Default'
> 2020-08-06 16:43:44,983-04 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engine-Thread-97)
> [51530ac3-6864-47fd-8910-9c1a2a825da8] EVENT_ID: VDS_ACTIVATE_FAILED(18),
> Failed to activate Host ovhost3.(User: admin@internal-authz
>
> after that the host end up in unassign.
> my engine is also on 4.2.8
>
> any suggestions will be appreciated.
>
> Regards
> Carl
>
> On Thu, Aug 6, 2020 at 11:42 AM carl langlois 
> wrote:
>
>> Hi,
>>
>> Thanks for the suggestion. I will try it.
>> But at one point I will need to update the OS past 7.6 as 4.3.9 needs 7.7
>> or later.
>>
>> Regards
>> Carl
>>
>>
>>
>> On Thu, Aug 6, 2020 at 9:49 AM Alex K  wrote:
>>
>>> Hi
>>>
>>> On Thu, Aug 6, 2020 at 3:45 PM carl langlois 
>>> wrote:
>>>
 Hi all,

 I am in the process of upgrading our cluster to 4.3. But first i need
 to update everything to 4.2.8 and update the os to the latest 7.x. I was
 able to update the self-hosted engine to the latest 4.2.8 and centos 7.8.
 But when i tried to update the host yum update got broken gluster
 packages.
 The current host that i'm trying to update is on 7.5. If i look at the
 release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve
 this.
 Any suggestions?.

>>> you need to amend  /etc/yum.repos.d/ovirt-4.2-dependencies.repo and edit
>>> the repos that contain the name ovirt-4.2 as following:
>>>
>>> from: *mirror.centos.org/centos/7 *
>>> to: *vault.centos.org/centos/7.6.1810
>>> *
>>>
>>> You will need to amend also base repo to avoid centos going to 7.8, as
>>> you will face dependency issues with 4.2.  You can point base repo at
>>> 7.6.1810, yum update, then follow upgrade to 4.3.
>>> For the base repo you need to comment out mirrorlist lines, uncomment
>>> baseurl and replace mirror.centos.org/centos/$releasever with
>>> *vault.centos.org/centos/7.6.1810
>>> . *
>>> Just followed this path the previous days and managed to complete the
>>> upgrade from 4.2 to 4.3.
>>> Good luck.
>>>

 Carl
 ___
 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/QTPJBNLETMHMDHBJXCGTIHRY53UTBJFK/

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

[ovirt-users] Re: 4.2.8 and yum update

[carl langlois]

Hi ,

I was able to update to ovirt 4.2.8 on one of my host using 7.6 centos repo
like Alex suggested. But now when i try to activate it i get this error in
the engine log

020-08-06 16:43:44,903-04 INFO
 [org.ovirt.engine.core.vdsbroker.gluster.ManageGlusterServiceVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-97)
[51530ac3-6864-47fd-8910-9c1a2a825da8] START,
ManageGlusterServiceVDSCommand(HostName = ovhost3,
GlusterServiceVDSParameters:{hostId='c85cd64e-94ff-4b0f-a9a0-c888d348b1aa'}),
log id: 5677f568
2020-08-06 16:43:44,970-04
* ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-97)
[51530ac3-6864-47fd-8910-9c1a2a825da8] EVENT_ID:
VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovhost3 command
ManageGlusterServiceVDS failed: The method does not exist or is not
available: {'method': u'GlusterService.action'}2020-08-06 16:43:44,970-04
ERROR
[org.ovirt.engine.core.vdsbroker.gluster.ManageGlusterServiceVDSCommand]
(EE-ManagedThreadFactory-engine-Thread-97)
[51530ac3-6864-47fd-8910-9c1a2a825da8] Command
'ManageGlusterServiceVDSCommand(HostName = ovhost3,
GlusterServiceVDSParameters:{hostId='c85cd64e-94ff-4b0f-a9a0-c888d348b1aa'})'
execution failed: VDSGenericException: VDSErrorException: Failed to
ManageGlusterServiceVDS, error = The method does not exist or is not
available: {'method': u'GlusterService.action'}, code = -32601*
2020-08-06 16:43:44,970-04 INFO
 [org.ovirt.engine.core.bll.ActivateVdsCommand]
(EE-ManagedThreadFactory-engine-Thread-97)
[51530ac3-6864-47fd-8910-9c1a2a825da8] Activate host finished. Lock
released. Monitoring can run now for host 'ovhost3' from data-center
'Default'
2020-08-06 16:43:44,983-04 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-97)
[51530ac3-6864-47fd-8910-9c1a2a825da8] EVENT_ID: VDS_ACTIVATE_FAILED(18),
Failed to activate Host ovhost3.(User: admin@internal-authz

after that the host end up in unassign.
my engine is also on 4.2.8

any suggestions will be appreciated.

Regards
Carl

On Thu, Aug 6, 2020 at 11:42 AM carl langlois 
wrote:

> Hi,
>
> Thanks for the suggestion. I will try it.
> But at one point I will need to update the OS past 7.6 as 4.3.9 needs 7.7
> or later.
>
> Regards
> Carl
>
>
>
> On Thu, Aug 6, 2020 at 9:49 AM Alex K  wrote:
>
>> Hi
>>
>> On Thu, Aug 6, 2020 at 3:45 PM carl langlois 
>> wrote:
>>
>>> Hi all,
>>>
>>> I am in the process of upgrading our cluster to 4.3. But first i need to
>>> update everything to 4.2.8 and update the os to the latest 7.x. I was able
>>> to update the self-hosted engine to the latest 4.2.8 and centos 7.8. But
>>> when i tried to update the host yum update got broken gluster packages.
>>> The current host that i'm trying to update is on 7.5. If i look at the
>>> release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve
>>> this.
>>> Any suggestions?.
>>>
>> you need to amend  /etc/yum.repos.d/ovirt-4.2-dependencies.repo and edit
>> the repos that contain the name ovirt-4.2 as following:
>>
>> from: *mirror.centos.org/centos/7 *
>> to: *vault.centos.org/centos/7.6.1810
>> *
>>
>> You will need to amend also base repo to avoid centos going to 7.8, as
>> you will face dependency issues with 4.2.  You can point base repo at
>> 7.6.1810, yum update, then follow upgrade to 4.3.
>> For the base repo you need to comment out mirrorlist lines, uncomment
>> baseurl and replace mirror.centos.org/centos/$releasever with
>> *vault.centos.org/centos/7.6.1810
>> . *
>> Just followed this path the previous days and managed to complete the
>> upgrade from 4.2 to 4.3.
>> Good luck.
>>
>>>
>>> Carl
>>> ___
>>> 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/QTPJBNLETMHMDHBJXCGTIHRY53UTBJFK/
>>>
>>
___
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/AZTIFQWILQVW4LUXRCF2JHEFJBYM5QYU/

[ovirt-users] Re: 4.2.8 and yum update

[Alex K]

On Thu, Aug 6, 2020 at 6:42 PM carl langlois  wrote:

> Hi,
>
> Thanks for the suggestion. I will try it.
> But at one point I will need to update the OS past 7.6 as 4.3.9 needs 7.7
> or later.
>
At that point you just switch back your repos at their previous state,
install 4.3 repo, and proceed with your major upgrade. In this way centos
will upgrade also to latest (7.8.2003) Upon completion of the major
upgrade, you remove 4.2 repo.

>
> Regards
> Carl
>
>
>
> On Thu, Aug 6, 2020 at 9:49 AM Alex K  wrote:
>
>> Hi
>>
>> On Thu, Aug 6, 2020 at 3:45 PM carl langlois 
>> wrote:
>>
>>> Hi all,
>>>
>>> I am in the process of upgrading our cluster to 4.3. But first i need to
>>> update everything to 4.2.8 and update the os to the latest 7.x. I was able
>>> to update the self-hosted engine to the latest 4.2.8 and centos 7.8. But
>>> when i tried to update the host yum update got broken gluster packages.
>>> The current host that i'm trying to update is on 7.5. If i look at the
>>> release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve
>>> this.
>>> Any suggestions?.
>>>
>> you need to amend  /etc/yum.repos.d/ovirt-4.2-dependencies.repo and edit
>> the repos that contain the name ovirt-4.2 as following:
>>
>> from: *mirror.centos.org/centos/7 *
>> to: *vault.centos.org/centos/7.6.1810
>> *
>>
>> You will need to amend also base repo to avoid centos going to 7.8, as
>> you will face dependency issues with 4.2.  You can point base repo at
>> 7.6.1810, yum update, then follow upgrade to 4.3.
>> For the base repo you need to comment out mirrorlist lines, uncomment
>> baseurl and replace mirror.centos.org/centos/$releasever with
>> *vault.centos.org/centos/7.6.1810
>> . *
>> Just followed this path the previous days and managed to complete the
>> upgrade from 4.2 to 4.3.
>> Good luck.
>>
>>>
>>> Carl
>>> ___
>>> 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/QTPJBNLETMHMDHBJXCGTIHRY53UTBJFK/
>>>
>>
___
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/5QPGHL6KIAX32O7KTW3LIBU5GCAU4P64/

[ovirt-users] Re: Has anyone ever had success importing an OVA VM exported from oVirt to VirtualBox or VMware? On Windows?

[Gianluca Cecchi]

On Thu, Aug 6, 2020 at 6:33 PM  wrote:

> I have tried importing oVirt exported VMs (which correctly imported and
> ran on a second oVirt host) both on VMware workstation 15.5.6 and
> VirtualBox 6.1.12 running on a Windows 2019 host without success.
>
> I've also tried untaring the *.ova into the component *.ovf + image file,
> but the issue seems to be with the XML description which has both imports
> fail pretty much instantly, before they even read the disk image file.
>
> From what I can tell, the XML created by qemu-img looks just fine, the
> error messages emitted by both products are very sparse and seem misleading.
>
>
Just a guess, but have you already tried to do a similar VM OVA export from
Virtualbox (or vSphere) and try to compare the generated xm, so to
"accommodate" the oVirt generated one and recomposing the ova and retrying
the import...?

Gianluca
___
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/HBESJS4DMQR3BLM3LGTCW2276X5NRTC4/

[ovirt-users] Has anyone ever had success importing an OVA VM exported from oVirt to VirtualBox or VMware? On Windows?

[thomas]

After applying the OVA export patch, that ensured disk content was actually 
written ino the OVA image, I have been able to transfer *.ova VMs between two 
oVirt clusters. There are still problems that I will report once I have fully 
tested what's going on, but in the mean-time for all those, who want to be able 
to move VMs not only in the direction of oVirt (seems well tested), but also 
the other way (e.g. local desktop use, or even a vSphere farm) an OVA export 
could be a life saver--if it worked.

I have tried importing oVirt exported VMs (which correctly imported and ran on 
a second oVirt host) both on VMware workstation 15.5.6 and VirtualBox 6.1.12 
running on a Windows 2019 host without success.

I've also tried untaring the *.ova into the component *.ovf + image file, but 
the issue seems to be with the XML description which has both imports fail 
pretty much instantly, before they even read the disk image file.

From what I can tell, the XML created by qemu-img looks just fine, the error 
messages emitted by both products are very sparse and seem misleading.

E.g. VirtualBox complains "Empty element ResourceType under Item element, line 
1.", while I see all  well constructed with a ResourceType in every one 
of them.

VMware Workstation is completely useless in terms of log-file-diagnostics: It 
reports an invalid value for the "populatedSize" for the "Disk", but doesn't 
log that to the ovftool.log. I am pretty sure the error is in the inconsistent 
interpretation of this section, where the AllocationUnits, capacity and 
populatedSize leave some room for misinterpretation:

-

List of Virtual Disks

http://www.vmware.com/specifications/vmdk.html#sparse; 
ovf:fileRef="974ad04f-d9bb-4881-aad2-c1d5404200ef" ovf:parentRef="" 
ovf:populatedSize="536953094144" ovf:capacityAllocationUnits="byte * 2^30" 
ovf:capacity="500" ovf:diskId="02b8d976-7e42-44e7-8e24-06f974f1c3ea"/>



I am trying to import the *.ova files on a Windows host and the sparsity get 
typically lost on the scp file transfer, too.

Yes, this most likely isn't an oVirt bug, qemu-img is maintained elsewhere and 
the problem to me looks more on the receiver side.

But have you tried it? Can you imagine it being important, too?
___
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/YQI3ZUSZHKPDCHG6ECNBCPQ472HLQTAZ/

[ovirt-users] Re: 4.2.8 and yum update

[carl langlois]

Hi,

Thanks for the suggestion. I will try it.
But at one point I will need to update the OS past 7.6 as 4.3.9 needs 7.7
or later.

Regards
Carl



On Thu, Aug 6, 2020 at 9:49 AM Alex K  wrote:

> Hi
>
> On Thu, Aug 6, 2020 at 3:45 PM carl langlois 
> wrote:
>
>> Hi all,
>>
>> I am in the process of upgrading our cluster to 4.3. But first i need to
>> update everything to 4.2.8 and update the os to the latest 7.x. I was able
>> to update the self-hosted engine to the latest 4.2.8 and centos 7.8. But
>> when i tried to update the host yum update got broken gluster packages.
>> The current host that i'm trying to update is on 7.5. If i look at the
>> release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve
>> this.
>> Any suggestions?.
>>
> you need to amend  /etc/yum.repos.d/ovirt-4.2-dependencies.repo and edit
> the repos that contain the name ovirt-4.2 as following:
>
> from: *mirror.centos.org/centos/7 *
> to: *vault.centos.org/centos/7.6.1810
> *
>
> You will need to amend also base repo to avoid centos going to 7.8, as you
> will face dependency issues with 4.2.  You can point base repo at 7.6.1810,
> yum update, then follow upgrade to 4.3.
> For the base repo you need to comment out mirrorlist lines, uncomment
> baseurl and replace mirror.centos.org/centos/$releasever with
> *vault.centos.org/centos/7.6.1810
> . *
> Just followed this path the previous days and managed to complete the
> upgrade from 4.2 to 4.3.
> Good luck.
>
>>
>> Carl
>> ___
>> 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/QTPJBNLETMHMDHBJXCGTIHRY53UTBJFK/
>>
>
___
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/LY7YCA7OWVB2QTKFZRKN4MG3W6BNWP62/

[ovirt-users] [ANN] oVirt 4.4.2 Second Release Candidate is now available for testing

[Lev Veyde]

oVirt 4.4.2 Second Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.2
Second Release Candidate for testing, as of August 6th, 2020.

This update is the second in a series of stabilization updates to the 4.4
series.
Important notes before you try it

Please note this is a pre-release build.

The oVirt Project makes no guarantees as to its suitability or usefulness.

This pre-release must not be used in production.
Installation instructions

For the engine: either use appliance or:

- Install CentOS Linux 8.2 minimal from:

https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004-x86_64-minimal.iso

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- dnf module enable -y javapackages-tools pki-deps postgresql:12

- dnf install ovirt-engine

- engine-setup

For the nodes:

Either use oVirt Node ISO or:

- Install CentOS Linux 8.2 from

https://mirrors.edge.kernel.org/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004-x86_64-minimal.iso
; select minimal installation

- dnf install
https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm

- dnf update (reboot if needed)

- Attach the host to the engine and let it be deployed.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

* Red Hat Enterprise Linux 8.2 or newer

* CentOS Linux (or similar) 8.2 or newer

* oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)

See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

- oVirt Appliance is already available for CentOS Linux 8

- oVirt Node NG is already available for CentOS Linux 8

Additional Resources:

* Read more about the oVirt 4.4.2 release highlights:
http://www.ovirt.org/release/4.4.2/

* Get more oVirt project updates on Twitter: https://twitter.com/ovirt

* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.2/

[2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel



l...@redhat.com | lve...@redhat.com

TRIED. TESTED. TRUSTED. 
___
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/GAYKPI6NOVZ6XRS75UYMY65JKZBGB4XG/

[ovirt-users] Re: oVirt Hyperconverged question

[thomas]

I have done that, even added five nodes that contribute a separate Gluster file 
system using dispersed (erasure codes, more efficient) mode.

But in another cluster with such a 3-node-HCI base, I had a lot (3 or 4) of 
compute nodes, that were actually dual-boot or just shut off when not used: 
Even used the GUI to do that properly.

This caused strange issues as I shut down all three compute-only nodes: Gluster 
reported loss of quorum, and essentially the entire HCI lost storage, even if 
these compute nodes didn't add bricks to the Gluster at all. In fact the 
compute nodes probably shouldn't have even participated in the Gluster, since 
they were only clients, but the Cockpit wizard added them anyway.

I believe this is because HCI is designed to support adding extra nodes in sets 
of three e.g. for a 9-node setup, which should be really nice with 7+2 disperse 
encoding.

I didn't dare reproduce the situation intentionally, but if you should come 
across this, perhaps you can document and report it. If the (most of) extra 
nodes are permanently running, you don't need to worry.

In terms of regaining control, you mostly have to make sure you turn the 
missing nodes back on, oVirt can be astonishingly resilient. If you then remove 
the nodes prior to shutdown, the quorum issue goes away.
___
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/A4EDM3RYVIYXZ5QAJO4VOYKQUDWYDA4P/

[ovirt-users] Re: Unassigned hosts

[Martin Perina]

Hi Nardus,

I'm assuming that your setup was stable and you were able to run your VMs
without problems. If so, then below is not a solution to your problem, you
should really check engine and VDSM logs for reasons why your hosts become
NonResponsive. Most probably there is underlying storage or network issue
which prevents correct engine <-> hosts communications and which made your
hosts NonResponsive. The solution below will just hide the issues you
currently have.

If your problem started suddenly when you significantly increased the
number of running VMs or decreased the number of available hosts, then you
are suffering from those issues because of not having enough resources.

Regards,
Martin

On Thu, Aug 6, 2020 at 4:51 PM Artur Socha  wrote:

> Thanks Nardus,
> After a quick look I found what I was suspecting - there are way too many
> threads in Blocked state. I don't know yet the reason but this is very
> helpful. I'll let you know about the findings/investigation. Meanwhile, you
> may try restarting the engine as (a very brute and ugly) workaround).
> You may try to setup slightly bigger thread pool - may save you some time
> until the next hiccup. However, please be aware that this may come with the
> cost in memory usage and higher cpu usage (due to increased context
> switching)
> Here are some docs:
>
> # Specify the thread pool size for jboss managed scheduled executor service 
> used by commands to periodically execute
> # methods. It is generally not necessary to increase the number of threads in 
> this thread pool. To change the value
> # permanently create a conf file 99-engine-scheduled-thread-pool.conf in 
> /etc/ovirt-engine/engine.conf.d/
> ENGINE_SCHEDULED_THREAD_POOL_SIZE=100
>
>
> A.
>
>
> On Thu, Aug 6, 2020 at 4:19 PM Nardus Geldenhuys 
> wrote:
>
>> Hi Artur
>>
>> Please find attached, also let me know if I need to rerun. They 5 min
>> apart
>>
>> [root@engine-aa-1-01 ovirt-engine]#  ps -ef | grep jboss | grep -v grep
>> | awk '{ print $2 }'
>> 27390
>> [root@engine-aa-1-01 ovirt-engine]# jstack -F 27390 >
>> your_engine_thread_dump_1.txt
>> [root@engine-aa-1-01 ovirt-engine]# jstack -F 27390 >
>> your_engine_thread_dump_2.txt
>> [root@engine-aa-1-01 ovirt-engine]# jstack -F 27390 >
>> your_engine_thread_dump_3.txt
>>
>> Regards
>>
>> Nar
>>
>> On Thu, 6 Aug 2020 at 15:55, Artur Socha  wrote:
>>
>>> Sure thing.
>>> On engine host please find  jboss pid. You can use this command:
>>>
>>>  ps -ef | grep jboss | grep -v grep | awk '{ print $2 }'
>>>
>>> or jps tool from jdk. Sample output on my dev environment is:
>>>
>>> ± % jps
>>>!2860
>>> 64853 jboss-modules.jar
>>> 196217 Jps
>>>
>>> Then use jstack from jdk:
>>> jstack   > your_engine_thread_dump.txt
>>> 2 or 3 dumps taken in approximately 5 minutes intervals would be even
>>> more useful.
>>>
>>> Here you can find even more options
>>> https://www.baeldung.com/java-thread-dump
>>>
>>> Artur
>>>
>>> On Thu, Aug 6, 2020 at 3:15 PM Nardus Geldenhuys 
>>> wrote:
>>>
 Hi

 Can create thread dump, please send details on howto.

 Regards

 Nardus

 On Thu, 6 Aug 2020 at 14:17, Artur Socha  wrote:

> Hi Nardus,
> You might have hit an issue I have been hunting for some time ( [1]
> and  [2] ).
> [1] could not be properly resolved because at a time was not able to
> recreate an issue on dev setup.
> I suspect [2] is related.
>
> Would you be able to prepare a thread dump from your engine instance?
> Additionally, please check for potential libvirt errors/warnings.
> Can you also paste the output of:
> sudo yum list installed | grep vdsm
> sudo yum list installed | grep ovirt-engine
> sudo yum list installed | grep libvirt
>
> Usually, according to previous reports, restarting the engine helps to
> restore connectivity with hosts ... at least for some time.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1845152
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1846338
>
> regards,
> Artur
>
>
>
> On Thu, Aug 6, 2020 at 8:01 AM Nardus Geldenhuys 
> wrote:
>
>> Also see this in engine:
>>
>> Aug 6, 2020, 7:37:17 AM
>> VDSM someserver command Get Host Capabilities failed: Message timeout
>> which can be caused by communication issues
>>
>> On Thu, 6 Aug 2020 at 07:09, Strahil Nikolov 
>> wrote:
>>
>>> Can you fheck for errors on the affected host. Most probably you
>>> need the vdsm logs.
>>>
>>> Best Regards,
>>> Strahil Nikolov
>>>
>>> На 6 август 2020 г. 7:40:23 GMT+03:00, Nardus Geldenhuys <
>>> nard...@gmail.com> написа:
>>> >Hi Strahil
>>> >
>>> >Hope you are well. I get the following error when I tried to confirm
>>> >reboot:
>>> >
>>> >Error while executing action: Cannot confirm 'Host has been
>>> rebooted'
>>> >Host.

[ovirt-users] Re: Thin Provisioned to Preallocated

[thomas]

If OVA export and import work for you, you get to chose between the two at 
import.
___
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/A66DP3GH3C32MFPDUHAZR3GZLXOL7UXG/

[ovirt-users] Re: Unassigned hosts

[Artur Socha]

Thanks Nardus,
After a quick look I found what I was suspecting - there are way too many
threads in Blocked state. I don't know yet the reason but this is very
helpful. I'll let you know about the findings/investigation. Meanwhile, you
may try restarting the engine as (a very brute and ugly) workaround).
You may try to setup slightly bigger thread pool - may save you some time
until the next hiccup. However, please be aware that this may come with the
cost in memory usage and higher cpu usage (due to increased context
switching)
Here are some docs:

# Specify the thread pool size for jboss managed scheduled executor
service used by commands to periodically execute
# methods. It is generally not necessary to increase the number of
threads in this thread pool. To change the value
# permanently create a conf file 99-engine-scheduled-thread-pool.conf
in /etc/ovirt-engine/engine.conf.d/
ENGINE_SCHEDULED_THREAD_POOL_SIZE=100


A.


On Thu, Aug 6, 2020 at 4:19 PM Nardus Geldenhuys  wrote:

> Hi Artur
>
> Please find attached, also let me know if I need to rerun. They 5 min apart
>
> [root@engine-aa-1-01 ovirt-engine]#  ps -ef | grep jboss | grep -v grep |
> awk '{ print $2 }'
> 27390
> [root@engine-aa-1-01 ovirt-engine]# jstack -F 27390 >
> your_engine_thread_dump_1.txt
> [root@engine-aa-1-01 ovirt-engine]# jstack -F 27390 >
> your_engine_thread_dump_2.txt
> [root@engine-aa-1-01 ovirt-engine]# jstack -F 27390 >
> your_engine_thread_dump_3.txt
>
> Regards
>
> Nar
>
> On Thu, 6 Aug 2020 at 15:55, Artur Socha  wrote:
>
>> Sure thing.
>> On engine host please find  jboss pid. You can use this command:
>>
>>  ps -ef | grep jboss | grep -v grep | awk '{ print $2 }'
>>
>> or jps tool from jdk. Sample output on my dev environment is:
>>
>> ± % jps
>>  !2860
>> 64853 jboss-modules.jar
>> 196217 Jps
>>
>> Then use jstack from jdk:
>> jstack   > your_engine_thread_dump.txt
>> 2 or 3 dumps taken in approximately 5 minutes intervals would be even
>> more useful.
>>
>> Here you can find even more options
>> https://www.baeldung.com/java-thread-dump
>>
>> Artur
>>
>> On Thu, Aug 6, 2020 at 3:15 PM Nardus Geldenhuys 
>> wrote:
>>
>>> Hi
>>>
>>> Can create thread dump, please send details on howto.
>>>
>>> Regards
>>>
>>> Nardus
>>>
>>> On Thu, 6 Aug 2020 at 14:17, Artur Socha  wrote:
>>>
 Hi Nardus,
 You might have hit an issue I have been hunting for some time ( [1]
 and  [2] ).
 [1] could not be properly resolved because at a time was not able to
 recreate an issue on dev setup.
 I suspect [2] is related.

 Would you be able to prepare a thread dump from your engine instance?
 Additionally, please check for potential libvirt errors/warnings.
 Can you also paste the output of:
 sudo yum list installed | grep vdsm
 sudo yum list installed | grep ovirt-engine
 sudo yum list installed | grep libvirt

 Usually, according to previous reports, restarting the engine helps to
 restore connectivity with hosts ... at least for some time.

 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1845152
 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1846338

 regards,
 Artur



 On Thu, Aug 6, 2020 at 8:01 AM Nardus Geldenhuys 
 wrote:

> Also see this in engine:
>
> Aug 6, 2020, 7:37:17 AM
> VDSM someserver command Get Host Capabilities failed: Message timeout
> which can be caused by communication issues
>
> On Thu, 6 Aug 2020 at 07:09, Strahil Nikolov 
> wrote:
>
>> Can you fheck for errors on the affected host. Most probably you need
>> the vdsm logs.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> На 6 август 2020 г. 7:40:23 GMT+03:00, Nardus Geldenhuys <
>> nard...@gmail.com> написа:
>> >Hi Strahil
>> >
>> >Hope you are well. I get the following error when I tried to confirm
>> >reboot:
>> >
>> >Error while executing action: Cannot confirm 'Host has been rebooted'
>> >Host.
>> >Valid Host statuses are "Non operational", "Maintenance" or
>> >"Connecting".
>> >
>> >And I can't put it in maintenance, only option is "restart" or
>> "stop".
>> >
>> >Regards
>> >
>> >Nar
>> >
>> >On Thu, 6 Aug 2020 at 06:16, Strahil Nikolov 
>> >wrote:
>> >
>> >> After rebooting the node, have you "marked" it that it was
>> rebooted ?
>> >>
>> >> Best Regards,
>> >> Strahil Nikolov
>> >>
>> >> На 5 август 2020 г. 21:29:04 GMT+03:00, Nardus Geldenhuys <
>> >> nard...@gmail.com> написа:
>> >> >Hi oVirt land
>> >> >
>> >> >Hope you are well. Got a bit of an issue, actually a big issue. We
>> >had
>> >> >some
>> >> >sort of dip of some sort. All the VM's is still running, but some
>> of
>> >> >the
>> >> >hosts is show "Unassigned" or "NonResponsive". So all the hosts
>> was
>> >> 

[ovirt-users] Thin Provisioned to Preallocated

[Jorge Visentini]

Hi oVirt land.

Can I convert the disks of Thin Provision to Preallocated?

Best Regards.
-- 
Att,
Jorge Visentini
+55 55 98432-9868
___
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/M5DGZFUB5KVW6LWQKRC5NFDUMOUN7RKD/

[ovirt-users] Re: Unassigned hosts

[Artur Socha]

Sure thing.
On engine host please find  jboss pid. You can use this command:

 ps -ef | grep jboss | grep -v grep | awk '{ print $2 }'

or jps tool from jdk. Sample output on my dev environment is:

± % jps
   !2860
64853 jboss-modules.jar
196217 Jps

Then use jstack from jdk:
jstack   > your_engine_thread_dump.txt
2 or 3 dumps taken in approximately 5 minutes intervals would be even more
useful.

Here you can find even more options
https://www.baeldung.com/java-thread-dump

Artur

On Thu, Aug 6, 2020 at 3:15 PM Nardus Geldenhuys  wrote:

> Hi
>
> Can create thread dump, please send details on howto.
>
> Regards
>
> Nardus
>
> On Thu, 6 Aug 2020 at 14:17, Artur Socha  wrote:
>
>> Hi Nardus,
>> You might have hit an issue I have been hunting for some time ( [1] and
>> [2] ).
>> [1] could not be properly resolved because at a time was not able to
>> recreate an issue on dev setup.
>> I suspect [2] is related.
>>
>> Would you be able to prepare a thread dump from your engine instance?
>> Additionally, please check for potential libvirt errors/warnings.
>> Can you also paste the output of:
>> sudo yum list installed | grep vdsm
>> sudo yum list installed | grep ovirt-engine
>> sudo yum list installed | grep libvirt
>>
>> Usually, according to previous reports, restarting the engine helps to
>> restore connectivity with hosts ... at least for some time.
>>
>> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1845152
>> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1846338
>>
>> regards,
>> Artur
>>
>>
>>
>> On Thu, Aug 6, 2020 at 8:01 AM Nardus Geldenhuys 
>> wrote:
>>
>>> Also see this in engine:
>>>
>>> Aug 6, 2020, 7:37:17 AM
>>> VDSM someserver command Get Host Capabilities failed: Message timeout
>>> which can be caused by communication issues
>>>
>>> On Thu, 6 Aug 2020 at 07:09, Strahil Nikolov 
>>> wrote:
>>>
 Can you fheck for errors on the affected host. Most probably you need
 the vdsm logs.

 Best Regards,
 Strahil Nikolov

 На 6 август 2020 г. 7:40:23 GMT+03:00, Nardus Geldenhuys <
 nard...@gmail.com> написа:
 >Hi Strahil
 >
 >Hope you are well. I get the following error when I tried to confirm
 >reboot:
 >
 >Error while executing action: Cannot confirm 'Host has been rebooted'
 >Host.
 >Valid Host statuses are "Non operational", "Maintenance" or
 >"Connecting".
 >
 >And I can't put it in maintenance, only option is "restart" or "stop".
 >
 >Regards
 >
 >Nar
 >
 >On Thu, 6 Aug 2020 at 06:16, Strahil Nikolov 
 >wrote:
 >
 >> After rebooting the node, have you "marked" it that it was rebooted ?
 >>
 >> Best Regards,
 >> Strahil Nikolov
 >>
 >> На 5 август 2020 г. 21:29:04 GMT+03:00, Nardus Geldenhuys <
 >> nard...@gmail.com> написа:
 >> >Hi oVirt land
 >> >
 >> >Hope you are well. Got a bit of an issue, actually a big issue. We
 >had
 >> >some
 >> >sort of dip of some sort. All the VM's is still running, but some of
 >> >the
 >> >hosts is show "Unassigned" or "NonResponsive". So all the hosts was
 >> >showing
 >> >UP and was fine before our dip. So I did increase
 >vdsHeartbeatInSecond
 >> >to
 >> >240, no luck.
 >> >
 >> >I still get a timeout on the engine lock even thou I can connect to
 >> >that
 >> >host from the engine using nc to test to port 54321. I also did
 >restart
 >> >vdsmd and also rebooted the host with no luck.
 >> >
 >> > nc -v someserver 54321
 >> >Ncat: Version 7.50 ( https://nmap.org/ncat )
 >> >Ncat: Connected to 172.40.2.172:54321.
 >> >
 >> >2020-08-05 20:20:34,256+02 ERROR
 >>
 >>[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
 >> >(EE-ManagedThreadFactory-engineScheduled-Thread-70) [] EVENT_ID:
 >> >VDS_BROKER_COMMAND_FAILURE(10,802), VDSM someserver command Get Host
 >> >Capabilities failed: Message timeout which can be caused by
 >> >communication
 >> >issues
 >> >
 >> >Any troubleshoot ideas will be gladly appreciated.
 >> >
 >> >Regards
 >> >
 >> >Nar
 >>

>>> ___
>>> 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/C4HB2J3MH76FI2325Z4AV4VCCEKH4M3S/
>>>
>>
>>
>> --
>> Artur Socha
>> Senior Software Engineer, RHV
>> Red Hat
>>
>

-- 
Artur Socha
Senior Software Engineer, RHV
Red Hat
___
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 

[ovirt-users] Re: 4.2.8 and yum update

[Alex K]

Hi

On Thu, Aug 6, 2020 at 3:45 PM carl langlois  wrote:

> Hi all,
>
> I am in the process of upgrading our cluster to 4.3. But first i need to
> update everything to 4.2.8 and update the os to the latest 7.x. I was able
> to update the self-hosted engine to the latest 4.2.8 and centos 7.8. But
> when i tried to update the host yum update got broken gluster packages.
> The current host that i'm trying to update is on 7.5. If i look at the
> release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve
> this.
> Any suggestions?.
>
you need to amend  /etc/yum.repos.d/ovirt-4.2-dependencies.repo and edit
the repos that contain the name ovirt-4.2 as following:

from: *mirror.centos.org/centos/7 *
to: *vault.centos.org/centos/7.6.1810
*

You will need to amend also base repo to avoid centos going to 7.8, as you
will face dependency issues with 4.2.  You can point base repo at 7.6.1810,
yum update, then follow upgrade to 4.3.
For the base repo you need to comment out mirrorlist lines, uncomment
baseurl and replace mirror.centos.org/centos/$releasever with
*vault.centos.org/centos/7.6.1810
. *
Just followed this path the previous days and managed to complete the
upgrade from 4.2 to 4.3.
Good luck.

>
> Carl
> ___
> 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/QTPJBNLETMHMDHBJXCGTIHRY53UTBJFK/
>
___
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/FWTNCPRIPY6XONQG32WIGROOQKGENLQC/

[ovirt-users] Re: 4.2.8 and yum update

[carl langlois]

Here is a sample os the error :

 glusterfs = 3.12.15-1.el7
Error: Package: glusterfs-server-3.12.15-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   Requires: glusterfs-api = 3.12.15-1.el7
   Removing: glusterfs-api-3.12.11-1.el7.x86_64
(@ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.11-1.el7
   Updated By: glusterfs-api-6.0-29.el7.x86_64 (base)
   glusterfs-api = 6.0-29.el7
   Available: glusterfs-api-3.12.0-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.0-1.el7
   Available: glusterfs-api-3.12.1-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.1-1.el7
   Available: glusterfs-api-3.12.1-2.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.1-2.el7
   Available: glusterfs-api-3.12.3-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.3-1.el7
   Available: glusterfs-api-3.12.4-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.4-1.el7
   Available: glusterfs-api-3.12.5-2.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.5-2.el7
   Available: glusterfs-api-3.12.6-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.6-1.el7
   Available: glusterfs-api-3.12.8-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.8-1.el7
   Available: glusterfs-api-3.12.9-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.9-1.el7
   Available: glusterfs-api-3.12.13-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.13-1.el7
   Available: glusterfs-api-3.12.14-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.14-1.el7
   Available: glusterfs-api-3.12.15-1.el7.x86_64
(ovirt-4.2-centos-gluster312)
   glusterfs-api = 3.12.15-1.el7
 You could try using --skip-broken to work around the problem

On Thu, Aug 6, 2020 at 8:43 AM carl langlois  wrote:

> Hi all,
>
> I am in the process of upgrading our cluster to 4.3. But first i need to
> update everything to 4.2.8 and update the os to the latest 7.x. I was able
> to update the self-hosted engine to the latest 4.2.8 and centos 7.8. But
> when i tried to update the host yum update got broken gluster packages.
> The current host that i'm trying to update is on 7.5. If i look at the
> release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve
> this.
> Any suggestions?.
>
> Carl
>
___
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/5RWM3SR6EBLLHNTTHSCYZN2MT3SHKHT6/

[ovirt-users] Re: Unassigned hosts

[Nardus Geldenhuys]

Hi

Can create thread dump, please send details on howto.

Regards

Nardus

On Thu, 6 Aug 2020 at 14:17, Artur Socha  wrote:

> Hi Nardus,
> You might have hit an issue I have been hunting for some time ( [1] and
> [2] ).
> [1] could not be properly resolved because at a time was not able to
> recreate an issue on dev setup.
> I suspect [2] is related.
>
> Would you be able to prepare a thread dump from your engine instance?
> Additionally, please check for potential libvirt errors/warnings.
> Can you also paste the output of:
> sudo yum list installed | grep vdsm
> sudo yum list installed | grep ovirt-engine
> sudo yum list installed | grep libvirt
>
> Usually, according to previous reports, restarting the engine helps to
> restore connectivity with hosts ... at least for some time.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1845152
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1846338
>
> regards,
> Artur
>
>
>
> On Thu, Aug 6, 2020 at 8:01 AM Nardus Geldenhuys 
> wrote:
>
>> Also see this in engine:
>>
>> Aug 6, 2020, 7:37:17 AM
>> VDSM someserver command Get Host Capabilities failed: Message timeout
>> which can be caused by communication issues
>>
>> On Thu, 6 Aug 2020 at 07:09, Strahil Nikolov 
>> wrote:
>>
>>> Can you fheck for errors on the affected host. Most probably you need
>>> the vdsm logs.
>>>
>>> Best Regards,
>>> Strahil Nikolov
>>>
>>> На 6 август 2020 г. 7:40:23 GMT+03:00, Nardus Geldenhuys <
>>> nard...@gmail.com> написа:
>>> >Hi Strahil
>>> >
>>> >Hope you are well. I get the following error when I tried to confirm
>>> >reboot:
>>> >
>>> >Error while executing action: Cannot confirm 'Host has been rebooted'
>>> >Host.
>>> >Valid Host statuses are "Non operational", "Maintenance" or
>>> >"Connecting".
>>> >
>>> >And I can't put it in maintenance, only option is "restart" or "stop".
>>> >
>>> >Regards
>>> >
>>> >Nar
>>> >
>>> >On Thu, 6 Aug 2020 at 06:16, Strahil Nikolov 
>>> >wrote:
>>> >
>>> >> After rebooting the node, have you "marked" it that it was rebooted ?
>>> >>
>>> >> Best Regards,
>>> >> Strahil Nikolov
>>> >>
>>> >> На 5 август 2020 г. 21:29:04 GMT+03:00, Nardus Geldenhuys <
>>> >> nard...@gmail.com> написа:
>>> >> >Hi oVirt land
>>> >> >
>>> >> >Hope you are well. Got a bit of an issue, actually a big issue. We
>>> >had
>>> >> >some
>>> >> >sort of dip of some sort. All the VM's is still running, but some of
>>> >> >the
>>> >> >hosts is show "Unassigned" or "NonResponsive". So all the hosts was
>>> >> >showing
>>> >> >UP and was fine before our dip. So I did increase
>>> >vdsHeartbeatInSecond
>>> >> >to
>>> >> >240, no luck.
>>> >> >
>>> >> >I still get a timeout on the engine lock even thou I can connect to
>>> >> >that
>>> >> >host from the engine using nc to test to port 54321. I also did
>>> >restart
>>> >> >vdsmd and also rebooted the host with no luck.
>>> >> >
>>> >> > nc -v someserver 54321
>>> >> >Ncat: Version 7.50 ( https://nmap.org/ncat )
>>> >> >Ncat: Connected to 172.40.2.172:54321.
>>> >> >
>>> >> >2020-08-05 20:20:34,256+02 ERROR
>>> >>
>>> >>[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>>> >> >(EE-ManagedThreadFactory-engineScheduled-Thread-70) [] EVENT_ID:
>>> >> >VDS_BROKER_COMMAND_FAILURE(10,802), VDSM someserver command Get Host
>>> >> >Capabilities failed: Message timeout which can be caused by
>>> >> >communication
>>> >> >issues
>>> >> >
>>> >> >Any troubleshoot ideas will be gladly appreciated.
>>> >> >
>>> >> >Regards
>>> >> >
>>> >> >Nar
>>> >>
>>>
>> ___
>> 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/C4HB2J3MH76FI2325Z4AV4VCCEKH4M3S/
>>
>
>
> --
> Artur Socha
> Senior Software Engineer, RHV
> Red Hat
>
___
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/YYUSMPZHIKV57X3L44ODZV47IMFQEVZE/

[ovirt-users] Re: Unassigned hosts

[Nardus Geldenhuys]

Hi

[root@engine-aa-1-01 ovirt-engine]# sudo yum list installed | grep vdsm
vdsm-jsonrpc-java.noarch   1.4.18-1.el7
@ovirt-4.3
[root@engine-aa-1-01 ovirt-engine]# sudo yum list installed | grep vdsm
vdsm-jsonrpc-java.noarch   1.4.18-1.el7
@ovirt-4.3
[root@engine-aa-1-01 ovirt-engine]# sudo yum list installed | grep
ovirt-engine
ovirt-engine.noarch4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-api-explorer.noarch   0.0.5-1.el7
 @ovirt-4.3
ovirt-engine-backend.noarch4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-dbscripts.noarch  4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-dwh.noarch4.3.6-1.el7
 @ovirt-4.3
ovirt-engine-dwh-setup.noarch  4.3.6-1.el7
 @ovirt-4.3
ovirt-engine-extension-aaa-jdbc.noarch 1.1.10-1.el7
@ovirt-4.3
ovirt-engine-extension-aaa-ldap.noarch 1.3.10-1.el7
@ovirt-4.3
ovirt-engine-extension-aaa-ldap-setup.noarch
ovirt-engine-extensions-api-impl.noarch4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-metrics.noarch1.3.4.1-1.el7
 @ovirt-4.3
ovirt-engine-restapi.noarch4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-setup.noarch  4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-setup-base.noarch 4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-setup-plugin-cinderlib.noarch 4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-setup-plugin-ovirt-engine.noarch
ovirt-engine-setup-plugin-ovirt-engine-common.noarch
ovirt-engine-setup-plugin-vmconsole-proxy-helper.noarch
ovirt-engine-setup-plugin-websocket-proxy.noarch
ovirt-engine-tools.noarch  4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-tools-backup.noarch   4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-ui-extensions.noarch  1.0.10-1.el7
@ovirt-4.3
ovirt-engine-vmconsole-proxy-helper.noarch 4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-webadmin-portal.noarch4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-websocket-proxy.noarch4.3.6.7-1.el7
 @ovirt-4.3
ovirt-engine-wildfly.x86_6417.0.1-1.el7
@ovirt-4.3
ovirt-engine-wildfly-overlay.noarch17.0.1-1.el7
@ovirt-4.3
python-ovirt-engine-sdk4.x86_644.3.2-2.el7
 @ovirt-4.3
python2-ovirt-engine-lib.noarch4.3.6.7-1.el7
 @ovirt-4.3
[root@engine-aa-1-01 ovirt-engine]# sudo yum list installed | grep libvirt
[root@engine-aa-1-01 ovirt-engine]#

I can send more info if needed. And yes, it looks like sometimes it helps
if you restart the engine.

Regards

Nardus

On Thu, 6 Aug 2020 at 14:17, Artur Socha  wrote:

> Hi Nardus,
> You might have hit an issue I have been hunting for some time ( [1] and
> [2] ).
> [1] could not be properly resolved because at a time was not able to
> recreate an issue on dev setup.
> I suspect [2] is related.
>
> Would you be able to prepare a thread dump from your engine instance?
> Additionally, please check for potential libvirt errors/warnings.
> Can you also paste the output of:
> sudo yum list installed | grep vdsm
> sudo yum list installed | grep ovirt-engine
> sudo yum list installed | grep libvirt
>
> Usually, according to previous reports, restarting the engine helps to
> restore connectivity with hosts ... at least for some time.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1845152
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1846338
>
> regards,
> Artur
>
>
>
> On Thu, Aug 6, 2020 at 8:01 AM Nardus Geldenhuys 
> wrote:
>
>> Also see this in engine:
>>
>> Aug 6, 2020, 7:37:17 AM
>> VDSM someserver command Get Host Capabilities failed: Message timeout
>> which can be caused by communication issues
>>
>> On Thu, 6 Aug 2020 at 07:09, Strahil Nikolov 
>> wrote:
>>
>>> Can you fheck for errors on the affected host. Most probably you need
>>> the vdsm logs.
>>>
>>> Best Regards,
>>> Strahil Nikolov
>>>
>>> На 6 август 2020 г. 7:40:23 GMT+03:00, Nardus Geldenhuys <
>>> nard...@gmail.com> написа:
>>> >Hi Strahil
>>> >
>>> >Hope you are well. I get the following error when I tried to confirm
>>> >reboot:
>>> >
>>> >Error while executing action: Cannot confirm 'Host has been rebooted'
>>> >Host.
>>> >Valid Host statuses are "Non operational", "Maintenance" or
>>> >"Connecting".
>>> >
>>> >And I can't put it in maintenance, only option is "restart" or "stop".
>>> >
>>> >Regards
>>> >
>>> >Nar
>>> >
>>> >On Thu, 6 Aug 2020 at 06:16, Strahil Nikolov 
>>> >wrote:
>>> >
>>> >> After rebooting the node, have you "marked" it that it was rebooted ?
>>> >>
>>> >> Best Regards,
>>> >> Strahil Nikolov
>>> >>
>>> >> На 5 август 2020 г. 21:29:04 GMT+03:00, Nardus Geldenhuys <
>>> >> nard...@gmail.com> написа:
>>> >> >Hi oVirt land
>>> >> >
>>> >> >Hope you are well. Got a bit of an issue, actually a big issue. We
>>> >had
>>> >> >some
>>> >> >sort of dip of some sort. All the VM's is still running, but some of
>>> >> >the
>>> >> >hosts is show "Unassigned" or "NonResponsive". So all the hosts was
>>> >> >showing
>>> >> >UP and was fine before our dip. So I did increase
>>> >vdsHeartbeatInSecond
>>> >> >to

[ovirt-users] 4.2.8 and yum update

[carl langlois]

Hi all,

I am in the process of upgrading our cluster to 4.3. But first i need to
update everything to 4.2.8 and update the os to the latest 7.x. I was able
to update the self-hosted engine to the latest 4.2.8 and centos 7.8. But
when i tried to update the host yum update got broken gluster packages.
The current host that i'm trying to update is on 7.5. If i look at the
release note i can see that ovirt 4.2.8 needs 7.6. Not sure how to resolve
this.
Any suggestions?.

Carl
___
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/QTPJBNLETMHMDHBJXCGTIHRY53UTBJFK/

[ovirt-users] Re: Unassigned hosts

[Artur Socha]

Hi Nardus,
You might have hit an issue I have been hunting for some time ( [1] and
[2] ).
[1] could not be properly resolved because at a time was not able to
recreate an issue on dev setup.
I suspect [2] is related.

Would you be able to prepare a thread dump from your engine instance?
Additionally, please check for potential libvirt errors/warnings.
Can you also paste the output of:
sudo yum list installed | grep vdsm
sudo yum list installed | grep ovirt-engine
sudo yum list installed | grep libvirt

Usually, according to previous reports, restarting the engine helps to
restore connectivity with hosts ... at least for some time.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1845152
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1846338

regards,
Artur



On Thu, Aug 6, 2020 at 8:01 AM Nardus Geldenhuys  wrote:

> Also see this in engine:
>
> Aug 6, 2020, 7:37:17 AM
> VDSM someserver command Get Host Capabilities failed: Message timeout
> which can be caused by communication issues
>
> On Thu, 6 Aug 2020 at 07:09, Strahil Nikolov 
> wrote:
>
>> Can you fheck for errors on the affected host. Most probably you need the
>> vdsm logs.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> На 6 август 2020 г. 7:40:23 GMT+03:00, Nardus Geldenhuys <
>> nard...@gmail.com> написа:
>> >Hi Strahil
>> >
>> >Hope you are well. I get the following error when I tried to confirm
>> >reboot:
>> >
>> >Error while executing action: Cannot confirm 'Host has been rebooted'
>> >Host.
>> >Valid Host statuses are "Non operational", "Maintenance" or
>> >"Connecting".
>> >
>> >And I can't put it in maintenance, only option is "restart" or "stop".
>> >
>> >Regards
>> >
>> >Nar
>> >
>> >On Thu, 6 Aug 2020 at 06:16, Strahil Nikolov 
>> >wrote:
>> >
>> >> After rebooting the node, have you "marked" it that it was rebooted ?
>> >>
>> >> Best Regards,
>> >> Strahil Nikolov
>> >>
>> >> На 5 август 2020 г. 21:29:04 GMT+03:00, Nardus Geldenhuys <
>> >> nard...@gmail.com> написа:
>> >> >Hi oVirt land
>> >> >
>> >> >Hope you are well. Got a bit of an issue, actually a big issue. We
>> >had
>> >> >some
>> >> >sort of dip of some sort. All the VM's is still running, but some of
>> >> >the
>> >> >hosts is show "Unassigned" or "NonResponsive". So all the hosts was
>> >> >showing
>> >> >UP and was fine before our dip. So I did increase
>> >vdsHeartbeatInSecond
>> >> >to
>> >> >240, no luck.
>> >> >
>> >> >I still get a timeout on the engine lock even thou I can connect to
>> >> >that
>> >> >host from the engine using nc to test to port 54321. I also did
>> >restart
>> >> >vdsmd and also rebooted the host with no luck.
>> >> >
>> >> > nc -v someserver 54321
>> >> >Ncat: Version 7.50 ( https://nmap.org/ncat )
>> >> >Ncat: Connected to 172.40.2.172:54321.
>> >> >
>> >> >2020-08-05 20:20:34,256+02 ERROR
>> >>
>> >>[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> >> >(EE-ManagedThreadFactory-engineScheduled-Thread-70) [] EVENT_ID:
>> >> >VDS_BROKER_COMMAND_FAILURE(10,802), VDSM someserver command Get Host
>> >> >Capabilities failed: Message timeout which can be caused by
>> >> >communication
>> >> >issues
>> >> >
>> >> >Any troubleshoot ideas will be gladly appreciated.
>> >> >
>> >> >Regards
>> >> >
>> >> >Nar
>> >>
>>
> ___
> 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/C4HB2J3MH76FI2325Z4AV4VCCEKH4M3S/
>


-- 
Artur Socha
Senior Software Engineer, RHV
Red Hat
___
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/RZPEGTZ6WD35MMSHF357RQI34E66N7MB/

[ovirt-users] Re: VDSM can't see StoragePool

[Nardus Geldenhuys]

Hi

Hope you are well. Did you find a solution for this? Think we have the same
type of issue.

Regards

Nar
___
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/KAUAL3OSRCALWXNWVPNL3YEKGC6P42O3/

[ovirt-users] Re: Unassigned hosts

[Nardus Geldenhuys]

Also see this in engine:

Aug 6, 2020, 7:37:17 AM
VDSM someserver command Get Host Capabilities failed: Message timeout which
can be caused by communication issues

On Thu, 6 Aug 2020 at 07:09, Strahil Nikolov  wrote:

> Can you fheck for errors on the affected host. Most probably you need the
> vdsm logs.
>
> Best Regards,
> Strahil Nikolov
>
> На 6 август 2020 г. 7:40:23 GMT+03:00, Nardus Geldenhuys <
> nard...@gmail.com> написа:
> >Hi Strahil
> >
> >Hope you are well. I get the following error when I tried to confirm
> >reboot:
> >
> >Error while executing action: Cannot confirm 'Host has been rebooted'
> >Host.
> >Valid Host statuses are "Non operational", "Maintenance" or
> >"Connecting".
> >
> >And I can't put it in maintenance, only option is "restart" or "stop".
> >
> >Regards
> >
> >Nar
> >
> >On Thu, 6 Aug 2020 at 06:16, Strahil Nikolov 
> >wrote:
> >
> >> After rebooting the node, have you "marked" it that it was rebooted ?
> >>
> >> Best Regards,
> >> Strahil Nikolov
> >>
> >> На 5 август 2020 г. 21:29:04 GMT+03:00, Nardus Geldenhuys <
> >> nard...@gmail.com> написа:
> >> >Hi oVirt land
> >> >
> >> >Hope you are well. Got a bit of an issue, actually a big issue. We
> >had
> >> >some
> >> >sort of dip of some sort. All the VM's is still running, but some of
> >> >the
> >> >hosts is show "Unassigned" or "NonResponsive". So all the hosts was
> >> >showing
> >> >UP and was fine before our dip. So I did increase
> >vdsHeartbeatInSecond
> >> >to
> >> >240, no luck.
> >> >
> >> >I still get a timeout on the engine lock even thou I can connect to
> >> >that
> >> >host from the engine using nc to test to port 54321. I also did
> >restart
> >> >vdsmd and also rebooted the host with no luck.
> >> >
> >> > nc -v someserver 54321
> >> >Ncat: Version 7.50 ( https://nmap.org/ncat )
> >> >Ncat: Connected to 172.40.2.172:54321.
> >> >
> >> >2020-08-05 20:20:34,256+02 ERROR
> >>
> >>[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> >> >(EE-ManagedThreadFactory-engineScheduled-Thread-70) [] EVENT_ID:
> >> >VDS_BROKER_COMMAND_FAILURE(10,802), VDSM someserver command Get Host
> >> >Capabilities failed: Message timeout which can be caused by
> >> >communication
> >> >issues
> >> >
> >> >Any troubleshoot ideas will be gladly appreciated.
> >> >
> >> >Regards
> >> >
> >> >Nar
> >>
>
___
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/C4HB2J3MH76FI2325Z4AV4VCCEKH4M3S/