[ovirt-users] Re: VDI and ovirt

[Pascal D]

Alex

From your response  it looks you were able to use spicehtml5 using a squid 
proxy. Do you mind sharing your setup or some howto ou followed. I have been 
wanting to deploy it in our setup. 

TIA

Pascal
___
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/APOEDY7XEIVPJ6SDGLFMEVHRHE77KZO6/

[ovirt-users] oVirt fails to update OVF

[Jürgen Walch via Users]

Hi everybody,

we are running an oVirt 4.3.10 production cluster with 9 hosts and 5 datastore 
domains.
Since yesterday we get error messages

26.02.2021 02:00:48 VDSM command SetVolumeDescriptionVDS failed: Could 
not acquire resource. Probably resource factory threw an exception.: ()
26.02.2021 02:00:48 Failed to update OVF disks 
5aa438e3-8d22-4b6c-bccf-a843151ca0be, OVF data isn't updated on those OVF 
stores (Data Center datacenter01, Storage Domain vmstore13).
26.02.2021 02:00:48 Failed to update VMs/Templates OVF data for Storage 
Domain vmstore13 in Data Center datacenter01.

every hour.
Only one domain (vmstore13) is affected, this domain is (like 3 others in the 
cluster) based on glusterfs.
Trying to update the OVF's manually from the engine web-gui leads to the same 
result followed by (a misleading)

26.02.2021 02:00:49 OVF_STORE for domain vmstore13 was updated by 
admin@internal-authz.

The vm's with discs on the affected domain are running fine, snapshots are 
working.
So far I have tried to move the SPM role to another host. This succeeded, but 
the error messages persist.

The vdsm log on the SPM host contains something like

2021-02-26 03:00:57,701+0100 INFO  (jsonrpc/2) [vdsm.api] START 
setVolumeDescription(sdUUID=u'9f731135-f5d9-4609-9e3b-fa9cae75e314', 
spUUID=u'33e8dc9e-8bc8-11ea-bd76-00163e741033', 
imgUUID=u'5aa438e3-8d22-4b6c-bccf-a843151ca0be', 
volUUID=u'0795e58c-4960-413a-a0b4-e8a6d547fda5', 
description=u'{"Updated":false,"Last Updated":"Wed Feb 24 17:48:17 CET 
2021","Storage Domains":[{"uuid":"9f731135-f5d9-4609-9e3b-fa9cae75e314"}],"Disk 
Description":"OVF_STORE"}', options=None) from=:::10.70.1.1,46968, 
flow_id=1f314676, task_id=9101db01-b4f0-447e-a5a9-b6af76278d55 (api:48)
2021-02-26 03:00:57,712+0100 ERROR (jsonrpc/2) [storage.VolumeManifest] 
[Errno 116] Stale file handle (fileVolume:155)

for each error, I have attached the relevant part of vdsm.log.

Has anyone experienced this behaviour before and can provide help ?

-- 
   
 juergen


vdsm.log
Description: vdsm.log
___
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/VF7RSZLVRGBTZ57FMSZB6TMOXEL47WS2/

[ovirt-users] Re: Multipath flapping with SAS via FCP

[Nir Soffer]

On Thu, Feb 25, 2021 at 2:29 PM Benoit Chatelain  wrote:
>
> Hi,
>
> I have some troubles with multipath.
> When I add SAS disk over FCP as Storage Domain via oVirt WebUI,
> The first link as active, but the second is stuck as failed.
>
> Volum disk is provided from Dell Compellent via FCP, and disk is transported 
> in SAS.
>
> multipath is flapping in all hypervisor from the same domain disk:
>
> [root@isildur-adm ~]# tail -f /var/log/messages
> Feb 25 11:48:21 isildur-adm kernel: device-mapper: multipath: 253:3: Failing 
> path 8:32.
> Feb 25 11:48:24 isildur-adm multipathd[659460]: 
> 36000d31003d5c210: sdc - tur checker reports path is up
> Feb 25 11:48:24 isildur-adm multipathd[659460]: 8:32: reinstated
> Feb 25 11:48:24 isildur-adm multipathd[659460]: 
> 36000d31003d5c210: remaining active paths: 2
> Feb 25 11:48:24 isildur-adm kernel: device-mapper: multipath: 253:3: 
> Reinstating path 8:32.
> Feb 25 11:48:24 isildur-adm kernel: sd 1:0:1:2: alua: port group f01c state S 
> non-preferred supports toluSNA
> Feb 25 11:48:24 isildur-adm kernel: sd 1:0:1:2: alua: port group f01c state S 
> non-preferred supports toluSNA
> Feb 25 11:48:24 isildur-adm kernel: device-mapper: multipath: 253:3: Failing 
> path 8:32.

Looks like the device fails immediately after it was reinstated.

> Feb 25 11:48:25 isildur-adm multipathd[659460]: sdc: mark as failed
> Feb 25 11:48:25 isildur-adm multipathd[659460]: 
> 36000d31003d5c210: remaining active paths: 1
> ---
> [root@isildur-adm ~]# multipath -ll
> 36000d31003d5c210 dm-3 COMPELNT,Compellent Vol
> size=1.5T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
> `-+- policy='service-time 0' prio=25 status=active
>   |- 1:0:0:2 sdb 8:16 active ready running
>   `- 1:0:1:2 sdc 8:32 failed ready running
> ---
> VDSM generate multipath.conf like this ( I have remove commented lines for 
> read confort ) :
>
> [root@isildur-adm ~]# cat /etc/multipath.conf
> # VDSM REVISION 2.0
>
> # This file is managed by vdsm.
> defaults {
> polling_interval5
> no_path_retry   16
> user_friendly_names no
> flush_on_last_del   yes
> fast_io_fail_tmo5
> dev_loss_tmo30
> max_fds 4096
> }
> blacklist {
> protocol "(scsi:adt|scsi:sbp)"
> }
>
> no_path_retry   16
> }
>
> Have you some idea why this link is flapping on my two hypervisor?

Maybe Ben have an idea.

You may need some configuration for that device. Not all devices have
built in configuration in multipath.

You can find the device details with "multipath -ll". Then look at

   multipathd show config

And find the section related to you device. If the device is not there,
you may need to add device configuration for your device.  You can
check with the vendor about this configuration.

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

[ovirt-users] [ANN] oVirt 4.4.5 Seventh Release Candidate is now available for testing

[Lev Veyde]

oVirt 4.4.5 Seventh Release Candidate is now available for testing

The oVirt Project is pleased to announce the availability of oVirt 4.4.5
Seventh Release Candidate for testing, as of February 25th, 2021.

This update is the fifth in a series of stabilization updates to the 4.4
series.
How to prevent hosts entering emergency mode after upgrade from oVirt 4.4.1

Note: Upgrading from 4.4.2 GA or later should not require re-doing these
steps, if already performed while upgrading from 4.4.1 to 4.4.2 GA. These
are only required to be done once.

Due to Bug 1837864  -
Host enter emergency mode after upgrading to latest build

If you have your root file system on a multipath device on your hosts you
should be aware that after upgrading from 4.4.1 to 4.4.5 you may get your
host entering emergency mode.

In order to prevent this be sure to upgrade oVirt Engine first, then on
your hosts:

   1.

   Remove the current lvm filter while still on 4.4.1, or in emergency mode
   (if rebooted).
   2.

   Reboot.
   3.

   Upgrade to 4.4.5 (redeploy in case of already being on 4.4.5).
   4.

   Run vdsm-tool config-lvm-filter to confirm there is a new filter in
   place.
   5.

   Only if not using oVirt Node:
   - run "dracut --force --add multipath” to rebuild initramfs with the
   correct filter configuration
   6.

   Reboot.

Documentation

   -

   If you want to try oVirt as quickly as possible, follow the instructions
   on the Download  page.
   -

   For complete installation, administration, and usage instructions, see
   the oVirt Documentation .
   -

   For upgrading from a previous version, see the oVirt Upgrade Guide
   .
   -

   For a general overview of oVirt, see About oVirt
   .

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 installation instructions and additional information please refer to:

https://ovirt.org/documentation/

This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

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

* Red Hat Enterprise Linux 8.3 or newer

* CentOS Linux (or similar) 8.3 or newer

* oVirt Node 4.4 based on CentOS Linux 8.3 (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

- We found a few issues while testing on CentOS Stream so we are still
basing oVirt 4.4.5 Node and Appliance on CentOS Linux.

Additional Resources:

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

* 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.5/

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

[ovirt-users] Starting a defined VM on a different host

[lavi.buchnik--- via Users]

Hi,
I might be missing something here, but I'm looking for the right API way to 
start a defined VM on a different host.
The scenario is this:
1. VM is running under Cluster Affinity Host. and there is a need to cold 
migrate it to another host on that Affinity.
2. for that I will stop the VM.
3. And now I would like to start the VM on another host, I tried few ways like:
vm_service.start(
vm=types.Vm(
host=types.Host(
name=''
),
)
)

But VM keep starting on the current host.
Can you please show me the right way to do it.

Thanks,
Lavi
___
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/EJH2X5X5FDIR7Q7NTHOPYTNMOE3M6JDD/

[ovirt-users] oVirt and OL8

[Nur Imam Febrianto]

Anybody have any experience deploying oVirt on OL8 ? Not OLVM.
Thanks before.

Regards,
Nur Imam Febrianto

Sent from Mail for Windows 10

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

[ovirt-users] Multipath flapping with SAS via FCP

[Benoit Chatelain]

Hi,

I have some troubles with multipath. 
When I add SAS disk over FCP as Storage Domain via oVirt WebUI, 
The first link as active, but the second is stuck as failed.

Volum disk is provided from Dell Compellent via FCP, and disk is transported in 
SAS.

multipath is flapping in all hypervisor from the same domain disk:

[root@isildur-adm ~]# tail -f /var/log/messages
Feb 25 11:48:21 isildur-adm kernel: device-mapper: multipath: 253:3: Failing 
path 8:32.
Feb 25 11:48:24 isildur-adm multipathd[659460]: 
36000d31003d5c210: sdc - tur checker reports path is up
Feb 25 11:48:24 isildur-adm multipathd[659460]: 8:32: reinstated
Feb 25 11:48:24 isildur-adm multipathd[659460]: 
36000d31003d5c210: remaining active paths: 2
Feb 25 11:48:24 isildur-adm kernel: device-mapper: multipath: 253:3: 
Reinstating path 8:32.
Feb 25 11:48:24 isildur-adm kernel: sd 1:0:1:2: alua: port group f01c state S 
non-preferred supports toluSNA
Feb 25 11:48:24 isildur-adm kernel: sd 1:0:1:2: alua: port group f01c state S 
non-preferred supports toluSNA
Feb 25 11:48:24 isildur-adm kernel: device-mapper: multipath: 253:3: Failing 
path 8:32.
Feb 25 11:48:25 isildur-adm multipathd[659460]: sdc: mark as failed
Feb 25 11:48:25 isildur-adm multipathd[659460]: 
36000d31003d5c210: remaining active paths: 1
--- 
[root@isildur-adm ~]# multipath -ll
36000d31003d5c210 dm-3 COMPELNT,Compellent Vol
size=1.5T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
`-+- policy='service-time 0' prio=25 status=active
  |- 1:0:0:2 sdb 8:16 active ready running
  `- 1:0:1:2 sdc 8:32 failed ready running
---
VDSM generate multipath.conf like this ( I have remove commented lines for read 
confort ) : 

[root@isildur-adm ~]# cat /etc/multipath.conf 
# VDSM REVISION 2.0

# This file is managed by vdsm.
defaults {
polling_interval5
no_path_retry   16
user_friendly_names no
flush_on_last_del   yes
fast_io_fail_tmo5
dev_loss_tmo30
max_fds 4096
}
blacklist {
protocol "(scsi:adt|scsi:sbp)"
}

no_path_retry   16
}

Have you some idea why this link is flapping on my two hypervisor?

Thanks a lot in advance.
- Benoit Chatelain
___
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/M426QWSHTUYSNROKH5CRUIU44PFFZD4Y/

[ovirt-users] Re: FQDN is not reachable | oVirt 4.4.4

[Guillem Liarte via Users]

I submitted a bug as I do not think this is normal. It looks like the  fqdn 
check happens in the UI context only, not in the system.

https://bugzilla.redhat.com/show_bug.cgi?id=1932851
___
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/V2MMQNUZZNZMYGRO244JLE65N2PUNNXQ/

[ovirt-users] Re: Python SDK - get host VM is running on.

[Roni Eliezer]

You can also use the SDK wrapper:
https://github.com/rhevm-qe-automation/ovirtlib4

eng = OvirtLib("fqdn.something.com", username="myuser", password="mypassword")

for vm in eng.vms():
 if vm.entity.status.name == "UP":
 print(vm(follow="host").entity.host.name)


Thx

Roni


On Sun, Feb 21, 2021 at 11:47 PM  wrote:

> Thanks heaps.
>
> I've realised that I can use the follow_link method to get a reference to
> the host as well as below:
>
> ...
> vms_service = connection.system_service().vms_service()
> vms = vms_service.list()
> for vm in vms:
>   vm_service = vms_service.vm_service(vm.id)
>   if vm.status == types.VmStatus.UP:
> vmhost = connection.follow_link(vm.host)
> print("{0:<30s}{1:<30}{2:<30}".format(vm.name,vmhost.name,host.name))
> connection.close()
> ...
> ___
> 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/OOOUUP5SJBQWSYYNF4HLG6YQSFE3RDLM/
>
___
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/WL5ZYHHLZ24TNHI6WAZQQOJMZERDHHUP/

[ovirt-users] Re: FQDN is not reachable | oVirt 4.4.4

[Guillem Liarte via Users]

I made sure `host` commands reply properly so I setup dnsmasq to be able to 
return correct local values too:


[root@ndoamsel001 ]# host ndoamsel001s.home.lab
ndoamsel001s.home.lab has address 10.0.1.1
[root@ndoamsel001 ]# host ndoamsel001v.home.lab
ndoamsel001v.home.lab address 10.0.2.1
[root@ndoamsel001 ]# host ndoamsel001.home.lab
ndoamsel001.home.lab has address 10.91.197.132

It still fails with the dreaded message on the title.

I am really at loss.
___
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/MASEPY4WP6AURAXPYK2Y5JEZQYUB3QGP/