[ovirt-users] Re: how to debug sanlock issue

2022-01-13 Thread Vojtech Juranek
Hi,

> Hello,
> 
> I have 3 node HCI cluster with glusterfs. oVirt 4.4.9.5-1. In last 2
> weeks I experience 2 outages where HE and all/some vms were restarted.
> While digging in logs I can see that sanlock cannot renew leases and it
> leads to killing vms as is very good described in [1].
> 
> It looks to me like some hw issue with one of the hosts but cannot find
> which one.

when you check the sanlock logs (/var/log/sanlock.log) around the time of 
outage, you should be able to see which of the host failed to renew its 
sanlock leases. It could be on some of them (could be some issue with these 
host(s)) or on all of them (in this case is more likely a network issue or 
storage issue).

Also, if you want only find out which hosts wasn't able to renew the leases, 
it's even more easy - it was the host whose VMs were killed. If the host runs 
HA VMs and host is not able to renew its leases, sanlock will kill VMs running 
on this host.

Vojta
 
> for example today's outage restarted vms on hosts 1 and 2 but not 3.
> Sanlock logs
> 
> there are these lines in /var/log/messages on host 2 (ovirt-hci02)
> 
> Jan 13 08:27:25 ovirt-hci02 sanlock[1263]: 2022-01-13 08:27:25 1416706
> [341378]: s7 delta_renew read timeout 10 sec offset 0
> /rhev/data-center/mnt/glusterSD/10.0.4.11:_vms/6de5ae6d-c7cc-4292-bdbf-10495
> a38837b/dom_md/ids Jan 13 08:28:59 ovirt-hci02 sanlock[1263]: 2022-01-13
> 08:28:59 1416800 [341257]: write_sectors delta_leader offset 1024 rv -202
> /rhev/data-center/mnt/glusterSD/10.0.4.11:_engine/816a3d0b-2e10-4900-b3cb-4a
> 9b5cd0dd5d/dom_md/ids Jan 13 08:29:27 ovirt-hci02 sanlock[1263]: 2022-01-13
> 08:29:27 1416828 [4189968]: write_sectors delta_leader offset 1024 rv -202
> /rhev/data-center/mnt/glusterSD/10.0.4.11:_engine/816a3d0b-2e10-4900-b3cb-4a
> 9b5cd0dd5d/dom_md/ids
> 
> but not on hosts 1 and 3. Could it indicate that there could be storage
> related problem on host 1?
> 
> could you please suggest further/better debugging approach?
> 
> Thanx a lot,
> 
> Jiri
> 
> [1] https://www.ovirt.org/develop/developer-guide/vdsm/sanlock.html



signature.asc
Description: This is a digitally signed message part.
___
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/UJYSBUBM3CGP762Q4WRZSF67KJNGGIVC/


[ovirt-users] Re: After restored hosted engine as a new vms, all the existing & live hosts and storage domain are showing offline

2022-01-11 Thread Vojtech Juranek
On Tuesday, 11 January 2022 01:54:55 CET dhanaraj.ramesh--- via Users wrote:
> Hi Team
> 
> due to some reasons one of our  slef hosted engine went down, hence we
> provisioned new centos vm and restored the hosted engine backup file. After
> restoring we could see all the Datacenter, cluster, storage, hosts and vm
> entities in restored ovirt engine but they all are offline. 
 
> please help us how to we connect all the running hosts and storage domain,
> vms back to restored hosted engine.  do we need to get a down time for all
> the vms to restore the hosts? how do I activate all the existing storage
> domains as is. 
 
Could you please check the logs (engine as well as vdsm logs on the hosts) why 
the storage domains are offline and post relevant parts here?

Thanks
Vojta

signature.asc
Description: This is a digitally signed message part.
___
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/HOTFMNK4VVQI7ITLEI72JGFKHUHHOCZ3/


[ovirt-users] Re: Linux VMs cannot boot from software raid0

2022-01-07 Thread Vojtech Juranek
Hi,

> Hi All,
> I recently migrated from 4.3.10 to 4.4.9 and it seems that booting from
> software raid0 (I have multiple gluster volumes) is not possible with
> Cluster compatibility 4.6 . I've tested creating a fresh VM and it also
> suffers the problem. Changing various options (virtio-scsi to virtio,
> chipset, VM type) did not help . Booting from rescue media shows that the
> data is still there, but grub always drops to rescue. Any hints are
> welcome.
> Host: CentOS Stream 8 with qemu-6.0.0oVirt 4.4.9 (latest)VM OS:
> RHEL7.9/RHEL8.5 Best Regards,Strahil Nikolov

What is the lvm version? There was recently issue [1] with specific lvm version 
(lvm2-2.03.14-1.el8.x86_64) which could cause boot failures.

Vojta

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2026370



signature.asc
Description: This is a digitally signed message part.
___
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/R2NI7T7QUD7MMIXWFRH4K7ZBTSCZSUWG/


[ovirt-users] Re: new host addition, Cannot find master domain

2021-12-09 Thread Vojtech Juranek
 
> > /usr/bin/lsblk --raw --noheadings --paths --inverse --include 253 --nodeps
> > --output type,name,mountpoint
> =
> empty output of above command

could you run it again, but instead of "--include 253" use number you get when 
run 

cat /proc/devices |grep device-mapper| cut -f 1 -d ' '

i.e.

INC=`cat /proc/devices |grep device-mapper| cut -f 1 -d ' '` &&  
/usr/bin/lsblk --raw --noheadings --paths --inverse --include $INC --nodeps  
--output type,name,mountpoint
 
> 
> 
> > vgs --readonly --config 'devices {filter=["a|.*|"]}' $VG_NAME
> 
> 
>   VG   #PV #LV #SN Attr   VSize   VFree
>   2047ffc7-cb32-4663-81ad-7f4e0becdf13   1  13   0 wz--n- 544.62g 41.00g

sorry, I was interested in LV tags, i.e. the command should be

lvs --readonly --config 'devices {filter=["a|.*|"]}' --options 
vg_name,vg_tags /dev/sdb


> 
> > remove it from blacklist
> 
> 
> but the message in the vdsm_blacklist.conf warns me against manual editing.
> Ignore ?

yes, it won't be overwritten until you run "vdsm-tool config-lvm-filter" and 
confirm you
want to overwrite it

> ___
> 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/MLBFU56KZTUJW
> NCPKPYC5AS5RWBGSSWK/



signature.asc
Description: This is a digitally signed message part.
___
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/VTB6EJGPVNYH4INI54UYP42G77R463GS/


[ovirt-users] Re: new host addition, Cannot find master domain

2021-12-08 Thread Vojtech Juranek
On Tuesday, 7 December 2021 09:03:17 CET david wrote:
> hello
> i'm adding a new host into ovirt
> after the installation procces is finished I got an error: "VDSM kvm6
> command ConnectStoragePoolVDS failed: Cannot find master domain".
> on the vdsm server in /dev/disk/by-path/ i see the block device but
> device-mapper not mappying it
> then I found the master's lun in the blacklist:
> /etc/multipath/conf.d/vdsm_blacklist.conf
> why vdsm host put the lun wwn in blacklist and

Better to check /dev/disk/by-id/. Could you check the ID of this device is the 
same as one in the blacklist?

If so, could you please also share output of 

/usr/bin/lsblk --raw --noheadings --paths --inverse --include 253 --nodeps 
--output type,name,mountpoint

and also VG info of this device:

vgs --readonly --config 'devices {filter=["a|.*|"]}' $VG_NAME

so we can analyze it?

> what I can do ?

remove it from blacklist

> 
> addition info:
> 
> Ovirt-engine 4.4.7
> vdsm server:
>  - OS Version: RHEL - 8.5 - 1.2111.el8
>  - OS Description: CentOS Linux 8
>  - Kernel Version: 4.18.0 - 348.2.1.el8_5.x86_64
>  - KVM Version: 6.0.0 - 33.el8
>  - LIBVIRT Version: libvirt-7.6.0-6.el8
>  - VDSM Version: vdsm-4.40.90.4-1.el8
> 
> the vdsm server has one link connection to the fc storage lun



signature.asc
Description: This is a digitally signed message part.
___
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/YTMPA46T53VYPSIKKQW3YROA2RU3K7UL/


[ovirt-users] Re: How to debug "Non Operational" host

2021-11-23 Thread Vojtech Juranek
On Tuesday, 23 November 2021 14:42:31 CET Gervais de Montbrun wrote:
> Hi Vojta,
> 
> Thanks for the help.
> 
> I tried to activate my server this morning and captured the logs from
> vdsm.log and engine.log. They are attached.
> 
> Something went awry with my gluster (I think) as it is showing that the
> bricks on the affected server (ovirt1) are not mounted:

It seems not to be available, therefore vdsm fails with "OSError: [Errno 116] 
Stale file handle" and therefore fails to mount it. I'd suggest to investigate 
what's happening with you Gluster storage, eventually try to mount it manually 
from affected machine - if you are able to mount it manually, vdsm should be 
able to mount it as well.

Given lots of warning in engine log "Could not associate brick 'ovirt1-
storage.dgi:/gluster_bricks/vmstore/vmstore' of volume '2670ff29-8d43-4610-
a437-c6ec2c235753' with correct network as no gluster network found in cluster 
'404c8d14-73c1-11eb-8755-00163e5907f6'", I'd probably first take a look on the 
network.

Vojta


signature.asc
Description: This is a digitally signed message part.
___
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/PZ5HTE5WOZYE4FGAUNI472IW7NE56M5V/


[ovirt-users] Re: How to debug "Non Operational" host

2021-11-22 Thread Vojtech Juranek
On Tuesday, 23 November 2021 03:36:07 CET Gervais de Montbrun wrote:
> Hi Folks,
> 
> I did a minor upgrade on the first host in my cluster and now it is
> reporting "Non Operational"
> 
> This is what yum showed as updatable. However, I did the update through the
> ovirt-engine web interface.
> 
> ovirt-node-ng-image-update.noarch   
>4.4.9-1.el8 
> ovirt-4.4 Obsoleting Packages
> ovirt-node-ng-image-update.noarch   
>4.4.9-1.el8 
> ovirt-4.4 ovirt-node-ng-image-update.noarch
>   4.4.8.3-1.el8
>@System ovirt-node-ng-image-update.noarch   
>4.4.9-1.el8 
> ovirt-4.4
> ovirt-node-ng-image-update-placeholder.noarch  
> 4.4.8.3-1.el8  
>  @System
> 
> How do I start to debug this issue?

Check engine log in /var/log/ovirt-engine/engine.log on the machine where 
engine runs

> 
> 
> Also, it looks like the vmstore brick is not mounting on that host. I only
> see the engine mounted.


Could you also attach relevant part of vdsm log (/var/log/vdsm/vdsm.log) from 
the machine where mount failed? You should see some mount related error there. 
This could be also a reason why hosts become non-operational.

Thanks
Vojta

> Broken server:
> r...@ovirt1.dgi log]# mount | grep storage
> ovirt1-storage.dgi:/engine on
> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type
> fuse.glusterfs
> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
> 131072) Working server:
> [r...@ovirt2.dgi ~]# mount | grep storage
> ovirt1-storage.dgi:/engine on
> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_engine type
> fuse.glusterfs
> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
> 131072) ovirt1-storage.dgi:/vmstore on
> /rhev/data-center/mnt/glusterSD/ovirt1-storage.dgi:_vmstore type
> fuse.glusterfs
> (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=
> 131072)
> 
> 
> I tried putting the server into maintenance mode and running a reinstall on
> it. No change. I'de really appreciate some help sorting this our.
> 
> Cheers,
> Gervais



signature.asc
Description: This is a digitally signed message part.
___
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/S6C7R6LUTJXFMG7WIODA53VEU4O7ZNHJ/


[ovirt-users] Re: Using file storage(NFS, cephfs) directly in oVirt vm

2021-10-25 Thread Vojtech Juranek
On Friday, 22 October 2021 04:08:57 CEST ssarang...@gmail.com wrote:
> Hi, I want to use NFS directly in oVirt vm. NFS server is installed on the
> oVirt host.
 How can I use it if the oVirt vm and oVirt host cannot
> communicate?

What do you mean by VM and host cannot communicate? If want to mount NFS 
export on the VM, the NFS server has to be visible from the VM. If it's not, 
you have to configure your network so that VM can reach to NFS sever. No matter 
if NFS server runs on the host which runs the VM or somewhere else.

> ___
> 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/UF7WMFT7OED4T
> V2FZR74AE47QAGB3PYT/



signature.asc
Description: This is a digitally signed message part.
___
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/LWJH7WVRNEOPFVAGDE4CRHPCEFBBLYUL/


[ovirt-users] Re: not able to upload disks, iso - paused by the system error -- Version 4.4.6.7-1.el8

2021-10-12 Thread Vojtech Juranek
On Tuesday, 12 October 2021 07:53:46 CEST dhanaraj.ramesh--- via Users wrote:
> Hi Team
> 
> in one of the cluster infra, we are unable to upload the images or disks via
> gui. up on checking the /var/log/ovirt-imageio/daemon.log found that
> throwing ssl connection failure, help us to check what are we missing.. 

looks like certificate is not trusted (invalid/missing root certificates on 
given machine?)

> We are using thirdparty CA approved SSL for web GUI.. 

did you try "Test connection" button on the upload page? If it fails, you need 
to download the certificate from [1] and make it trusted in your browser

[1] 
https://$ENGINE_ADDRESS/ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA

> 2021-10-11 22:45:42,812 INFO(Thread-6) [http] OPEN connection=6
> client=127.0.0.1
 2021-10-11 22:45:42,812 INFO(Thread-6) [tickets]
> [127.0.0.1] REMOVE ticket=f18cff91-1fc4-43b6-91ea-ca2a11d409a6 2021-10-11
> 22:45:42,813 INFO(Thread-6) [http] CLOSE connection=6 client=127.0.0.1
> [connection 1 ops, 0.000539 s] [dispatch 1 ops, 0.000216 s] 2021-10-11
> 22:45:43,621 INFO(Thread-4) [images] [:::10.12.23.212] OPTIONS
> ticket=53ff98f9-f429-4880-abe6-06c6c01473de 2021-10-11 22:45:43,621 INFO   
> (Thread-4) [backends.http] Open backend
> netloc='renlovkvma01.test.lab:54322'
> path='/images/53ff98f9-f429-4880-abe6-06c6c01473de'
> cafile='/etc/pki/ovirt-engine/ca.pem' secure=True 2021-10-11 22:45:43,626
> ERROR   (Thread-4) [http] Server error
> Traceback (most recent call last):
>   File
> "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/__init
> __.py", line 66, in get
 return ticket.get_context(req.connection_id)
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/auth.py",
> line 146, in get_context
 return self._connections[con_id]
> KeyError: 4
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/http.py",
> line 774, in __call__
 self.dispatch(req, resp)
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/http.py",
> line 819, in dispatch
 return method(req, resp, *match.groups())
>   File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/cors.py",
> line 84, in wrapper
 return func(self, req, resp, *args)
>   File
> "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/images.py",
> line 246, in options
 ctx = backends.get(req, ticket, self.config)
>   File
> "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/__init
> __.py", line 85, in get
 cafile=ca_file)
>   File
> "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.p
> y", line 48, in open
 return Backend(url, **options)
>   File
> "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.p
> y", line 76, in __init__
 self._connect()
>   File
> "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.p
> y", line 117, in _connect
 self._con = self._create_tcp_connection()
>   File
> "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.p
> y", line 379, in _create_tcp_connection
 con.connect()
>   File "/usr/lib64/python3.6/http/client.py", line 1437, in connect
> server_hostname=server_hostname)
>   File "/usr/lib64/python3.6/ssl.py", line 365, in wrap_socket
> _context=self, _session=session)
>   File "/usr/lib64/python3.6/ssl.py", line 776, in __init__
> self.do_handshake()
>   File "/usr/lib64/python3.6/ssl.py", line 1036, in do_handshake
> self._sslobj.do_handshake()
>   File "/usr/lib64/python3.6/ssl.py", line 648, in do_handshake
> self._sslobj.do_handshake()
> ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed
> (_ssl.c:897)
 ___
> 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/XMBNYE7E7C5XY
> UKO6FARQQAHCT4HOYSJ/



signature.asc
Description: This is a digitally signed message part.
___
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/ZANHCS7OZRS6MSHR7GF7LC62UJGP4F4O/


[ovirt-users] Re: API how to increase extend resize disk VM

2021-10-06 Thread Vojtech Juranek
On Wednesday, 6 October 2021 15:14:10 CEST ovirt@nevim.eu wrote:
> ovirt.domain.com: Software Version:4.3.4.3-1.el7
> ovirt2.domain.com: Software Version:4.3.10.4-1.el7
> 
> I test everything on the server ovirt2.domains.com.
> 
> No i try #1:
> GET
> https://ovirt2.domain.com/ovirt-engine/api/disks/f770c0d1-dd0d-40a8-a69a-a6
> 3d8db5c2cc
 
> Result #2:
>  id="1e0a39c1-08d5-41b1-8e4e-5174597c59c9">
 
> false
> 107374182400
> qcow2_v3
> false
> true
> ok
> image
> 20090257408
> ...
> 
> 
> No i try #2:
> PUT
> https://ovirt2.domain.com/ovirt-engine/api/disks/f770c0d1-dd0d-40a8-a69a-a6
> 3d8db5c2cc
 
>   30737418240
> 
> 
> Result #2:   
> "content": " standalone=\"yes\"?>\n\nUpdating disk attributes other
> than QCOW version is permitted only for disk-attachments, which reside
> under VMs.\nOperation Failed\n\n",
> "msg": "Status code was 409 and not [200]: HTTP Error 409: Conflict",
> "url":
> "https://ovirt2.domain.com/ovirt-engine/api/disks/f770c0d1-dd0d-40a8-a69a-a
> 63d8db5c2cc", 
> So version 4.3 really has no way to adjust the disk size via the API? The
> only way is to upgrade to 4.4?

It does, but the disk has t be attached to a VM (Vm don't has to be running).
Example XML (extend.xml):


  
2147483648
  


Example command using this XML:

curl --insecure -X PUT --header "Accept: application/xml" --header 
"Content-Type: application/xml" --user "admin@internal:ovirt" -T extend.xml 
https://engine-test.local/ovirt-engine/api/vms/651faf06-9dd3-41a5-94f6-ef126a933923/diskattachments/69f96ba5-df7b-46d7-93c1-93e4adf0404b

signature.asc
Description: This is a digitally signed message part.
___
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/L6YNAFWU5AQEGCQQ76BFY2OXBNEOJEDX/


[ovirt-users] Re: API how to increase extend resize disk VM

2021-10-05 Thread Vojtech Juranek
On Tuesday, 5 October 2021 15:44:40 CEST ovirt@nevim.eu wrote:
> But for me there is no element for the value of space. It looks something
> like this:
 
>  href="/ovirt-engine/api/vms/678faf6f-fa5f-4785-a365-e1b85925575f/diskattach
> ments/f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc"
> id="f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc">
 true
> true
> virtio_scsi
> false
> false
> false
>  id="f770c0d1-dd0d-40a8-a69a-a63d8db5c2cc"/>
  href="/ovirt-engine/api/vms/678faf6f-fa5f-4785-a365-e1b85925575f"
> id="678faf6f-fa5f-4785-a365-e1b85925575f"/> 
> 
> So is it not possible to increase extend space using the API in ovirt?


 should do the job, try to use XML snippet from

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/rest_api_guide/index#services-disk_attachment-methods-update

signature.asc
Description: This is a digitally signed message part.
___
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/OGAK4GQK5GG6U6XYQCJCXDPSSKLNPQ6K/


[ovirt-users] Re: API how to increase extend resize disk VM

2021-10-05 Thread Vojtech Juranek
On Tuesday, 5 October 2021 09:47:45 CEST ovirt@nevim.eu wrote:
> This is informations from apidoc
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/ht
> ml-single/rest_api_guide/index#services-disk-methods-update

which says
"The only field that can be updated is qcow_version."

I guess you are looking for disk_attachment update, in this manual here:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/rest_api_guide/index#services-disk_attachment-methods-update


> Here is example:
> 
> 
>   qcow2_v3
> 
> 
> But this not working if i change to this:
> 
> 
>   {{ new size > actual size }}
> 
> 
> OR
> 
> 
>   {{ new size > actual size }}
> 
> 
> I get this error: I have HTTP Error 400: Bad Request  Request syntactically
> incorrect. But syntax is OK:
> ___
> 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/E73S45SOELXWQ
> 3TCHEGLHNSZ55JGQBPL/



signature.asc
Description: This is a digitally signed message part.
___
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/VCECXIAHC6VRL4V5EKIUE3G734IPDKBL/


[ovirt-users] Re: importing an ovirt vm via the API for "Virtual Appliance OVA"

2021-10-05 Thread Vojtech Juranek
On Monday, 4 October 2021 21:56:53 CEST Divan Santana wrote:
> Vojtech Juranek  writes:
> > On Friday, 1 October 2021 07:51:56 CEST di...@santanas.co.za wrote:
> >> Hi oVirt Team,
> >> 
> >> Reading the API docs
> >> 
> >> http://ovirt.github.io/ovirt-engine-api-model/4.3/#services/external_vm_i
> >> mpo rts
> >> http://ovirt.github.io/ovirt-engine-api-model/4.3/#types/external_vm_prov
> >> id
> >> er_type
> >> and ovirt_vm module
> >> https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_
> >> mod ule.html#ansible-collections-ovirt-ovirt-ovirt-vm-module
> >> 
> >> I see support for
> >> - kvm
> >> - vmware
> >> - XEN
> >> 
> >> In the oVirt web GUI (4.3) there is under compute -> VM -> import ->
> >> source options for:
> >> - kvm
> >> - vmware
> >> - XEN
> >> - Virtual Appliance OVA
> >> 
> >> I'm trying to import an OVA that sits on the file system on the oVirt
> >> node.  Via the GUI selecting Virtual Appliance OVA does the job.
> >> 
> >> Is the API missing this functionality or am I missing something?
> > 
> > here is example how to import OVA file (for 4.4, not
> > sure about 4.3, but probably should work as well):
> > 
> > https://github.com/oVirt/python-ovirt-engine-sdk4/blob/main/examples/impor
> > t_vm_from_ova.py
> Thanks. This example is useful indeed.
> 
> Though it doesn't really answer the question.  Because this example
> uses requires KVM/libvirt storage domain AFAIK.

not sure what you mean by "KVM/libvirt storage domain", but what matters is 
what's inside OVA file which you specify on line 63 (https://github.com/oVirt/
python-ovirt-engine-sdk4/blob/main/examples/import_vm_from_ova.py#L63). 

See Arik's answer for more detail explanation. (maybe we should add it direcly 
into example?)

> Unlike the web interface which can import an ova file that is residing
> on the file system.
> 
> Having an API for that, would be nice.



signature.asc
Description: This is a digitally signed message part.
___
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/7THHASSRWQVDYLJDJ3K2G4TUKOT7FOK4/


[ovirt-users] Re: importing an ovirt vm via the API for "Virtual Appliance OVA"

2021-10-01 Thread Vojtech Juranek
On Friday, 1 October 2021 07:51:56 CEST di...@santanas.co.za wrote:
> Hi oVirt Team,
> 
> Reading the API docs
> 
> http://ovirt.github.io/ovirt-engine-api-model/4.3/#services/external_vm_impo
> rts
> http://ovirt.github.io/ovirt-engine-api-model/4.3/#types/external_vm_provid
> er_type 
> and ovirt_vm module
> https://docs.ansible.com/ansible/latest/collections/ovirt/ovirt/ovirt_vm_mod
> ule.html#ansible-collections-ovirt-ovirt-ovirt-vm-module
 
> I see support for
> - kvm
> - vmware
> - XEN
> 
> In the oVirt web GUI (4.3) there is under compute -> VM -> import ->
> source options for:
> - kvm
> - vmware
> - XEN
> - Virtual Appliance OVA
> 
> I'm trying to import an OVA that sits on the file system on the oVirt
> node.  Via the GUI selecting Virtual Appliance OVA does the job.
> 
> Is the API missing this functionality or am I missing something?

here is example how to import OVA file (for 4.4, not
sure about 4.3, but probably should work as well):

https://github.com/oVirt/python-ovirt-engine-sdk4/blob/main/examples/import_vm_from_ova.py

 
> --
> Divan Santana
> ___
> 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/2WWHXYKDSB2PG
> QVEQEV3FUPDWNCQBUXY/



signature.asc
Description: This is a digitally signed message part.
___
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/YWAC57VJL6MZX6K53QUWCGMJAMAYQH24/


[ovirt-users] Re: Host reboots when network switch goes down

2021-09-29 Thread Vojtech Juranek
On Wednesday, 29 September 2021 09:43:56 CEST cen wrote:
> Hi,
> 
> we are experiencing a weird issue with our Ovirt setup. We have two 
> physical hosts (DC1 and DC2) and mounted Lenovo NAS storage for all VM
> data.
 
> They are connected via a managed network switch.
> 
> What happens is that if switch goes down for whatever reason (firmware 
> update etc), physical host reboots. Not sure if this is an action 
> performed by Ovirt but I suspect it is because connection to mounted 
> storage is lost and it  performs some kind of an emergency action. I 
> would need to get some direction pointers to find out
> 
> a) who triggers the reboot and why

sanlock, resp. wdmd because it cannot renew the lease of some HA resource (it 
renews it by writing to the storage) and failed to kill the process using this 
resource (it should first try to kill the process and only if it fails reboot 
the host)

> c) a way to prevent reboots by increasing storage? timeouts

this is possible, but changing sanlock timeouts can be very tricky and can 
have unwanted/unexpected consequences, so be very careful. Here is a guideline 
how to do it:

https://github.com/oVirt/vdsm/blob/master/doc/io-timeouts.md


> Switch reboot takes 2-3 minutes.
> 
> 
> These are the host /var/log/messages just before reboot occurs:
> 
> Sep 28 16:20:00 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:00 7690984 
> [10993]: s11 check_our_lease warning 72 last_success 7690912
> Sep 28 16:20:00 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:00 7690984 
> [10993]: s3 check_our_lease warning 76 last_success 7690908
> Sep 28 16:20:00 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:00 7690984 
> [10993]: s1 check_our_lease warning 68 last_success 7690916
> Sep 28 16:20:00 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:00 7690984 
> [27983]: s11 delta_renew read timeout 10 sec offset 0 
> /var/run/vdsm/storage/15514c65-5d45-4ba7-bcd4-cc772351c940/fce598a8-11c3-44f
> 9-8aaf-8712c96e00ce/65413499-6970-4a4c-af04-609ef78891a2
 Sep 28 16:20:00
> ovirtnode02 sanlock[10993]: 2021-09-28 16:20:00 7690984 [27983]: s11
> renewal error -202 delta_length 20 last_success 7690912 Sep 28 16:20:00
> ovirtnode02 wdmd[11102]: test warning now 7690984 ping 7690970 close
> 7690980 renewal 7690912 expire 7690992 client 10993 sanlock_hosted-engine:2
> Sep 28 16:20:00 ovirtnode02 wdmd[11102]: test warning now 7690984 ping 
> 7690970 close 7690980 renewal 7690908 expire 7690988 client 10993 
> sanlock_3cb12f04-5d68-4d79-8663-f33c0655baa6:2
> Sep 28 16:20:01 ovirtnode02 systemd: Created slice User Slice of root.
> Sep 28 16:20:01 ovirtnode02 systemd: Started Session 15148 of user root.
> Sep 28 16:20:01 ovirtnode02 systemd: Removed slice User Slice of root.
> Sep 28 16:20:01 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:01 7690985 
> [10993]: s11 check_our_lease warning 73 last_success 7690912
> Sep 28 16:20:01 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:01 7690985 
> [10993]: s3 check_our_lease warning 77 last_success 7690908
> Sep 28 16:20:01 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:01 7690985 
> [10993]: s1 check_our_lease warning 69 last_success 7690916
> Sep 28 16:20:01 ovirtnode02 wdmd[11102]: test warning now 7690985 ping 
> 7690970 close 7690980 renewal 7690912 expire 7690992 client 10993 
> sanlock_hosted-engine:2
> Sep 28 16:20:01 ovirtnode02 wdmd[11102]: test warning now 7690985 ping 
> 7690970 close 7690980 renewal 7690908 expire 7690988 client 10993 
> sanlock_3cb12f04-5d68-4d79-8663-f33c0655baa6:2
> Sep 28 16:20:02 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:02 7690986 
> [10993]: s11 check_our_lease warning 74 last_success 7690912
> Sep 28 16:20:02 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:02 7690986 
> [10993]: s3 check_our_lease warning 78 last_success 7690908
> Sep 28 16:20:02 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:02 7690986 
> [10993]: s1 check_our_lease warning 70 last_success 7690916
> Sep 28 16:20:02 ovirtnode02 wdmd[11102]: test warning now 7690986 ping 
> 7690970 close 7690980 renewal 7690916 expire 7690996 client 10993 
> sanlock_15514c65-5d45-4ba7-bcd4-cc772351c940:2
> Sep 28 16:20:02 ovirtnode02 wdmd[11102]: test warning now 7690986 ping 
> 7690970 close 7690980 renewal 7690912 expire 7690992 client 10993 
> sanlock_hosted-engine:2
> Sep 28 16:20:02 ovirtnode02 wdmd[11102]: test warning now 7690986 ping 
> 7690970 close 7690980 renewal 7690908 expire 7690988 client 10993 
> sanlock_3cb12f04-5d68-4d79-8663-f33c0655baa6:2
> Sep 28 16:20:03 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:03 7690987 
> [10993]: s11 check_our_lease warning 75 last_success 7690912
> Sep 28 16:20:03 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:03 7690987 
> [10993]: s3 check_our_lease warning 79 last_success 7690908
> Sep 28 16:20:03 ovirtnode02 sanlock[10993]: 2021-09-28 16:20:03 7690987 
> [10993]: s1 check_our_lease warning 71 last_success 7690916
> 
> 
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email 

[ovirt-users] Re: about the Live Storage Migration

2021-09-27 Thread Vojtech Juranek
On Monday, 27 September 2021 10:32:26 CEST Tommy Sway wrote:
> Engine:
> 
> 2021-09-27 16:26:40,363+08 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HSMGetAllTasksStatusesVDSCommand]
> (EE-ManagedThreadFactory-engineScheduled-Thread-90) [] Failed in
> 'HSMGetAllTasksStatusesVDS' method
> 2021-09-27 16:26:40,390+08 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (EE-ManagedThreadFactory-engineScheduled-Thread-90) [] EVENT_ID:
> VDS_BROKER_COMMAND_FAILURE(10,802), VDSM olvms2 command
> HSMGetAllTasksStatusesVDS failed: low level Image copy failed: ()
> 2021-09-27 16:26:40,390+08 INFO
> [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
> (EE-ManagedThreadFactory-engineScheduled-Thread-90) []
> SPMAsyncTask::PollTask: Polling task '46aa9508-1029-4d8f-8840-d2c23041a6eb'
> (Parent Command 'SyncImageGroupData', Parameters Type
> 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned
> status 'finished', result 'cleanSuccess'.
> 2021-09-27 16:26:40,394+08 ERROR
> [org.ovirt.engine.core.bll.tasks.SPMAsyncTask]
> (EE-ManagedThreadFactory-engineScheduled-Thread-90) []
> BaseAsyncTask::logEndTaskFailure: Task
> '46aa9508-1029-4d8f-8840-d2c23041a6eb' (Parent Command 'SyncImageGroupData',
> Parameters Type
> 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') ended with
> failure:
> -- Result: 'cleanSuccess'
> -- Message: 'VDSGenericException: VDSErrorException: Failed to
> HSMGetAllTasksStatusesVDS, error = low level Image copy failed: (), code =
> 261',
> -- Exception: 'VDSGenericException: VDSErrorException: Failed to
> HSMGetAllTasksStatusesVDS, error = low level Image copy failed: (), code =
> 261'
> 2021-09-27 16:26:40,396+08 INFO
> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask]
> (EE-ManagedThreadFactory-engineScheduled-Thread-90) []
> CommandAsyncTask::endActionIfNecessary: All tasks of command
> '40bd5b89-54cd-4d6f-aa18-69747241eed0' has ended -> executing 'endAction'
> 2021-09-27 16:26:40,396+08 INFO
> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask]
> (EE-ManagedThreadFactory-engineScheduled-Thread-90) []
> CommandAsyncTask::endAction: Ending action for '1' tasks (command ID:
> '40bd5b89-54cd-4d6f-aa18-69747241eed0'): calling endAction '.
> 2021-09-27 16:26:40,397+08 INFO
> [org.ovirt.engine.core.bll.tasks.CommandAsyncTask]
> (EE-ManagedThreadFactory-engine-Thread-452957) []
> CommandAsyncTask::endCommandAction [within thread] context: Attempting to
> endAction 'SyncImageGroupData',
> 2021-09-27 16:26:40,404+08 ERROR
> [org.ovirt.engine.core.bll.storage.lsm.SyncImageGroupDataCommand]
> (EE-ManagedThreadFactory-engine-Thread-452957)
> [bf830d22-1724-45fa-a3c3-6f543f331397] Ending command
> 'org.ovirt.engine.core.bll.storage.lsm.SyncImageGroupDataCommand' with
> failure.
> 
> 
> VDSM.log:
> 
> 2021-09-27 16:26:51,609+0800 ERROR (libvirt/events) [virt.vm]
> (vmId='3261ae19-ddb6-4d73-9e79-55530b564999') Block job COPY for drive
> /rhev/data-center/mnt/blockSD/41bc1316-5c1d-4836-a103-5acbbf0c47a1/images/0f
> c2697b-2727-4dd2-89c4-4f3d104c1898/b3811b1e-d229-438b-9a4a-fbf5955830c6 has
> failed (vm:5892)


Is this the only vdsm error? Based on the engine log, there should be also 
some CopyImageError in the vdsm log - this would give us more context where 
exactly it failed.

Also, given that libvirt block job failed, is there any error in libvirt/qemu 
log?

 
> 
> 
> 
> 
> 
> 
> 
> 
> -Original Message-
> From: users-boun...@ovirt.org  On Behalf Of Vojtech
> Juranek
> Sent: Monday, September 27, 2021 3:23 PM
> To: users@ovirt.org; Tommy Sway 
> Subject: [ovirt-users] Re: about the Live Storage Migration
> 
> On Sunday, 26 September 2021 14:07:01 CEST Tommy Sway wrote:
> > Why always fail ?
> 
> please provide relevant part of engine and vdsm logs



signature.asc
Description: This is a digitally signed message part.
___
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/WTFNVBLJIHK4W2CZINDXP4ON56JAQIZY/


[ovirt-users] Re: about the Live Storage Migration

2021-09-27 Thread Vojtech Juranek
On Sunday, 26 September 2021 14:07:01 CEST Tommy Sway wrote:
> Why always fail ?
> 

please provide relevant part of engine and vdsm logs

signature.asc
Description: This is a digitally signed message part.
___
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/QUBCZRKOTAKUTLRSTY2L7CTDG7VMANKV/


[ovirt-users] Re: Sparse VMs from Templates - Storage issues

2021-09-22 Thread Vojtech Juranek
On Wednesday, 22 September 2021 18:09:28 CEST Shantur Rathore wrote:
> I have actually tried many types of storage now and all have this issue.

This is weird. Could you please use file-based storage (e.g. NFS) and post here 
whole exceptions from vdsm log (/var/log/vdsm/vdsm.log) and qemu log (/var/
log/libvirt/qemu/vm_name.log) from the host which runs the VM? Hopefully this 
will give us some hint what is the real issue there.
Thanks
Vojta

> 
> I am not of ideas what to do
> 
> On Wed, Sep 22, 2021 at 4:39 PM Shantur Rathore
>  wrote:
> 
> >
> >
> > Hi Nir,
> >
> >
> >
> > Just to report.
> > As suggested, I created a Posix compliant storage domain with CephFS
> > and copied my templates to CephFS.
> > Now I created VMs from CephFS templates and the storage error happens
> > again.
 As I understand, the storage growth issue is only on iSCSI.
> >
> >
> >
> > Am I doing something wrong?
> >
> >
> >
> > Kind regards,
> > Shantur
> >
> >
> >
> > On Wed, Aug 11, 2021 at 2:42 PM Nir Soffer  wrote:
> > 
> > >
> > >
> > > On Wed, Aug 11, 2021 at 4:24 PM Arik Hadas  wrote:
> > > 
> > > >
> > > >
> > > >
> > > >
> > > > On Wed, Aug 11, 2021 at 2:56 PM Benny Zlotnik 
> > > > wrote:
> > > > 
> > > >>
> > > >>
> > > >> > If your vm is temporary and you like to drop the data written
> > > >> > while
> > > >> > the vm is running, you
> > > >> > could use a temporary disk based on the template. This is called a
> > > >> > "transient disk" in vdsm.
> > > >> >
> > > >> >
> > > >> >
> > > >> > Arik, maybe you remember how transient disks are used in engine?
> > > >> > Do we have an API to run a VM once, dropping the changes to the
> > > >> > disk
> > > >> > done while the VM was running?
> > > >>
> > > >>
> > > >>
> > > >> I think that's how stateless VMs work
> > > >
> > > >
> > > >
> > > >
> > > > +1
> > > > It doesn't work exactly like Nir wrote above - stateless VMs that are
> > > > thin-provisioned would have a qcow volume on top of each template's
> > > > volume and when they starts, their active volume would be a qcow
> > > > volume on top of the aforementioned qcow volume and that active
> > > > volume will be removed when the VM goes down
 But yeah, stateless VMs
> > > > are intended for such use case
> > >
> > >
> > >
> > > I was referring to transient disks - created in vdsm:
> > > https://github.com/oVirt/vdsm/blob/45903d01e142047093bf844628b5d90df12b6
> > > ffb/lib/vdsm/virt/vm.py#L3789
> >
> > >
> > >
> > > This creates a *local* temporary file using qcow2 format, using the
> > > disk on shared
> > > storage as a backing file.
> > >
> > >
> > >
> > > Maybe this is not used by engine?
> 
> ___
> 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/3UEXYH2IGNDWW
> YEHEHKLAREJS74LMXUI/



signature.asc
Description: This is a digitally signed message part.
___
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/EWFNVMHJFES5CICXVUIRDAYAOQSB4Y57/


[ovirt-users] Re: about the vm disk type

2021-09-22 Thread Vojtech Juranek
> According to what you said, qemU-img info tool was used to query the result.
> On Block storage, theses are results:
> if preallocated, the storage format is RAW;

correct

> If Thin mode, is QCOW2;

correct

> If the VM is cloned from a template in preallocated mode, the disk consists
> of two files: the bottom back-end file is RAW, and the front end file is
> QCOW2.

correct, second one is snapshot (not to modify template image) and snaphosts 
are always qcow2

> If the vm is cloned from a Thin template, I haven't had time to test this.

both disks should be qcow2

> According to the above classification, the performance of QCOW2 is worse
> than that of RAW format.
> Therefore, using preallocation mode for Block storage can not only remove
> interference at the file system level, but also achieve performance
> advantages in file types, thus achieving the best I/O effect.
> 
> The last sentence was the result I really wanted, as I was running IO heavy
> systems on OLVM.

if you want to use only raw file format, you should use preallocated disks on 
block storage (on file storage doesn't matter) and avoid snapshots, as 
snapshots are always qcow2 format

signature.asc
Description: This is a digitally signed message part.
___
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/SUDW42FEFBDFUUOYUOX6QC2ZRPEWPMMW/


[ovirt-users] Re: about the vm disk type

2021-09-22 Thread Vojtech Juranek
Sorry for my misleading previous answer, I thought you are asking how to 
create pre/thin allocated disk. As for the format, you cannot choose it. As 
for the defaults, Benny already answered this.

> I also have block storage on my environment. How do I observe the type of a
> vm image (LV)?

What do you exactly mean? Do you ask about image format (raw vs. cow)? If so, 
you can deduce it from Benny's answer, based on the facts on which domain is 
disk stored and if it's pre-allocated or not. If you are asking how to check 
it on the storage, you can check disk metadata or you can use directly qemu-
img utility (qemu-img info /path/to/the/disk)

signature.asc
Description: This is a digitally signed message part.
___
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/VEIAVO4SPBEFHTEP7DK5ZIRDB77EGAMA/


[ovirt-users] Re: about the OVF_STORE and the xleases volume

2021-09-22 Thread Vojtech Juranek
On Wednesday, 22 September 2021 10:39:34 CEST Tommy Sway wrote:
> I wonder if the xleases volume mentioned here refers to ovf_store ?

No, xleases is part of the disk space used internally by oVirt (to manage 
concurrent access to the resources, e.g. disk image) and shouldn't be touched 
by the user.

OVF store is Open Virtualization Format [1] and it's used for storing these 
files, see [2] for more details.

[1] https://en.wikipedia.org/wiki/Open_Virtualization_Format
[2] https://www.ovirt.org/develop/release-management/features/storage/
importstoragedomain.html

> 
> 
> 
> 
> * A new xleases volume to support VM leases - this feature adds the
> ability to acquire a lease per virtual machine on shared storage without
> attaching the lease to a virtual machine disk.
> 
> A VM lease offers two important capabilities:
> 
> * Avoiding split-brain.
> * Starting a VM on another host if the original host becomes
> non-responsive, which improves the availability of HA VMs.



signature.asc
Description: This is a digitally signed message part.
___
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/7AEPIXWSX2ZJ5BRW6S3ATUEOGA3V65J7/


[ovirt-users] Re: about the vm disk type

2021-09-22 Thread Vojtech Juranek
On Wednesday, 22 September 2021 09:55:26 CEST Tommy Sway wrote:
> When I create the VM's image disk, I am not asked to select the following
> type of disk.

Actually you are, it's "Allocation Policy" drop down menu.
Thin provisioned == qcow format
Preallocated == raw

> 
> 
> What is the default value ?

Thin provisioned, i.e. qcow.

> 
> 
> Thanks.
> 
> 
> 
> 
> 
> QCOW2 Formatted Virtual Machine Storage
> 
> QCOW2 is a storage format for virtual disks. QCOW stands for QEMU
> copy-on-write. The QCOW2 format decouples the physical storage layer from
> the virtual layer by adding a mapping between logical and physical blocks.
> Each logical block is mapped to its physical offset, which enables storage
> over-commitment and virtual machine snapshots, where each QCOW volume only
> represents changes made to an underlying virtual disk.
> 
> The initial mapping points all logical blocks to the offsets in the backing
> file or volume. When a virtual machine writes data to a QCOW2 volume after a
> snapshot, the relevant block is read from the backing volume, modified with
> the new information and written into a new snapshot QCOW2 volume. Then the
> map is updated to point to the new place.
> 
> Raw
> 
> The raw storage format has a performance advantage over QCOW2 in that no
> formatting is applied to virtual disks stored in the raw format. Virtual
> machine data operations on virtual disks stored in raw format require no
> additional work from hosts. When a virtual machine writes data to a given
> offset in its virtual disk, the I/O is written to the same offset on the
> backing file or logical volume.
> 
> Raw format requires that the entire space of the defined image be
> preallocated unless using externally managed thin provisioned LUNs from a
> storage array.



signature.asc
Description: This is a digitally signed message part.
___
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/MTSUQ3FSTNQGIB6EZ7U6R7ZIKFLAEVK3/


[ovirt-users] Re: Frequent events seen like VM "vmname" is not responding

2021-09-21 Thread Vojtech Juranek
On Tuesday, 21 September 2021 11:29:06 CEST manoj.sharma99...@gmail.com wrote:
> Thanks Vojtech Juranek for quick response please find logs below
> We got vm non responsive and at the same time vdsm log shows "monitor became
> unresponsive (command timeout, age=61.88649625200196) (vm:5944)" 
 
This means that thread which collects statistics about VM didn't get a 
response in expected time. Does VM response? You can also investigate VM using 
virsh. Or maybe overloaded host which makes all operations very slow and thus 
time out?

> Please refer below logs for more details.
> 
> [root@host vdsm]# cat vdsm.log | grep WARN
> 2021-09-21 14:30:19,487+0530 WARN  (vdsm.Scheduler) [Executor] executor
> state: count=5 workers={  0x7f025051dc18> at 0x7f02502ff5f8> timeout=7.5, duration=7.50 at
> 0x7f023860d6d8> discarded task#=2334 at 0x7f02709edc88>,  name=periodic/493 waiting task#=0 at 0x7f02381016a0>,  name=periodic/489 waiting task#=2701 at 0x7f02386faef0>,  name=periodic/491 waiting task#=1807 at 0x7f0270903908>,  name=periodic/483 waiting task#=2144 at 0x7f0270b12940>} (executor:213)
> 2021-09-21 14:30:34,487+0530 WARN  (vdsm.Scheduler) [Executor] executor
> state: count=5 workers={ 0x7f02381016a0>,  0x7f02386faef0>,  0x7f0270903908>,   0x7f025051dc18> at 0x7f02502ff5f8> timeout=7.5, duration=7.50 at
> 0x7f02384a7780> discarded task#=2146 at 0x7f0270b12940>,  name=periodic/494 waiting task#=0 at 0x7f02386d2f60>} (executor:213)
> 2021-09-21 14:30:49,844+0530 WARN  (vdsm.Scheduler) [Executor] executor
> state: count=5 workers={ 0x7f02381016a0>,  0x7f02386faef0>,   0x7f025051dc18> at 0x7f02502ff5f8> timeout=7.5, duration=7.50 at
> 0x7f02147e0ac8> discarded task#=1897 at 0x7f0270903908>,  name=periodic/495 waiting task#=0 at 0x7f023847d550>,  name=periodic/494 waiting task#=12 at 0x7f02386d2f60>} (executor:213)
> 2021-09-21 14:31:04,491+0530 WARN  (vdsm.Scheduler) [Executor] executor
> state: count=5 workers={ 0x7f0270c70c18>,  0x7f02381016a0>,   0x7f025051dc18> at 0x7f02502ff5f8> timeout=7.5, duration=7.50 at
> 0x7f0238494240> discarded task#=2719 at 0x7f02386faef0>,  name=periodic/495 waiting task#=2 at 0x7f023847d550>,  name=periodic/494 waiting task#=15 at 0x7f02386d2f60>} (executor:213)
> 2021-09-21 14:31:19,491+0530 WARN  (vdsm.Scheduler) [Executor] executor
> state: count=5 workers={ 0x7f0270c70c18>,  0x7f0238756828>,  0x7f02381016a0>,  0x7f023847d550>,   0x7f025051dc18> at 0x7f02502ff5f8> timeout=7.5, duration=7.50 at
> 0x7f02386182e8> discarded task#=17 at 0x7f02386d2f60>} (executor:213)
> 2021-09-21 14:31:34,492+0530 WARN  (vdsm.Scheduler) [Executor] executor
> state: count=5 workers={ 0x7f0270c70c18>,  0x7f0238756828>,  0x7f02384aca58>,   0x7f025051dc18> at 0x7f02502ff5f8> timeout=7.5, duration=7.50 at
> 0x7f02380652e8> discarded task#=22 at 0x7f02381016a0>,  name=periodic/495 waiting task#=8 at 0x7f023847d550>} (executor:213)
> 2021-09-21 14:31:42,418+0530 WARN  (jsonrpc/5) [virt.vm]
> (vmId='b994fb6c-4a7d-469a-82fb-1d776e9f7ae9') monitor became unresponsive
> (command timeout, age=60.07553722700686) (vm:5944) 2021-09-21
> 14:31:49,492+0530 WARN  (vdsm.Scheduler) [Executor] executor state: count=5
> workers={,
> ,  name=periodic/498 waiting task#=12 at 0x7f02384aca58>,  name=periodic/499 waiting task#=0 at 0x7f0270d3d710>,  name=periodic/495 running  action= at
> 0x7f02502ff5f8> timeout=7.5, duration=7.50 at 0x7f02384768d0> discarded
> task#=22 at 0x7f023847d550>} (executor:213) 2021-09-21 14:32:19,492+0530
> WARN  (vdsm.Scheduler) [Executor] executor state: count=5 workers={ name=periodic/496 running  action= at
> 0x7f02502ff5f8> timeout=7.5, duration=7.50 at 0x7f027098a400> discarded
> task#=97 at 0x7f0270c70c18>,  0x7f0238756828>,  0x7f02384aca58>,  0x7f0270ff02b0>,  0x7f0270d3d710>} (executor:213) 2021-09-21 14:33:19,494+0530 WARN 
> (vdsm.Scheduler) [Executor] executor state: count=5 workers={ name=periodic/497 waiting task#=115 at 0x7f0238756828>,  name=periodic/498 waiting task#=40 at 0x7f02384aca58>,  name=periodic/500 waiting task#=22 at 0x7f0270ff02b0>,  name=periodic/499 running  action= at
> 0x7f02502ff5f8> timeout=7.5, duration=7.50 at 0x7f0270d25be0> discarded
> task#=23 at 0x7f0270d3d710>,  0x7f02709ebdd8>} (executor:213) 2021-09-21 14:33:34,494+0530 WARN 
> (vdsm.Scheduler) [Executor] executor state: count=5 workers={ name=periodic/497 waiting task#=117 at 0x7f0238756828>,  name=periodic/498 running  action= at
> 0x7f02502ff5f8> timeout=7.5, duration=7.50 at 0x7f0270c4b198> discarded
> task#=42 at 0x7f02384aca58>,  0x7f0270ff02b0>,  0x7f0270d17978>,  0x7f02709ebdd8>} (executor:213) 2021-09-21 14:33:40,755+0530 WARN 
> (periodic/502

[ovirt-users] Re: Frequent events seen like VM "vmname" is not responding

2021-09-21 Thread Vojtech Juranek
On Tuesday, 21 September 2021 10:25:49 CEST manoj.sharma99...@gmail.com wrote:
> I am using oVirt Open Virtualization Manager Software Version:4.4.6.8-1.el8
> and we have single node running on oVirt Node 4.4.6.
 
> We are facing slowness while using VM and also we face connection reset
> issue between VM and Target servers ( Nexus )
 
> We are getting below logs in ovirt manager events 
> 
> VM "vmname" is not responding
> 
> Getting this for all the running VMs .
> 
> We checked resources  and utilization of the node everything seems very
> normal.  Could you please guide on how can we solve/debug further on this ?

I'd recommend to check the host, if vdsmd service is running (systemct status 
vdsmd) and check vdsm log (/var/log/vdsm/vdsm.log) for any errors and 
eventually share the error here if it's not straightforward how to solve it.

HTH
Vojta

signature.asc
Description: This is a digitally signed message part.
___
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/2HSYXJ6Q5W5DS63BKVAHVZZGVOSBOMO7/


[ovirt-users] Re: Cannot activate a Storage Domain after an oVirt crash

2021-09-16 Thread Vojtech Juranek
On Wednesday, 15 September 2021 14:52:27 CEST nico...@devels.es wrote:
> Hi,
> 
> We're running oVirt 4.3.8 and we recently had a oVirt crash after moving 
> too much disks between storage domains.
> 
> Concretely, one of the Storage Domains reports status "Unknown", 
> "Total/Free/Guaranteed free spaces" are "[N/A]".
> 
> After trying to activate it in the Domain Center we see messages like 
> these from all of the hosts:
> 
>  VDSM hostX command GetVGInfoVDS failed: Volume Group does not exist: 
> (u'vg_uuid: Usi3y8-S4eq-EXtl-FA58-MA3K-b4vE-4d9SCp',)
> 
> I tried putting the Storage Domain in maintenance and it fails with 
> messages like:
> 
>  Storage Domain iaasb13 (Data Center KVMRojo) was deactivated by 
> system because it's not visible by any of the hosts.
>  Failed to update OVF disks 8661acd1-d1c4-44a0-a4d4-ddee834844e9, OVF 
> data isn't updated on those OVF stores (Data Center KVMRojo, Storage 
> Domain iaasb13).
>  Failed to update VMs/Templates OVF data for Storage Domain iaasb13 
> in Data Center KVMRojo.
> 
> I'm sure the storage domain backend is up and running, and the LUN being 
> exported.
> 
> Any hints how can I debug this problem and restore the Storage Domain?

I'd suggest to ssh to any of the host from given data center and investigate 
manually, if the device is visible to the host (e.g. using lsblk) and 
eventually check /var/log/messages to determine where the problem could be.

 
> 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/UNXKR7HRCRDTT
> WLEYO6FFM4WOLD6YATW/



signature.asc
Description: This is a digitally signed message part.
___
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/Y6BBLM6M5Z5S25HGLS7N3GJ7OX7M2L6U/


[ovirt-users] Re: mom-vdsm doesn't restart after upgrade

2021-09-08 Thread Vojtech Juranek
Hi,

> 
> I performed a host upgrade from 4.4.5  to 4.4.8, and vdsmd failed to
> launch with this log:
> 
> Sep 07 16:16:52 kamen systemd[1]: mom-vdsm.service: Job
> mom-vdsm.service/start failed with result 'dependency'.
> Sep 07 16:16:54 kamen systemd[1]: Dependency failed for MOM instance
> configured for VDSM purposes.
> 
> Following this ticket
> https://bugzilla.redhat.com/show_bug.cgi?id=1557735, I managed to launch
> mom-vdsm and so vdsmd doing:
> 
> vdsm-tool configure

thanks for letting us know. Could you please provide more details what was the 
issue and how vdsm-tool configure fix it?

Thanks
Vojta

signature.asc
Description: This is a digitally signed message part.
___
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/QYDEGC2C62GWUSRUWNEI5AJ7RJ3IALUH/


[ovirt-users] Re: ISO Upload in in Paused by System Status

2021-08-05 Thread Vojtech Juranek
On Thursday, 5 August 2021 00:43:15 CEST lou...@ameritech.net wrote:
> I'm attempting to upload an ISO that is approximately 9GB in size.  I've
> succssfullly started th upload process via the oVirt Management
> Console/Disk.  The upload started however, it now has a status of "Paused
> by System".  My storage type is set to NFS Data.  


there is a bug [1] (fix recently), that you have to click "Test connection" 
before upload, otherwise you upload gets stuck.

I'd recommend clicking "Test connection" button anyway to verify connection 
works and your certificates are setup correctly.

> Is something happing the back ground that contributing to the "Paused by
> System"?   I have mor the 84TB of space available so I don't think it is a
> space issue.  Is there something that I need to do?  At this time I'm going
> to wait and see if it moves forward on its own.  
 
> Please provide me with any help or direction.

You can check imageio logs on /var/log/ovirt-imageio/daemon.log both on engine 
and on the host to see if there are any issues and eventually also engine log 
/var/log/ovirt-engine/engine.log


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1950593



> 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/X2CYDZITCYRPW
> JIXHP32H6G3K2QI6OLQ/



signature.asc
Description: This is a digitally signed message part.
___
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/VBJQLGYBWYHSB3M66VN6HDUZ7KSZIFUF/


[ovirt-users] Re: Combining Virtual machine image with multiple disks attached

2021-08-04 Thread Vojtech Juranek
On Wednesday, 4 August 2021 03:54:36 CEST KK CHN wrote:
> On Wed, Aug 4, 2021 at 1:38 AM Nir Soffer  wrote:
> > On Tue, Aug 3, 2021 at 7:29 PM KK CHN  wrote:
> > > I have asked our VM maintainer to run the  command
> > > 
> > > # virsh -r dumpxml vm-name_blah//as Super user
> > > 
> > > But no output :   No matching domains found that was the TTY  output on
> > 
> > that rhevm node when I executed the command.
> > 
> > > Then I tried to execute #  virsh list //  it doesn't list any VMs
> > 
> > !!!   ( How come this ? Does the Rhevm node need to enable any CLI  with
> > License key or something to list Vms or  to dumpxml   with   virsh ? or
> > its
> > CLI commands ?
> > 
> > RHV undefine the vms when they are not running.
> > 
> > > Any way I want to know what I have to ask the   maintainerto provide
> > 
> > a working a working  CLI   or ? which do the tasks expected to do with
> > command line utilities in rhevm.
> > 
> > If the vm is not running you can get the vm configuration from ovirt
> > 
> > using the API:
> > GET /api/vms/{vm-id}
> > 
> > You may need more API calls to get info about the disks, follow the
> > 
> > in the returned xml.
> > 
> > > I have one more question :Which command can I execute on an rhevm
> > 
> > node  to manually export ( not through GUI portal) a   VMs to   required
> > format  ?
> > 
> > > For example;   1.  I need to get  one  VM and disks attached to it  as
> > 
> > raw images.  Is this possible how?
> > 
> > > and another2. VM and disk attached to it as  Ova or( what other good
> > 
> > format) which suitable to upload to glance ?
> > 
> > Arik can add more info on exporting.
> > 
> > >   Each VMs are around 200 to 300 GB with disk volumes ( so where should
> > 
> > be the images exported to which path to specify ? to the host node(if the
> > host doesn't have space  or NFS mount ? how to specify the target location
> > where the VM image get stored in case of NFS mount ( available ?)
> > 
> > You have 2 options:
> > - Download the disks using the SDK
> > - Export the VM to OVA
> > 
> > When exporting to OVA, you will always get qcow2 images, which you can
> > later
> > convert to raw using "qemu-img convert"
> > 
> > When downloading the disks, you control the image format, for example
> > this will download
> > 
> > the disk in any format, collapsing all snapshots to the raw format:
> >  $ python3
> > 
> > /usr/share/doc/python3-ovirt-engine-sdk4/examples/download_disk.py
> > -c engine-dev 3649d84b-6f35-4314-900a-5e8024e3905c /var/tmp/disk1.raw
> > 
> > To perform this which modules/packages need to be installed in the rhevm
> 
> host node ?  Does the rhevm hosts come with python3 installed by default ?
> or I need to install  python3 on rhevm node ? 

You don't have to install anything on oVirt hosts. SDK has to be installed on 
the machine from which you run the script. See 

https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/README.adoc

for more details, how to install and use it.

> Then  using pip3 to install
> the  download_disk.py / what the module name to install this sdk ?  any
> dependency before installing this sdk ? like java need to be installed on
> the rhevm node ?
> 
> One doubt:  came across  virt v2v while google search,  can virtv2v  be
> used in rhevm node to export VMs to images ?  or only from other
> hypervisors   to rhevm only virt v2v supports ?
> 
> This requires ovirt.conf file:   // ovirt.conf file need to be created
> ? or already there  in any rhevm node?

again, this has to be on the machine from which you run the script

> > $ cat ~/.config/ovirt.conf
> > [engine-dev]
> > engine_url = https://engine-dev
> > username = admin@internal
> > password = mypassword
> > cafile = /etc/pki/vdsm/certs/cacert.pem
> > 
> > Nir
> > 
> > > Thanks in advance
> > > 
> > > On Mon, Aug 2, 2021 at 8:22 PM Nir Soffer  wrote:
> > >> On Mon, Aug 2, 2021 at 12:22 PM  wrote:
> > >> > I have  few VMs in   Redhat Virtualisation environment  RHeV ( using
> > 
> > Rhevm4.1 ) managed by a third party
> > 
> > >> > Now I am in the process of migrating  those VMs to  my cloud setup
> > 
> > with  OpenStack ussuri  version  with KVM hypervisor and Glance storage.
> > 
> > >> > The third party is making down each VM and giving the each VM image
> > 
> > with their attached volume disks along with it.
> > 
> > >> > There are three folders  which contain images for each VM .
> > >> > These folders contain the base OS image, and attached LVM disk images
> > 
> > ( from time to time they added hard disks  and used LVM for storing data )
> > where data is stored.
> > 
> > >> > Is there a way to  get all these images to be exported as  Single
> > 
> > image file Instead of  multiple image files from Rhevm it self.  Is this
> > possible ?
> > 
> > >> > If possible how to combine e all these disk images to a single image
> > 
> > and that image  can upload to our  cloud  glance storage as a single image
> > ?> 
> > >> It is not clear what 

[ovirt-users] Re: About the cluster compatibility version

2021-07-30 Thread Vojtech Juranek
On Friday, 30 July 2021 09:51:08 CEST you wrote:
> I still find a lot of errors in the document, but I don't know how to help?
> Can you tell me the steps to improve the documentation?

you need to find appropriate document, fix it and send a pull request. There's 
a 
README [1] with the step in oVirt site git repo [1] or if you want to send a 
pull request, you can find guide how to do it on [2].

Looking more into the original question you asked, it's maybe correct. I don't 
know if we have any strict rules when cluster version is bumped, but it seems 
in the past it was done mainly to ensure OS has specific features provided 
advanced virtualization packages, which are usually available only on specific 
OS version and higher. So in this case the documentation is correct (and I was 
wrong in my previous answer), as OS version determines packages available on 
the host and these determines capabilities of tools (like libvirt, qemu) which 
oVirt is build upon.

Hopefully makes sense.


[1] https://github.com/oVirt/ovirt-site/blob/master/README.md
[2] https://docs.github.com/en/github/collaborating-with-pull-requests/
proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

> I'd like to help in any way I can.
> 
> 
> 
> -Original Message-
> From: Vojtech Juranek 
> Sent: Friday, July 30, 2021 3:01 PM
> To: 'users' 
> Cc: tommy 
> Subject: Re: [ovirt-users] About the cluster compatibility version
> 
> On Friday, 30 July 2021 06:57:04 CEST tommy wrote:
> > From the document:
> > 
> > oVirt clusters have a compatibility version. The cluster compatibility
> > version indicates the features of oVirt supported by all of the hosts
> > in the cluster.
> > 
> > The cluster compatibility is set according to the version of the least
> > capable host operating system in the cluster.
> > 
> > 
> > 
> > I didn't quite understand the last sentence.
> > 
> > How can the version of the cluster be determined based on the
> > operating system version of the host?
> > 
> > Should the cluster compatibility version be determined based on the
> > version of the oVirt engine on the host?
> 
> yes, it's not operating system version, but installed oVirt version on the
> host (but not oVirt engine, there's only one engine and host haven't engine
> installed).
> 
> Could you please improve the doc [1]?
> Thanks
> Vojta
> 
> 
> [1] https://github.com/oVirt/ovirt-site/edit/master/source/documentation/
> upgrade_guide/index.adoc



signature.asc
Description: This is a digitally signed message part.
___
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/3NLRI4TADHYF7AQ4S7TPOP6D7UPV6LPM/


[ovirt-users] Re: About the cluster compatibility version

2021-07-30 Thread Vojtech Juranek
On Friday, 30 July 2021 06:57:04 CEST tommy wrote:
> From the document:
> 
> oVirt clusters have a compatibility version. The cluster compatibility
> version indicates the features of oVirt supported by all of the hosts in the
> cluster.
> 
> The cluster compatibility is set according to the version of the least
> capable host operating system in the cluster.
> 
> 
> 
> I didn't quite understand the last sentence.
> 
> How can the version of the cluster be determined based on the operating
> system version of the host?
> 
> Should the cluster compatibility version be determined based on the version
> of the oVirt engine on the host?

yes, it's not operating system version, but installed oVirt version on the 
host (but not oVirt engine, there's only one engine and host haven't engine 
installed).

Could you please improve the doc [1]?
Thanks
Vojta


[1] https://github.com/oVirt/ovirt-site/edit/master/source/documentation/
upgrade_guide/index.adoc


signature.asc
Description: This is a digitally signed message part.
___
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/JYKFI3ZRLGEOP2R7PNKRUHFCKXH465XO/


[ovirt-users] Re: Password at install for admin@internal not working

2021-07-28 Thread Vojtech Juranek
On Wednesday, 28 July 2021 00:31:49 CEST lou...@ameritech.net wrote:
> I've installed ovirt several times on a fresh machine from scratch.  I've
> had no problems with the install however I'm unable to login via the web
> console using the assigned password entered at the time of the install. 

What login do you use? While when using e.g. REST API you log in as 
admin@inernal, when you log in in web UI, you have to use just admin and 
eventually choose correct profile in Profile combo under password.

> On
> the last 3 tries I've kept the password simple to insure that I was not
> entering the assigned password incorrectly.  I continued tp get with each
> install the message: 
 
> Unable to log in. Verify your login information or contact the system
> administrator.
 
> I've checked the install log for errors and not found any.  While trying to
> keep the password simple I was warned about the simplicity password but
> decided to continue because of previous attempts were not successful.  are
> there any addtitional log that I can view to help with this issue?  Is
> there possibly a bug in the install process that has a work around? 
 
> 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/4RL3EMEO5V6A3
> 2JE6APF6D3RK6GPEFBT/



signature.asc
Description: This is a digitally signed message part.
___
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/5ZZVN6D23MNZXPYNDV5SS4YJS3K7Q2J4/


[ovirt-users] Re: Removing Direct Mapped LUNs

2021-07-16 Thread Vojtech Juranek
On Friday, 16 July 2021 12:31:34 CEST Gianluca Cecchi wrote:
> On Fri, Jul 16, 2021 at 11:15 AM Vojtech Juranek 
> 
> wrote:
> > > What to do to crosscheck what is using the device and so preventing the
> > > "-f" to complete?
> > 
> > can you try
> > 
> > dmsetup info  /dev/mapper/36090a0d800851c9d2195d5b837c9e328
> > 
> > and check "Open count" filed to see if there is still anything open?
> > 
> > Also, you can try
> > 
> > fuser /dev/dm-2
> > 
> > to see which process is using the device
> 
> [root@ov301 ~]# dmsetup info  /dev/mapper/36090a0d800851c9d2195d5b837c9e328
> Name:  36090a0d800851c9d2195d5b837c9e328
> State: ACTIVE
> Read Ahead:256
> Tables present:LIVE
> Open count:1

This means there's some open connection. As lsof or fuser doesn't show 
anything I wonder how this could happen.

Theoretically (not tested as I actually don't know how to reproduce this) and 
on your own risk:-), you can try

dmsetup suspend /dev/mapper/36090a0d800851c9d2195d5b837c9e328
dmsetup clear /dev/mapper/36090a0d800851c9d2195d5b837c9e328
dmsetup wipe_table /dev/mapper/36090a0d800851c9d2195d5b837c9e328

which should remove any stale connection. After that dmsetup info should show 
Open count 0 and multipath -f 36090a0d800851c9d2195d5b837c9e328 should work


> Event number:  0
> Major, minor:  253, 2
> Number of targets: 1
> UUID: mpath-36090a0d800851c9d2195d5b837c9e328
> 
> [root@ov301 ~]# fuser /dev/dm-2
> [root@ov301 ~]# echo $?
> 1
> [root@ov301 ~]# ll /dev/dm-2
> brw-rw. 1 root disk 253, 2 Jul 15 11:28 /dev/dm-2
> 
> I'm still unable to remove it:
> [root@ov301 ~]# multipath -f 36090a0d800851c9d2195d5b837c9e328
> Jul 16 12:25:11 | 36090a0d800851c9d2195d5b837c9e328: map in use
> [root@ov301 ~]#



signature.asc
Description: This is a digitally signed message part.
___
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/6FB6FRML44TOVIHGMVPCCL5BMGCECVNX/


[ovirt-users] Re: Removing Direct Mapped LUNs

2021-07-16 Thread Vojtech Juranek
On Thursday, 15 July 2021 14:49:45 CEST Gianluca Cecchi wrote:
> On Fri, Apr 23, 2021 at 7:15 PM Nir Soffer  wrote:
> > >> > 1) Is this the expected behavior?
> > >> 
> > >> yes, before removing multipath devices, you need to unzone LUN on
> > 
> > storage
> > 
> > >> server. As oVirt doesn't manage storage server in case of iSCSI, it has
> > 
> > to be
> > 
> > >> done by storage sever admin and therefore oVirt cannot manage whole
> > 
> > flow.
> > 
> > > Thank you for the information. Perhaps you can expand then on how the
> > 
> > volumes are picked up once mapped from the Storage system?  Traditionally
> > when mapping storage from an iSCSI or Fibre Channel storage we have to
> > initiate a LIP or iSCSI login. How is it that oVirt doesn't need to do
> > this?> 
> > >> > 2) Are we supposed to go to each KVM host and manually remove the
> > >> > underlying multipath devices?
> > >> 
> > >> oVirt provides ansible script for it:
> > >> 
> > >> https://github.com/oVirt/ovirt-ansible-collection/blob/master/examples/
> > >> remove_mpath_device.yml
> > >> 
> > >> Usage is as follows:
> > >> 
> > >> ansible-playbook --extra-vars "lun=" remove_mpath_device.yml
> 
> I had to decommission one iSCSI based storage domain, after having added
> one new iSCSI one (with another portal) and moved all the objects into the
> new one (vm disks, template disks, iso disks, leases).
> The Environment is based on 4.4.6, with 3 hosts, external engine.
> So I tried the ansible playbook way to verify it.
> 
> Initial situation is this below; the storage domain to decommission is the
> ovsd3750, based on the 5Tb LUN.
> 
> $ sudo multipath -l
> 364817197c52f98316900666e8c2b0b2b dm-13 EQLOGIC,100E-00
> size=2.0T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
> `-+- policy='round-robin 0' prio=0 status=active
> 
>   |- 16:0:0:0 sde 8:64 active undef running
> 
>   `- 17:0:0:0 sdf 8:80 active undef running
> 36090a0d800851c9d2195d5b837c9e328 dm-2 EQLOGIC,100E-00
> size=5.0T features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
> `-+- policy='round-robin 0' prio=0 status=active
> 
>   |- 13:0:0:0 sdb 8:16 active undef running
> 
>   `- 14:0:0:0 sdc 8:32 active undef running
> 
> Connections are using iSCSI multipathing (iscsi1 and iscs2 in web admin
> gui), so that I have two paths to each LUN:
> 
> $sudo  iscsiadm -m node
> 10.10.100.7:3260,1
> iqn.2001-05.com.equallogic:0-8a0906-9d1c8500d-28e3c937b8d59521-ovsd3750
> 10.10.100.7:3260,1
> iqn.2001-05.com.equallogic:0-8a0906-9d1c8500d-28e3c937b8d59521-ovsd3750
> 10.10.100.9:3260,1
> iqn.2001-05.com.equallogic:4-771816-31982fc59-2b0b2b8c6e660069-ovsd3920
> 10.10.100.9:3260,1
> iqn.2001-05.com.equallogic:4-771816-31982fc59-2b0b2b8c6e660069-ovsd3920
> 
> $ sudo iscsiadm -m session
> tcp: [1] 10.10.100.7:3260,1
> iqn.2001-05.com.equallogic:0-8a0906-9d1c8500d-28e3c937b8d59521-ovsd3750
> (non-flash)
> tcp: [2] 10.10.100.7:3260,1
> iqn.2001-05.com.equallogic:0-8a0906-9d1c8500d-28e3c937b8d59521-ovsd3750
> (non-flash)
> tcp: [4] 10.10.100.9:3260,1
> iqn.2001-05.com.equallogic:4-771816-31982fc59-2b0b2b8c6e660069-ovsd3920
> (non-flash)
> tcp: [5] 10.10.100.9:3260,1
> iqn.2001-05.com.equallogic:4-771816-31982fc59-2b0b2b8c6e660069-ovsd3920
> (non-flash)
> 
> One point not taken in consideration inside the previously opened bugs in
> my opinion is the deletion of iSCSI connections and node at host side
> (probably to be done by the os admin, but it could be taken in charge by
> the ansible playbook...)
> The bugs I'm referring are:
> Bug 1310330 - [RFE] Provide a way to remove stale LUNs from hypervisors
> Bug 1928041 - Stale DM links after block SD removal
> 
> Actions done:
> put storage domain into maintenance
> detach storage domain
> remove storage domain
> remove access from equallogic admin gui
> 
> I have a group named ovirt in ansible inventory composed by my 3 hosts:
> ov200, ov300 and ov301
> executed
> $ ansible-playbook -b -l ovirt --extra-vars
> "lun=36090a0d800851c9d2195d5b837c9e328" remove_mpath_device.yml
> 
> it went all ok with ov200 and ov300, but for ov301 I got
> 
> fatal: [ov301: FAILED! => {"changed": true, "cmd": "multipath -f
> \"36090a0d800851c9d2195d5b837c9e328\"", "delta": "0:00:00.009003", "end":
> "2021-07-15 11:17:37.340584", "msg": "non-zero return code", "rc": 1,
> "start": "2021-07-15 11:17:37.331581", "stderr": "Jul 15 11:17:37 |
> 36090a0d800851c9d2195d5b837c9e328: map in use", "stderr_lines": ["Jul 15
> 11:17:37 | 36090a0d800851c9d2195d5b837c9e328: map in use"], "stdout": "",
> "stdout_lines": []}
> 
> the complete output:
> 
> $ ansible-playbook -b -l ovirt --extra-vars
> "lun=36090a0d800851c9d2195d5b837c9e328" remove_mpath_device.yml
> 
> PLAY [Cleanly remove unzoned storage devices (LUNs)]
> *
> 
> TASK [Gathering Facts]
> 
> *** ok: [ov200]
> ok: [ov300]
> ok: [ov301]
> 
> TASK [Get underlying disks 

[ovirt-users] Re: Create new disk failure

2021-07-13 Thread Vojtech Juranek
On Monday, 12 July 2021 16:59:40 CEST Gangi Reddy wrote:
> Thank you. 
> 
> Kindly share the Ovirt Node and VM max limits please. In terms  of
> CPU/Memory/Storage.
 
> How many storage disks we can provision through one storage domain?

see e.g.
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/R3BF7D6ZNVVI4ASJ44MYXEPGR3C4QBKS/


> ___
> 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/EJVYPGMT2MJGD
> LER4OL672LEWMJRUSCW/



signature.asc
Description: This is a digitally signed message part.
___
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/IUMVPPGQZEWB7TTPU5YKQXC26LULUFSC/


[ovirt-users] Re: upgrading to 4.4.6 with Rocky Linux 8

2021-07-02 Thread Vojtech Juranek
> I would prefer to stay away from CentOS Stream for the virtualization 
> platform.   The RHEL product itself would be a perfect solution, but 
> it's rather costly if just using it for a virtualization host OS, and 
> there are surprisingly no education discounts.  

I don't know all the details, but it would worth to check the possibility to 
get RHEL for free for your organization, see

https://www.redhat.com/en/blog/extending-no-cost-red-hat-enterprise-linux-open-source-organizations

There is also some program for universities, but no idea, how much you can 
safe with it or if it worth in your case

https://www.redhat.com/en/resources/rhel-site-subscription-academics-brochure

signature.asc
Description: This is a digitally signed message part.
___
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/R4NDKM66NEU7SU2XBERXHVTDPFVM2S6P/


[ovirt-users] Re: Booting VMs from RHEL ISOs fail

2021-06-09 Thread Vojtech Juranek
On Tuesday, 8 June 2021 21:45:58 CEST David White via Users wrote:
> Correct, I didn't see any errors.
> I seem to recall this happening to me a couple months ago or so when I was
> first setting up the environment as well.
> 
> I'll spend some time (it may not be until this weekend) trying to reproduce
> the error, and collecting some logs.
> 
> No, I do not use an external certificate. 
> (And I did / do use the "Test Connection" button)
> 
> Which logs would be helpful?

* engine log (/var/log/ovirt-engine/engine.log)
* vdsm log from the host (/var/log/vdsm/vdsm.log)
* imageio log from engine as well as from host (/var/log/ovirt-imageio/
daemon.log)

Thanks

signature.asc
Description: This is a digitally signed message part.
___
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/ZMHDJ55ZTKVN6POA7YBAYFK7VAHDU4JX/


[ovirt-users] Re: Is there a way to find the creation date of a Virtual Machines from Ovirt Manager

2021-06-09 Thread Vojtech Juranek
On Wednesday, 9 June 2021 08:19:04 CEST Ritesh Chikatwar wrote:
> Creation date of vm is not shown in the Ui. There is one option: you can
> connect to the database and query for it.


select _create_date from vm_static where vm_name='vm_name';




> On Tue, Jun 8, 2021 at 9:56 PM Strahil Nikolov via Users 
> 
> wrote:
> > I have no clue, but if you have centralized logging (or you keep logs long
> > enough), uou can check vdsm's log on all hosts and identify when the VM
> > was
> > first start.
> > 
> > Best Regards,
> > Strahil Nikolov
> > 
> > On Tue, Jun 8, 2021 at 17:26, k.gunasekhar--- via Users
> >  wrote:
> > Is there a way to find the creation date of a Virtual Machines from Ovirt
> > Manager command line or psql
> > ___
> > 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/OA7KGOSJQQGE
> > CW3LTGW34OE4DFU5JPI7/
> > 
> > ___
> > 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/6R6DG5HVHE2Y
> > C53TQOBIL5FHD73TX25A/



signature.asc
Description: This is a digitally signed message part.
___
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/VT2SHN6DQTAGHVS6E5UHOGCXLPWGUF7F/


[ovirt-users] Re: ovirt engine 4.4.6.8-1.el8 Connection to ovirt-imageio-proxy service has failed. Make sure the service is installed, configured, and ovirt-engine certificate is registered as a valid

2021-06-08 Thread Vojtech Juranek
On Tuesday, 8 June 2021 09:20:33 CEST dhanaraj.ramesh--- via Users wrote:
> Hi 
> Thanks for the reply, above mentioned thread is something else, i'm not able
> to upload any os iso whereas in above state issue centos vm is working fine

please check you have valid certificates by clicking on "Test connection" in 
upload dialogue. If yes, please file a bug for imageio [1] and please attach 
all relevant logs:

* engine log (/var/log/ovirt-engine/engine.log)
* vdsm log from the host (/var/log/vdsm/vdsm.log)
* imageio log from engine as well as from host (/var/log/ovirt-imageio/
daemon.log)

and post a link to bug here.

Thanks
Vojta

[1] https://bugzilla.redhat.com/enter_bug.cgi?product=ovirt-imageio

___
> 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/ZJF6H5G5UH6C3
> AMGCUG4JDK77BVEDGJY/



signature.asc
Description: This is a digitally signed message part.
___
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/IE4D2M3C6H4VK3IRSNG5U4EY4RDRIW2E/


[ovirt-users] Re: Booting VMs from RHEL ISOs fail

2021-06-07 Thread Vojtech Juranek
On Sunday, 6 June 2021 10:40:17 CEST Strahil Nikolov wrote:
> As far as I remember a feature was introduced that allows the end-user to
> verify the disk checksum after an upload. Most probably it's not integrated
> in the WEB UI, but the API should have it. 

correct, here are examples/script how to compute checksum for image and 
uploaded disk:

https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/checksum_image.py
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/checksum_disk.py


> Best Regards,Strahil Nikolov
> 
> 
>   On Sun, Jun 6, 2021 at 9:54, Yedidyah Bar David wrote:  
> ___ 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/AFN6Y44BG7BVK
> W4VFBBVH22NX7MSHRLT/



signature.asc
Description: This is a digitally signed message part.
___
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/IZXIJHLKXSJIOS7BCON5M5USWJLE5T4N/


[ovirt-users] Re: Booting VMs from RHEL ISOs fail

2021-06-07 Thread Vojtech Juranek
On Sunday, 6 June 2021 08:52:36 CEST Yedidyah Bar David wrote:
> On Sat, Jun 5, 2021 at 2:41 PM David White via Users 
> 
> wrote:
> > I finally got this to work.
> > I believe that my issue was that when I thought I had uploaded the ISO,
> > the ISO wasn't actually being uploaded successfully.
> > 
> > I tried to upload various ISOs to different Storage Domains, and
> > eventually noticed that in a couple of cases, I would see a status bar
> > that
> > slowly incremented over time indicating the percentage of the upload
> > complete - whereas before, there would be no status bar, and the oVirt
> > Manager would indicate that the ISO had just been uploaded completely.
> 
> But you got no actual error anywhere? I'd consider this a bug. Would you
> like to report one in bugzilla? Thanks!
> 
> Some points to test/include in your report:
> 
> Do you use an external certificate for https?
> 
> If so, did you follow the documented procedure to do this? Perhaps you can
> tell the exact steps you took?
> 
> I'd still expect some error - so there are perhaps (at least) two separate
> issues here.

yes, definitely a bug. If you managed to reproduce and file a bug for it, 
besides standard logs (engine and vdsm logs), please provide also ovirt-
imageio log (from engine as well as from host), which can be found in /var/
log/ovirt-imageio/daemon.log

Thanks!

> Adding Vojtech.
> 
> > I was able to "replicate" this status bar with the RHEL ISO, and now my VM
> > is booting to that ISO fine.
> 
> Perhaps you can tell what you did differently for this?
> 
> Thanks for the report.
> 
> Best regards,



signature.asc
Description: This is a digitally signed message part.
___
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/I5XN3NJHPNICOGHT3XG5V23DR5UYHXVC/


[ovirt-users] Re: How to handle broken NFS storage?

2021-06-04 Thread Vojtech Juranek
On Friday, 4 June 2021 10:50:47 CEST David White via Users wrote:
> I'm trying to figure out how to keep a "broken" NFS mount point from causing
> the entire HCI cluster to crash.
> 
> HCI is working beautifully.
> Last night, I finished adding some NFS storage to the cluster - this is
> storage that I don't necessarily need to be HA, and I was hoping to store
> some backups and less-important VMs on, since my Gluster (sssd) storage
> availability is pretty limited.
> 
> But as a test, after I got everything setup, I stopped the nfs-server.
> This caused the entire cluster to go down, and several VMs - that are not
> stored on the NFS storage - went belly up.

what was the error? Was NFS domain master storage domain?

> Once I started the NFS server process again, HCI did what it was supposed to
> do, and was able to automatically recover. My concern is that NFS is a
> single point of failure, and if VMs that don't even rely on that storage
> are affected if the NFS storage goes away, then I don't want anything to do
> with it. On the other hand, I'm still struggling to come up with a good way
> to run on-site backups and snapshots without using up more gluster space on
> my (more expensive) sssd storage.
> 
> Is there any way to setup NFS storage for a Backup Domain - as well as a
> Data domain (for lesser important VMs) - such that, if the NFS server
> crashed, all of my non-NFS stuff would be unaffected?
> 
> Sent with ProtonMail Secure Email.



signature.asc
Description: This is a digitally signed message part.
___
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/ME7AHEOOL4WOSNOYKMZ24YIHSD725OQU/


[ovirt-users] Re: issue creating disk with rest api using json format

2021-05-26 Thread Vojtech Juranek
On Wednesday, 26 May 2021 04:27:27 CEST Pascal D wrote:
> I am unable to create disk using JSON however the same query in XML works
> great. In Json I get the following message back: 
 {
>   "detail": "For correct usage, see:
> https://ov1.butterflyit.com/ovirt-engine/apidoc#services/disks/methods/add;
> ,
 "reason": "Request syntactically incorrect."
> }
> 
> Both use POST /ovirt-engine/api/disks and the content-type is either
> application/json or application/xml
 
> Here is the request in JSON:
> 
> {
>"id": "866770c3-acf9-4f67-b72c-05ed241908e4",
>   "name": "mydisk",
>   "description": "test disk",
>   "bootable": false,
>   "shareable": true,
>   "provisioned_size": 1024000,
>   "interface": "virtio",
>   "format": "cow",
>   "storage_domains": {
>   "storage_domain": {
> "name": "VMS"
>   }
>   }
> }

I didn't try, but I guess you need

{
disk = {
"id": "",
...
}
}

> And here it is in XML
> 
> 
>   false
>   mydisk
>   test Drive
>   virtio
>   1024000
>   cow
>   
>   
>   VMS
>   
>   
> 
> ___
> 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/S7PPYRFB5AIRR
> BW5PMNTCMB2PTIF6FT2/



signature.asc
Description: This is a digitally signed message part.
___
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/GM37DPIYWSEXKUGF2GWTHDWCD7QAUJ4Y/


[ovirt-users] Re: Data Centers status Not Operational

2021-05-26 Thread Vojtech Juranek
On Tuesday, 25 May 2021 19:56:29 CEST nexp...@gmail.com wrote:
> Thank you for your time.
> 
> SSH is working in every host and I can connect to everyone.
> 
> I'm not sure Super VDSM daemon server is vdsmd service.

No, it's something little it different. I'm not sure if " VDS daemon server" 
in 3.X is the same as vdsmd. Try to start vdsmd service and check vdsm logs.

> 
> See commands and responses from HV3
> 
> systemctl
> -bash: systemctl: command not found
> 
> service --status-all
> 
> 
> abrt-ccpp hook is not installed
> abrtd (pid  2709) is running...
> abrt-dump-oops is stopped
> acpid (pid  2163) is running...
> atd (pid  2775) is running...
> auditd (pid  1903) is running...
> automount (pid  2404) is running...
> certmonger (pid  2814) is running...
> Running
> cgred is stopped
> cpuspeed is stopped
> crond (pid  2762) is running...
> cupsd (pid  2138) is running...
> dnsmasq is stopped
> # Generated by ebtables-save v1.0 on Tue May 25 18:54:05 CEST 2021
> *nat
> 
> :PREROUTING ACCEPT
> :OUTPUT ACCEPT
> :POSTROUTING ACCEPT
> :libvirt-I-vnet7 ACCEPT
> :I-vnet7-mac ACCEPT
> :I-vnet7-arp-mac ACCEPT
> :libvirt-I-vnet0 ACCEPT
> :I-vnet0-mac ACCEPT
> :I-vnet0-arp-mac ACCEPT
> :libvirt-I-vnet4 ACCEPT
> :I-vnet4-mac ACCEPT
> :I-vnet4-arp-mac ACCEPT
> :libvirt-I-vnet5 ACCEPT
> :I-vnet5-mac ACCEPT
> :I-vnet5-arp-mac ACCEPT
> :libvirt-I-vnet1 ACCEPT
> :I-vnet1-mac ACCEPT
> :I-vnet1-arp-mac ACCEPT
> :libvirt-I-vnet2 ACCEPT
> :I-vnet2-mac ACCEPT
> :I-vnet2-arp-mac ACCEPT
> :libvirt-I-vnet3 ACCEPT
> :I-vnet3-mac ACCEPT
> :I-vnet3-arp-mac ACCEPT
> 
> -A PREROUTING -i vnet7 -j libvirt-I-vnet7
> -A PREROUTING -i vnet0 -j libvirt-I-vnet0
> -A PREROUTING -i vnet4 -j libvirt-I-vnet4
> -A PREROUTING -i vnet5 -j libvirt-I-vnet5
> -A PREROUTING -i vnet1 -j libvirt-I-vnet1
> -A PREROUTING -i vnet2 -j libvirt-I-vnet2
> -A PREROUTING -i vnet3 -j libvirt-I-vnet3
> -A libvirt-I-vnet7 -j I-vnet7-mac
> -A libvirt-I-vnet7 -p ARP -j I-vnet7-arp-mac
> -A I-vnet7-mac -s 0:1a:4a:6b:89:df -j RETURN
> -A I-vnet7-mac -j DROP
> -A I-vnet7-arp-mac -p ARP --arp-mac-src 0:1a:4a:6b:89:df -j RETURN
> -A I-vnet7-arp-mac -j DROP
> -A libvirt-I-vnet0 -j I-vnet0-mac
> -A libvirt-I-vnet0 -p ARP -j I-vnet0-arp-mac
> -A I-vnet0-mac -s 0:1a:4a:6b:89:12 -j RETURN
> -A I-vnet0-mac -j DROP
> -A I-vnet0-arp-mac -p ARP --arp-mac-src 0:1a:4a:6b:89:12 -j RETURN
> -A I-vnet0-arp-mac -j DROP
> -A libvirt-I-vnet4 -j I-vnet4-mac
> -A libvirt-I-vnet4 -p ARP -j I-vnet4-arp-mac
> -A I-vnet4-mac -s 0:1a:4a:6b:89:f5 -j RETURN
> -A I-vnet4-mac -j DROP
> -A I-vnet4-arp-mac -p ARP --arp-mac-src 0:1a:4a:6b:89:f5 -j RETURN
> -A I-vnet4-arp-mac -j DROP
> -A libvirt-I-vnet5 -j I-vnet5-mac
> -A libvirt-I-vnet5 -p ARP -j I-vnet5-arp-mac
> -A I-vnet5-mac -s 0:1a:4a:6b:89:fe -j RETURN
> -A I-vnet5-mac -j DROP
> -A I-vnet5-arp-mac -p ARP --arp-mac-src 0:1a:4a:6b:89:fe -j RETURN
> -A I-vnet5-arp-mac -j DROP
> -A libvirt-I-vnet1 -j I-vnet1-mac
> -A libvirt-I-vnet1 -p ARP -j I-vnet1-arp-mac
> -A I-vnet1-mac -s 0:1a:4a:6b:89:f8 -j RETURN
> -A I-vnet1-mac -j DROP
> -A I-vnet1-arp-mac -p ARP --arp-mac-src 0:1a:4a:6b:89:f8 -j RETURN
> -A I-vnet1-arp-mac -j DROP
> -A libvirt-I-vnet2 -j I-vnet2-mac
> -A libvirt-I-vnet2 -p ARP -j I-vnet2-arp-mac
> -A I-vnet2-mac -s 0:1a:4a:6b:89:11 -j RETURN
> -A I-vnet2-mac -j DROP
> -A I-vnet2-arp-mac -p ARP --arp-mac-src 0:1a:4a:6b:89:11 -j RETURN
> -A I-vnet2-arp-mac -j DROP
> -A libvirt-I-vnet3 -j I-vnet3-mac
> -A libvirt-I-vnet3 -p ARP -j I-vnet3-arp-mac
> -A I-vnet3-mac -s 0:1a:4a:6b:89:15 -j RETURN
> -A I-vnet3-mac -j DROP
> -A I-vnet3-arp-mac -p ARP --arp-mac-src 0:1a:4a:6b:89:15 -j RETURN
> -A I-vnet3-arp-mac -j DROP
> 
> hald (pid  2172) is running...
> htcacheclean is stopped
> httpd (pid  11862) is running...
> Table: filter
> Chain INPUT (policy ACCEPT)
> num  target prot opt source   destination
> 1ACCEPT all  ::/0 ::/0state
> RELATED,ESTABLISHED
 2ACCEPT icmpv6::/0 ::/0
> 3ACCEPT all  ::/0 ::/0
> 4ACCEPT tcp  ::/0 ::/0state NEW
> tcp dpt:22
 5REJECT all  ::/0 ::/0 
>   reject-with icmp6-adm-prohibited 
> Chain FORWARD (policy ACCEPT)
> num  target prot opt source   destination
> 1REJECT all  ::/0 ::/0   
> reject-with icmp6-adm-prohibited
 
> Chain OUTPUT (policy ACCEPT)
> num  target prot opt source   destination
> 
> ipmievd is stopped
> Table: nat
> Chain PREROUTING (policy ACCEPT)
> num  target prot opt source   destination
> 
> Chain POSTROUTING (policy ACCEPT)
> num  target prot opt source   destination
> 
> Chain OUTPUT (policy ACCEPT)
> num  target prot opt source   destination
> 
> Table: filter
> Chain INPUT (policy ACCEPT)
> num  target prot opt source   destination
> 
> Chain FORWARD 

[ovirt-users] Re: Data Centers status Not Operational

2021-05-25 Thread Vojtech Juranek
Hi,

On Tuesday, 25 May 2021 16:00:13 CEST nexp...@gmail.com wrote:
> Hi everyone,
> I found 3 servers (HV1, HV2, HV3) that contains VMs at another servers room.
> These servers are hosts based on KVM.
 I logged into oVirt Engine Web
> Administration. Data Centers tab show me only one entry Name: RCV
> Storage: Shared
> Status: Not Operational
> Compability Version: 3.4 
> Description: [Empty]
> Webbrowser oVirt Engine Web Administrator show me
> oVirt Engine Version: 3.4.0-1.el6
> One VM on HV3 has stopped, Hosts tab show Non Responsive Status for every
> host (HV1-3);

If all the hosts are non-responding, the data center status is also non-
operational. Start with investigation why these hosts are down/non-responsive. 
If there are alive and you can ssh there, check is vdsmd service is running. 
If it's running, check vdsm logs (/var/log/vdsm/vdsm.log) if there are any 
error.

Also 3.4 is very old version, once you make it running, you should really 
consider to upgrade

> every VM in Virtual Machines tab  show Unknown status. 
 What
> do I'll do to change status in Data Center? How to start debug the reason?
> Last administrator leave documentation in vestigial form :) 
> DataCenter: RCV
> -->Cluster: RCV_Cluster
> >Host: HV1 node
> >Host: Hv2 node
> >Host: HV3 engine
> 
> Best regards,
> nexpron
> ___
> 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/CMC2S5HGV7JLA
> QZAE5IVFCYWNIRPRTCP/



signature.asc
Description: This is a digitally signed message part.
___
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/JXAP5UUQ3FU5UUJSBWKZBGVFENZSQ2LJ/


[ovirt-users] Re: Import Ge0-Replicated Storage Domain fails

2021-05-25 Thread Vojtech Juranek
(CC Pavel, who recently worked on DR, maybe he will have some thoughts)

On Monday, 24 May 2021 17:56:56 CEST si...@justconnect.ie wrote:
> Hi All,
> 
> I have 2 independent Hyperconverged Sites/Data Centers.
> 
> Site A has a GlusterFS Replica 3 + Arbiter Volume that is Storage Domain
> data2
 This Volume is Geo-Replicated to a Replica 3 + Arbiter Volume at
> Site B called data2_bdt 
> I have simulated a DR event and now want to import the Ge0-Replicated volume
> data2_bdt as a Storage Domain on Site B. Once imported I need to import the
> VMs on this volume to run in Site B.
 
> The Geo-Replication now works perfectly (thanks Strahil) but I haven't been
> able to import the Storage Domain.
 
> Please can someone point me in the right direction or documentation on how
> this can be achieved.
 
> Kind Regards
> 
> Shimme...
> ___
> 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/LQCTZS6YTKMME
> 2EHBXJEGUM2WDNSYXEC/



signature.asc
Description: This is a digitally signed message part.
___
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/A6J63RH74YKX7OCK5RCR5IQOUDSF7GG7/


[ovirt-users] Re: Import to VMware

2021-05-21 Thread Vojtech Juranek
On Friday, 21 May 2021 13:50:15 CEST Darin Schmidt wrote:
> I believe you are partially right? Originally it was an OVA file. I
> uncompressed the file which gave me another file and the vm.ovf. The OVF
> file appears to be only an xml file? Or are you saying I can also
> uncompressed the ovf file as well like I did the OVA?

yes, OVA is tar archive of OVF directory (see e.g. [1]) and OVF is again tar 
archive of one XML descriptor and VM disks, so you should be able to get the 
VM disk this way

[1] https://fileinfo.com/extension/ova

> 
> On Fri, May 21, 2021, 2:39 AM Vojtech Juranek  wrote:
> > On Thursday, 20 May 2021 22:58:22 CEST Darin Schmidt wrote:
> > > Hello,
> > > 
> > > Ive exported an OVA of a server we had made on OVIRT and Im trying to
> > 
> > import
> > 
> > > it to VMware. Its complaining that the ovf:format is incorrect.
> > > 
> > > ovf:format="http://www.gnome.org/~markmc/qcow-image-format.html;
> > > 
> > > That link doesnt resolve to anywhere because it appears its now
> > > http://people.gnome.org/~markmc/qcow-image-format.html
> > > 
> > > But I dont know whats supposed to go there nor have I been able to
> > > locate
> > > anything to help solve this issue. All I really need is access to the
> > 
> > files
> > 
> > > in the, what I assume is, vdmk file that comes along with the ovf file,
> > > which mine is called: 154b3d77-d340-4d24-a448-66265c5fb613
> > > 
> > > So if anything, is there a way to open this vm disk so I can gain access
> > 
> > to
> > 
> > > the files?
> > 
> > OVF file is just a tar archive with disks and XML descriptor. So untar the
> > OVF
> > file should work.
> > 
> > > 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/3YAA7Z3SLLDX
> > 4
> > 
> > > GBW6EXPGNOII3OGRYJF/



signature.asc
Description: This is a digitally signed message part.
___
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/KLBH57ZTAEV3YJY23Q27J2B63ODXSR7Z/


[ovirt-users] Re: Import to VMware

2021-05-21 Thread Vojtech Juranek
On Thursday, 20 May 2021 22:58:22 CEST Darin Schmidt wrote:
> Hello,
> 
> Ive exported an OVA of a server we had made on OVIRT and Im trying to import
> it to VMware. Its complaining that the ovf:format is incorrect.
 
> ovf:format="http://www.gnome.org/~markmc/qcow-image-format.html;
> 
> That link doesnt resolve to anywhere because it appears its now
> http://people.gnome.org/~markmc/qcow-image-format.html
 
> But I dont know whats supposed to go there nor have I been able to locate
> anything to help solve this issue. All I really need is access to the files
> in the, what I assume is, vdmk file that comes along with the ovf file,
> which mine is called: 154b3d77-d340-4d24-a448-66265c5fb613
 
> So if anything, is there a way to open this vm disk so I can gain access to
> the files?

OVF file is just a tar archive with disks and XML descriptor. So untar the OVF 
file should work.

> 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/3YAA7Z3SLLDX4
> GBW6EXPGNOII3OGRYJF/



signature.asc
Description: This is a digitally signed message part.
___
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/LRDLZGPH2ISGZ6JLOGTO3OH444YSCRLY/


[ovirt-users] Re: error: Engine VM IP address is ... what?

2021-05-20 Thread Vojtech Juranek
On Wednesday, 19 May 2021 20:09:22 CEST lejeczek via Users wrote:
> Hi guys.
> 
> Would anybody be able to decipher this below?
> 
> [ INFO  ] TASK [ovirt.ovirt.hosted_engine_setup : Fail if 
> Engine IP is different from engine's he_fqdn resolved IP]
> [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, 
> "msg": "Engine VM IP address is  while the engine's he_fqdn 
> buster.private.road resolves to 10.3.1.113. If you are using 
> DHCP, check your DHCP reservation configuration"}
> [ ERROR ] Failed to execute stage 'Closing up': Failed 
> executing ansible-playbook

looks like your HE IP address is different from IP address which your HE FQDN 
resolves to. Strange that the IP address of HE is missing in error message. 
Maybe misconfigured netwotk on HE?

> many thanks, L.
> ___
> 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/GWZ7CLHKGRKGD
> QUOPPF6OEYYPFVXNEPP/



signature.asc
Description: This is a digitally signed message part.
___
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/REMXRHJ4ZDAFIRE33JL6KXMFYRJOSDOG/


[ovirt-users] Re: Restoring hosted engine from backup fails on new FC storage domain creation

2021-04-28 Thread Vojtech Juranek
On Wednesday, 28 April 2021 13:02:01 CEST Juhani Rautiainen wrote:
> Hi!
> 
> I know something about multipathing and LVM but I'm not quite familiar
> how this is supposed to look. I compared 4.4 node to 4.3 node and it
> looks totally different from lvm perpective. I'm not sure if this is
> because of changes 

there are no change in disk layout between 4.3 and 4.4 AFAIK 

> or problems in this node. Multipath shows same
> disks but for example pvdisplay on 4.4 node shows only local disk PV:

showing all PVs means you don't have configured lvm filter on the hosts, you 
should run

vdsm-tool config-lvm-filter

on each host, see [1] for more details.

Not showing any PVs on may be caused by installed lvm filter (you can run it 
again with --config 'devices {filter=["a|.*|"]}' to find out) or because there 
are no PVs created yet, which is more likely as in previous log there was an 
error during pvcreate.

[1] https://blogs.ovirt.org/2017/12/lvm-configuration-the-easy-way/

> [root@ovirt02 tmp]# pvdisplay
>   --- Physical volume ---
>   PV Name   /dev/sda3
>   VG Name   onn
> 
> On old node:
> [root@ovirt01 ~]# pvdisplay
>   --- Physical volume ---
>   PV Name   /dev/mapper/36000d31005b4f61a
> --- Physical volume ---
>   PV Name   /dev/mapper/36000d31005b4f61d
>  --- Physical volume ---
>   PV Name   /dev/mapper/360002ac0026157b9
> --- Physical volume ---
>   PV Name   /dev/mapper/3600508b1001cce98eb718bd780426566p3
>   VG Name   onn_ovirt01
> 
> This worries me as I don't have an idea how to fix this.
> 
> Thanks,
> Juhani


signature.asc
Description: This is a digitally signed message part.
___
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/EFVILP2ZIGGQ43SDUEIBOYXWIVHBHWCV/


[ovirt-users] Re: Restoring hosted engine from backup fails on new FC storage domain creation

2021-04-28 Thread Vojtech Juranek
On Wednesday, 28 April 2021 08:57:32 CEST Yedidyah Bar David wrote:
> On Wed, Apr 28, 2021 at 9:29 AM Juhani Rautiainen
>  wrote:
> 
> >
> >
> > Hi!
> >
> >
> >
> > This is from ansible logs:
> > 2021-04-27 22:20:38,286+0300 ERROR ansible failed {
> > 
> > "ansible_host": "localhost",
> > "ansible_playbook":
> > 
> > "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
> > 
> > "ansible_result": {
> > 
> > "_ansible_no_log": false,
> > "changed": false,
> > "exception": "Traceback (most recent call last):\n  File
> > 
> > \"/tmp/ansible_ovirt_storage_domain_payload_hlz7j9sk/ansible_ovirt_storage
> > _domain_payload.zip/ansible_collections/ovirt/ovirt/plugins/modules/ovirt_
> > storage_domain.py\",
 line 804, in main\n  File
> > \"/tmp/ansible_ovirt_storage_domain_payload_hlz7j9sk/ansible_ovirt_storage
> > _domain_payload.zip/ansible_collections/ovirt/ovirt/plugins/module_utils/o
> > virt.py\",
 line 651, in create\n**kwargs\n  File
> > \"/usr/lib64/python3.6/site-packages/ovirtsdk4/services.py\", line
> > 26182, in add\nreturn self._internal_add(storage_domain, headers,
> > query, wait)\n  File
> > \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 232,
> > in _internal_add\nreturn future.wait() if wait else future\n  File
> > \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 55,
> > in wait\nreturn self._code(response)\n  File
> > \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 229,
> > in callback\nself._check_fault(response)\n  File
> > \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 132,
> > in _check_fault\nself._raise_error(response, body)\n  File
> > \"/usr/lib64/python3.6/site-packages/ovirtsdk4/service.py\", line 118,
> > in _raise_error\nraise error\novirtsdk4.Error: Fault reason is
> > \"Operation Failed\". Fault detail is \"[Physical device
> > initialization failed. Please check that the device is empty and
> > accessible by the host.]\". HTTP response code is 400.\n",
> > 
> > "invocation": {
> > 
> > "module_args": {
> > 
> > "backup": null,
> > "comment": null,
> > "critical_space_action_blocker": null,
> > "data_center": "Default",
> > "description": null,
> > "destroy": null,
> > "discard_after_delete": true,
> > "domain_function": "data",
> > "fcp": {
> > 
> > "lun_id": "36000d31005b4f629"
> > 
> > },
> > "fetch_nested": false,
> > "format": null,
> > "glusterfs": null,
> > "host": "ovirt02.virt.local",
> > "id": null,
> > "iscsi": null,
> > "localfs": null,
> > "managed_block_storage": null,
> > "name": "hosted_storage",
> > "nested_attributes": [],
> > "nfs": null,
> > "poll_interval": 3,
> > "posixfs": null,
> > "state": "unattached",
> > "timeout": 180,
> > "wait": true,
> > "warning_low_space": null,
> > "wipe_after_delete": null
> > 
> > }
> > 
> > },
> > "msg": "Fault reason is \"Operation Failed\". Fault detail is
> > 
> > \"[Physical device initialization failed. Please check that the device
> > is empty and accessible by the host.]\". HTTP response code is 400."
> > 
> > },
> > "ansible_task": "Add Fibre Channel storage domain",
> > "ansible_type": "task",
> > "status": "FAILED",
> >
> >
> >
> > This seem to happen same time:
> >
> >
> >
> > 2021-04-27 22:20:37,576+0300 INFO  (jsonrpc/5) [vdsm.api] FINISH
> > getDeviceList return={'devList': [{'GUID':
> > '36000d31005b4f629', 'capacity': '536870912000',
> > 'devtype': 'FCP', 'fwrev': '0704', 'logicalblocksize': '512',
> > 'pathlist': [], 'pathstatus': [{'physdev': 'sdu', 'state': 'active',
> > 'capacity': '536870912000', 'lun': '3', 'type': 'FCP'}, {'physdev':
> > 'sds', 'state': 'active', 'capacity': '536870912000', 'lun': '3',
> > 'type': 'FCP'}, {'physdev': 'sdv', 'state': 'active', 'capacity':
> > '536870912000', 'lun': '3', 'type': 'FCP'}, {'physdev': 'sdt',
> > 'state': 'active', 'capacity': '536870912000', 'lun': '3', 'type':
> > 'FCP'}], 'physicalblocksize': '4096', 'productID': 'Compellent Vol',
> > 'pvUUID': '', 'pvsize': '', 'serial':
> > 'SCOMPELNTCompellent_Vol_0005b4f6-0029', 'vendorID': 'COMPELNT',
> > 'vgUUID': '', 'discard_max_bytes': 268435456, 'discard_zeroes_data':
> > 0, 'status': 'unknown'}]} from=:::192.168.222.89,57472,
> > flow_id=676e5ced-7a4f-4a36-8842-cb98a38f5f4b,
> > task_id=792a93ab-5129-4bf2-8ff0-70b5cdf19221 (api:54)
> 

[ovirt-users] Re: Attempting to detach a storage domain

2021-04-27 Thread Vojtech Juranek
On Tuesday, 27 April 2021 02:18:18 CEST matthew.st...@fujitsu.com wrote:
> There is no /var/log/vdsm directory on the hosted-engine.
> 
> This is from the current host, hosting the engine:  aaa.bbb.ccc.100 is the
> hosted-engine
 
> 2021-04-26 19:12:42,760-0500 INFO  (jsonrpc/2) [api.host] START
> getCapabilities() from=:::aaa.bbb.ccc.100,37812 (api:48)
 2021-04-26
> 19:12:42,763-0500 INFO  (jsonrpc/2) [api.host] FINISH getCapabilities
> error=internal error: Duplicate key from=:::168.127.151.100,37812
> (api:52) 2021-04-26 19:12:42,763-0500 ERROR (jsonrpc/2)
> [jsonrpc.JsonRpcServer] Internal server error (__init__:350) Traceback
> (most recent call last):
>   File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 345,
> in _handle_request
 res = method(**params)
>   File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 198, in
> _dynamicMethod
 result = fn(*methodArgs)
>   File "", line 2, in getCapabilities
>   File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in
> method
 ret = func(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1371, in
> getCapabilities
 c = caps.get()
>   File "/usr/lib/python2.7/site-packages/vdsm/host/caps.py", line 95, in
> get
 machinetype.compatible_cpu_models())
>   File "/usr/lib/python2.7/site-packages/vdsm/common/cache.py", line 43, in
> __call__
 value = self.func(*args)
>   File "/usr/lib/python2.7/site-packages/vdsm/machinetype.py", line 142, in
> compatible_cpu_models
 all_models = domain_cpu_models(c, arch, cpu_mode)
>   File "/usr/lib/python2.7/site-packages/vdsm/machinetype.py", line 97, in
> domain_cpu_models
 domcaps = conn.getDomainCapabilities(None, arch, None,
> virt_type, 0) File
> "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line
> 131, in wrapper ret = f(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 94,
> in wrapper
 return func(inst, *args, **kwargs)
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3844, in
> getDomainCapabilities
 if ret is None: raise libvirtError
> ('virConnectGetDomainCapabilities() failed', conn=self) libvirtError:
> internal error: Duplicate key

looks like https://bugzilla.redhat.com/show_bug.cgi?id=1791790
The fix should be contained in recent oVirt relases.

> 2021-04-26 19:12:42,764-0500 INFO  (jsonrpc/2) [jsonrpc.JsonRpcServer] RPC
> call Host.getCapabilities failed (error -32603) in 0.00 seconds
> (__init__:312)
 
> 
> -Original Message-
> From: Nir Soffer  
> Sent: Monday, April 26, 2021 5:12 PM
> To: Stier, Matthew 
> Cc: Benny Zlotnik ; users@ovirt.org
> Subject: Re: [ovirt-users] Re: Attempting to detach a storage domain
> 
> On Tue, Apr 27, 2021 at 12:48 AM matthew.st...@fujitsu.com
>  wrote:
> >
> >
> > I'm getting tons of these in the 
> > hosted-engine:/var/log/ovirt-engine/engine.log
> >
> >
> >
> > 2021-04-26 16:40:40,260-05 ERROR 
> > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> > (EE-ManagedThreadFactory-engineScheduled-Thread-8) [] EVENT_ID: 
> > VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ..zzz command Get 
> > Host Capabilities failed: Internal JSON-RPC error: {'reason': 
> > 'internal error: Duplicate key'}
> 
> 
> This looks like bad response from vdsm. Can you share the vdsm log from the
> host ..zzz?
 
> /var/log/vdsm/vdsm.log
> 
> 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/Z2GOGEZ2DZX34
> ADZ5L2BATIINYGVWYJD/



signature.asc
Description: This is a digitally signed message part.
___
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/BO4LDETTPXHB2ZSH4MNN6RSYSQEYTFEN/


[ovirt-users] Re: Removing Direct Mapped LUNs

2021-04-23 Thread Vojtech Juranek
On Friday, 23 April 2021 02:44:43 CEST Ryan Chewning wrote:
> Hi List,
> 
> We need to add and remove directly mapped LUNs to multiple VMs in our
> Non-Production environment. The environment is backed by an iSCSI SAN. In
> testing when removing a directly mapped LUN it doesn't remove the
> underlying multipath and devices. Several questions.
> 
> 1) Is this the expected behavior?

yes, before removing multipath devices, you need to unzone LUN on storage 
server. As oVirt doesn't manage storage server in case of iSCSI, it has to be 
done by storage sever admin and therefore oVirt cannot manage whole flow.

> 2) Are we supposed to go to each KVM host and manually remove the
> underlying multipath devices?

oVirt provides ansible script for it:

https://github.com/oVirt/ovirt-ansible-collection/blob/master/examples/
remove_mpath_device.yml

Usage is as follows:

ansible-playbook --extra-vars "lun=" remove_mpath_device.yml

> 3) Is there a technical reason that oVirt doesn't do this as part of the
> steps to removing the storage?

as mentioned above, oVirt doesn't manage iSCSI server and cannot unzone LUN 
from the server. For managed storage oVirt does that.

> This is something that was handled by the manager in the previous
> virtualization that we used, Oracle's  Xen based Oracle VM.
> 
> Thanks!
> 
> Ryan



signature.asc
Description: This is a digitally signed message part.
___
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/FR4PIIUO325VT5KE2FUTWNHKFGLYZACC/


[ovirt-users] Re: How to Upgrade Node with Local Storage ?

2021-04-21 Thread Vojtech Juranek
On Wednesday, 21 April 2021 16:40:29 CEST Nur Imam Febrianto wrote:
> Set global maintenance and then turn off all vm, do yum update but it
> completed with failed. Am I missing something ?

can you share the details? What failed, wthat was the error?


> From: Adam Xu
> Sent: 20 April 2021 7:36
> To: users@ovirt.org
> Subject: [ovirt-users] Re: How to Upgrade Node with Local Storage ?
> 
> 
> For  oVirt Node that using Local Storage, I think you should shutdown all
> your vms before you upgrade the Node. 在 2021/4/19 22:09, Nur Imam Febrianto
> 写道:
> Hi,
> 
> How we can upgrade oVirt Node that using Local Storage ? Seems I cant find
> any good documentation about this. Planning to upgrade one 4.4.4 node with
> local storage to 4.4.5.
> Thanks before.
> 
> Regards,
> Nur Imam Febrianto
> 
> 
> 
> ___
> 
> 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 on.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fprivacy-policy.html=0
> 4%7C01%7C%7C2817620cd2134104f81908d90394654e%7C84df9e7fe9f640afb435a
> aaa%7C1%7C0%7C637544758156873163%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA
> iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=VV663qDHl6C24C0
> XTZLoUF4n%2Bm4umP4dkG1EsKS895E%3D=0>
> 
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/ safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunit
> y%2Fabout%2Fcommunity-guidelines%2F=04%7C01%7C%7C2817620cd2134104f81908
> d90394654e%7C84df9e7fe9f640afb435%7C1%7C0%7C637544758156883118%7
> CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL
> CJXVCI6Mn0%3D%7C1000=XF1vC3JCyVjQCsD1x%2FDQinfKOImw5VJbZIryDg9sKKg%3D&
> reserved=0>
> 
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZOCHCAJPXO4LT
> IMA4JHK3WMR5CTKR37C/ tps%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%
> 2FZOCHCAJPXO4LTIMA4JHK3WMR5CTKR37C%2F=04%7C01%7C%7C2817620cd2134104f819
> 08d90394654e%7C84df9e7fe9f640afb435%7C1%7C0%7C637544758156883118
> %7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWw
> iLCJXVCI6Mn0%3D%7C1000=raH9RGOWlZIWlj%2FCWFJUbqI94y0U2TR9lUukXhzi2B8%3
> D=0>



signature.asc
Description: This is a digitally signed message part.
___
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/JVTFTHF3LSGAFHBKN4X6W63HSEK3BFFX/


[ovirt-users] Re: glance repo in 4.3

2021-04-16 Thread Vojtech Juranek
On Friday, 16 April 2021 09:58:42 CEST Christoph Köhler wrote:
> I use ovirt 4.3.10 and need to get access to a glance repo for vm
> images/templates. The buld-in external provider 'Public Glance
> repository for oVirt' (glance.ovirt.org) does not work, it seems not to
> be maintained.

It is maintained, but IIRC glance.ovirt.org updated to v2 API during upgrade 
(v1 API was deprecated for very long time and IIRC was removed from recent 
Glance releases) and therefor older oVirt installations which uses only v1 API 
stopped working. 
 
> Does someone knows what to do?

upgrade to more recent oVirt, 4.3 is not supported for quite a long time

Vojta


signature.asc
Description: This is a digitally signed message part.
___
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/H6Z3R3MJODDQ7JUHFPTFXQXR3YTFIKS2/


[ovirt-users] Re: How do I share a disk across multiple VMs?

2021-04-16 Thread Vojtech Juranek
Hi,
another approach you may consider is to use HA functionality provided by oVirt 
which re-create VM on another host if original host become unavailable and 
attach the disk from underlying Gluster (which is already HA) to newly created 
VM, so you don't have to care about creating HA storage on your VMs. You also 
save some resources as you don't have to have backup VMs running.

The drawback of this approach that re-creating new VM takes more time than 
switching the traffic to already running VM on load balancer. This depends on 
your constraints but IMHO worth to consider.

Vojta

On Friday, 16 April 2021 03:00:23 CEST David White via Users wrote:
> I'm currently thinking about just setting up a rsync cron to run every
> minute.
> 
> 
> Sent with ProtonMail Secure Email.
> 
> ‐‐‐ Original Message ‐‐‐
> 
> On Thursday, April 15, 2021 8:55 PM, David White via Users  
wrote:
> > > David, I’m curious what the use case is
> > 
> > This is for a customer who wants as much high availability as possible for
> > their website, which relies on a basic LAMP or LNMP stack.
> > 
> > 
> > The plan is to create a MariaDB Galera cluster.
> > 
> > 
> > Each of the 3 VMs will run MariaDB, as well as Apache or Nginx (I haven't
> > decided which, yet), and will be able to accept web traffic.
> > 
> > 
> > So the website files will need to be the same across all 3 virtual
> > servers.
> > 
> > 
> > My original intent was to setup a mount point on all 3 virtual servers
> > that mapped back to the same shared disk.
> > 
> > 
> > Strahil, 1 idea I had, which I don't think would be ideal at all, was to
> > setup a separate, new, gluster configuration on each of the 3 VMs.
> > Gluster virtualized on top of gluster! If that doesn't make your head
> > spin, what will? But I'm not seriously thinking about that. :)
> > 
> > 
> > It did occur to me that I could setup a 4th VM to host the NFS share.
> > 
> > 
> > But I'm trying to stay away from as many single points of failures as
> > possible.
> > 
> > 
> > Sent with ProtonMail Secure Email.
> > 
> > 
> > ‐‐‐ Original Message ‐‐‐
> > 
> > On Thursday, April 15, 2021 7:40 PM, Strahil Nikolov via Users 
users@ovirt.org wrote:
> > > I know that clusterizing applications (for example corosync/pacemaker
> > > Active-Passive or even GFS2) require simultaneous access to the data.
> > > 
> > > 
> > > In your case you can create:
> > > 
> > > 
> > > -   2 separate VMs replicating over DRBD and sharing the storage over
> > > NFS/iSCSI -   Using NFS Ganesha (this is just a theory but should work)
> > > to export your Gluster volumes in a redundant and highly available way> 
> 
> > > Best Regards,
> > > Strahil Nikolov
> > > 
> > > В петък, 16 април 2021 г., 01:56:09 ч. Гринуич+3, Jayme 
jay...@gmail.com написа:
> > > David, I’m curious what the use case is. :9 you plan on using the disk
> > > with three vms at the same time?  This isn’t really what shareable
> > > disks are meant to do afaik. If you want to share storage with multiple
> > > vms I’d probably just setup an nfs share on one of the vms> > 
> > > On Thu, Apr 15, 2021 at 7:37 PM David White via Users users@ovirt.org 
wrote:
> > > > I found the proper documentation
> > > > at https://www.ovirt.org/documentation/administration_guide/#Shareabl
> > > > e_Disks. When I tried to edit the disk, I see that sharable is grayed
> > > > out, and when I hover my mouse over it, I see "Sharable Storage is
> > > > not supported on Gluster/Offload Domain". So to confirm, is there any
> > > > circumstance where a Gluster volume can support sharable storage?
> > > > Unfortunately, I don't have any other storage available, and I chose
> > > > to use Gluster, so that I could have a HA environment. Sent with
> > > > ProtonMail Secure Email.
> > > > ‐‐‐ Original Message ‐‐‐
> > > > 
> > > >   On Thursday, April 15, 2021 5:05 PM, David White via Users 
users@ovirt.org wrote:
> > > > > I need to mount a partition across 3 different VMs.
> > > > > How do I attach a disk to multiple VMs?
> > > > > This looks like fairly old
> > > > > documentation-not-documentation: https://www.ovirt.org/develop/rele
> > > > > ase-management/features/storage/sharedrawdisk.html Sent with
> > > > > ProtonMail Secure Email.
> > > > 
> > > > 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/WZY6OJW
> > > > BH5KAB5H2XXYJOVI7BLR4Z67F/> > 
> > > Users mailing list -- users@ovirt.org
> > > To unsubscribe send an email to users-le...@ovirt.org
> > > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > > oVirt Code of Conduct:
> > > https://www.ovirt.org/community/about/community-guidelines/ List
> > > Archives:
> > > 

[ovirt-users] Re: Import VMs from disk

2021-03-31 Thread Vojtech Juranek
> First I had to run remotely a browser on the server, the only way to upload
> files on the storage attached to it.
 
Probably too late, but FIY, there's also an option to do it from command line 
using ovirt-sdk [1]. You can use upload_disk example [2]. This is also very 
use useful when you need to upload many images.

[1] https://github.com/oVirt/ovirt-engine-sdk/
[2] https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/
upload_disk.py

signature.asc
Description: This is a digitally signed message part.
___
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/REBTNHDTP5UQCBE3WRJG5T7D2W6U5KAQ/


[ovirt-users] Re: Deployment issues

2021-03-29 Thread Vojtech Juranek
On Monday, 29 March 2021 16:20:38 CEST valerio.luc...@nyu.edu wrote:
> OK, I downgraded glusterfs to 7.9 (got the RPMs from the CentOS mirror and
> did a "dnf --allowerasing downgrade ") and I was able to deploy a new
> engine.
 
> Now on to solve all my other problems ;-(

do you still fail to create SD metadata? If so, why it fails when you try 
manually from cmd line?

> ___
> 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/7TBEXM4XYNFCF
> ITYXL3CCLPDSQ77HHQK/



signature.asc
Description: This is a digitally signed message part.
___
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/3XNA2IOKK2RMNTZ5ZKFPJKOYZX2ADPOY/


[ovirt-users] Re: Deployment issues

2021-03-29 Thread Vojtech Juranek
On Sunday, 28 March 2021 06:49:18 CEST valerio.luc...@nyu.edu wrote:
> So it does turn out that I have some issue with gluster. I was fooled by
> seeing that the wizard does create the top-level directory and the ids
> file, but if I try to create a file from command line I get an error. I
> don't have an issue from other servers, so it's not a problem with the
> gluster storage.
 
> Nice catch Strahil, you pointed me in the right direction. 
> 
> In the latest update, which I did Friday (not part of my initial ovirt
> update), it upgraded gluster from 7 to 8. What happens if I roll these
> back. Is gluster 8 really necessary at this point ? 

I don't think this is required by oVirt, e.g. in vdsm spec file I can see we 
require version 6.0 [1]. Maybe was upgraded during general OS upgrade?

[1] https://github.com/oVirt/vdsm/blob/master/vdsm.spec.in#L25

> I have some legacy
> systems that use that gluster storage and I'm afraid of breaking them.
> ___
> 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/2QA5DN47ZIHSC
> PCBTQTQ3Z6WG5NKSJF3/



signature.asc
Description: This is a digitally signed message part.
___
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/EW4X4VCOCCVJOP54HWTOCZ7VXLUNBMCP/


[ovirt-users] Re: Ovirt Node (iso) - OK to enable Centos-BaseOS/Centos-Appstream repos ?

2021-03-25 Thread Vojtech Juranek
On Wednesday, 24 March 2021 15:20:21 CET jb wrote:
> Am 23.03.21 um 12:45 schrieb Vojtech Juranek:
> 
> > On Tuesday, 23 March 2021 11:56:26 CET morgan cox wrote:
> > 
> >> Hi.
> >>
> >>
> >>
> >> I have installed Ovirt nodes via the ovirt-node iso (centos8 based) - on
> >> a
> >> fresh install the standard CentOS repos are disabled (the ovirt 4-4 
> >> repo
> >> is enabled)
> >> 
> >   
> >> 
> >> As part of our company hardening we need to install a few packages from
> >> the
 Centos repos.
> >> 
> >   
> >> 
> >> Can I enable the CentOS-Linux-AppStream.repo + CentOS-Linux-BaseOS.repo
> >> repos or will this cause issues when we update the node ?
> > 
> > AFAIK it shouldn't break anything. ovirt repos have newer versions, so
> > anything required by ovirt should be installed from ovirt repo during
> > upgrade.
> I made the experience that after installing a upgrade, everything which 
> I installed from that repos disappear.

yes, AFAIK this happens when you install host as ovirt node. If you install 
from rpm (enterprise host), this shouldn't happen

> ___
> 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/CTW2PKGCC62IV
> IZTTQG3BQPQUFERZBB2/



signature.asc
Description: This is a digitally signed message part.
___
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/WFVINXBMVGPPYDEEGIIEXK5NK7BNTUE3/


[ovirt-users] Re: Ovirt Node (iso) - OK to enable Centos-BaseOS/Centos-Appstream repos ?

2021-03-23 Thread Vojtech Juranek
On Tuesday, 23 March 2021 11:56:26 CET morgan cox wrote:
> Hi.
> 
> I have installed Ovirt nodes via the ovirt-node iso (centos8 based) - on a
> fresh install the standard CentOS repos are disabled (the ovirt 4-4  repo
> is enabled)
 
> As part of our company hardening we need to install a few packages from the
> Centos repos.
 
> Can I enable the CentOS-Linux-AppStream.repo + CentOS-Linux-BaseOS.repo
> repos or will this cause issues when we update the node ?

AFAIK it shouldn't break anything. ovirt repos have newer versions, so 
anything required by ovirt should be installed from ovirt repo during upgrade.


> 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/JITF2KTDAE7V2
> FMEYRJZOMUDCNKBGL56/



signature.asc
Description: This is a digitally signed message part.
___
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/3FWG6DQOQ5ZSO2SMGUNX2BYUY4NUVARH/


[ovirt-users] Re: One host 4.4.5 upgade failed

2021-03-23 Thread Vojtech Juranek
Is vdsmd running on the host?
If not, what is in the vdsm log?
If yes, what is in engine log (/var/log/ovirt-engine/engine.log) - why it 
failed to activate it?


On Tuesday, 23 March 2021 09:54:40 CET ozme...@hotmail.com wrote:
> journalctl returns
> WARN Failed to retrieve Hosted Engine HA info, is Hosted Engine setup
> finished?
 
> also, #  cat /var/log/vdsm/vdsm.log | grep ERROR
> 
> ERROR (jsonrpc/6) [storage.TaskManager.Task]
> (Task='039a0aea-a855-4e3e-b3ff-0f26c0c3900a') Unexpected error (task:880)
> ERROR (jsonrpc/6) [storage.Dispatcher] FINISH getStorageDomainStats
> error=Storage domain does not exist:
> ___
> 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/L3QSU4V3FVH6C
> IKTBG5H26ZMOAILACHO/



signature.asc
Description: This is a digitally signed message part.
___
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/ZE3RKBV3FLZ5TLTQTZDODM3BXZMI52I2/


[ovirt-users] Re: One host 4.4.5 upgade failed

2021-03-23 Thread Vojtech Juranek
On Tuesday, 23 March 2021 07:47:23 CET ozme...@hotmail.com wrote:
> Stop failed\nb'Job for vdsmd.service canceled.\\n' ", "stderr_lines":
> ["Error:  ServiceOperationError: _systemctlStop failed", "b'Job for
> vdsmd.service canceled.\\n' "], "stdout": "\nChecking configuration
> status...\n\nlibvirt is already configured for vdsm\nSUCCESS: ssl config

it looks like systemd failed to restart vdsmd service. Configuration itself 
looks good. Could you try manually restart vdsmd service:

systemctl restart vdsmd

If it fails, please provide output of 

journalctl -u vdsmd


signature.asc
Description: This is a digitally signed message part.
___
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/BL7MQDJQOBPXCZZQOEO4RP6KGZZOLHK5/


[ovirt-users] Re: sanlock error

2021-03-08 Thread Vojtech Juranek
On Monday, 8 March 2021 12:46:58 CET kim.karga...@noroff.no wrote:
> Hi,
> 
> We have plenty of space, I have checked with both df -h and df -i. 
> 
> Here are the vdsm logs from one node. 

what is the whole flow you are running? This looks like a flow where you try 
to delete an image, which is probably missing one of its volumes.
In the log bellow there isn't anything related to sanlock. Or maybe wrong log?

> 2021-03-08 12:09:15,550+0100 INFO  (jsonrpc/7) [vdsm.api] START
> deleteImage(sdUUID=u'fb14e013-15f1-49b6-b129-210517aca0da',
> spUUID=u'aec485fa-cdbb-4979-8dc9-a2376559b2a4',
> imgUUID=u'459872a1-8783-463a-98ae-9e56d8883abb', postZero=u'false',
> force=u'false', discard=False) from=:::172.16.122.253,44650,
> flow_id=39b2eddb, task_id=969cdd60-9b4c-43d9-960a-2a3b467b227c (api:48)
> 2021-03-08 12:09:15,719+0100 INFO  (tasks/9)
> [storage.StorageDomainManifest] Unlink volume symlink
> u'/rhev/data-center/mnt/blockSD/fb14e013-15f1-49b6-b129-210517aca0da/images
> /01af322e-ff54-4981-9842-0f0a608da17c/46bf0806-8d16-40db-92df-8436f43628a4'
> (blockSD:722) 2021-03-08 12:09:15,719+0100 INFO  (tasks/9)
> [storage.StorageDomainManifest] Unlink volume symlink
> u'/rhev/data-center/mnt/blockSD/fb14e013-15f1-49b6-b129-210517aca0da/images
> /01af322e-ff54-4981-9842-0f0a608da17c/27638d78-e935-44f4-b0cc-5ee2459e204a'
> (blockSD:722) 2021-03-08 12:09:15,719+0100 INFO  (tasks/9)
> [storage.StorageDomainManifest] removed:
> [u'/rhev/data-center/mnt/blockSD/fb14e013-15f1-49b6-b129-210517aca0da/image
> s/01af322e-ff54-4981-9842-0f0a608da17c/27638d78-e935-44f4-b0cc-5ee2459e204a'
> ] (blockSD:729) 2021-03-08 12:09:15,719+0100 INFO  (tasks/9)
> [storage.StorageDomainManifest] Removing image directory
> u'/rhev/data-center/mnt/blockSD/fb14e013-15f1-49b6-b129-210517aca0da/images
> /01af322e-ff54-4981-9842-0f0a608da17c' (blockSD:735) 2021-03-08
> 12:09:15,729+0100 INFO  (tasks/9) [storage.ThreadPool.WorkerThread] FINISH
> task 9a57dcf5-85b2-4c7c-8ffb-f11eecc2313f (threadPool:210) 2021-03-08
> 12:09:16,671+0100 WARN  (jsonrpc/7) [storage.LVM] Removing stale lv:
> fb14e013-15f1-49b6-b129-210517aca0da/46bf0806-8d16-40db-92df-8436f43628a4
> (lvm:564) 2021-03-08 12:09:17,920+0100 WARN  (tasks/7) [storage.LVM] lv:
> 46bf0806-8d16-40db-92df-8436f43628a4 not found in lvs vg:
> fb14e013-15f1-49b6-b129-210517aca0da response (lvm:736) 2021-03-08
> 12:09:17,921+0100 ERROR (tasks/7) [storage.TaskManager.Task]
> (Task='d4aa81a1-9adc-45c9-be46-05bc63862f4e') Unexpected error (task:875)
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in
> _run
 return fn(*args, **kargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 336, in
> run
 return self.cmd(*self.argslist, **self.argsdict)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line
> 79, in wrapper
 return method(self, *args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 1966, in
> deleteVolume
 vol = dom.produceVolume(imgUUID, volUUID)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 913, in
> produceVolume
 volUUID)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 814,
> in __init__
 self._manifest = self.manifestClass(repoPath, sdUUID, imgUUID,
> volUUID) File
> "/usr/lib/python2.7/site-packages/vdsm/storage/blockVolume.py", line 62, in
> __init__ volUUID)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/volume.py", line 86,
> in __init__
 self.validate()
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/blockVolume.py", line
> 151, in validate
 raise se.VolumeDoesNotExist(self.volUUID)
> VolumeDoesNotExist: Volume does not exist:
> (u'46bf0806-8d16-40db-92df-8436f43628a4',)
 2021-03-08 12:09:17,946+0100
> INFO  (tasks/7) [storage.ThreadPool.WorkerThread] FINISH task
> d4aa81a1-9adc-45c9-be46-05bc63862f4e (threadPool:210) 2021-03-08
> 12:09:18,273+0100 WARN  (jsonrpc/7) [storage.LVM] Command ['/usr/sbin/lvm',
> 'lvchange', '--config', 'devices {  preferred_names=["^/dev/mapper/"] 
> ignore_suspended_devices=1  write_cache_state=0 
> disable_after_error_count=3 
> filter=["a|^/dev/mapper/2181ad2edfa7b485c6c9ce90045609718$|^/dev/mapper/276
> 3fdda70ca458906c9ce90045609718$|^/dev/mapper/28ba7d1d12c7099ef6c9ce900456097
> 18$|^/dev/mapper/2e9d013564898d36f6c9ce90045609718$|", "r|.*|"] } global { 
> locking_type=1  prioritise_write_locks=1  wait_for_locks=1  use_lvmetad=0 }
> backup {  retain_min=50  retain_days=0 }', '--autobackup', 'n', '-a', 'y',
> '--deltag', u'IU_459872a1-8783-463a-98ae-9e56d8883abb', '--addtag',
> u'IU__remove_me_459872a1-8783-463a-98ae-9e56d8883abb',
> 'fb14e013-15f1-49b6-b129-210517aca0da/5d51973d-4198-4cec-994a-727317640ccb'
> ] succeeded with warnings: ['  WARNING: Combining activation change with
> other commands is not advised.', '  Scan of VG
> fb14e013-15f1-49b6-b129-210517aca0da from /dev/mapper/2763fdda70ca
> 458906c9ce90045609718 found metadata seqno 26448 

[ovirt-users] Re: Removed FC LUN causes multipath to spam syslog

2021-03-05 Thread Vojtech Juranek
On Friday, 5 March 2021 12:16:56 CET Juhani Rautiainen wrote:
> Hi!
> 
> Ansible script fails and reason seems to be those stale DM links. We
> are currently still in 4.3.10 as I wanted to do this change before the
> upgrade to 4.4. We have SHE and it is currently on a 3PAR disk. When
> we upgrade we can do the SHE change at the same time as I didn't want
> to do two SHE restores (1st in 4.3 and then in 4.4). As there wasn't
> any hint how you can remove those stale DM links the best solution
> probably is to put nodes in maintenance and reboot them.

you can remove the stale links by

dmsetup remove -f /dev/mapper/


> BTW I did dezone those disks after I had removed them from oVirt UI. I
> mean you can't remove them while they are still on oVirt?

if the LUN is on target where no other LUN are used by oVirt, multipath 
devices should be removed and vdsm should be logged out from the tergat (at 
least on recent oVirt release). If you still use other LUNs from the storage 
server on the host (as part of other storage domains), there's no point in 
removing the LUN as it will be discovered again, as vdsm does rescans of the 
storage in various flows. So the flow has to be

1. remove storage domain using the LUN
2. unzone the LUN on storage server
3. remove corresponding multipath devices from the hosts

There can be some improvement as proposed by Nir under BZ #1310330 like 
blacklisting removed devices, but this makes everything more complex. It may 
be considered and implemented in the future, but unfortunately not available 
right now.

> Thanks,
> Juhani
> 
> On Fri, Mar 5, 2021 at 11:02 AM Vojtech Juranek  wrote:
> > On Friday, 5 March 2021 09:02:51 CET Juhani Rautiainen wrote:
> > > Hi!
> > > 
> > > We are running ovirt 4.3.10 and we are migrating from 3PAR to Dell SC.
> > > I've managed to transfer disks from one LUN away and removed it (put
> > > it in maintenanced, detached it and removed it). Now multipath seems
> > > to spam the logs for missing disks. How can I stop this?
> > 
> > you can remove multipath device either manually or you can use ansible
> > playbook for it, please try one attached to
> > 
> > https://bugzilla.redhat.com/1310330
> > 
> > see
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1310330#c56
> > 
> > how to use it. You also have to change `hosts` to group of hosts you want
> > to test on and remove `connection: local`
> > 
> > If it fail, please report back. It can fail as there are stale DM links,
> > see
> > 
> > bugzilla.redhat.com/1928041
> > 
> > this was fixed recently and should be in next oVirt relase.
> > 
> > Alternatively, you can reboot the host.
> > 
> > > Mar  5 09:58:58 ovirt01 multipathd: 360002ac0027257b9:
> > > sdr - tur checker reports path is down
> > > Mar  5 09:58:59 ovirt01 multipathd: 360002ac0027257b9:
> > > sdh - tur checker reports path is down
> > > 
> > > And so on. Any idea how I can quiet this? And why didn't oVirt do this
> > > automatically?
> > 
> > to be able to remove multipath devices, the LUN has to be unzoned first on
> > the storage server and this cannot be done by oVirt, as oVirt doesn't
> > manage the storage server - this has to be done by administator of
> > storage server which has subsequently remove multipath devices from the
> > hosts e.g. by using ansible script mention above.
> > 
> > > Thanks,
> > > Juhani
> > > ___
> > > 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/QLENIZGWGU
> > > U4J
> > > OETXNQCNIK5GTU2EFVZ/



signature.asc
Description: This is a digitally signed message part.
___
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/UZLRKGUFWY5QLV5W2XMNZ3LNLPRKV2O5/


[ovirt-users] Re: Removed FC LUN causes multipath to spam syslog

2021-03-05 Thread Vojtech Juranek
On Friday, 5 March 2021 09:02:51 CET Juhani Rautiainen wrote:
> Hi!
> 
> We are running ovirt 4.3.10 and we are migrating from 3PAR to Dell SC.
> I've managed to transfer disks from one LUN away and removed it (put
> it in maintenanced, detached it and removed it). Now multipath seems
> to spam the logs for missing disks. How can I stop this?

you can remove multipath device either manually or you can use ansible 
playbook for it, please try one attached to 

https://bugzilla.redhat.com/1310330

see

https://bugzilla.redhat.com/show_bug.cgi?id=1310330#c56

how to use it. You also have to change `hosts` to group of hosts you want to 
test on and remove `connection: local`

If it fail, please report back. It can fail as there are stale DM links, see 

bugzilla.redhat.com/1928041

this was fixed recently and should be in next oVirt relase.

Alternatively, you can reboot the host.

> Mar  5 09:58:58 ovirt01 multipathd: 360002ac0027257b9:
> sdr - tur checker reports path is down
> Mar  5 09:58:59 ovirt01 multipathd: 360002ac0027257b9:
> sdh - tur checker reports path is down
> 
> And so on. Any idea how I can quiet this? And why didn't oVirt do this
> automatically?

to be able to remove multipath devices, the LUN has to be unzoned first on the 
storage server and this cannot be done by oVirt, as oVirt doesn't manage the 
storage server - this has to be done by administator of storage server which 
has subsequently remove multipath devices from the hosts e.g. by using ansible 
script mention above.

> Thanks,
> Juhani
> ___
> 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/QLENIZGWGUU4J
> OETXNQCNIK5GTU2EFVZ/



signature.asc
Description: This is a digitally signed message part.
___
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/WZ65BOYS47ULYGMNWHB7LDJ2T26L2DOR/


[ovirt-users] Re: Achieving high availability

2021-02-02 Thread Vojtech Juranek
On Tuesday, 2 February 2021 11:37:01 CET Andrea Chierici wrote:
> Hi,
> I am trying to configure high availability on a critical VM. My ovirt
> version is 4.3.10.4-1.el7.
> My question is about the best settings to specify, since it's not
> completely clear to me how they influence the availability.
> 
> What I want is simply to have a specific machine ALWAYS running, or at
> least, to be available as much as possible. I have no special
> requirements on the VM, if it goes down, simply restarting it is fine.
> 
> Here is my current setting. Is it good or I'd better chage anything?

you may want to configure VM lease. If you don't do so, in case of split 
brain, there can be two VMs running and accessing the same storage, leading to 
the data corruption. With VM leases this cannot happen - only one VM can 
access the storage. To speed up the switch, you may want to configure also 
watchdog. But there can be use cases (e.g. stateless server which just 
forwards received packet somewhere) where leases are not needed or not using 
them won't cause any harm. See [1] for more details.

[1] https://www.ovirt.org/develop/ha-vms.html
 
> 
> 
> Thanks,
> Andrea



signature.asc
Description: This is a digitally signed message part.
___
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/IYHLDVK7UNFBHAT7ZQ3J7LIJSS24AZ5B/


[ovirt-users] Re: Gluster Storage

2021-01-25 Thread Vojtech Juranek
On Monday, 25 January 2021 12:22:51 CET dkipla...@outlook.com wrote:
> Hi Nikolov,
> I have installed ovirt with default settings and seems i cant find any
> detail steps to set up Gluster storage after that, if there is any link i
> will appreciate if you can share.

please check 

https://www.ovirt.org/documentation/gluster-hyperconverged/chap-Deploying_Hyperconverged.html

or

https://www.ovirt.org/documentation/installing_ovirt_as_a_standalone_manager_with_local_databases/#Adding_Red_Hat_Gluster_Storage_SM_localDB_deploy


> ___
> 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/GCQO223RHZCUE
> WTWKP23SE25ARMT5WO6/



signature.asc
Description: This is a digitally signed message part.
___
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/G3OEQEHNYIWDGBTUELTSFGYLGQWHMW2F/


[ovirt-users] Re: not able to upload disks, iso - Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate is registered as a valid CA in the browser.

2021-01-11 Thread Vojtech Juranek
On Monday, 11 January 2021 09:44:57 CET dhanaraj.ramesh--- via Users wrote:
> given recommendation is not working.

could you be more specific, what exactly doesn't work, what kind of error you 
got etc?

Thanks
Vojta

signature.asc
Description: This is a digitally signed message part.
___
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/BNZ642XR3N7ZGZTCXUJVGMJK75IOIFNF/


[ovirt-users] Re: not able to upload disks, iso - Connection to ovirt-imageio service has failed. Ensure that ovirt-engine certificate is registered as a valid CA in the browser.

2021-01-08 Thread Vojtech Juranek
Hi,

> We are unning with 4.4.3.12-1.el8 version and so far working fine, but today
> users complained they are unable to upload new disks and upon checking
> found "Connection to ovirt-imageio service has failed. Ensure that
> ovirt-engine certificate is registered as a valid CA in the browser" during
> testing option. please help on this and if there is any temp solution is
> available share me the steps

if you want to upload imgaes from browser, you have to import certificates into 
the *browser*.
So follow the link, download the certificate and import it into the browser as 
a trusted. I.e. this
is related to browser configuration, not oVirt configuration. See [1, 2] for 
more details.

Alternatively, you can upload image using upload_disk example script from 
ovirt-engine-sdk [3], e.g.

curl -k 
"https://$ENGINE_URL/ovirt-engine/services/pki-resource?resource=ca-certificate=X509-PEM-CA;
 > cert.pem
./upload_disk.py --insecure --engine-url $ENGINE_URL --username 
admin@internal --password-file $PASSWD_FILE --disk-format raw --sd-name 
$STORAGE_DOMAIN_NAME -c cert.pem $PATH_TO_IMAGE

HTH
Vojta

[1] Browser configuration section in 
http://ovirt.github.io/ovirt-imageio/configuration.html
[2] https://www.ovirt.org/develop/release-management/features/infra/pki.html
[3] 
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk.py

signature.asc
Description: This is a digitally signed message part.
___
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/UQNLKIAMIDEADBRYS7U3CTREKZRKECQC/


[ovirt-users] Re: Imageio Daemon not listening on port 54323

2020-10-13 Thread Vojtech Juranek
On úterý 13. října 2020 9:37:11 CEST Tim Bordemann wrote:
> > On 12. Oct 2020, at 12:15, Vojtech Juranek  wrote:
> > 
> > On pátek 9. října 2020 19:02:32 CEST tim-nospam--- via Users wrote:
> >> Hello.
> >> 
> >> After an upgrade I am not able to upload images anymore via the ovirt ui.
> >> When testing the connection, I always get the error message "Connection
> >> to
> >> ovirt-imageio-proxy service has failed. Make sure the service is
> >> installed,
> >> configured, and ovirt-engine certificate is registered as a valid CA in
> >> the
> >> browser.".
> >> 
> >> I found out that the imageio daemon doesn't listen on port 54323 anymore,
> >> so the browser can not connect to it. The daemon is configured to listen
> >> on port 54323 though:
> >> 
> >> # cat /etc/ovirt-imageio/conf.d/50-engine.conf
> >> [...]
> >> [remote]
> >> port = 54323
> >> [...]
> >> 
> >> The imageio daemon has been started successfully on the engine host as
> >> well
> >> as on the other hosts.
> >> 
> >> I am currently stuck, what should I do next?
> >> The ovirt version I am using is 4.4.
> > 
> > what is exact version of imageio? (rpm -qa|grep imageio)
> 
> # rpm -qa|grep imageio
> ovirt-engine-setup-plugin-imageio-4.4.2.6-1.el8.noarch
> ovirt-imageio-daemon-2.0.10-1.el8.x86_64
> ovirt-imageio-common-2.0.10-1.el8.x86_64
> ovirt-imageio-client-2.0.10-1.el8.x86_64
> 
> > On which port imageio listens? You can use e.g. netstat etc. Also plase
> > check imageio logs (/var/log/ovirt-imageio/daemon.log), what is there,
> > there shold
> > be something like this:
> # netstat -tulpn | grep 543
> tcp0  0 0.0.0.0:54322   0.0.0.0:*   LISTEN  
>2527872/platform-py tcp0  0 127.0.0.1:54324
> 0.0.0.0:*   LISTEN  2527872/platform-py
> > 2020-10-08 08:37:48,906 INFO(MainThread) [services] remote.service
> > listening on ('::', 54323)
> 
> 2020-10-09 17:46:38,216 INFO(MainThread) [server] Starting (pid=2527872,
> version=2.0.10) 2020-10-09 17:46:38,220 INFO(MainThread) [services]
> remote.service listening on ('0.0.0.0', 54322) 2020-10-09 17:46:38,221 INFO
>(MainThread) [services] control.service listening on ('127.0.0.1',
> 54324) 2020-10-09 17:46:38,227 INFO(MainThread) [server] Ready for
> requests
> 
> No entries for Port 54323 in the last 3 months. I found logentries in july
> though:
> 
> [root@helios ~]# cat /var/log/ovirt-imageio/daemon.log | grep 54323
> 2020-07-11 10:13:24,777 INFO(MainThread) [services] remote.service
> listening on ('::', 54323) [...]
> 2020-07-16 19:54:13,398 INFO(MainThread) [services] remote.service
> listening on ('::', 54323) 2020-07-16 19:54:36,715 INFO(MainThread)
> [services] remote.service listening on ('::', 54323)
> > Also, please check if there are any other config files (*.conf) in
> > /etc/ovirt- imageio/conf.d or in /usr/lib/ovirt-imageio/conf.d
> 
> I have, but I couldn't find anything interesting in those two files:
> 
> # ls -l /etc/ovirt-imageio/conf.d/
> total 8
> -rw-r--r--. 1 root root 1458 Oct  9 17:54 50-engine.conf
> -rw-r--r--. 1 root root 1014 Sep 15 11:16 50-vdsm.conf

50-vdsm.conf overwrites 50-engine.conf (later config taken alphabetically 
overwrites previous config if there is any).

If you don't use engine as a host at the same time, stop an uninstall vdsm from 
engine (should remove also 50-vdsm.conf) and restart ovirt-imageio service.

If you use engine as a host at the same time, note that this is unsupported. 
However, there were some patches in this area recently, but they are not 
released yet AFAICT. See [1, 2] for more details.

[1] https://bugzilla.redhat.com/1871348
[2] 
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/W4OTINLXYDWG3YSF2OUQU3NW3ADRPGUR/

> The imageio daemon should listen on Port 54323:
> 
> 
> # /etc/ovirt-imageio/conf.d/50-engine.conf
> [...]
> [remote]
> # Port cannot be changed as it's currently hardcoded in engine code.
> port = 54323
> [...]
> 
> >> There is one machine running the ovirt
> >> engine and there are 2 additional hosts. The OS on the machines is Centos
> >> 8.
> >> 
> >> 
> >> 
> >> 
> >> Thank you,
> >> Tim
> >> ___
> >> Users mailing list -- users@ovirt.org
> >> To unsubscribe send an email to users-le...@ovirt.org
> >> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> >> oVirt 

[ovirt-users] Re: Imageio Daemon not listening on port 54323

2020-10-12 Thread Vojtech Juranek
On pátek 9. října 2020 19:02:32 CEST tim-nospam--- via Users wrote:
> Hello.
> 
> After an upgrade I am not able to upload images anymore via the ovirt ui.
> When testing the connection, I always get the error message "Connection to
> ovirt-imageio-proxy service has failed. Make sure the service is installed,
> configured, and ovirt-engine certificate is registered as a valid CA in the
> browser.".
 
> I found out that the imageio daemon doesn't listen on port 54323 anymore, so
> the browser can not connect to it. The daemon is configured to listen on
> port 54323 though:
 
> # cat /etc/ovirt-imageio/conf.d/50-engine.conf
> [...]
> [remote]
> port = 54323
> [...]
> 
> The imageio daemon has been started successfully on the engine host as well
> as on the other hosts.
 
> I am currently stuck, what should I do next?
> The ovirt version I am using is 4.4.

what is exact version of imageio? (rpm -qa|grep imageio)

On which port imageio listens? You can use e.g. netstat etc. Also plase check 
imageio logs (/var/log/ovirt-imageio/daemon.log), what is there, there shold 
be something like this:

2020-10-08 08:37:48,906 INFO(MainThread) [services] remote.service 
listening on ('::', 54323)


Also, please check if there are any other config files (*.conf) in /etc/ovirt-
imageio/conf.d or in /usr/lib/ovirt-imageio/conf.d

> There is one machine running the ovirt
> engine and there are 2 additional hosts. The OS on the machines is Centos
> 8.




> Thank you,
> Tim
> ___
> 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/GWIVRHYHNGUVJ
> NSQTYCDQBOG6VFXCZPB/



signature.asc
Description: This is a digitally signed message part.
___
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/KTZ3GQYZD5JREK75DP3LVOEJFYOL3ZR5/


[ovirt-users] Re: oVirt - vdo: ERROR - Device /dev/sd excluded by a filter

2020-09-21 Thread Vojtech Juranek
On sobota 19. září 2020 5:58:43 CEST Jeremey Wise wrote:
> [image: image.png]
> 
> vdo: ERROR - Device /dev/sdc excluded by a filter
> 
> [image: image.png]

when this error happens? When you install ovirt HCI?


> Where is getting this filter.
> I have done gdisk /dev/sdc ( new 1TB Drive) and shows no partition.  I even
> did a full dd if=/dev/zero   and no change.

it's installed by vdsm to exclude ovirt devices from common use



signature.asc
Description: This is a digitally signed message part.
___
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/OK6TE456D37ZHGVT7XBDFLKLT6EH4HAM/


[ovirt-users] Re: Bad volume specification

2020-09-18 Thread Vojtech Juranek
On čtvrtek 17. září 2020 16:07:16 CEST Facundo Garat wrote:
> I don't think so, We have bigger LUNs assigned so if that were the case we
> would have lost access to many LVs.
> 
> Do I have a way to manually query the LVs content to find out if it's still
> there?.

you can ssh to a host and check LV

lvs 55327311-e47c-46b5-b168-258c5924757b/bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f 
--config 'devices {filter=["a|.*|"]}'

and path

/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/images/f5bd2e15-a1ab-4724-883a-988b4dc7985b/bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f

If path exists, you can run qemu-img info on it.

Looking more into vdsm log, it seems that volume 
bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f
is not part of the disk image (f5bd2e15-a1ab-4724-883a-988b4dc7985b).

Unfortunately no idea how it got into such state, maybe engine DB is out of 
sync with storage?
(you can check the DB on engine, by connecting to postgres DB "engine" and 
running 
select image_group_id from images where 
image_guid='bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f';
to see to what image this volume belong to according to engine DB)

> On Thu, Sep 17, 2020 at 10:55 AM Vojtech Juranek 
> 
> wrote:
> > On čtvrtek 17. září 2020 14:30:12 CEST Facundo Garat wrote:
> > > Hi Vojtech,
> > > 
> > >   find the log attached.
> > 
> > thanks. It fails as one of the image volumes
> > (6058a880-9ee6-4c57-9db0-5946c6dab676) is now available/present on the
> > storage. You can check manually if there's such LV, but it's not very
> > likely.
> > Didn't you by accident remove the volume?
> > 
> > > On Thu, Sep 17, 2020 at 4:27 AM Vojtech Juranek 
> > 
> > wrote:
> > > > Hi,
> > > > could you please send us also relevant part of vdsm log
> > > > (/var/log/vdsm/
> > > > vdsm.log)?
> > > > Thanks
> > > > Vojta
> > > > 
> > > > > The VM has one snapshot which I can't delete because it shows a
> > 
> > similar
> > 
> > > > > error. That doesn't allow me to attach the disks to another VM. This
> > 
> > VM
> > 
> > > > > will boot ok if the disks are deactivated.
> > > > > 
> > > > > Find the engine.log attached.
> > > > > 
> > > > > The steps associated with the engine log:
> > > > >- The VM is on booted from CD with all disks deactivated
> > > > >- Try to attach all three disks (fail!)
> > > > >- Power off the VM
> > > > >- Activate all three disks
> > > > >- Try to delete the snapshot.
> > > > > 
> > > > > Thanks.
> > > > > 
> > > > > On Wed, Sep 16, 2020 at 9:35 AM Ahmad Khiet 
> > 
> > wrote:
> > > > > > Hi,
> > > > > > 
> > > > > > can you please attach the engine log? what steps did you make
> > 
> > before
> > 
> > > > > > this error is shown? did you tried to create a snapshot and failed
> > > > 
> > > > before
> > > > 
> > > > > > On Wed, Sep 16, 2020 at 7:49 AM Strahil Nikolov via Users
> > > > > > 
> > > > > > 
> > > > > > wrote:
> > > > > >> What happens if you create another VM and attach the disks to it
> > > > > >> ?
> > > > > >> Does it boot properly ?
> > > > > >> 
> > > > > >> Best Regards,
> > > > > >> Strahil Nikolov
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> В сряда, 16 септември 2020 г., 02:19:26 Гринуич+3, Facundo Garat
> > > > > >> <
> > > > > >> fga...@gmail.com> написа:
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> 
> > > > > >> Hi all,
> > > > > >> 
> > > > > >>  I'm having some issues with one VM. The VM won't start and it's
> > > > 
> > > > showing
> > > > 
> > > > > >> problems with the virtual disks so I started the VM without any
> > 
> > disks
> > 
> > > &

[ovirt-users] Re: Bad volume specification

2020-09-17 Thread Vojtech Juranek
On čtvrtek 17. září 2020 14:30:12 CEST Facundo Garat wrote:
> Hi Vojtech,
>   find the log attached.

thanks. It fails as one of the image volumes 
(6058a880-9ee6-4c57-9db0-5946c6dab676) is now available/present on the 
storage. You can check manually if there's such LV, but it's not very likely. 
Didn't you by accident remove the volume?

> On Thu, Sep 17, 2020 at 4:27 AM Vojtech Juranek  wrote:
> > Hi,
> > could you please send us also relevant part of vdsm log (/var/log/vdsm/
> > vdsm.log)?
> > Thanks
> > Vojta
> > 
> > > The VM has one snapshot which I can't delete because it shows a similar
> > > error. That doesn't allow me to attach the disks to another VM. This VM
> > > will boot ok if the disks are deactivated.
> > > 
> > > Find the engine.log attached.
> > > 
> > > The steps associated with the engine log:
> > >- The VM is on booted from CD with all disks deactivated
> > >- Try to attach all three disks (fail!)
> > >- Power off the VM
> > >- Activate all three disks
> > >- Try to delete the snapshot.
> > > 
> > > Thanks.
> > > 
> > > On Wed, Sep 16, 2020 at 9:35 AM Ahmad Khiet  wrote:
> > > > Hi,
> > > > 
> > > > can you please attach the engine log? what steps did you make before
> > > > this error is shown? did you tried to create a snapshot and failed
> > 
> > before
> > 
> > > > On Wed, Sep 16, 2020 at 7:49 AM Strahil Nikolov via Users
> > > > 
> > > > 
> > > > wrote:
> > > >> What happens if you create another VM and attach the disks to it ?
> > > >> Does it boot properly ?
> > > >> 
> > > >> Best Regards,
> > > >> Strahil Nikolov
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> В сряда, 16 септември 2020 г., 02:19:26 Гринуич+3, Facundo Garat <
> > > >> fga...@gmail.com> написа:
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> 
> > > >> Hi all,
> > > >> 
> > > >>  I'm having some issues with one VM. The VM won't start and it's
> > 
> > showing
> > 
> > > >> problems with the virtual disks so I started the VM without any disks
> > 
> > and
> > 
> > > >> trying to hot adding the disk and that's fail too.
> > > >> 
> > > >>  The servers are connected thru FC, all the other VMs are working
> > 
> > fine.
> > 
> > > >>   Any ideas?.
> > > >> 
> > > >> Thanks!!
> > > >> 
> > > >> PS: The engine.log is showing this:
> > > >> 2020-09-15 20:10:37,926-03 INFO
> > > >> 
> > > >>  [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand]
> > 
> > (default
> > 
> > > >> task-168) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Lock Acquired to
> > 
> > object
> > 
> > 'EngineLock:{exclusiveLocks='[f5bd2e15-a1ab-4724-883a-988b4dc7985b=DISK]'
> > 
> > > >> ,
> > > >> sharedLocks='[71db02c2-df29-4552-8a7e-cb8bb429a2ac=VM]'}'
> > > >> 2020-09-15 20:10:38,082-03 INFO
> > > >> 
> > > >>  [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand]
> > > >> 
> > > >> (EE-ManagedThreadFactory-engine-Thread-36528)
> > > >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Running command:
> > > >> HotPlugDiskToVmCommand internal: false. Entities affected :  ID:
> > > >> 71db02c2-df29-4552-8a7e-cb8bb429a2ac Type: VMAction group
> > > >> CONFIGURE_VM_STORAGE with role type USER
> > > >> 2020-09-15 20:10:38,117-03 INFO
> > > >> 
> > > >>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> > > >> 
> > > >> (EE-ManagedThreadFactory-engine-Thread-36528)
> > > >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] START,
> > > >> HotPlugDiskVDSCommand(HostName = nodo2,
> > 
> > HotPlugDiskVDSParameters:{hostId='1c24c269-76c3-468d-a7ce-d0332beb7aef',
> > 
> > > >> vmId='71db02c2-df29-4552-8a7e-cb8bb429a2ac',
> > > >> diskId='f5bd2e15-a1ab-4724-883a-988b4dc7985

[ovirt-users] Re: Bad volume specification

2020-09-17 Thread Vojtech Juranek
Hi,
could you please send us also relevant part of vdsm log (/var/log/vdsm/
vdsm.log)?
Thanks
Vojta


> The VM has one snapshot which I can't delete because it shows a similar
> error. That doesn't allow me to attach the disks to another VM. This VM
> will boot ok if the disks are deactivated.
> 
> Find the engine.log attached.
> 
> The steps associated with the engine log:
> 
>- The VM is on booted from CD with all disks deactivated
>- Try to attach all three disks (fail!)
>- Power off the VM
>- Activate all three disks
>- Try to delete the snapshot.
> 
> Thanks.
> 
> On Wed, Sep 16, 2020 at 9:35 AM Ahmad Khiet  wrote:
> > Hi,
> > 
> > can you please attach the engine log? what steps did you make before
> > this error is shown? did you tried to create a snapshot and failed before
> > 
> > 
> > On Wed, Sep 16, 2020 at 7:49 AM Strahil Nikolov via Users
> > 
> > 
> > wrote:
> >> What happens if you create another VM and attach the disks to it ?
> >> Does it boot properly ?
> >> 
> >> Best Regards,
> >> Strahil Nikolov
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> В сряда, 16 септември 2020 г., 02:19:26 Гринуич+3, Facundo Garat <
> >> fga...@gmail.com> написа:
> >> 
> >> 
> >> 
> >> 
> >> 
> >> 
> >> Hi all,
> >> 
> >>  I'm having some issues with one VM. The VM won't start and it's showing
> >> 
> >> problems with the virtual disks so I started the VM without any disks and
> >> trying to hot adding the disk and that's fail too.
> >> 
> >>  The servers are connected thru FC, all the other VMs are working fine.
> >>  
> >>   Any ideas?.
> >> 
> >> Thanks!!
> >> 
> >> PS: The engine.log is showing this:
> >> 2020-09-15 20:10:37,926-03 INFO
> >> 
> >>  [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand] (default
> >> 
> >> task-168) [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Lock Acquired to object
> >> 'EngineLock:{exclusiveLocks='[f5bd2e15-a1ab-4724-883a-988b4dc7985b=DISK]'
> >> ,
> >> sharedLocks='[71db02c2-df29-4552-8a7e-cb8bb429a2ac=VM]'}'
> >> 2020-09-15 20:10:38,082-03 INFO
> >> 
> >>  [org.ovirt.engine.core.bll.storage.disk.HotPlugDiskToVmCommand]
> >> 
> >> (EE-ManagedThreadFactory-engine-Thread-36528)
> >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Running command:
> >> HotPlugDiskToVmCommand internal: false. Entities affected :  ID:
> >> 71db02c2-df29-4552-8a7e-cb8bb429a2ac Type: VMAction group
> >> CONFIGURE_VM_STORAGE with role type USER
> >> 2020-09-15 20:10:38,117-03 INFO
> >> 
> >>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> >> 
> >> (EE-ManagedThreadFactory-engine-Thread-36528)
> >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] START,
> >> HotPlugDiskVDSCommand(HostName = nodo2,
> >> HotPlugDiskVDSParameters:{hostId='1c24c269-76c3-468d-a7ce-d0332beb7aef',
> >> vmId='71db02c2-df29-4552-8a7e-cb8bb429a2ac',
> >> diskId='f5bd2e15-a1ab-4724-883a-988b4dc7985b', addressMap='null'}), log
> >> id:
> >> f57ee9e
> >> 2020-09-15 20:10:38,125-03 INFO
> >> 
> >>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> >> 
> >> (EE-ManagedThreadFactory-engine-Thread-36528)
> >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Disk hot-plug:  >> encoding="UTF-8"?>
> >> 
> >>   
> >>   
> >> 
> >> 
> >>   
> >>>> 
> >> dev="/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/i
> >> mages/f5bd2e15-a1ab-4724-883a-988b4dc7985b/bd714f21-8eed-43ee-a2d4-3d2ef1
> >> ee4c3f">>> 
> >> 
> >>   
> >>   
> >>>> 
> >> cache="none"/>
> >> 
> >>   
> >>   f5bd2e15-a1ab-4724-883a-988b4dc7985b
> >> 
> >> 
> >>   
> >>   
> >>   http://ovirt.org/vm/1.0;>
> >>   
> >> 
> >> 
> >>   
> >> 
> >> 0001-0001-0001-0001-0311
> >> 
> >> bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f >> D>
> >> 
> >> f5bd2e15-a1ab-4724-883a-988b4dc7985b
> >> 
> >> 55327311-e47c-46b5-b168-258c5924757b >> D>
> >> 
> >>   
> >> 
> >> 
> >>   
> >>   
> >> 
> >> 
> >> 
> >> 2020-09-15 20:10:38,289-03 ERROR
> >> [org.ovirt.engine.core.vdsbroker.vdsbroker.HotPlugDiskVDSCommand]
> >> (EE-ManagedThreadFactory-engine-Thread-36528)
> >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] Failed in 'HotPlugDiskVDS' method
> >> 2020-09-15 20:10:38,295-03 ERROR
> >> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> >> (EE-ManagedThreadFactory-engine-Thread-36528)
> >> [dd72c8e8-cdbe-470f-8e32-b3d14b96f37a] EVENT_ID:
> >> VDS_BROKER_COMMAND_FAILURE(10,802), VDSM nodo2 command HotPlugDiskVDS
> >> failed: General Exception: ("Bad volume specification {'device': 'disk',
> >> 'type': 'disk', 'diskType': 'block', 'specParams': {}, 'alias':
> >> 'ua-f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'domainID':
> >> '55327311-e47c-46b5-b168-258c5924757b', 'imageID':
> >> 'f5bd2e15-a1ab-4724-883a-988b4dc7985b', 'poolID':
> >> '0001-0001-0001-0001-0311', 'volumeID':
> >> 'bd714f21-8eed-43ee-a2d4-3d2ef1ee4c3f', 'path':
> >> '/rhev/data-center/mnt/blockSD/55327311-e47c-46b5-b168-258c5924757b/image
> >> 

[ovirt-users] Re: Storage Domain won't activate

2020-09-04 Thread Vojtech Juranek
On čtvrtek 3. září 2020 22:49:17 CEST Gillingham, Eric J (US 393D) via Users 
wrote:
> I recently removed a host from my cluster to upgrade it to 4.4, after I
> removed the host from the datacenter VMs started to pause on the second
> system they all migrated to. Investigating via the engine showed the
> storage domain was showing as "unknown", when I try to activate it via the
> engine it cycles to locked then to unknown again.
 
> /var/log/sanlock.log contains a repeating:
> add_lockspace
> e1270474-108c-4cae-83d6-51698cffebbf:1:/dev/e1270474-108c-4cae-83d6-51698cf
> febbf/ids:0 conflicts with name of list1 s1
> e1270474-108c-4cae-83d6-51698cffebbf:3:/dev/e1270474-108c-4cae-83d6-51698cf
> febbf/ids:0

how do you remove the fist host, did you put it into maintenance first? I 
wonder, how this situation (two lockspaces with conflicting names) can occur.

You can try to re-initialize the lockspace directly using sanlock command (see 
man sanlock), but it would be good to understand the situation first.


> 
> vdsm.log contains these (maybe related) snippets:
> ---
> 2020-09-03 20:19:53,483+ INFO  (jsonrpc/6) [vdsm.api] FINISH
> getAllTasksStatuses error=Secured object is not in safe state
> from=:::137.79.52.43,36326, flow_id=18031a91,
> task_id=8e92f059-743a-48c8-aa9d-e7c4c836337b (api:52)
 2020-09-03
> 20:19:53,483+ ERROR (jsonrpc/6) [storage.TaskManager.Task]
> (Task='8e92f059-743a-48c8-aa9d-e7c4c836337b') Unexpected error (task:875)
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in
> _run
 return fn(*args, **kargs)
>   File "", line 2, in getAllTasksStatuses
>   File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 50, in
> method
 ret = func(*args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 2201, in
> getAllTasksStatuses
 allTasksStatus = self._pool.getAllTasksStatuses()
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line
> 77, in wrapper
 raise SecureError("Secured object is not in safe state")
> SecureError: Secured object is not in safe state
> 2020-09-03 20:19:53,483+ INFO  (jsonrpc/6) [storage.TaskManager.Task]
> (Task='8e92f059-743a-48c8-aa9d-e7c4c836337b') aborting: Task is aborted:
> u'Secured object is not in safe state' - code 100 (task:1181)
 2020-09-03
> 20:19:53,483+ ERROR (jsonrpc/6) [storage.Dispatcher] FINISH
> getAllTasksStatuses error=Secured object is not in safe state
> (dispatcher:87) Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/dispatcher.py", line
> 74, in wrapper
 result = ctask.prepare(func, *args, **kwargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 108, in
> wrapper
 return m(self, *a, **kw)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 1189,
> in prepare
 raise self.error
> SecureError: Secured object is not in safe state
> ---
> 2020-09-03 20:44:23,252+ INFO  (tasks/2)
> [storage.ThreadPool.WorkerThread] START task
> 76415a77-9d29-4b72-ade1-53207cfc503b (cmd= >, args=None) (thre
> adPool:208)
> 2020-09-03 20:44:23,266+ INFO  (tasks/2) [storage.SANLock] Acquiring
> host id for domain e1270474-108c-4cae-83d6-51698cffebbf (id=1, wait=True)
> (clusterlock:313)
 2020-09-03 20:44:23,267+ ERROR (tasks/2)
> [storage.TaskManager.Task] (Task='76415a77-9d29-4b72-ade1-53207cfc503b')
> Unexpected error (task:875) Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in
> _run
 return fn(*args, **kargs)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 336, in
> run
 return self.cmd(*self.argslist, **self.argsdict)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/sp.py", line 317, in
> startSpm
 self.masterDomain.acquireHostId(self.id)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 957, in
> acquireHostId
 self._manifest.acquireHostId(hostId, wait)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/sd.py", line 501, in
> acquireHostId
 self._domainLock.acquireHostId(hostId, wait)
>   File "/usr/lib/python2.7/site-packages/vdsm/storage/clusterlock.py", line
> 344, in acquireHostId
 raise se.AcquireHostIdFailure(self._sdUUID, e)
> AcquireHostIdFailure: Cannot acquire host id:
> ('e1270474-108c-4cae-83d6-51698cffebbf', SanlockException(22, 'Sanlock
> lockspace add failure', 'Invalid argument'))
 ---
> 
> Another symptom is in the hosts view of the engine SPM bounces between
> "Normal" and "Contending". When it's Normal if I select Management ->
> Select as SPM I get "Error while executing action: Cannot force select SPM.
> Unknown Data Center status."
 
> I've tried rebooting the one remaining host in the cluster no to avail,
> hosted-engine --reinitialize-lockspace also seems to not solve the issue.
 
> 
> I'm kind of stumped as to what else to try, would appreciate any guidance on
> how to resolve this.
 
> Thank 

[ovirt-users] Re: HA Storage options

2020-08-19 Thread Vojtech Juranek
On úterý 18. srpna 2020 1:37:09 CEST David White via Users wrote:
> Hi,
> I started an email thread a couple months ago, and felt like I got some
> great feedback and suggestions on how to best setup an oVirt cluster.
> Thanks for your responses thus far.My goal is to take a total of 3-4
> servers that I can use for both the storage and the virtualization, and I
> want both to be highly available. 
> 
> You guys told me about oVirt Hyperconverged with Gluster, and that seemed
> like a great option. However, I'm concerned that this may not actually be
> the best approach. I've spoken with multiple people at Red Hat who I have a
> relationship with (outside of the context of the project I'm working on
> here), and all of them have indicated to me that Gluster is being
> deprecated, and that most of the engineering focus these days is on Ceph. I
> was also told by a Solutions Architect who has extensive experience with
> RHV that the hyperconverged clusters he used to build would always give him
> problems.
> 
> Does oVirt support DRBD or Ceph storage? From what I can find, I think that
> the answer to both of those is, sadly, no.

ceph (and anything supported by cindelib) is available via Managed block 
storage:

https://www.ovirt.org/develop/release-management/features/storage/cinderlib-integration.html


> So now I'm thinking about switching gears, and going with iSCSI instead. 
> But I'm still trying to think about the best way to replicate the storage,
> and possibly use multipathing so that it will be HA for the VMs that rely
> on it.
> 
> Has anyone else experienced problems with the Gluster hyperconverged
> solution? Am I overthinking this whole thing, and am I being too paranoid?
> Is it possible to setup some sort of software-RAID with multiple iSCSI
> targets? 
> 
> As an aside, I now have a machine that I was planning to begin doing some
> testing and practicing with. Previous to my conversations with the folks at
> Red Hat, I was planning on doing some initial testing and config with this
> server before purchasing another 2-3 servers to build the hyperconverged
> cluster.
> 
> Sent with ProtonMail Secure Email.



signature.asc
Description: This is a digitally signed message part.
___
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/DFLKXVLMPN4ZTPVQJXDB33XZCABD3JR2/


[ovirt-users] Re: Ovirt fails to retrieve iSCSI targets during installation

2020-06-18 Thread Vojtech Juranek
> "port\": \"3260,3260\"

this looks strange. Did you specify port correctly?



signature.asc
Description: This is a digitally signed message part.
___
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/RHGFZ5J5HK7DBVD5NONCCJZFFMDTFD6Y/


[ovirt-users] Re: ovirt imageio problem...

2020-06-01 Thread Vojtech Juranek
> I tried the same to perform the upload ignoring the error, the ISO was in
> paused state,

have you imported the certificates? If you click on test connection button in 
upload dialogue, does it work?

If so, please file a bug and attach vdsm logs and imageio logs (/var/log/
ovirt-imageio/daemon.log) both from engine and host.

> I clicked to delete it. The result? iso loaded! How is it
> possible?

this looks like a bug, if you click on delete, it should delete the image

signature.asc
Description: This is a digitally signed message part.
___
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/FOWFP7QAQMBC6LA44VUCSRBU64OSAHI2/


[ovirt-users] Re: ovirt imageio problem...

2020-06-01 Thread Vojtech Juranek
On sobota 30. května 2020 19:59:40 CEST matteo fedeli wrote:
> Hi! I' installed CentOS 8 and ovirt package following this step:
> 
> systemctl enable --now cockpit.socket
> yum install https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
> yum module -y enable javapackages-tools
> yum module -y enable pki-deps
> yum module -y enable postgresql:12
> yum -y install glibc-locale-source glibc-langpack-en
> localedef -v -c -i en_US -f UTF-8 en_US.UTF-8
> yum update
> yum install ovirt-engine
> engine-setup (by keeping all default)
> 
> It's possible ovirt-imageio-proxy service is not installed? 

yes, imageio-proxy was replaced by imageio-daemon is not installed any more. 
Daemon now takes all proxy responsibilities.

signature.asc
Description: This is a digitally signed message part.
___
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/4HJDFJUHWSZXTGWGNHH3PDMK3MA65Z7O/


[ovirt-users] Re: Can anyone explain what gluster 4k support is?

2020-03-17 Thread Vojtech Juranek
> Is there performance improvements using larger block size?

yes, it *should* give you better performance

> On Tue, Mar 17, 2020 at 5:29 AM Vojtech Juranek  wrote:
> > On pondělí 16. března 2020 22:53:32 CET Strahil Nikolov wrote:
> > > On March 16, 2020 11:08:16 PM GMT+02:00, Vojtech Juranek
> > 
> >  wrote:
> > > >On středa 11. března 2020 21:13:13 CET Jayme wrote:
> > > >> I noticed Gluster 4k support mentioned in recent oVirt release notes.
> > > >
> > > >Can
> > > >
> > > >> anyone explain what this is about?
> > > >
> > > >before we supported only disks with block size 512 B. Now, we support
> > > >also
> > > >disks with 4 kB (aka 4k), for now only on Gluster SD. If you want to
> > > >learn more about
> > > >this feature, you can check slides [1] and I noticed that videos
> > > >recording of
> > > >Nir's talk he had on Fosdem is already available, so you can watch
> > > >whole
> > > >talk [2].
> > > >
> > > >Vojta
> > > >
> > > >[1]
> > 
> > https://docs.google.com/presentation/d/1ClLMZ4XAb8CPhYOw6mNpv0va5JWcAgpyFb
> > J
> > 
> > > >n-Bml_aY/ [2] https://video.fosdem.org/2020/H.1309/vai_ovirt_4k.webm
> > > 
> > > Can I switch off VDO's 512byte emulation ?
> > 
> > yes, now Gluster SD should work without 512 block size
> > emulation___
> > 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/LEG5DXY3A5HS
> > ABLDHQAO2M53G3SC4E2U/



signature.asc
Description: This is a digitally signed message part.
___
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/7M2RTTGZUWNRP2YOMPP6JVBY5JGYWC3R/


[ovirt-users] Re: Can anyone explain what gluster 4k support is?

2020-03-17 Thread Vojtech Juranek
On pondělí 16. března 2020 22:53:32 CET Strahil Nikolov wrote:
> On March 16, 2020 11:08:16 PM GMT+02:00, Vojtech Juranek 
 wrote:
> >On středa 11. března 2020 21:13:13 CET Jayme wrote:
> >> I noticed Gluster 4k support mentioned in recent oVirt release notes.
> >
> >Can
> >
> >> anyone explain what this is about?
> >
> >before we supported only disks with block size 512 B. Now, we support
> >also
> >disks with 4 kB (aka 4k), for now only on Gluster SD. If you want to
> >learn more about
> >this feature, you can check slides [1] and I noticed that videos
> >recording of
> >Nir's talk he had on Fosdem is already available, so you can watch
> >whole
> >talk [2].
> >
> >Vojta
> >
> >[1]
> >https://docs.google.com/presentation/d/1ClLMZ4XAb8CPhYOw6mNpv0va5JWcAgpyFbJ
> >n-Bml_aY/ [2] https://video.fosdem.org/2020/H.1309/vai_ovirt_4k.webm
> 
> Can I switch off VDO's 512byte emulation ?

yes, now Gluster SD should work without 512 block size emulation

signature.asc
Description: This is a digitally signed message part.
___
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/LEG5DXY3A5HSABLDHQAO2M53G3SC4E2U/


[ovirt-users] Re: Can anyone explain what gluster 4k support is?

2020-03-16 Thread Vojtech Juranek
On středa 11. března 2020 21:13:13 CET Jayme wrote:
> I noticed Gluster 4k support mentioned in recent oVirt release notes. Can
> anyone explain what this is about?

before we supported only disks with block size 512 B. Now, we support also 
disks with 4 kB (aka 4k), for now only on Gluster SD. If you want to learn more 
about
this feature, you can check slides [1] and I noticed that videos recording of
Nir's talk he had on Fosdem is already available, so you can watch whole
talk [2].

Vojta

[1] 
https://docs.google.com/presentation/d/1ClLMZ4XAb8CPhYOw6mNpv0va5JWcAgpyFbJn-Bml_aY/
[2] https://video.fosdem.org/2020/H.1309/vai_ovirt_4k.webm

signature.asc
Description: This is a digitally signed message part.
___
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/J5ZVKMKLCZP77CYUSPR53TITX5FDYQDH/


[ovirt-users] Re: oVirt 4.4.0 Alpha release refresh is now available for testing

2020-03-16 Thread Vojtech Juranek
On pondělí 16. března 2020 9:32:53 CET you wrote:
> On Mon, Mar 16, 2020 at 2:37 AM Sakari Poussa  wrote:
> > Hi,
> > 
> > The pre-release seems to be missing the ovirt-imageio-proxy.
> > 
> > Why is that? How can one import a (non-openstack glance) template to the
> > system? Both UI and ovirt.image-template ansible role seems to require
> > it.
> The project is working on getting rid of the duplications between the
> daemon and the proxy, and have a single program doing both functions.

correct, in the future we want only daemon module and remove proxy completely 
as it's not PY3 ready

> Not sure about current status, adding Vojtech.

WIP, we had some more urgent issue to work on, but I'm returning back to this 
now

> > Thanks, Sakari
> > 
> > On Mon, Mar 9, 2020 at 11:16 AM Sandro Bonazzola  
wrote:
> >> Il giorno dom 8 mar 2020 alle ore 08:49  ha scritto:
> >>> Hi
> >>> Is this also working on Centos Stream?
> >> 
> >> Yes, should work fine on CentOS Stream too.
> >> 
> >>> ___
> >>> Users mailing list -- users@ovirt.org
> >>> To unsubscribe send an email to users-le...@ovirt.org
> >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> >>> oVirt Code of Conduct:
> >>> https://www.ovirt.org/community/about/community-guidelines/ List
> >>> Archives:
> >>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/YVJ7AKI7F
> >>> GFUXQN2L4YXJT3N2YQXDAQR/>> 
> >> --
> >> 
> >> 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/7FHJY4HCHG
> >> ZNPEOBPNEFU663V5DQKBRR/> 
> > --
> > Sakari Poussa
> > 040 348 2970
> > ___
> > 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/R4PPALDFIHA
> > PRQVCCYL2ZHTZ52BDM7NG/



signature.asc
Description: This is a digitally signed message part.
___
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/MRKJZBMX2OMZFSTOFDBKJAKTIVIHLR3S/


[ovirt-users] Re: Do I need to use self hosted engine with a GlusterFs three node setup

2019-11-14 Thread Vojtech Juranek
> Hi Vojtech 
> 
> Thanks for the info, I have been looking for a method of creating the
> gluster cluster via cockpit on one of my three hosts but the only way I can
> see is via the hosted engine setup. Is it a case that we need to configure
> the hosts to use gluster storage with the cli commands prior to adding it
> to a pre-existing non hosted engine? 

you have to setup Gluster cluster first and then you can connect it as a 
storage domain via engine UI (select Gluster in drop down menu when creating 
new storage). Some documentation (with little bit outdated UI) can be found on 
[1], section "Attaching a Gluster Storage Volume as a Storage Domain".

Check Gluster documentation how to setup Gluster cluster. For quick test you 
can use scripts [2, 3, 4] - but please note these are not intended for 
production use (e.g. turned off firewall etc, also use VDO which you may not 
want to use).

HTH
Vojta

[1] 
https://www.ovirt.org/documentation/admin-guide/chap-Working_with_Gluster_Storage.html
[2] https://github.com/oVirt/vdsm/blob/master/contrib/deploy-gluster.sh
[3] https://github.com/oVirt/vdsm/blob/master/contrib/create-vdo-brick.sh
[4] https://github.com/oVirt/vdsm/blob/master/contrib/create-gluster-volume.sh


> Donagh
> ___
> 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/IIEY3Z3GDGH4V
> 6CPE6LUKYORH4SUVLDA/



signature.asc
Description: This is a digitally signed message part.
___
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/N4RX4ET3QRRJKWBYFT7K4LYTDYXIGHJ4/


[ovirt-users] Re: Do I need to use self hosted engine with a GlusterFs three node setup

2019-11-13 Thread Vojtech Juranek
Hi,

> Every piece of documentation I read regarding the setup of Gluster seems to
> suggest using at least one of the the nodes to host the engine. Is this a
> requirement of can I use an engine that is deployed on a VM on another
> server in the same network?

yes, this is definitely possible, you can create Gluster storage domain and 
use it no matter there your engine runs

> Any info would be much appreciated.
> ___
> 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/LN4CTUMQSTJX4
> EO7ZHHO3QAM2NR6USGS/



signature.asc
Description: This is a digitally signed message part.
___
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/N2STTIQ6AGHMHWRYRSXFLJQI5EX6W4YV/


[ovirt-users] Re: Does ovirt support sshfs?

2019-11-12 Thread Vojtech Juranek
Hi,

> Does ovirt support sshfs for mount locally accessible LUN's instead of NFS?

no, this is not supported.
Vojta

signature.asc
Description: This is a digitally signed message part.
___
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/ESBX3VNNBF6XQ7GSQB74QGSDVBSCX6U7/


[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

2019-09-30 Thread Vojtech Juranek
Hi,

> > Engine reports the block size reported by vdsm. Once we get the system
> > up with your 4k storage domain,
> > we can check that engine reports the right value and update it if needed.
> > I think what you should do is:
> > 
> > 1. Backup storage domain metadata
> > /path/to/domain/domain-uuid/dom_md
> > 
> > 2. Deactivate the storage domain (from engine)
> > 
> > 3. Edit the metadata file:
> > - change BLOCK_SIZE to 4096
> > - delete the checksum line
> > (_SHA_CKSUM=9dde06bbc9f2316efc141565738ff32037b1ff66)
> > 
> > 4. Activate the domain
> > 
> > With vdsm < 4.3.6, the domain should be active, ignoring the block size.
> > 
> > 5. Upgrade back to 4.3.6
> > 
> > The system should detect the block size and work normally.
> > 
> > 6. File ovirt bug for this issue
> > 
> > We need at least to document the way to fix the storage domain manually.
> > 
> > We also should consider checking storage domain metadata during
> > upgrades. I think it will be
> > a better experience if upgrade will fail and you have a working system
> > with older version.
> 
> I've tried this procedure and it has worked! Thanks!
> 
> If you would like me to file a bug, which component should I log it against?

for vdms. Please include all the logs and db dump as Nir mentioned in previous 
email (see bellow).
Thanks

> >> 
> >> Please share more data so we can understand the failure:
> >> 
> >> - complete vdsm log showing the failure to activate the domain
> >>   - with 4.3.6
> >>   - with 4.3.5 (after you downgraded
> >> - contents of
> >> /rhev/data-center/mnt/_/domain-uuid/dom_md/metadata
> >>   (assuming your local domain mount is /domaindir)
> >> - engine db dump
> >> 


signature.asc
Description: This is a digitally signed message part.
___
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/EDTQ3WUXGWEOA7O2LTXQNJXYP6RYQKIB/


[ovirt-users] Re: nfs

2019-09-09 Thread Vojtech Juranek
Hi,

> I`m trying to mount a nfs share.
> 
> 
> 
> if I manually mount it from ssh, I can access it without issues.
> 
> 
> 
> However when I do it from the web config, it keeps failing:

the error means sanlock cannot write a resource on our device. Please check 
you have proper permission on your NFS (has to be writeable by uid:guid 36:36) 
and eventually check /var/log/sanlock.log if there are any details

> 
> 
> Not sure how to solve that.
> 
> 
> 
> Thanks
> 
> 
> 
> Simon
> 
> 
> 
> 2019-09-09 09:08:47,601-0400 INFO  (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:47,610-0400 INFO  (jsonrpc/3) [vdsm.api] START
> repoStats(domains=[u'4f4828c2-8f78-4566-a69d-a37cd73446d4']) from=::1,42394,
> task_id=6c1eeef7-ff8c-4d0d-be85-ced03aae4bc2 (api:48)
> 
> 2019-09-09 09:08:47,610-0400 INFO  (jsonrpc/3) [vdsm.api] FINISH repoStats
> return={u'4f4828c2-8f78-4566-a69d-a37cd73446d4': {'code': 0, 'actual': True,
> 'version': 5, 'acquired': True, 'delay': '0.00101971', 'lastCheck': '0.4',
> 'valid': True}} from=::1,42394,
> task_id=6c1eeef7-ff8c-4d0d-be85-ced03aae4bc2 (api:54)
> 
> 2019-09-09 09:08:47,611-0400 INFO  (jsonrpc/3) [jsonrpc.JsonRpcServer] RPC
> call Host.getStorageRepoStats succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:47,839-0400 INFO  (jsonrpc/4) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:47,846-0400 INFO  (jsonrpc/2) [api.host] START
> getCapabilities() from=::1,42394 (api:48)
> 
> 2019-09-09 09:08:48,149-0400 INFO  (jsonrpc/2) [root] managedvolume not
> supported: Managed Volume Not Supported. Missing package os-brick.: ('Cannot
> import os_brick',) (caps:152)
> 
> 2019-09-09 09:08:49,212-0400 INFO  (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.01 seconds (__init__:312)
> 
> 2019-09-09 09:08:49,263-0400 INFO  (jsonrpc/2) [root]
> /usr/libexec/vdsm/hooks/after_get_caps/50_openstacknet: rc=0 err=
> (hooks:114)
> 
> 2019-09-09 09:08:49,497-0400 INFO  (jsonrpc/0) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:49,657-0400 INFO  (jsonrpc/1) [jsonrpc.JsonRpcServer] RPC
> call Host.ping2 succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:49,665-0400 INFO  (jsonrpc/7) [vdsm.api] START
> repoStats(domains=[u'4f4828c2-8f78-4566-a69d-a37cd73446d4']) from=::1,42394,
> task_id=14b596bf-bc1c-412b-b1fc-8d53f17d88f7 (api:48)
> 
> 2019-09-09 09:08:49,666-0400 INFO  (jsonrpc/7) [vdsm.api] FINISH repoStats
> return={u'4f4828c2-8f78-4566-a69d-a37cd73446d4': {'code': 0, 'actual': True,
> 'version': 5, 'acquired': True, 'delay': '0.00101971', 'lastCheck': '2.4',
> 'valid': True}} from=::1,42394,
> task_id=14b596bf-bc1c-412b-b1fc-8d53f17d88f7 (api:54)
> 
> 2019-09-09 09:08:49,667-0400 INFO  (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC
> call Host.getStorageRepoStats succeeded in 0.00 seconds (__init__:312)
> 
> 2019-09-09 09:08:49,800-0400 INFO  (jsonrpc/2) [root]
> /usr/libexec/vdsm/hooks/after_get_caps/openstacknet_utils.py: rc=0 err=
> (hooks:114)
> 
> 2019-09-09 09:08:50,464-0400 INFO  (jsonrpc/2) [root]
> /usr/libexec/vdsm/hooks/after_get_caps/ovirt_provider_ovn_hook: rc=0 err=
> (hooks:114)
> 
> 2019-09-09 09:08:50,467-0400 INFO  (jsonrpc/2) [api.host] FINISH
> getCapabilities return={'status': {'message': 'Done', 'code': 0}, 'info':
> {u'HBAInventory': {u'iSCSI': [{u'InitiatorName':
> u'iqn.1994-05.com.redhat:d8c85fc0ab85'}], u'FC': []}, u'packages2':
> {u'kernel': {u'release': u'957.27.2.el7.x86_64', u'version': u'3.10.0'},
> u'spice-server': {u'release': u'6.el7_6.1', u'version': u'0.14.0'},
> u'librbd1': {u'release': u'4.el7', u'version': u'10.2.5'}, u'vdsm':
> {u'release': u'1.el7', u'version': u'4.30.24'}, u'qemu-kvm': {u'release':
> u'18.el7_6.7.1', u'version': u'2.12.0'}, u'openvswitch': {u'release':
> u'4.el7', u'version': u'2.11.0'}, u'libvirt': {u'release': u'10.el7_6.12',
> u'version': u'4.5.0'}, u'ovirt-hosted-engine-ha': {u'release': u'1.el7',
> u'version': u'2.3.3'}, u'qemu-img': {u'release': u'18.el7_6.7.1',
> u'version': u'2.12.0'}, u'mom': {u'release': u'1.el7.centos', u'version':
> u'0.5.12'}, u'glusterfs-cli': {u'release': u'1.el7', u'version': u'6.5'}},
> u'numaNodeDistance': {u'1': [20, 10], u'0': [10, 20]}, u'cpuModel':
> u'Intel(R) Xeon(R) CPU E5-2640 v2 @ 2.00GHz', u'nestedVirtualization':
> False, u'liveMerge': u'true', u'hooks': {u'before_vm_start':
> {u'50_hostedengine': {u'md5': u'95c810cdcfe4195302a59574a5148289'},
> u'50_vhostmd': {u'md5': u'9206bc390bcbf208b06a8e899581be2d'}},
> u'after_network_setup': {u'30_ethtool_options': {u'md5':
> u'ce1fbad7aa0389e3b06231219140bf0d'}}, u'after_vm_destroy':
> {u'delete_vhostuserclient_hook': {u'md5':
> u'c2f279cc9483a3f842f6c29df13994c1'}, u'50_vhostmd': {u'md5':
> u'bdf4802c0521cf1bae08f2b90a9559cf'}}, u'after_vm_start':
> {u'openstacknet_utils.py': {u'md5': u'1ed38ddf30f8a9c7574589e77e2c0b1f'},

[ovirt-users] Re: Storage domain format version info

2019-07-09 Thread Vojtech Juranek
Hi,

> part of updating a DC from 4.2 to 4.3 consists in updating format of data
> storage domains from V4 to V5.
> Questions:
> - where can I find list of differences between V4 and V5? And in general
> between previous ones?

I'm afraid there's no design doc for it. Here's list of changes:

* domain metadata
  * added: alignment, block_size
  * removed: logblksize, phyblksize

* volume metadata
  * added: cap (replacement for size, capacity is size in bytes, while size 
was in mutiples of block size (512B))
  * removed mtime, pool_uuid, size

If you want more details about the changes, you can check slides [1]

> - can I force only a particular storage domain to remain in V4 while having
> the other ones upgraded to V5, for any reason? Or the reverse: update only
> one of the defined domains?

I don't think this is possible. 

HTH
Vojta

[1] https://github.com/vjuranek/presentations/blob/master/internal/oVirt/
storage_v5/storage_v5.pdf

signature.asc
Description: This is a digitally signed message part.
___
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/2JF5ODAW2LBPPDWHM5VU4FHPSDKLOMVQ/


[ovirt-users] Re: 4K Sector Hard drive Support - oVirt 4.3.4

2019-06-12 Thread Vojtech Juranek
Hi,

> Does anyone have any idea if/when 4K Sector drives will be supported? 
> 
> My understanding is that this was one of the features for 4.3.4

I'm sorry, we didn't make it for 4.3.4 and still working on it. You can follow 
BZ #1592916 [1] to track the progress, but I'd not promise any hard deadlines 
when it's finished.

Thanks
Vojta

[1] https://bugzilla.redhat.com/1592916

signature.asc
Description: This is a digitally signed message part.
___
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/UF6C6HGNNKWS2IITS65P3J6K2VJTFSDJ/


[ovirt-users] Re: ovirt - in docker

2018-10-15 Thread Vojtech Juranek
On neděle 14. října 2018 0:44:22 CEST Vojtech Juranek wrote:
> On pátek 12. října 2018 12:49:03 CEST ReSearchIT Eng wrote:
> > We mainly need a good answers file, while entrypoint might be kept from
> > 4.1, right?
> 
> I looked on it and there are some smaller changes needed. I'll send an
> update soon

patch for oVirt 4.2 for ovirt-container-engine is in gerrit [1]. It works with 
published rmohr/ovirt-postgres (postgres 9.2), but as recommended DB for oVirt 
4.2 is postgres 9.5, you may download patch for 9.5 [2] and build it locally 
(from previous answers it looks like project is not maintained, so review may 
take some time:-)
Let ma know if you spot any issues.
Thanks
Vojta

[1] https://gerrit.ovirt.org/94916
[2] https://github.com/rmohr/docker-ovirt-postgres/pull/3

signature.asc
Description: This is a digitally signed message part.
___
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/SZSNCPHX5DPMLQ247SVY4EMJFP7EUQTV/


[ovirt-users] Re: ovirt - in docker

2018-10-13 Thread Vojtech Juranek
On pátek 12. října 2018 12:49:03 CEST ReSearchIT Eng wrote:
> We mainly need a good answers file, while entrypoint might be kept from
> 4.1, right?

I looked on it and there are some smaller changes needed. I'll send an update 
soon


signature.asc
Description: This is a digitally signed message part.
___
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/J65APKCQW5CSIED2HH3NUHEYMAW4LG3B/


[ovirt-users] Re: Resizing ovirt-engine disk

2018-10-12 Thread Vojtech Juranek
> Do you know if this patch will be backported in 4.2 or it will land only in
> the next major release ?

Unfortunately I don't know (even don't know if the patch will be accepted:-). 
I'm very new to oVirt so don't know yet what the rules for backporting are 
etc. Hopefully someone else on the list can answer it.

Cheers
Vojta



signature.asc
Description: This is a digitally signed message part.
___
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/NYMDHEP5CUTU4UOUWQZ26G3MQQAN7MSJ/


[ovirt-users] Re: Resizing ovirt-engine disk

2018-10-11 Thread Vojtech Juranek
Hi,

> Can we grow the ovirt-engine disk like any other managed VM ?

I assume you mean hosted engine. No, unfortunately this is not possible right 
now. Today I proposed a patch [1] which should fix it.
 
> And if not, how can we grow the ovirt-engine disk out of standard
> installation procedure ?

it's possible, but includes calling vdsm client directly and editing the 
database, so I'd recommend to avoid it.

Cheers
Vojta

[1] https://gerrit.ovirt.org/94855



signature.asc
Description: This is a digitally signed message part.
___
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/GR7MTEEE3ZRJGKUVYQFAJPJTWPQGGJX7/