[ovirt-users] Re: Issues with resizing Gluster Volumes with sharding and lookup-optimize enabled

2021-11-08 Thread Strahil Nikolov via Users 
What about Listing volumes via:
http://ovirt.github.io/ovirt-engine-api-model/4.4/#services/gluster_volumes -> 
list

And changing the option via:
http://ovirt.github.io/ovirt-engine-api-model/4.4/#services/gluster_volume -> 
setoption


Best Regards,
Strahil Nikolov




В понеделник, 8 ноември 2021 г., 16:47:06 ч. Гринуич+2, Gobinda Das 
 написа: 







On Mon, Nov 8, 2021 at 7:45 PM Satheesaran Sundaramoorthi  
wrote:
> On Mon, Nov 8, 2021 at 4:01 PM Sandro Bonazzola  wrote:
>> Il giorno dom 7 nov 2021 alle ore 17:27 Strahil Nikolov 
>>  ha scritto:
>>> Hello All,
>>> 
>>> I recently found a RH solution regards issues with resizing Gluster volumes 
>>> with lookup-optimize enabled and I think it's worth sharing:
>>> https://access.redhat.com/solutions/5896761
>>> https://github.com/gluster/glusterfs/issues/1918
>>> 
>>> @Sandro,
>>> Do you think it's worth checking and disabling that Gluster option on oVirt 
>>> upgrade ? It might affect older setups that might still have it enabled.
>>> 
>>> Best Regards,
>>> Strahil Nikolov
>>> 
> Hello Strahil and others,
> 
> Yes, it would definitely help if we could disable the gluster volume option 
> 'lookup-optimize' during upgrade.
> The challenge here would be how to achieve this, we do not have any hooks in 
> place for upgrade neither in ovirt nor in gluster.
> @Gobinda Das Do you see any way to achieve this ?
I don't remember any option available for this instead of a manual way. 
> 
> Thanks,
> Satheesaran Sundaramoorthi
> 
> 


-- 


Thanks,
Gobinda
___
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/T6YLQROR2ANQWFELCFPSH73SAXOKGUDY/

[ovirt-users] Re: Viewing and hopefully, modifying the VM's qemu command line

2021-11-08 Thread Gilboa Davara 
On Mon, Nov 8, 2021 at 5:37 PM Gilboa Davara  wrote:

> Hello all,
>
> I'm setting up a fairly (?) complex oVirt over Gluster setup built around
> 3 Xeon servers-turned-into-workstations, each doubling as oVirt node + one
> primary Fedora VM w/ a dedicated passthrough GPU (+audio and a couple of
> USB root devices).
> One of the servers seems to have some weird issue w/ the passthrough
> nVidia GPU that seems to require me to edit the VM iommu (1) and
> passthrough device (2) command line.
> I tried using the qemu-cmdline addon to add the missing parameters, but it
> seems that qemu treats the added parameters as an additional device / iommu
> instead of editing the existing parameters.
>
> So:
> 1. How can I view the VM qemu command line?
> 2. Can I somehow manually edit the qemu command line, either directly or
> by somehow adding parameters in the HE XML file?
>
> - Gilboa.
> [1] iommu:  VM XXX is down with error. Exit message: internal error: qemu
> unexpectedly closed the monitor: 2021-11-05T14:59:44.499366Z qemu-kvm: We
> need to set caching-mode=on for intel-iommu to enable device assignment
> with IOMMU protection.
> [2] GPU: May need to add x-vga=off,
>

BTW, FWIW, by isolated I mean device attached during boot to vfio_pci, and
passed to the VM with all of its iommu group members (e.g. nVidia GPU +
nVidia HDMI audio).

- Gilboa
___
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/QB5JWEEGXKMR36EJDTDZCIORFPEBJYRZ/

[ovirt-users] Re: Viewing and hopefully, modifying the VM's qemu command line

2021-11-08 Thread Nir Soffer 
On Mon, Nov 8, 2021 at 5:47 PM Gilboa Davara  wrote:
>
> Hello all,
>
> I'm setting up a fairly (?) complex oVirt over Gluster setup built around 3 
> Xeon servers-turned-into-workstations, each doubling as oVirt node + one 
> primary Fedora VM w/ a dedicated passthrough GPU (+audio and a couple of USB 
> root devices).
> One of the servers seems to have some weird issue w/ the passthrough nVidia 
> GPU that seems to require me to edit the VM iommu (1) and passthrough device 
> (2) command line.
> I tried using the qemu-cmdline addon to add the missing parameters, but it 
> seems that qemu treats the added parameters as an additional device / iommu 
> instead of editing the existing parameters.
>
> So:
> 1. How can I view the VM qemu command line?

less /var/log/libvirt/qemu/vm-name.log

> 2. Can I somehow manually edit the qemu command line, either directly or by 
> somehow adding parameters in the HE XML file?

I think this should be possible via vdsm hook, but hooks are bad.
Can you explain what do you want to change?

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

[ovirt-users] Viewing and hopefully, modifying the VM's qemu command line

2021-11-08 Thread Gilboa Davara 
Hello all,

I'm setting up a fairly (?) complex oVirt over Gluster setup built around 3
Xeon servers-turned-into-workstations, each doubling as oVirt node + one
primary Fedora VM w/ a dedicated passthrough GPU (+audio and a couple of
USB root devices).
One of the servers seems to have some weird issue w/ the passthrough nVidia
GPU that seems to require me to edit the VM iommu (1) and passthrough
device (2) command line.
I tried using the qemu-cmdline addon to add the missing parameters, but it
seems that qemu treats the added parameters as an additional device / iommu
instead of editing the existing parameters.

So:
1. How can I view the VM qemu command line?
2. Can I somehow manually edit the qemu command line, either directly or by
somehow adding parameters in the HE XML file?

- Gilboa.
[1] iommu:  VM XXX is down with error. Exit message: internal error: qemu
unexpectedly closed the monitor: 2021-11-05T14:59:44.499366Z qemu-kvm: We
need to set caching-mode=on for intel-iommu to enable device assignment
with IOMMU protection.
[2] GPU: May need to add x-vga=off,
___
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/WGP2VUHG3QHZKCEX2GE3DFLGEI4DT7FW/

[ovirt-users] Re: Suggested upgrading path from CentOS based 4.4.8 to 4.4.9

2021-11-08 Thread Christoph Timm 

Hi Gianluca,

I have a self hosted platform with plain CentOS 8.4 host. Also my engine 
is currently running CentOS 8.4.

I updated my whole system from 4.4.7 to 4.4.9.

As 4.4.9 does not support CentOS hosts I had to migrate them to CentOS 
Stream 8 as well.
Due to dependency issues I have put the host into maintenance mode and 
did the rest through CLI.


# dnf swap centos-linux-repos centos-stream-repos
# dnf update ovirt-release44
# dnf distro-sync
# reboot
Done

I did not change the engine OS aa CentOS 8.4 is still supported here.

Also I did the update in multiple steps over a couple of days which did 
not cause any issue on my side.


Hope this helps.

Best regards
Christoph

Am 08.11.21 um 13:41 schrieb Gianluca Cecchi:
I have a lab with an environment based on 4.4.8.6-1, with 3 CentOS 
Linux 8.4 hosts and a CentOS 8.4 external engine system (that is a VM 
on vSphere, so that I can leverage a snapshot methodology for the 
process...).
I would like to pass to 4.4.9 and retain a full plain OS on hosts for 
the moment, without going through oVirt nodes, but standing the repo 
problems and CentOS 8.x going through EOL this is what I'm planning to do:


1. stop engine service on engine system

2. convert engine to CentOS Stream
This step needs some confirmation.
Could you provide an official link about the process?
I'm not able to find it again. Is it a problem of mine or all (CentOS 
website, RHEL website) seem to point only to conversion from CentOS 
Linux to RHEL??
Apart external websites provided workflows, I was only able to find a 
mid January youtube video, when CentOS was based on 8.3, with these steps:

yum install centos-release-stream
yum swap centos-{linux,stream}-repos
yum repolist
yum distro-sync
reboot
The video link is here:
https://www.youtube.com/watch?v=Ba2ytp_8x7s

No mention at
https://www.redhat.com/en/blog/faq-centos-stream-updates

And on CentOS page I only found this:
https://centos.org/distro-faq/
with Q7 containing only the two instructions:
dnf swap centos-linux-repos centos-stream-repos
dnf distro-sync

What to use safely?
Is it possible to include some sort of documentation or links on oVirt 
page, to migrate from CentOS Linux to CentOS Stream for oVirt upgrade 
purposes?


3. After reboot implied, I think, in step 2., use the usual steps to 
update engine to 4.4.9


4. update the first out of three hosts from CentOS Linux to CentOS 
Stream and to 4.4.9.


4.a follow the same approach of engine (when defined) and pass it to 
Stream retaining the 4.4.8.

4.b upgrade from the web admin gui to 4.4.9

5. Do the same for second host and third hosts

Any hints, comments, limitations in having mixed 4.4.8 and 4.4.9 hosts 
for a while and such?


Thanks,
Gianluca



___
Users mailing list --users@ovirt.org
To unsubscribe send an email tousers-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/L3CRTNR2IUGNRZNVQMROQABHHBKMEYPP/
___
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/RGF6HG7LSJOYTV3AVYK4VP7HPQ4UAK2A/

[ovirt-users] Re: Missing snapshot in the engine

2021-11-08 Thread Benny Zlotnik 
can you attach the output of:
  $ vdsm-tool dump-volume-chains e25db7d0-060a-4046-94b5-235f38097cd8

as well as:
  $ psql -U engine -d engine -c "\x on" -c "select * from images where
image_group_id = '4d79c1da-34f0-44e3-8b92-c4bcb8524d83'"



On Mon, Nov 8, 2021 at 11:58 AM francesco--- via Users  wrote:
>
> Hi,
>
> I have an issue with a VM (Windows Server 2016), running on Centos8, oVirt 
> host 4.4.8, oVirt engine 4.4.5. I used to perform regular snapshot (deleting 
> the previous one) on this VM but starting from 25/10 the task fail with the 
> errors that I'll attach at the bottom. The volume ID mentioned in the 
> error... :
>
> [...] vdsm.storage.exception.prepareIllegalVolumeError: Cannot prepare 
> illegal volume: ('5cb3fe58-3e01-4d32-bc7c-5907a4f858a8',) [...]
>
> ... refers to a snapshot's volume, because the ID of the current volume is 
> different and smaller that one in the engine UI with ID 
> 5aad30c7-96f0-433d-95c8-2317e5f80045:
>
> [root@ovirt-host44 4d79c1da-34f0-44e3-8b92-c4bcb8524d83]# ls -lh
> total 163G
> -rw-rw 1 vdsm kvm 154G Nov  8 10:32 5aad30c7-96f0-433d-95c8-2317e5f80045
> -rw-rw 1 vdsm kvm 1.0M Aug 31 11:49 
> 5aad30c7-96f0-433d-95c8-2317e5f80045.lease
> -rw-r--r-- 1 vdsm kvm  360 Nov  8 10:19 
> 5aad30c7-96f0-433d-95c8-2317e5f80045.meta
> -rw-rw 1 vdsm kvm 8.2G Oct 25 05:16 5cb3fe58-3e01-4d32-bc7c-5907a4f858a8
> -rw-rw 1 vdsm kvm 1.0M Oct 23 05:15 
> 5cb3fe58-3e01-4d32-bc7c-5907a4f858a8.lease
> -rw-r--r-- 1 vdsm kvm  254 Oct 25 05:16 
> 5cb3fe58-3e01-4d32-bc7c-5907a4f858a8.meta
>
>
> It seems that the last working snapshot performend on 25/10 was not 
> completely deleted and now is used as the base from a new snapshot on the 
> host side, but is not listed on the engine.
>
> Any idea? I should manually merge the snapsot on the host side? If yes, any 
> indications on that?
>
> Thank you for your time,
> Francesco
>
>
>
> --- Engine log during snapshot removal:
>
>
>
> 2021-11-08 10:19:25,751+01 INFO  
> [org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] (default 
> task-63) [469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] Lock Acquired to object 
> 'EngineLock:{exclusiveLocks='[f1d56493-b5e0-480f-87a3-5e7f373712fa=VM]', 
> sharedLocks=''}'
> 2021-11-08 10:19:26,306+01 INFO  
> [org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] 
> (EE-ManagedThreadFactory-engine-Thread-49) 
> [469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] Running command: 
> CreateSnapshotForVmCommand internal: false. Entities affected :  ID: 
> f1d56493-b5e0-480f-87a3-5e7f373712fa Type: VMAction group 
> MANIPULATE_VM_SNAPSHOTS with role type USER
> 2021-11-08 10:19:26,383+01 INFO  
> [org.ovirt.engine.core.bll.snapshots.CreateSnapshotDiskCommand] 
> (EE-ManagedThreadFactory-engine-Thread-49) 
> [469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] Running command: 
> CreateSnapshotDiskCommand internal: true. Entities affected :  ID: 
> f1d56493-b5e0-480f-87a3-5e7f373712fa Type: VMAction group 
> MANIPULATE_VM_SNAPSHOTS with role type USER
> 2021-11-08 10:19:26,503+01 INFO  
> [org.ovirt.engine.core.bll.snapshots.CreateSnapshotCommand] 
> (EE-ManagedThreadFactory-engine-Thread-49) 
> [469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] Running command: CreateSnapshotCommand 
> internal: true. Entities affected :  ID: ---- 
> Type: Storage
> 2021-11-08 10:19:26,616+01 INFO  
> [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-49) 
> [469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] START, CreateVolumeVDSCommand( 
> CreateVolumeVDSCommandParameters:{storagePoolId='609ff8db-09c5-435b-b2e5-023d57003138',
>  ignoreFailoverLimit='false', 
> storageDomainId='e25db7d0-060a-4046-94b5-235f38097cd8', 
> imageGroupId='4d79c1da-34f0-44e3-8b92-c4bcb8524d83', 
> imageSizeInBytes='214748364800', volumeFormat='COW', 
> newImageId='74e7188d-3727-4ed6-a2e5-dfa73b9e7da3', imageType='Sparse', 
> newImageDescription='', imageInitialSizeInBytes='0', 
> imageId='5aad30c7-96f0-433d-95c8-2317e5f80045', 
> sourceImageGroupId='4d79c1da-34f0-44e3-8b92-c4bcb8524d83', 
> shouldAddBitmaps='false'}), log id: 514e7f02
> 2021-11-08 10:19:26,768+01 INFO  
> [org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] 
> (EE-ManagedThreadFactory-engine-Thread-49) 
> [469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] FINISH, CreateVolumeVDSCommand, 
> return: 74e7188d-3727-4ed6-a2e5-dfa73b9e7da3, log id: 514e7f02
> 2021-11-08 10:19:26,805+01 INFO  
> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask] 
> (EE-ManagedThreadFactory-engine-Thread-49) 
> [469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] CommandAsyncTask::Adding 
> CommandMultiAsyncTasks object for command 
> 'eb1f1fdd-a46e-45e1-a6f0-3a97fe1f6e28'
> 2021-11-08 10:19:26,805+01 INFO  
> [org.ovirt.engine.core.bll.CommandMultiAsyncTasks] 
> (EE-ManagedThreadFactory-engine-Thread-49) 
> [469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] CommandMultiAsyncTasks::attachTask: 
> Attaching task '4bb54004-f96c-4f14-abca-bea477d866ea' to command

[ovirt-users] Missing snapshot in the engine

2021-11-08 Thread francesco--- via Users 
Hi,

I have an issue with a VM (Windows Server 2016), running on Centos8, oVirt host 
4.4.8, oVirt engine 4.4.5. I used to perform regular snapshot (deleting the 
previous one) on this VM but starting from 25/10 the task fail with the errors 
that I'll attach at the bottom. The volume ID mentioned in the error... :

[...] vdsm.storage.exception.prepareIllegalVolumeError: Cannot prepare illegal 
volume: ('5cb3fe58-3e01-4d32-bc7c-5907a4f858a8',) [...]

... refers to a snapshot's volume, because the ID of the current volume is 
different and smaller that one in the engine UI with ID 
5aad30c7-96f0-433d-95c8-2317e5f80045:

[root@ovirt-host44 4d79c1da-34f0-44e3-8b92-c4bcb8524d83]# ls -lh
total 163G
-rw-rw 1 vdsm kvm 154G Nov  8 10:32 5aad30c7-96f0-433d-95c8-2317e5f80045
-rw-rw 1 vdsm kvm 1.0M Aug 31 11:49 
5aad30c7-96f0-433d-95c8-2317e5f80045.lease
-rw-r--r-- 1 vdsm kvm  360 Nov  8 10:19 
5aad30c7-96f0-433d-95c8-2317e5f80045.meta
-rw-rw 1 vdsm kvm 8.2G Oct 25 05:16 5cb3fe58-3e01-4d32-bc7c-5907a4f858a8
-rw-rw 1 vdsm kvm 1.0M Oct 23 05:15 
5cb3fe58-3e01-4d32-bc7c-5907a4f858a8.lease
-rw-r--r-- 1 vdsm kvm  254 Oct 25 05:16 
5cb3fe58-3e01-4d32-bc7c-5907a4f858a8.meta


It seems that the last working snapshot performend on 25/10 was not completely 
deleted and now is used as the base from a new snapshot on the host side, but 
is not listed on the engine.

Any idea? I should manually merge the snapsot on the host side? If yes, any 
indications on that?

Thank you for your time,
Francesco



--- Engine log during snapshot removal:



2021-11-08 10:19:25,751+01 INFO  
[org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] (default 
task-63) [469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] Lock Acquired to object 
'EngineLock:{exclusiveLocks='[f1d56493-b5e0-480f-87a3-5e7f373712fa=VM]', 
sharedLocks=''}'
2021-11-08 10:19:26,306+01 INFO  
[org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] 
(EE-ManagedThreadFactory-engine-Thread-49) 
[469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] Running command: 
CreateSnapshotForVmCommand internal: false. Entities affected :  ID: 
f1d56493-b5e0-480f-87a3-5e7f373712fa Type: VMAction group 
MANIPULATE_VM_SNAPSHOTS with role type USER
2021-11-08 10:19:26,383+01 INFO  
[org.ovirt.engine.core.bll.snapshots.CreateSnapshotDiskCommand] 
(EE-ManagedThreadFactory-engine-Thread-49) 
[469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] Running command: 
CreateSnapshotDiskCommand internal: true. Entities affected :  ID: 
f1d56493-b5e0-480f-87a3-5e7f373712fa Type: VMAction group 
MANIPULATE_VM_SNAPSHOTS with role type USER
2021-11-08 10:19:26,503+01 INFO  
[org.ovirt.engine.core.bll.snapshots.CreateSnapshotCommand] 
(EE-ManagedThreadFactory-engine-Thread-49) 
[469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] Running command: CreateSnapshotCommand 
internal: true. Entities affected :  ID: ---- 
Type: Storage
2021-11-08 10:19:26,616+01 INFO  
[org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-49) 
[469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] START, CreateVolumeVDSCommand( 
CreateVolumeVDSCommandParameters:{storagePoolId='609ff8db-09c5-435b-b2e5-023d57003138',
 ignoreFailoverLimit='false', 
storageDomainId='e25db7d0-060a-4046-94b5-235f38097cd8', 
imageGroupId='4d79c1da-34f0-44e3-8b92-c4bcb8524d83', 
imageSizeInBytes='214748364800', volumeFormat='COW', 
newImageId='74e7188d-3727-4ed6-a2e5-dfa73b9e7da3', imageType='Sparse', 
newImageDescription='', imageInitialSizeInBytes='0', 
imageId='5aad30c7-96f0-433d-95c8-2317e5f80045', 
sourceImageGroupId='4d79c1da-34f0-44e3-8b92-c4bcb8524d83', 
shouldAddBitmaps='false'}), log id: 514e7f02
2021-11-08 10:19:26,768+01 INFO  
[org.ovirt.engine.core.vdsbroker.irsbroker.CreateVolumeVDSCommand] 
(EE-ManagedThreadFactory-engine-Thread-49) 
[469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] FINISH, CreateVolumeVDSCommand, return: 
74e7188d-3727-4ed6-a2e5-dfa73b9e7da3, log id: 514e7f02
2021-11-08 10:19:26,805+01 INFO  
[org.ovirt.engine.core.bll.tasks.CommandAsyncTask] 
(EE-ManagedThreadFactory-engine-Thread-49) 
[469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] CommandAsyncTask::Adding 
CommandMultiAsyncTasks object for command 'eb1f1fdd-a46e-45e1-a6f0-3a97fe1f6e28'
2021-11-08 10:19:26,805+01 INFO  
[org.ovirt.engine.core.bll.CommandMultiAsyncTasks] 
(EE-ManagedThreadFactory-engine-Thread-49) 
[469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] CommandMultiAsyncTasks::attachTask: 
Attaching task '4bb54004-f96c-4f14-abca-bea477d866ea' to command 
'eb1f1fdd-a46e-45e1-a6f0-3a97fe1f6e28'.
2021-11-08 10:19:27,033+01 INFO  
[org.ovirt.engine.core.bll.tasks.AsyncTaskManager] 
(EE-ManagedThreadFactory-engine-Thread-49) 
[469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] Adding task 
'4bb54004-f96c-4f14-abca-bea477d866ea' (Parent Command 'CreateSnapshot', 
Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), 
polling hasn't started yet..
2021-11-08 10:19:27,282+01 INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]

[ovirt-users] Setting up a server via the REST API with adding your own SSH key

2021-11-08 Thread ovirt . org 
Hello, please, how i can set ssh_key via REST API on create VM (run-once)? 
Thanks

I have this XML code, but does not working:


  true
  

  $sudoUser
  $rootPassword
  

  
$sudoUser
  
  ssh-rsa CENSORED r...@1.server.com

  
..
___
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/GK2JGVJ4PAA3ONC2YDVOQEHXBW237H4N/

[ovirt-users] Re: Missing snapshot in the engine

2021-11-08 Thread Benny Zlotnik 
usually the snapshot remains in engine and is missing in vdsm, I wonder
what happened, do you have the logs from the delete attempt on
5cb3fe58-3e01-4d32-bc7c-5907a4f858a8?

On Mon, Nov 8, 2021 at 12:21 PM Francesco Lorenzini 
wrote:

> Hi Benny,
>
> here the output:
>
> can you attach the output of:
>   $ vdsm-tool dump-volume-chains e25db7d0-060a-4046-94b5-235f38097cd8
>
>
> [root@OVIRT-HOST-44 ~]#  vdsm-tool dump-volume-chains
> e25db7d0-060a-4046-94b5-235f38097cd8
>
> Images volume chains (base volume first)
>
>image:0285b926-dff5-4769-bcf5-bbeb886ad817
>
>  - ada65f83-2a16-4ad7-87ad-bc99cb8193fc
>status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
> type: SPARSE, capacity: 134217728, truesize: 36864
>
>
>image:4d79c1da-34f0-44e3-8b92-c4bcb8524d83
>
>  - 5aad30c7-96f0-433d-95c8-2317e5f80045
>status: OK, voltype: INTERNAL, format: COW, legality:
> LEGAL, type: SPARSE, capacity: 214748364800, truesize: 165235134464
>
>  - 5cb3fe58-3e01-4d32-bc7c-5907a4f858a8
>status: OK, voltype: LEAF, format: COW, legality: ILLEGAL,
> type: SPARSE, capacity: 214748364800, truesize: 8759619584
>
>
>image:72b67a6a-0ea3-4101-90cc-a18bcf774717
>
>  - 4506da8b-d73a-46ba-a91e-07e786ae934b
>status: OK, voltype: LEAF, format: COW, legality: LEGAL,
> type: SPARSE, capacity: 32212254720, truesize: 8427077632
>
>
>image:bfc94094-9367-4590-81f0-cc590c8f84ea
>
>  - 53bed4ac-5e59-4376-a611-675f2c888b99
>status: OK, voltype: LEAF, format: RAW, legality: LEGAL,
> type: SPARSE, capacity: 134217728, truesize: 36864
>
>
> as well as:
>   $ psql -U engine -d engine -c "\x on" -c "select * from images where
> image_group_id = '4d79c1da-34f0-44e3-8b92-c4bcb8524d83'"
>
>
> engine=# select * from images where image_group_id  =
> '4d79c1da-34f0-44e3-8b92-c4bcb8524d83';
> -[ RECORD 1 ]-+-
> image_guid| 5aad30c7-96f0-433d-95c8-2317e5f80045
> creation_date | 2021-08-31 11:29:31+02
> size  | 214748364800
> it_guid   | ----
> parentid  | ----
> imagestatus   | 1
> lastmodified  | 2021-10-23 05:15:24.043+02
> vm_snapshot_id| c8285f9f-03fa-4877-90a2-0baabf42f123
> volume_type   | 2
> volume_format | 4
> image_group_id| 4d79c1da-34f0-44e3-8b92-c4bcb8524d83
> _create_date  | 2021-08-31 11:29:31.980191+02
> _update_date  | 2021-11-08 10:19:39.477886+01
> active| t
> volume_classification | 1
> qcow_compat   | 2
>
>
>
> Francesco
>
> Il 08/11/2021 11:05, Benny Zlotnik ha scritto:
>
> can you attach the output of:
>   $ vdsm-tool dump-volume-chains e25db7d0-060a-4046-94b5-235f38097cd8
>
> as well as:
>   $ psql -U engine -d engine -c "\x on" -c "select * from images where
> image_group_id = '4d79c1da-34f0-44e3-8b92-c4bcb8524d83'"
>
>
>
> On Mon, Nov 8, 2021 at 11:58 AM francesco--- via Users  
>  wrote:
>
> Hi,
>
> I have an issue with a VM (Windows Server 2016), running on Centos8, oVirt 
> host 4.4.8, oVirt engine 4.4.5. I used to perform regular snapshot (deleting 
> the previous one) on this VM but starting from 25/10 the task fail with the 
> errors that I'll attach at the bottom. The volume ID mentioned in the 
> error... :
>
> [...] vdsm.storage.exception.prepareIllegalVolumeError: Cannot prepare 
> illegal volume: ('5cb3fe58-3e01-4d32-bc7c-5907a4f858a8',) [...]
>
> ... refers to a snapshot's volume, because the ID of the current volume is 
> different and smaller that one in the engine UI with ID 
> 5aad30c7-96f0-433d-95c8-2317e5f80045:
>
> [root@ovirt-host44 4d79c1da-34f0-44e3-8b92-c4bcb8524d83]# ls -lh
> total 163G
> -rw-rw 1 vdsm kvm 154G Nov  8 10:32 5aad30c7-96f0-433d-95c8-2317e5f80045
> -rw-rw 1 vdsm kvm 1.0M Aug 31 11:49 
> 5aad30c7-96f0-433d-95c8-2317e5f80045.lease
> -rw-r--r-- 1 vdsm kvm  360 Nov  8 10:19 
> 5aad30c7-96f0-433d-95c8-2317e5f80045.meta
> -rw-rw 1 vdsm kvm 8.2G Oct 25 05:16 5cb3fe58-3e01-4d32-bc7c-5907a4f858a8
> -rw-rw 1 vdsm kvm 1.0M Oct 23 05:15 
> 5cb3fe58-3e01-4d32-bc7c-5907a4f858a8.lease
> -rw-r--r-- 1 vdsm kvm  254 Oct 25 05:16 
> 5cb3fe58-3e01-4d32-bc7c-5907a4f858a8.meta
>
>
> It seems that the last working snapshot performend on 25/10 was not 
> completely deleted and now is used as the base from a new snapshot on the 
> host side, but is not listed on the engine.
>
> Any idea? I should manually merge the snapsot on the host side? If yes, any 
> indications on that?
>
> Thank you for your time,
> Francesco
>
>
>
> --- Engine log during snapshot removal:
>
>
>
> 2021-11-08 10:19:25,751+01 INFO  
> [org.ovirt.engine.core.bll.snapshots.CreateSnapshotForVmCommand] (default 
> task-63) [469dbfd8-2e2f-4cb3-84b1-d456acc78fd9] Lock Acquired to object 
>

[ovirt-users] Re: Issues with resizing Gluster Volumes with sharding and lookup-optimize enabled

2021-11-08 Thread Sandro Bonazzola 
Il giorno dom 7 nov 2021 alle ore 17:27 Strahil Nikolov <
hunter86...@yahoo.com> ha scritto:

> Hello All,
>
> I recently found a RH solution regards issues with resizing Gluster
> volumes with lookup-optimize enabled and I think it's worth sharing:
> https://access.redhat.com/solutions/5896761
> https://github.com/gluster/glusterfs/issues/1918
>
> @Sandro,
> Do you think it's worth checking and disabling that Gluster option on
> oVirt upgrade ? It might affect older setups that might still have it
> enabled.
>
> Best Regards,
> Strahil Nikolov
>
>
>
Redirecting the question to @Gobinda Das  and
@Sundaramoorthi,
Satheesaran 

-- 

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R RHV

Red Hat EMEA 

sbona...@redhat.com


*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/G3W3RPZROTCF3YC3JBH6BDHNRURS4EZD/

[ovirt-users] Suggested upgrading path from CentOS based 4.4.8 to 4.4.9

2021-11-08 Thread Gianluca Cecchi 
I have a lab with an environment based on 4.4.8.6-1, with 3 CentOS Linux
8.4 hosts and a CentOS 8.4 external engine system (that is a VM on vSphere,
so that I can leverage a snapshot methodology for the process...).
I would like to pass to 4.4.9 and retain a full plain OS on hosts for the
moment, without going through oVirt nodes, but standing the repo problems
and CentOS 8.x going through EOL this is what I'm planning to do:

1. stop engine service on engine system

2. convert engine to CentOS Stream
This step needs some confirmation.
Could you provide an official link about the process?
I'm not able to find it again. Is it a problem of mine or all (CentOS
website, RHEL website) seem to point only to conversion from CentOS Linux
to RHEL??
Apart external websites provided workflows, I was only able to find a mid
January youtube video, when CentOS was based on 8.3, with these steps:
yum install centos-release-stream
yum swap centos-{linux,stream}-repos
yum repolist
yum distro-sync
reboot
The video link is here:
https://www.youtube.com/watch?v=Ba2ytp_8x7s

No mention at
https://www.redhat.com/en/blog/faq-centos-stream-updates

And on CentOS page I only found this:
https://centos.org/distro-faq/
with Q7 containing only the two instructions:
dnf swap centos-linux-repos centos-stream-repos
dnf distro-sync

What to use safely?
Is it possible to include some sort of documentation or links on oVirt
page, to migrate from CentOS Linux to CentOS Stream for oVirt upgrade
purposes?

3. After reboot implied, I think, in step 2., use the usual steps to update
engine to 4.4.9

4. update the first out of three hosts from CentOS Linux to CentOS Stream
and to 4.4.9.

4.a follow the same approach of engine (when defined) and pass it to Stream
retaining the 4.4.8.
4.b upgrade from the web admin gui to 4.4.9

5. Do the same for second host and third hosts

Any hints, comments, limitations in having mixed 4.4.8 and 4.4.9 hosts for
a while and such?

Thanks,
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/L3CRTNR2IUGNRZNVQMROQABHHBKMEYPP/

[ovirt-users] Re: Issues with resizing Gluster Volumes with sharding and lookup-optimize enabled

2021-11-08 Thread Satheesaran Sundaramoorthi 
On Mon, Nov 8, 2021 at 4:01 PM Sandro Bonazzola  wrote:

> Il giorno dom 7 nov 2021 alle ore 17:27 Strahil Nikolov <
> hunter86...@yahoo.com> ha scritto:
>
>> Hello All,
>>
>> I recently found a RH solution regards issues with resizing Gluster
>> volumes with lookup-optimize enabled and I think it's worth sharing:
>> https://access.redhat.com/solutions/5896761
>> https://github.com/gluster/glusterfs/issues/1918
>>
>> @Sandro,
>> Do you think it's worth checking and disabling that Gluster option on
>> oVirt upgrade ? It might affect older setups that might still have it
>> enabled.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> Hello Strahil and others,

Yes, it would definitely help if we could disable the gluster volume option
'lookup-optimize' during upgrade.
The challenge here would be how to achieve this, we do not have any hooks
in place for upgrade neither in ovirt nor in gluster.
@Gobinda Das  Do you see any way to achieve this ?

Thanks,
Satheesaran Sundaramoorthi
___
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/LKZCDLGWCGWSNGS4CRZUZWK4JZJC5KMF/

[ovirt-users] Re: Setting up a server via the REST API with adding your own SSH key

2021-11-08 Thread ovirt . org 
I found: https://lists.ovirt.org/pipermail/users/2016-April/038848.html

I also use authorized_keys instead of authorized_ssh_keys.

This topic has been resolved, thanks.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/OCF5KRTPP4Y6ADUCYYFNKHG2T5Z2QVOD/

[ovirt-users] Re: Issues with resizing Gluster Volumes with sharding and lookup-optimize enabled

2021-11-08 Thread Gobinda Das 
On Mon, Nov 8, 2021 at 7:45 PM Satheesaran Sundaramoorthi <
sasun...@redhat.com> wrote:

> On Mon, Nov 8, 2021 at 4:01 PM Sandro Bonazzola 
> wrote:
>
>> Il giorno dom 7 nov 2021 alle ore 17:27 Strahil Nikolov <
>> hunter86...@yahoo.com> ha scritto:
>>
>>> Hello All,
>>>
>>> I recently found a RH solution regards issues with resizing Gluster
>>> volumes with lookup-optimize enabled and I think it's worth sharing:
>>> https://access.redhat.com/solutions/5896761
>>> https://github.com/gluster/glusterfs/issues/1918
>>>
>>> @Sandro,
>>> Do you think it's worth checking and disabling that Gluster option on
>>> oVirt upgrade ? It might affect older setups that might still have it
>>> enabled.
>>>
>>> Best Regards,
>>> Strahil Nikolov
>>>
>>> Hello Strahil and others,
>
> Yes, it would definitely help if we could disable the gluster volume
> option 'lookup-optimize' during upgrade.
> The challenge here would be how to achieve this, we do not have any hooks
> in place for upgrade neither in ovirt nor in gluster.
> @Gobinda Das  Do you see any way to achieve this ?
>
I don't remember any option available for this instead of a manual way.

>
> Thanks,
> Satheesaran Sundaramoorthi
>
>

-- 


Thanks,
Gobinda
___
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/7VG3M2M33F24XVQ7TFKQ7SN3H6GF4BZZ/

[ovirt-users] after restore check for upgrade fails

2021-11-08 Thread p . staniforth 
Hello

After doing a a backup and restoring to a new oVirt management server check for 
upgrade of hosts fails.

Also reinstall and enroll certificate fails.

The error message is

Failed to check for available updates on host node1.example.com with message 
'Failed to run check-update of host 'node1.example.com'. Error: Failed to read 
the runner-service response. Unexpected character ('<' (code 60)): expected a 
valid value (JSON String, Number, Array, Object or token 'null', 'true' or 
'false')
 at [Source: (org.apache.http.conn.EofSensorInputStream); line: 1, column: 2]'.

Also removing and adding a host back fails

The error message is
Host node3.example.com installation failed. Failed to execute Ansible 
host-deploy role: Failed to read the runner-service response. Unexpected 
character ('<' (code 60)): expected a valid value (JSON String, Number, Array, 
Object or token 'null', 'true' or 'false')
 at [Source: (org.apache.http.conn.EofSensorInputStream); line: 1, column: 2]. 
Please check logs for more details: 
/var/log/ovirt-engine/ansible-runner-service.log.

Unfortunately the file /var/log/ovirt-engine/ansible-runner-service.log doesn't 
exist.

Regards,
   Paul S.
___
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/7FVU4GYB4HXD3HBESUIHCUV5UWUSGYL2/