[ovirt-users] Re: python ovirtsdk

[serphentos]

Thank you very much for answer and for link.
It's very helpfull.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2ANCITHGJLJGPIX3HY5ZB4SDUF5W323C/

[ovirt-users] VMs Locked - vProtect snapshots

[joseph]

After a few tricky power issues at a site in a less developed country, I had to 
restart my 3 node ovirt cluster with hosted engine. Everything seemed to come 
up fine, but that night when my scheduled snapshots/backups etc ran (vProtect) 
some weird things happened. It created a couple snapshots and couldn't copy 
them saying disk is locked (even though in the GUI no disks or snapshots were 
locked)

After a couple tries all of a sudden the whole VM is 'locked' this means I 
can't migrate it, cant start it (if it shuts down) couldn't remove old 
snapshots etc. I had this happen on another VM and my only solution there was 
to clone it, but now its happened to all of them and im not sure why.

I have run the db utility on command line to unlock everything, nothing is 
listed as locked, but I still cant run any operations on the VM's. I even 
cloned them to get them up and running again, but I can't delete the old VM 
still sitting there (or the disk, snapshots or anything) just keep getting VM 
is locked.

How the hell do I force an unlock of these entities when everything tells me 
its not locked? I'm almost at a point where I want to back up all VM's and 
start again but i'd much rather learn some more so I can manage these issues in 
future.

Any help is appreciated!

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

[ovirt-users] Re: Ovirt 4.3.6 USB passthrough not working with iommu_intel=on iommu=pt

[Don Dupuis]

I have created a bug and the number is 1775306.

Thanks
Don

On Thu, Nov 21, 2019 at 9:46 AM Michal Skrivanek <
michal.skriva...@redhat.com> wrote:

>
>
> On 21 Nov 2019, at 16:31, Don Dupuis  wrote:
>
> Anyone else have this problem? I haven't been able to find a solution.
>
> Don
>
> On Tue, Nov 19, 2019 at 10:03 AM Don Dupuis  wrote:
>
>> with that approach, still get same error.
>>
>> Don
>>
>> On Mon, Nov 18, 2019 at 10:49 PM Strahil Nikolov 
>> wrote:
>>
>>> I would recommend you to "unpresent" that USB, then replug (if that's
>>> possible) the USB and then to refresh the hosts's Capabilities (management
>>> dropdown). Only then try to assign the USB.
>>>
>>> Best Regards,
>>> Strahil Nikolov
>>>
>>> В вторник, 19 ноември 2019 г., 05:30:00 ч. Гринуич+2, Don Dupuis <
>>> donds...@gmail.com> написа:
>>>
>>>
>>> I am trying to pass through a USB Dongle to a Windows virtual machine in
>>> ovirt 4.3.6. This will work if these options aren't used. Below is the
>>> output of lsusb with no iommu enable:
>>>
>>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>>> Bus 001 Device 005: ID 1604:10c0 Tascam
>>> Bus 001 Device 004: ID 1604:10c0 Tascam
>>> Bus 001 Device 003: ID 1604:10c0 Tascam
>>> Bus 001 Device 002: ID 07f2:0001 Microcomputer Applications, Inc. KEYLOK
>>> II
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>>
>>> The device I am passing through is Bus 001 Device 002.
>>>
>>> This is the error I get in vdsmd.log:
>>>
>>> Traceback (most recent call last):
>>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 867, in
>>> _startUnderlyingVm
>>> self._run()
>>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2890, in
>>> _run
>>> self._domDependentInit()
>>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2466, in
>>> _domDependentInit
>>> self._vmDependentInit()
>>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2480, in
>>> _vmDependentInit
>>> self._getUnderlyingVmDevicesInfo()
>>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2448, in
>>> _getUnderlyingVmDevicesInfo
>>> vmdevices.common.update_device_info(self, self._devices)
>>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/common.py",
>>> line 94, in update_device_info
>>> hostdevice.HostDevice.update_device_info(vm,
>>> devices[hwclass.HOSTDEV])
>>>   File
>>> "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/hostdevice.py", line
>>> 426, in update_device_info
>>> vm, device_conf, device_xml)
>>>   File
>>> "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/hostdevice.py", line
>>> 223, in update_from_xml
>>> if host_address == dev.hostAddress:
>>> AttributeError: 'MdevDevice' object has no attribute 'hostAddress'
>>> 2019-11-18 18:20:06,173-0600 INFO  (vm/9944089c) [virt.vm]
>>> (vmId='9944089c-2109-4352-a0c6-7d0d9e04bb3f') Changed state to Down:
>>> 'MdevDevice' object has no attribute 'hostAddress' (code=1) (vm:1690)
>>>
>>
> Looks like a code bug. Would you please open it? On vdsm, oVirt team “virt”
>
> Thanks,
> michal
>
>
>
>>> I am using kernel 3.10.0-957.12.1.el7.x86_64
>>>
>>> vdsm is vdsm-4.30.33-1.el7.x86_64
>>> libvirt is libvirt-5.0.0-1.el7.x86_64
>>> qemu is qemu-img-ev-2.12.0-33.1.el7.x86_64
>>>
>>> Any help with this issue would be appreciated.
>>>
>>> Thanks
>>> Don
>>> ___
>>> Users mailing list -- users@ovirt.org
>>> To unsubscribe send an email to users-le...@ovirt.org
>>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>>> oVirt Code of Conduct:
>>> https://www.ovirt.org/community/about/community-guidelines/
>>> List Archives:
>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/3JWP5GNYJWH7HDLBDRU3UGGHUENINW4I/
>>>
>> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BFES4PVZJ5LTNWPNOWZTZOB2DGUPDKCN/
>
>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/U7ZDDT5U5JT4SLMZBSYQVNJBMEFGGFSD/

[ovirt-users] How to tell a migrated engine it is not running as a hosted engine anymore?

[rens . verhage]

I migrated a hosted ovirt-engine to a standalone machine. To do so, I created a 
backup with scope=all and imported this back-up into a newly installed engine.

Everything was working fine. Not much later, I made a mistake and wanted to 
start over, so I decided to do an engine-cleanup and re-import my back-up.

However, when I perform the engine-cleanup, I get this error message:

[ ERROR ] It seems that you are running your engine inside of the 
hosted-engine VM and are not in "Global Maintenance" mode.
 In that case you should put the system into the "Global Maintenance" 
mode before running engine-setup, or the hosted-engine HA agent might kill the 
machine, which might corrupt your data.

This is not true. The engine is now running as a standalone server.

There must be a config parameter somewhere in a config file or in the database 
that tells the engine what mode it is running in, but I haven't found it yet.

I can't find any documentation for this issue, all migration guides tell you 
how to migrate from standalone to hosted engine, not the other way around.

How can I fix this?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/V55S6UH4ZWXDOLULQAHH7YL7FKJFXREY/

[ovirt-users] Re: Ovirt 4.3.6 USB passthrough not working with iommu_intel=on iommu=pt

[Michal Skrivanek]

> On 21 Nov 2019, at 16:31, Don Dupuis  wrote:
> 
> Anyone else have this problem? I haven't been able to find a solution.
> 
> Don
> 
> On Tue, Nov 19, 2019 at 10:03 AM Don Dupuis  > wrote:
> with that approach, still get same error.
> 
> Don
> 
> On Mon, Nov 18, 2019 at 10:49 PM Strahil Nikolov  > wrote:
> I would recommend you to "unpresent" that USB, then replug (if that's 
> possible) the USB and then to refresh the hosts's Capabilities (management 
> dropdown). Only then try to assign the USB.
> 
> Best Regards,
> Strahil Nikolov
> 
> В вторник, 19 ноември 2019 г., 05:30:00 ч. Гринуич+2, Don Dupuis 
> mailto:donds...@gmail.com>> написа:
> 
> 
> I am trying to pass through a USB Dongle to a Windows virtual machine in 
> ovirt 4.3.6. This will work if these options aren't used. Below is the output 
> of lsusb with no iommu enable:
> 
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 005: ID 1604:10c0 Tascam
> Bus 001 Device 004: ID 1604:10c0 Tascam
> Bus 001 Device 003: ID 1604:10c0 Tascam
> Bus 001 Device 002: ID 07f2:0001 Microcomputer Applications, Inc. KEYLOK II
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> 
> The device I am passing through is Bus 001 Device 002.
> 
> This is the error I get in vdsmd.log:
> 
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 867, in 
> _startUnderlyingVm
> self._run()
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2890, in _run
> self._domDependentInit()
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2466, in 
> _domDependentInit
> self._vmDependentInit()
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2480, in 
> _vmDependentInit
> self._getUnderlyingVmDevicesInfo()
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2448, in 
> _getUnderlyingVmDevicesInfo
> vmdevices.common.update_device_info(self, self._devices)
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/common.py", line 
> 94, in update_device_info
> hostdevice.HostDevice.update_device_info(vm, devices[hwclass.HOSTDEV])
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/hostdevice.py", 
> line 426, in update_device_info
> vm, device_conf, device_xml)
>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/hostdevice.py", 
> line 223, in update_from_xml
> if host_address == dev.hostAddress:
> AttributeError: 'MdevDevice' object has no attribute 'hostAddress'
> 2019-11-18 18:20:06,173-0600 INFO  (vm/9944089c) [virt.vm] 
> (vmId='9944089c-2109-4352-a0c6-7d0d9e04bb3f') Changed state to Down: 
> 'MdevDevice' object has no attribute 'hostAddress' (code=1) (vm:1690)

Looks like a code bug. Would you please open it? On vdsm, oVirt team “virt”

Thanks,
michal


> 
> I am using kernel 3.10.0-957.12.1.el7.x86_64
> 
> vdsm is vdsm-4.30.33-1.el7.x86_64
> libvirt is libvirt-5.0.0-1.el7.x86_64
> qemu is qemu-img-ev-2.12.0-33.1.el7.x86_64
> 
> Any help with this issue would be appreciated.
> 
> Thanks
> Don
> ___
> Users mailing list -- users@ovirt.org 
> To unsubscribe send an email to users-le...@ovirt.org 
> 
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ 
> 
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/ 
> 
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/3JWP5GNYJWH7HDLBDRU3UGGHUENINW4I/
>  
> 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BFES4PVZJ5LTNWPNOWZTZOB2DGUPDKCN/

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

[ovirt-users] Re: Ovirt 4.3.6 USB passthrough not working with iommu_intel=on iommu=pt

[Don Dupuis]

Anyone else have this problem? I haven't been able to find a solution.

Don

On Tue, Nov 19, 2019 at 10:03 AM Don Dupuis  wrote:

> with that approach, still get same error.
>
> Don
>
> On Mon, Nov 18, 2019 at 10:49 PM Strahil Nikolov 
> wrote:
>
>> I would recommend you to "unpresent" that USB, then replug (if that's
>> possible) the USB and then to refresh the hosts's Capabilities (management
>> dropdown). Only then try to assign the USB.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> В вторник, 19 ноември 2019 г., 05:30:00 ч. Гринуич+2, Don Dupuis <
>> donds...@gmail.com> написа:
>>
>>
>> I am trying to pass through a USB Dongle to a Windows virtual machine in
>> ovirt 4.3.6. This will work if these options aren't used. Below is the
>> output of lsusb with no iommu enable:
>>
>> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>> Bus 001 Device 005: ID 1604:10c0 Tascam
>> Bus 001 Device 004: ID 1604:10c0 Tascam
>> Bus 001 Device 003: ID 1604:10c0 Tascam
>> Bus 001 Device 002: ID 07f2:0001 Microcomputer Applications, Inc. KEYLOK
>> II
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>
>> The device I am passing through is Bus 001 Device 002.
>>
>> This is the error I get in vdsmd.log:
>>
>> Traceback (most recent call last):
>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 867, in
>> _startUnderlyingVm
>> self._run()
>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2890, in
>> _run
>> self._domDependentInit()
>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2466, in
>> _domDependentInit
>> self._vmDependentInit()
>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2480, in
>> _vmDependentInit
>> self._getUnderlyingVmDevicesInfo()
>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2448, in
>> _getUnderlyingVmDevicesInfo
>> vmdevices.common.update_device_info(self, self._devices)
>>   File "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/common.py",
>> line 94, in update_device_info
>> hostdevice.HostDevice.update_device_info(vm, devices[hwclass.HOSTDEV])
>>   File
>> "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/hostdevice.py", line
>> 426, in update_device_info
>> vm, device_conf, device_xml)
>>   File
>> "/usr/lib/python2.7/site-packages/vdsm/virt/vmdevices/hostdevice.py", line
>> 223, in update_from_xml
>> if host_address == dev.hostAddress:
>> AttributeError: 'MdevDevice' object has no attribute 'hostAddress'
>> 2019-11-18 18:20:06,173-0600 INFO  (vm/9944089c) [virt.vm]
>> (vmId='9944089c-2109-4352-a0c6-7d0d9e04bb3f') Changed state to Down:
>> 'MdevDevice' object has no attribute 'hostAddress' (code=1) (vm:1690)
>>
>> I am using kernel 3.10.0-957.12.1.el7.x86_64
>>
>> vdsm is vdsm-4.30.33-1.el7.x86_64
>> libvirt is libvirt-5.0.0-1.el7.x86_64
>> qemu is qemu-img-ev-2.12.0-33.1.el7.x86_64
>>
>> Any help with this issue would be appreciated.
>>
>> Thanks
>> Don
>> ___
>> Users mailing list -- users@ovirt.org
>> To unsubscribe send an email to users-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/3JWP5GNYJWH7HDLBDRU3UGGHUENINW4I/
>>
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BFES4PVZJ5LTNWPNOWZTZOB2DGUPDKCN/

[ovirt-users] Howto recover/reinstall a failed oVirt node in a 3 node HCI cluster

[Timo Eissler]

Hello,

i can't find the documentation on howto recover from a single host OS disk 
failure in a 3 node HCI cluster.
I already searched the ovirt, RHV and RHHI documentation but i can't find the 
corresponding documentation.
So can anyone please give me some hints?

In our dev lab i have 3 servers with 2 disks each. sda for ovirt node and sdb 
for gluster. Let's assume the disk sda of a single node is defunct and needs to 
be replaced.
So i grab a new disk and reinstall ovirt node from PXE.
After the installation is finished i would like to reinstall the host from 
ovirt admin portal, but that doesn't work because of an invalid fingerprint.

So how can i re-add that host to ovirt and gluster?

Kind regards,
Timo
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/23RGI637G7E24L2QBJRVVW5GQLXUKOUD/

[ovirt-users] Re: python ovirtsdk

[Dominik Holler]

On Thu, Nov 21, 2019 at 9:00 AM  wrote:

> Hello.
> Can someone explain how to attach logical network to host via ovirtsdk?
>

As a python snippet, attaching a network looks like this:

hosts_service = connection.system_service().hosts_service()
host = hosts_service.list(search='name=ovirt-node-ng-image-20190129-1')[0]
host_service = hosts_service.host_service(host.id)
host_service.setup_networks(
modified_network_attachments=[
types.NetworkAttachment(
network=types.Network(
name='ovirtmgmt',
),
host_nic=types.HostNic(
name='eth0',
),
ip_address_assignments=[
types.IpAddressAssignment(
assignment_method=types.BootProtocol.STATIC,
ip=types.Ip(
address='192.168.122.22',
netmask='255.255.255.0',
gateway='192.168.122.1'
),
),
],
),
]
)

Please find the documentation in
http://ovirt.github.io/ovirt-engine-api-model/4.3/#services/host/methods/setup_networks




> I saw a example of attaching networks to cluster or dc, but not a host
>
> https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/assign_network_to_cluster.py
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/6OH7ONBLNBN6NC52YWA3ARR7ZZLW6EKH/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZUYG7OC4MTEI2WGEC2FECA6UN63DJU7J/

[ovirt-users] Re: terraform integration

[Nathanaël Blanchet]

Le 21/11/2019 à 13:57, Roy Golan a écrit :



On Thu, 21 Nov 2019 at 08:48, Roy Golan > wrote:




On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet mailto:blanc...@abes.fr>> wrote:


Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :



Le 19/11/2019 à 13:43, Roy Golan a écrit :



On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet
mailto:blanc...@abes.fr>> wrote:

Le 19/11/2019 à 08:55, Roy Golan a écrit :

oc get -o json clusterversion


This is the output of the previous failed deployment,
I'll give a try to a newer one when I'll have a minute
to test


Without changing nothing with template,  I gave a new try
and... nothing works anymore now, none of provided IPs can be
pingued : dial tcp 10.34.212.51:6443
: connect: no route to host", so
none of masters can be provisonned by bootstrap.

I tried with the latest rhcos and latest ovirt 4.3.7, it is
the same. Obviously something changed since my first attempt
12 days ago... is your docker image for openshift-installer
up to date?

Are you still able to your side to deploy a valid cluster ?


I investigated looking at bootstrap logs (attached) and it
seems that every containers die immediately after been started.

Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.60107571 + UTC m=+0.794838407 container init
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.623197173 + UTC m=+0.816959853 container start
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:33 localhost podman[2024]: 2019-11-20
07:02:33.623814258 + UTC m=+0.817576965 container attach
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:34 localhost systemd[1]:

libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
Consumed 814ms CPU time
Nov 20 07:02:34 localhost podman[2024]: 2019-11-20
07:02:34.100569998 + UTC m=+1.294332779 container died
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)
Nov 20 07:02:35 localhost podman[2024]: 2019-11-20
07:02:35.138523102 + UTC m=+2.332285844 container remove
446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603
(image=registry.svc.ci.openshift.org/origin/release:4.3
,
name=eager_cannon)

and this:

Nov 20 07:04:16 localhost hyperkube[1909]: E1120
07:04:16.489527    1909 remote_runtime.go:200] CreateContainer
in sandbox
"58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5"
from runtime service failed: rpc error: code = Unknown desc =
container create failed: container_linux.go:345: starting
container process caused "exec: \"runtimecfg\": executable
file not found in $PATH"
Nov 20 07:04:16 localhost hyperkube[1909]: E1120
07:04:16.489714    1909 kuberuntime_manager.go:783] init
container start failed: CreateContainerError: container create
failed: container_linux.go:345: starting container process
caused "exec: \"runtimecfg\": executable file not found in $PATH"

What do you think about this?


I'm seeing the same now, checking...


Because of the move upstream to release OKD the release-image that 
comes with the installer I gave you are no longer valid.


I need to prepare an installer version with the preview of OKD, you 
can find the details here 
https://mobile.twitter.com/smarterclayton/status/1196477646885965824
Seems that okd4 
https://github.com/openshift/okd/releases/download/4.3.0-0.okd-2019-11-15-182656/openshift-install-linux-4.3.0-0.okd-2019-11-15-182656.tar.gz 
is a compiled binary without the ovirt installer. Can you tell where are 
sources so as to include ovirt extensions into the installer build?





(do I need to use the terraform-workers tag instead of
latest?)

docker pullquay.io/r

[ovirt-users] Re: Unable to attach ISO domain to Datacenter

[Ivan Apolonio]

Further system information:

oVirt installed packets:

$ rpm -qa '*ovirt*'
ovirt-engine-restapi-4.3.6.7-1.el7.noarch
ovirt-web-ui-1.6.0-1.el7.noarch
ovirt-vmconsole-proxy-1.0.7-2.el7.noarch
python2-ovirt-host-deploy-1.8.4-1.el7.noarch
ovirt-host-4.3.5-1.el7.x86_64
ovirt-engine-dwh-4.3.6-1.el7.noarch
cockpit-machines-ovirt-195.1-1.el7.centos.0.1.noarch
ovirt-ansible-repositories-1.1.5-1.el7.noarch
ovirt-ansible-roles-1.1.7-1.el7.noarch
python2-ovirt-engine-lib-4.3.7.2-1.el7.noarch
ovirt-provider-ovn-1.2.27-1.el7.noarch
ovirt-engine-setup-plugin-ovirt-engine-common-4.3.7.2-1.el7.noarch
ovirt-engine-setup-4.3.7.2-1.el7.noarch
ovirt-ansible-cluster-upgrade-1.1.14-1.el7.noarch
ovirt-cockpit-sso-0.1.1-1.el7.noarch
ovirt-engine-ui-extensions-1.0.10-1.el7.noarch
ovirt-engine-4.3.6.7-1.el7.noarch
ovirt-hosted-engine-setup-2.3.12-1.el7.noarch
ovirt-ansible-vm-infra-1.1.22-1.el7.noarch
ovirt-engine-setup-plugin-cinderlib-4.3.7.2-1.el7.noarch
python-ovirt-engine-sdk4-4.3.2-2.el7.x86_64
ovirt-release43-4.3.7-1.el7.noarch
python2-ovirt-setup-lib-1.2.0-1.el7.noarch
ovirt-engine-wildfly-overlay-17.0.1-1.el7.noarch
ovirt-imageio-proxy-1.5.2-0.el7.noarch
ovirt-engine-sdk-python-3.6.9.1-1.el7.noarch
ovirt-vmconsole-1.0.7-2.el7.noarch
ovirt-engine-wildfly-17.0.1-1.el7.x86_64
ovirt-ansible-image-template-1.1.12-1.el7.noarch
ovirt-ansible-manageiq-1.1.14-1.el7.noarch
ovirt-engine-tools-4.3.6.7-1.el7.noarch
ovirt-engine-dbscripts-4.3.6.7-1.el7.noarch
cockpit-ovirt-dashboard-0.13.8-1.el7.noarch
ovirt-engine-extension-aaa-ldap-1.3.10-1.el7.noarch
ovirt-engine-setup-plugin-ovirt-engine-4.3.7.2-1.el7.noarch
ovirt-host-deploy-java-1.8.4-1.el7.noarch
ovirt-hosted-engine-ha-2.3.6-1.el7.noarch
ovirt-engine-metrics-1.3.5.1-1.el7.noarch
ovirt-engine-extensions-api-impl-4.3.7.2-1.el7.noarch
ovirt-engine-dwh-setup-4.3.6-1.el7.noarch
ovirt-engine-api-explorer-0.0.5-1.el7.noarch
ovirt-host-deploy-common-1.8.4-1.el7.noarch
ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.7.2-1.el7.noarch
ovirt-engine-vmconsole-proxy-helper-4.3.7.2-1.el7.noarch
ovirt-engine-tools-backup-4.3.6.7-1.el7.noarch
ovirt-ansible-engine-setup-1.1.9-1.el7.noarch
ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch
ovirt-engine-webadmin-portal-4.3.6.7-1.el7.noarch
ovirt-imageio-daemon-1.5.2-0.el7.noarch
ovirt-vmconsole-host-1.0.7-2.el7.noarch
ovirt-engine-setup-plugin-websocket-proxy-4.3.7.2-1.el7.noarch
ovirt-host-dependencies-4.3.5-1.el7.x86_64
ovirt-ansible-hosted-engine-setup-1.0.32-1.el7.noarch
ovirt-imageio-proxy-setup-1.5.2-0.el7.noarch
ovirt-iso-uploader-4.3.2-1.el7.noarch
ovirt-ansible-disaster-recovery-1.2.0-1.el7.noarch
ovirt-engine-extension-aaa-jdbc-1.1.10-1.el7.noarch
ovirt-engine-backend-4.3.6.7-1.el7.noarch
ovirt-engine-extension-aaa-ldap-setup-1.3.10-1.el7.noarch
ovirt-imageio-common-1.5.2-0.el7.x86_64
ovirt-engine-cli-3.6.9.2-1.el7.noarch
ovirt-provider-ovn-driver-1.2.27-1.el7.noarch
ovirt-engine-setup-base-4.3.7.2-1.el7.noarch
ovirt-engine-websocket-proxy-4.3.7.2-1.el7.noarch
ovirt-ansible-infra-1.1.13-1.el7.noarch

Kernel Version:
$ uname -r
3.10.0-1062.4.3.el7.x86_64

RedHat Version:
$ cat /etc/redhat-release
CentOS Linux release 7.7.1908 (Core)
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3NEMXEWZYBGBZK4PK7FVIKCCUWQGZGPV/

[ovirt-users] Re: terraform integration

[Roy Golan]

On Thu, 21 Nov 2019 at 08:48, Roy Golan  wrote:

>
>
> On Wed, 20 Nov 2019 at 09:49, Nathanaël Blanchet  wrote:
>
>>
>> Le 19/11/2019 à 19:23, Nathanaël Blanchet a écrit :
>>
>>
>> Le 19/11/2019 à 13:43, Roy Golan a écrit :
>>
>>
>>
>> On Tue, 19 Nov 2019 at 14:34, Nathanaël Blanchet 
>> wrote:
>>
>>> Le 19/11/2019 à 08:55, Roy Golan a écrit :
>>>
>>> oc get -o json clusterversion
>>>
>>> This is the output of the previous failed deployment, I'll give a try to
>>> a newer one when I'll have a minute to test
>>>
>> Without changing nothing with template,  I gave a new try and... nothing
>> works anymore now, none of provided IPs can be pingued : dial tcp
>> 10.34.212.51:6443: connect: no route to host", so none of masters can be
>> provisonned by bootstrap.
>>
>> I tried with the latest rhcos and latest ovirt 4.3.7, it is the same.
>> Obviously something changed since my first attempt 12 days ago... is your
>> docker image for openshift-installer up to date?
>>
>> Are you still able to your side to deploy a valid cluster ?
>>
>> I investigated looking at bootstrap logs (attached) and it seems that
>> every containers die immediately after been started.
>>
>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.60107571
>> + UTC m=+0.794838407 container init
>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623197173
>> + UTC m=+0.816959853 container start
>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>> Nov 20 07:02:33 localhost podman[2024]: 2019-11-20 07:02:33.623814258
>> + UTC m=+0.817576965 container attach
>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>> Nov 20 07:02:34 localhost systemd[1]:
>> libpod-446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603.scope:
>> Consumed 814ms CPU time
>> Nov 20 07:02:34 localhost podman[2024]: 2019-11-20 07:02:34.100569998
>> + UTC m=+1.294332779 container died
>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>> Nov 20 07:02:35 localhost podman[2024]: 2019-11-20 07:02:35.138523102
>> + UTC m=+2.332285844 container remove
>> 446dc9b7a04ff3ff4bbcfa6750e3946c084741b39707eb088c9d7ae648e35603 (image=
>> registry.svc.ci.openshift.org/origin/release:4.3, name=eager_cannon)
>>
>> and this:
>>
>> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4895271909
>> remote_runtime.go:200] CreateContainer in sandbox
>> "58f2062aa7b6a5b2bdd6b9cf7b41a9f94ca2b30ad5a20e4fa4dec8a9b82f05e5" from
>> runtime service failed: rpc error: code = Unknown desc = container create
>> failed: container_linux.go:345: starting container process caused "exec:
>> \"runtimecfg\": executable file not found in $PATH"
>> Nov 20 07:04:16 localhost hyperkube[1909]: E1120 07:04:16.4897141909
>> kuberuntime_manager.go:783] init container start failed:
>> CreateContainerError: container create failed: container_linux.go:345:
>> starting container process caused "exec: \"runtimecfg\": executable file
>> not found in $PATH"
>>
>> What do you think about this?
>>
>
> I'm seeing the same now, checking...
>
>
Because of the move upstream to release OKD the release-image that comes
with the installer I gave you are no longer valid.

I need to prepare an installer version with the preview of OKD, you can
find the details here
https://mobile.twitter.com/smarterclayton/status/1196477646885965824



(do I need to use the terraform-workers tag instead of latest?)
>>>
>>> docker pull quay.io/rgolangh/openshift-installer:terraform-workers
>>>
>>>
>>> [root@openshift-installer
>>> openshift-origin-client-tools-v3.11.0-0cbc58b-linux-64bit]# ./oc get -o
>>> json clusterversion
>>> {
>>> "apiVersion": "v1",
>>> "items": [
>>> {
>>> "apiVersion": "config.openshift.io/v1",
>>> "kind": "ClusterVersion",
>>> "metadata": {
>>> "creationTimestamp": "2019-11-07T12:23:06Z",
>>> "generation": 1,
>>> "name": "version",
>>> "namespace": "",
>>> "resourceVersion": "3770202",
>>> "selfLink": "/apis/
>>> config.openshift.io/v1/clusterversions/version",
>>> "uid": "77600bba-6e71-4b35-a60b-d8ee6e0f545c"
>>> },
>>> "spec": {
>>> "channel": "stable-4.3",
>>> "clusterID": "6f87b719-e563-4c0b-ab5a-1144172bc983",
>>> "upstream":
>>> "https://api.openshift.com/api/upgrades_info/v1/graph";
>>> 
>>> },
>>> "status": {
>>>  

[ovirt-users] [ANN] oVirt 4.3.7 is now generally available

[Sandro Bonazzola]

The oVirt Project is pleased to announce the general availability of oVirt
4.3.7 as of November 21st, 2019.



This update is the seventh in a series of stabilization updates to the 4.3
series.



This release is available now on x86_64 architecture for:

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)



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

* Red Hat Enterprise Linux 7.7 or later (but < 8)

* CentOS Linux (or similar) 7.7 or later (but < 8)

* oVirt Node 4.3 (available for x86_64 only)



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



Notes:

- oVirt Appliance is already available

- oVirt Node is already available[2]

oVirt Node and Appliance have been updated including:

- oVirt 4.3.7: http://www.ovirt.org/release/4.3.7/

- Latest CentOS 7.7 updates including:

   -

   CEBA-2019:3077 CentOS 7 binutils BugFix Update
   
   -

   CEBA-2019:3057 CentOS 7 lvm2 BugFix Update
   
   -

   CEBA-2019:3081 CentOS 7 firewalld BugFix Update
   
   -

   CEBA-2019:3054 CentOS 7 hostname BugFix Update
   
   -

   CESA-2019:3128 Important CentOS 7 java-1.8.0-openjdk Security Update
   
   -

   (CESA not published yet, Important: kernel security update)
   https://access.redhat.com/errata/RHSA-2019:3889
   -

   CEEA-2019:3846 CentOS 7 microcode_ctl Enhancement Update
   

   -

   CESA-2019:2964 Important CentOS 7 patch Security Update
   
   -

   CEBA-2019:3068 CentOS 7 procps-ng BugFix Update
   
   -

   CEBA-2019:3061 CentOS 7 rsyslog BugFix Update
   
   -

   CESA-2019:3197 Important CentOS 7 sudo Security Update
   
   -

   CEBA-2019:3072 CentOS 7 systemd BugFix Update
   
   -

   CEBA-2019:3056 CentOS 7 dnsmasq BugFix Update
   

   -

   CEBA-2019:3070 CentOS 7 ipa BugFix Update
   
   -

   CEBA-2019:3071 CentOS 7 libguestfs BugFix Update
   

   -

   CEBA-2019:3066 CentOS 7 sos BugFix Update
   


- latest CentOS Virt and Storage SIG updates:

   -

   Ansible 2.9.1:
   
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-1
   -

   Glusterfs 6.6: https://docs.gluster.org/en/latest/release-notes/6.6/
   -

   QEMU KVM EV 2.12.0-33.1.el7_7.4 :
   https://cbs.centos.org/koji/buildinfo?buildID=27696



Given the amount of security fixes provided by this release, upgrade is
recommended as soon as practical.

Additional Resources:

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

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

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


-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D 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/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/R5HUCIHSRJHZPHALDEZM55UHQKCFNPP5/

[ovirt-users] Re: metrics

[Shirly Radco]

On Wed, Nov 20, 2019 at 5:46 PM  wrote:

> Hi,
>
> I overcame this problem after configuring an hostname on
> metrics-store-installer, add a static IP and add this host to /etc/hosts on
> the engine.
>

I'm happy to hear that!
Please note that adding the hot to  /etc/hosts can be done by setting the
"create_host_entry" to true
in the metrics-store-config.yml

Best,
Shirly

>
> --
> *De: *supo...@logicworks.pt
> *Para: *"Shirly Radco" 
> *Cc: *"users" 
> *Enviadas: *Terça-feira, 19 De Novembro de 2019 17:08:10
> *Assunto: *[ovirt-users] Re: metrics
>
> Hello,
>
> Still cannot find it.
>
> # echo $ANSIBLE_DEBUG
> 1
>
> I just find this:
>
> 2019-11-19 16:25:50,264 p=root u=6462 | ok: [localhost]
> 2019-11-19 16:25:50,296 p=root u=6462 | TASK
> [/usr/share/ansible/roles/oVirt.metrics/roles/oVirt.origin-on-ovirt :
> Collect oVirt VM facts]
> 
> 2019-11-19 16:30:54,647 p=root u=6462 | fatal: [localhost]: FAILED! =>
> {"attempts": 5, "censored": "the output has been hidden due to the fact
> that 'no_log: true' was specified for this result", "changed": false}
> 2019-11-19 16:30:54,679 p=root u=6462 | TASK
> [/usr/share/ansible/roles/oVirt.metrics/roles/oVirt.origin-on-ovirt :
> Logout from oVirt]
> *
> 2019-11-19 16:30:55,074 p=root u=6462 | ok: [localhost]
> 2019-11-19 16:30:55,107 p=root u=6462 | TASK
> [oVirt.metrics/roles/oVirt.metrics-store-installation : Delete
> engine_id_rsa.pub]
> 
>
>
> Maybe I'm missing something?
>
> --
> *De: *"Shirly Radco" 
> *Para: *supo...@logicworks.pt
> *Cc: *"Jayme" , "users" 
> *Enviadas: *Terça-feira, 19 De Novembro de 2019 14:01:20
> *Assunto: *Re: [ovirt-users] Re: metrics
>
> Hi,
>
> Did you try running the playbook with the ANSIBLE_DEBUG=1 ? It should show
> you the issue in the log that
> is located under /var/log/ovirt-engine/ansible/ .
>
> Best,
>
> Shirly
>
>
>
> On Mon, Nov 18, 2019 at 7:56 PM  wrote:
>
>> Hello,
>>
>> I attached the log. Cannot figure it out where is the issue.
>>
>> Any idea?
>>
>> Thanks
>>
>> José
>>
>> --
>> *De: *"Shirly Radco" 
>> *Para: *supo...@logicworks.pt
>> *Cc: *"Jayme" , "users" 
>> *Enviadas: *Segunda-feira, 18 De Novembro de 2019 10:24:28
>> *Assunto: *Re: [ovirt-users] Re: metrics
>>
>>
>> --
>>
>>
>> Shirly Radco
>>
>> BI Principal Software Engineer
>>
>> Red Hat 
>>
>>
>> 
>>
>>
>> On Fri, Nov 15, 2019 at 7:34 PM  wrote:
>>
>>> Ok, found this
>>> https://github.com/oVirt/ovirt-ansible-image-template/pull/47
>>> and change
>>>
>>> retries: "{{ (disk_resize_timeout / 3) | int }}"
>>> delay: 3
>>>
>>> to
>>>
>>> retries: 60
>>> delay: 3
>>>
>>> in
>>> /usr/share/ansible/roles/ovirt.image-template/tasks/qcow2_image.yml
>>>
>>> but now I'm stuck in here:
>>>
>>> TASK [/usr/share/ansible/roles/oVirt.metrics/roles/oVirt.origin-on-ovirt
>>> : Collect oVirt VM facts]
>>> *
>>> FAILED - RETRYING: Collect oVirt VM facts (5 retries left).
>>> FAILED - RETRYING: Collect oVirt VM facts (4 retries left).
>>> FAILED - RETRYING: Collect oVirt VM facts (3 retries left).
>>> FAILED - RETRYING: Collect oVirt VM facts (2 retries left).
>>> FAILED - RETRYING: Collect oVirt VM facts (1 retries left).
>>> fatal: [localhost]: FAILED! => {"attempts": 5, "censored": "the output
>>> has been hidden due to the fact that 'no_log: true' was specified for this
>>> result", "changed": false}
>>>
>>
>> There is probably something wrong with your engine credentials.
>> You try setting ANSIBLE_DEBUG to true to debug this issue.
>> ANSIBLE_DEBUG ignores np_log so please keep in mind that your password
>> will be readable and you might want to delete the log once you finish.
>>
>>
>>>
>>> after the creation of metrics-store-installer VM
>>>
>>>
>>>
>>> --
>>> *De: *supo...@logicworks.pt
>>> *Para: *"Jayme" 
>>> *Cc: *"users" 
>>> *Enviadas: *Sexta-feira, 15 De Novembro de 2019 16:11:25
>>> *Assunto: *[ovirt-users] Re: metrics
>>>
>>> Well, I did a mistake when copying the metrics-store-config.yml
>>>
>>> But now I'm getting this error
>>> ..
>>> FAILED - RETRYING: Wait for resize (1 retries left)
>>> fatal: [localhost]: FAILED! => {"attempts": 40, "changed": false,
>>> "disk": {"actual_size": 942409728, "alias": "centos76", "backup": "none",
>>> "content_type": "data",
>>> "description": "", "disk_profile": {"href":
>>> "/ovirt-engine/api/diskprofiles/13b70c52-8265-4cd2-aac0-3497750bd03b",
>>> "id": "13b70c52-8265-4cd2-aac0-3497750bd03b"},
>>> "format": "cow", "href":
>>> "/ovirt-engine/api/disks/2abbe5f5-7534-4d6e-bd91-9ce1c135de13", "id":
>>> "2abbe5f5-7534-4d6e-bd91-9ce1c135de13", "image_id":
>>> "ad50f9c0-1b07-43fb-bea2-9f38

[ovirt-users] Re: [ANN] oVirt 4.3.7 Third Release Candidate is now available for testing

[Nir Soffer]

On Thu, Nov 21, 2019 at 8:20 AM Sahina Bose  wrote:

>
>
> On Thu, Nov 21, 2019 at 6:03 AM Strahil Nikolov 
> wrote:
>
>> Hi All,
>>
>> another clue in the logs :
>> [2019-11-21 00:29:50.536631] W [MSGID: 114031]
>> [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-data_fast-client-1:
>> remote operation failed. Path:
>> /.shard/b0af2b81-22cf-482e-9b2f-c431b6449dae.79
>> (----) [Permission denied]
>> [2019-11-21 00:29:50.536798] W [MSGID: 114031]
>> [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-data_fast-client-0:
>> remote operation failed. Path:
>> /.shard/b0af2b81-22cf-482e-9b2f-c431b6449dae.79
>> (----) [Permission denied]
>> [2019-11-21 00:29:50.536959] W [MSGID: 114031]
>> [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-data_fast-client-2:
>> remote operation failed. Path:
>> /.shard/b0af2b81-22cf-482e-9b2f-c431b6449dae.79
>> (----) [Permission denied]
>> [2019-11-21 00:29:50.537007] E [MSGID: 133010]
>> [shard.c:2327:shard_common_lookup_shards_cbk] 0-data_fast-shard: Lookup on
>> shard 79 failed. Base file gfid = b0af2b81-22cf-482e-9b2f-c431b6449dae
>> [Permission denied]
>> [2019-11-21 00:29:50.537066] W [fuse-bridge.c:2830:fuse_readv_cbk]
>> 0-glusterfs-fuse: 12458: READ => -1
>> gfid=b0af2b81-22cf-482e-9b2f-c431b6449dae fd=0x7fc63c00fe18 (Permission
>> denied)
>> [2019-11-21 00:30:01.177665] I [MSGID: 133022]
>> [shard.c:3674:shard_delete_shards] 0-data_fast-shard: Deleted shards of
>> gfid=eb103fbf-80dc-425d-882f-1e4efe510db5 from backend
>> [2019-11-21 00:30:13.132756] W [MSGID: 114031]
>> [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-data_fast-client-0:
>> remote operation failed. Path:
>> /.shard/17c663c2-f582-455b-b806-3b9d01fb2c6c.79
>> (----) [Permission denied]
>> [2019-11-21 00:30:13.132824] W [MSGID: 114031]
>> [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-data_fast-client-1:
>> remote operation failed. Path:
>> /.shard/17c663c2-f582-455b-b806-3b9d01fb2c6c.79
>> (----) [Permission denied]
>> [2019-11-21 00:30:13.133217] W [MSGID: 114031]
>> [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-data_fast-client-2:
>> remote operation failed. Path:
>> /.shard/17c663c2-f582-455b-b806-3b9d01fb2c6c.79
>> (----) [Permission denied]
>> [2019-11-21 00:30:13.133238] E [MSGID: 133010]
>> [shard.c:2327:shard_common_lookup_shards_cbk] 0-data_fast-shard: Lookup on
>> shard 79 failed. Base file gfid = 17c663c2-f582-455b-b806-3b9d01fb2c6c
>> [Permission denied]
>> [2019-11-21 00:30:13.133264] W [fuse-bridge.c:2830:fuse_readv_cbk]
>> 0-glusterfs-fuse: 12660: READ => -1
>> gfid=17c663c2-f582-455b-b806-3b9d01fb2c6c fd=0x7fc63c007038 (Permission
>> denied)
>> [2019-11-21 00:30:38.489449] W [MSGID: 114031]
>> [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-data_fast-client-0:
>> remote operation failed. Path:
>> /.shard/a10a5ae8-108b-4d78-9e65-cca188c27fc4.6
>> (----) [Permission denied]
>> [2019-11-21 00:30:38.489520] W [MSGID: 114031]
>> [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-data_fast-client-1:
>> remote operation failed. Path:
>> /.shard/a10a5ae8-108b-4d78-9e65-cca188c27fc4.6
>> (----) [Permission denied]
>> [2019-11-21 00:30:38.489669] W [MSGID: 114031]
>> [client-rpc-fops_v2.c:2634:client4_0_lookup_cbk] 0-data_fast-client-2:
>> remote operation failed. Path:
>> /.shard/a10a5ae8-108b-4d78-9e65-cca188c27fc4.6
>> (----) [Permission denied]
>> [2019-11-21 00:30:38.489717] E [MSGID: 133010]
>> [shard.c:2327:shard_common_lookup_shards_cbk] 0-data_fast-shard: Lookup on
>> shard 6 failed. Base file gfid = a10a5ae8-108b-4d78-9e65-cca188c27fc4
>> [Permission denied]
>> [2019-11-21 00:30:38.489777] W [fuse-bridge.c:2830:fuse_readv_cbk]
>> 0-glusterfs-fuse: 12928: READ => -1
>> gfid=a10a5ae8-108b-4d78-9e65-cca188c27fc4 fd=0x7fc63c01a058 (Permission
>> denied)
>>
>>
>> Anyone got an idea why is it happening?
>> I checked user/group and selinux permissions - all OK
>>
>
Can you share the commands (and output) used to check this?

I would try this on the hypervisor to check what vdsm/qemu see:

$ ls -lahRZ /rhv/data-center/mnt/glusterSD/gluster-server:_path

Also, to make sure we don't have selinux issue on the hypervisor, you can
change
selinux to permissive mode:

setenforce 0

And then try again. If this was selinux issue the permission denied issue
will disappear.
If this is the case please provide the output of:

ausearh -m AVC -ts today

If the issue still exists, we eliminated selinux, and you can enable it
again:

setenforce 1

Nir


> I even replaced one of the disks and healed , but the result is the same
>> for all my VMs.
>>
>
> Have you checked the permission for user/group are set correctly across
> all the bricks in the cluster?
> What does ls -la on the images directory from

[ovirt-users] Can't start VM. An old snapshot is hold a vm state

[serphentos]

Hello.
I have a two vm's that can't start because a old snapshot (auto-generated then 
we migrate a disk to another storage)
I tried to unlock entity and start vm or remove snapshot but still receive an 
errors.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/X2R4S4WGTJSLKT4FGYQFKHQ3TTVYCBBJ/

[ovirt-users] python ovirtsdk

[serphentos]

Hello.
Can someone explain how to attach logical network to host via ovirtsdk?
I saw a example of attaching networks to cluster or dc, but not a host
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/assign_network_to_cluster.py
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/6OH7ONBLNBN6NC52YWA3ARR7ZZLW6EKH/