Re: Install fresh 4.3 fails with mounting shared storage
by Vrgotic, Marko
Roy,
It came down to manually mounting ovirt-storage domains and executing chown command.
Still, I took you advice and did NFS3-only and NFS4-only tests.
Here are the results:
Test1: Protocol NFS3 / ExportPolicy NFS3 with Default (allow all)
* ERROR:
[ INFO ] TASK [ovirt.hosted_engine_setup : Add NFS storage domain]
[ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[General Exception]". HTTP response code is 400.
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[General Exception]\". HTTP response code is 400."}
* Volume is mounted as:
172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs (rw,relatime,vers=3,rsize=65536,wsize=655
36,namlen=255,soft,nolock,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,mountaddr=172.17.28.5,mountvers=3,mountport=635,mountproto=udp,loc
al_lock=all,addr=172.17.28.5)
* ls -la /rhev/data-center/mnt:
[root@ovirt-hv-01 mnt]# ls -la
total 4
drwxr-xr-x. 3 vdsm kvm 48 May 31 07:55 .
drwxr-xr-x. 3 vdsm kvm 17 May 31 07:50 ..
drwxrwxr-x. 2 root root 4096 May 29 10:12 172.17.28.5:_ovirt__hosted__engine
* change ownership of mounted volume to vdsm:kvm
* umount
Reran deployment script and deployment completed successfully.
Test2: Protocol NFS4 / ExportPolicy NFS with Default (allow all)
Deployment went through without single issue.
Seems that even though vddm:vm group with an ID 36 are created and added to NetApp volume, they are not applicable.
It still required to mount manually, execute “chown -R vdsm:kvm <mounted_location>”, amount and rerun the deployment script or rather reenter storage information for deployment to proceed.
Adding next storage domain, fro example for all other test VMs, will again fail from UI, unless the manual mount and chow are executed previously.
Then I tried just mount second storage domain, and it failed reporting permission issue (which it was). After executing manual mount actions, adding domain from UI worked flawlessly.
Output of mount:
172.17.28.5:/ovirt_production on /rhev/data-center/mnt/172.17.28.5:_ovirt__production type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,
nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.12,local_lock=none,addr=172.17.28.5)
172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=25
5,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.12,local_lock=none,addr=172.17.28.5)
Test3: Protocol NFS4 / ExportPolicy NFS with limited IP group access
In progress, but I have high hopes now.
Will keep you posted.
BTW.I was not able to find location in NetApp Volume where squashing is being defined, so I can not answer that one yet.
Thank you.
Kind regards,
Marko Vrgotic
ActiveVideo
From: "Morris, Roy" <roy.morris(a)ventura.org>
Date: Thursday, 30 May 2019 at 21:29
To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>, "users(a)ovirt.org" <users(a)ovirt.org>
Cc: "Stojchev, Darko" <D.Stojchev(a)activevideo.com>
Subject: RE: Install fresh 4.3 fails with mounting shared storage
Marko,
No problem, here are some other things to check as well.
NetApp is weird about allowing changes done to the root directory of a share. I would recommend creating a folder on the NetApp share like “rhevstor” or something so that you can chown that folder and mount the folder for the storage domain. I never had much luck mounting and using the root level of the NetApp NFS share. I also have in my notes that I set “sec=sys” as a property of my NetApp data domain which wouldn’t allow me to mount it until I input it into the RHEV manager. However, you aren’t at a point of having the RHEV manager up and running so I’m not sure how much use this would be at the moment.
#mount -o sec=sys 172.17.28.5:/rhevstor /mnt/temp
NFS share will fail if it isn’t accessible from all hosts, so make sure to go into each host to run
#showmount -e 172.17.28.5
The ownership of the NFS share needs to be owned by vdsm:kvm. To do this, you have to manually mount the NFS share to one of the hosts temporarily then run the following command to get ownership settings setup.
#mkdir /mnt/temp
#mount -o sec=sys 172.17.28.5:/rhevstor /mnt/temp
#chown 36:36 /mnt/temp
#umount /mnt/temp
Then try and run the install again. If it fails, disable NFSv3 and run again to see if it is related to NFSv4 security settings.
Best regards,
Roy Morris
From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com>
Sent: Thursday, May 30, 2019 12:07 PM
To: Morris, Roy <roy.morris(a)ventura.org>; users(a)ovirt.org
Cc: Stojchev, Darko <D.Stojchev(a)activevideo.com>
Subject: [External] Re: Install fresh 4.3 fails with mounting shared storage
Hi Roy,
I will run all those tests tomorrow morning (Amsterdam TimeZone) and reply back with results.
Regarding NetApp documentation you mentioned below, I assume it should be enough to just “google” for it.
Thank you very much for jumping in, we really appreciate it.
Kind regards,
Marko Vrgotic
From: "Morris, Roy" <roy.morris(a)ventura.org<mailto:roy.morris@ventura.org>>
Date: Thursday, 30 May 2019 at 18:46
To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>, "users(a)ovirt.org<mailto:users@ovirt.org>" <users(a)ovirt.org<mailto:users@ovirt.org>>
Cc: "users-request(a)ovirt.org<mailto:users-request@ovirt.org>" <users-request(a)ovirt.org<mailto:users-request@ovirt.org>>, "Stojchev, Darko" <D.Stojchev(a)activevideo.com<mailto:D.Stojchev@activevideo.com>>
Subject: RE: Install fresh 4.3 fails with mounting shared storage
Marko,
Can you try disabling NFSv4 on the NetApp side for testing and rerun the installer? I don’t advise leaving it at NFSv3 but just for testing we can try it out.
Also, there is some documentation on NetApp support regarding manually mounting the NFS share to change permissions then unmount. It has to be done once but after that the mounting should be fine.
Do you have root squash set on NetApp?
Best regards,
Roy Morris
GSA Virtualization Systems Analyst
County of Ventura
(805) 654-3625
(805) 603-9403
[cid:7c03dd9d67a9cfb78447b56087323d91a66d7c29.camel@ventura.org]
From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>
Sent: Thursday, May 30, 2019 1:34 AM
To: Morris, Roy <roy.morris(a)ventura.org<mailto:roy.morris@ventura.org>>; users(a)ovirt.org<mailto:users@ovirt.org>
Cc: users-request(a)ovirt.org<mailto:users-request@ovirt.org>; Stojchev, Darko <D.Stojchev(a)activevideo.com<mailto:D.Stojchev@activevideo.com>>
Subject: [External] Re: Install fresh 4.3 fails with mounting shared storage
Hi Roy,
Sure, here is the output:
Last login: Wed May 29 17:25:30 2019 from ovirt-engine.avinity.tv
[root@ovirt-hv-03 ~]# showmount -e 172.17.28.5
Export list for 172.17.28.5:
/ (everyone)
[root@ovirt-hv-03 ~]# ls -la /rhev/data-center/mnt/
total 0
drwxr-xr-x. 2 vdsm kvm 6 May 29 17:14 .
drwxr-xr-x. 3 vdsm kvm 17 May 29 17:11 ..
[root@ovirt-hv-03 ~]#
In addition, if it helps, here is the list of shares/mount points from Netapp side, behind the 172.17.28.5 IP:
[cid:image003.png@01D516CC.8548AE10]
Kind regards
Marko Vrgotic
From: "Morris, Roy" <roy.morris(a)ventura.org<mailto:roy.morris@ventura.org>>
Date: Thursday, 30 May 2019 at 00:57
To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>, "users(a)ovirt.org<mailto:users@ovirt.org>" <users(a)ovirt.org<mailto:users@ovirt.org>>
Cc: "users-request(a)ovirt.org<mailto:users-request@ovirt.org>" <users-request(a)ovirt.org<mailto:users-request@ovirt.org>>
Subject: RE: Install fresh 4.3 fails with mounting shared storage
Marko,
Can you run the following commands and let us know the results.
showmount -e 172.17.28.5
ls -la /rhev/data-center/mnt/
Best regards,
Roy Morris
From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>
Sent: Wednesday, May 29, 2019 4:07 AM
To: users(a)ovirt.org<mailto:users@ovirt.org>
Cc: users-request(a)ovirt.org<mailto:users-request@ovirt.org>
Subject: [External] [ovirt-users] Install fresh 4.3 fails with mounting shared storage
CAUTION: This email contains links. If it looks suspicious or is not expected, DO NOT click and immediately forward to Spam.Manager(a)ventura.org<mailto:Spam.Manager@ventura.org>.
Dear oVIrt,
We are trying to deploy new setup with Hosted-Engine , oVirt version 4.3.
Volume is on the Netapp, protocol NFS v4.
Upon populating shared storage information and path:
Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: nfs
Please specify the nfs version you would like to use (auto, v3, v4, v4_1)[auto]: auto
Please specify the full shared storage connection path to use (example: host:/path): 172.17.28.5:/ovirt_hosted_engine
Following is displayed on the screen:
[ INFO ] Creating Storage Domain
[ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Check local VM dir stat]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Enforce local VM dir existence]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host facts]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster ID]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster facts]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter facts]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter ID]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter name]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Add NFS storage domain]
[ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[General Exception]". HTTP response code is 400.
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[General Exception]\". HTTP response code is 400."}
Even with this error – storage gets mounted on the Host:
172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.11,local_lock=none,addr=172.17.28.5)
But playbook execution fails and we can not proceed with install.
Please advise.
Kindly awaiting your reply.
Marko Vrgotic
4 years, 11 months
oVirt Node Blocks VirtViewer/SPICE connections (Did Not Auto-Configure Firewall?)
by Zachary Winter
I am unable to connect via SPICE (Windows VirtViewer) to VM's running on
my compute node. It appears the node did not auto-configure the
firewall because the .vv files appear to point to the correct IP address
and common ports. Is there a way to re-run/re-execute the firewall
auto-configuration now that the node has already been installed?
If not, does anyone happen to have firewall-cmd commands handy that I
can run to resolve this quickly? Which ports need to be opened?
The specs on the node are as follows:
OS Version:
RHEL - 7 - 6.1810.2.el7.centos
OS Description:
oVirt Node 4.3.3.1
Kernel Version:
3.10.0 - 957.10.1.el7.x86_64
KVM Version:
2.12.0 - 18.el7_6.3.1
LIBVIRT Version:
libvirt-4.5.0-10.el7_6.6
VDSM Version:
vdsm-4.30.13-1.el7
SPICE Version:
0.14.0 - 6.el7_6.1
GlusterFS Version:
glusterfs-5.5-1.el7
CEPH Version:
librbd1-10.2.5-4.el7
Open vSwitch Version:
openvswitch-2.10.1-3.el7
Kernel Features:
PTI: 1, IBRS: 0, RETP: 1, SSBD: 3
VNC Encryption:
Enabled
4 years, 11 months
oVirtSimpleBackup
by Tommaso - Shellrent
Hi to all.
I was looking for install oVirtSimpleBackup, but now i see:
" no longer use oVirt, so I wont be furthering this project. oVirt is
>>Awesome<< however, I decided to move all of my VMs into a large
managed datacentre that uses vmware.
I want to thank the oVirt community and all of the people over on IRC
for thier awesome support.
Feel free to use this code for your own ovirt backups or future oVirt
backup software."
Anyone kown if the projec will be mainted? There is an alternative
projet to look for?
--
Shellrent Logo
*Tommaso De Marchi*
COO Chief Operating Officer - Shellrent S.r.l.
Tel. 0444321155 <tel:+390444321155> | Fax 04441492177
Via dell'Edilizia, 19 - 36100 Vicenza
4 years, 11 months
4.3 hosted-engine setup & yum-utils RPM installation
by Simon Coter
Hi,
is there any particular reason to get “yum-utils” (and its dependency) RPM installed during the hosted-engine deployment ?
I mean, why don’t we get yum-utils RPM part of the hosted-engine image ?
This “yum” process, executed during the deployment, could fail (or wait forever) if the host/engine is behind a proxy — while trying to install the RPMs.
I see two options:
get all the required RPMs part of the hosted-engine image
add the option to supply a proxy for yum during the hosted-engine setup
Could this be a request for enhancement ?
Thanks
Simon
4 years, 11 months
Re: Install fresh 4.3 fails with mounting shared storage
by Vrgotic, Marko
Hi Roy,
I will run all those tests tomorrow morning (Amsterdam TimeZone) and reply back with results.
Regarding NetApp documentation you mentioned below, I assume it should be enough to just “google” for it.
Thank you very much for jumping in, we really appreciate it.
Kind regards,
Marko Vrgotic
From: "Morris, Roy" <roy.morris(a)ventura.org>
Date: Thursday, 30 May 2019 at 18:46
To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>, "users(a)ovirt.org" <users(a)ovirt.org>
Cc: "users-request(a)ovirt.org" <users-request(a)ovirt.org>, "Stojchev, Darko" <D.Stojchev(a)activevideo.com>
Subject: RE: Install fresh 4.3 fails with mounting shared storage
Marko,
Can you try disabling NFSv4 on the NetApp side for testing and rerun the installer? I don’t advise leaving it at NFSv3 but just for testing we can try it out.
Also, there is some documentation on NetApp support regarding manually mounting the NFS share to change permissions then unmount. It has to be done once but after that the mounting should be fine.
Do you have root squash set on NetApp?
Best regards,
Roy Morris
GSA Virtualization Systems Analyst
County of Ventura
(805) 654-3625
(805) 603-9403
[cid:7c03dd9d67a9cfb78447b56087323d91a66d7c29.camel@ventura.org]
From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com>
Sent: Thursday, May 30, 2019 1:34 AM
To: Morris, Roy <roy.morris(a)ventura.org>; users(a)ovirt.org
Cc: users-request(a)ovirt.org; Stojchev, Darko <D.Stojchev(a)activevideo.com>
Subject: [External] Re: Install fresh 4.3 fails with mounting shared storage
Hi Roy,
Sure, here is the output:
Last login: Wed May 29 17:25:30 2019 from ovirt-engine.avinity.tv
[root@ovirt-hv-03 ~]# showmount -e 172.17.28.5
Export list for 172.17.28.5:
/ (everyone)
[root@ovirt-hv-03 ~]# ls -la /rhev/data-center/mnt/
total 0
drwxr-xr-x. 2 vdsm kvm 6 May 29 17:14 .
drwxr-xr-x. 3 vdsm kvm 17 May 29 17:11 ..
[root@ovirt-hv-03 ~]#
In addition, if it helps, here is the list of shares/mount points from Netapp side, behind the 172.17.28.5 IP:
[cid:image003.png@01D516CC.8548AE10]
Kind regards
Marko Vrgotic
From: "Morris, Roy" <roy.morris(a)ventura.org<mailto:roy.morris@ventura.org>>
Date: Thursday, 30 May 2019 at 00:57
To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>, "users(a)ovirt.org<mailto:users@ovirt.org>" <users(a)ovirt.org<mailto:users@ovirt.org>>
Cc: "users-request(a)ovirt.org<mailto:users-request@ovirt.org>" <users-request(a)ovirt.org<mailto:users-request@ovirt.org>>
Subject: RE: Install fresh 4.3 fails with mounting shared storage
Marko,
Can you run the following commands and let us know the results.
showmount -e 172.17.28.5
ls -la /rhev/data-center/mnt/
Best regards,
Roy Morris
From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com<mailto:M.Vrgotic@activevideo.com>>
Sent: Wednesday, May 29, 2019 4:07 AM
To: users(a)ovirt.org<mailto:users@ovirt.org>
Cc: users-request(a)ovirt.org<mailto:users-request@ovirt.org>
Subject: [External] [ovirt-users] Install fresh 4.3 fails with mounting shared storage
CAUTION: This email contains links. If it looks suspicious or is not expected, DO NOT click and immediately forward to Spam.Manager(a)ventura.org<mailto:Spam.Manager@ventura.org>.
Dear oVIrt,
We are trying to deploy new setup with Hosted-Engine , oVirt version 4.3.
Volume is on the Netapp, protocol NFS v4.
Upon populating shared storage information and path:
Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: nfs
Please specify the nfs version you would like to use (auto, v3, v4, v4_1)[auto]: auto
Please specify the full shared storage connection path to use (example: host:/path): 172.17.28.5:/ovirt_hosted_engine
Following is displayed on the screen:
[ INFO ] Creating Storage Domain
[ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Check local VM dir stat]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Enforce local VM dir existence]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host facts]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster ID]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster facts]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter facts]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter ID]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter name]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Add NFS storage domain]
[ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[General Exception]". HTTP response code is 400.
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[General Exception]\". HTTP response code is 400."}
Even with this error – storage gets mounted on the Host:
172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.11,local_lock=none,addr=172.17.28.5)
But playbook execution fails and we can not proceed with install.
Please advise.
Kindly awaiting your reply.
Marko Vrgotic
4 years, 11 months
Re: Install fresh 4.3 fails with mounting shared storage
by Vrgotic, Marko
Hi Roy,
Sure, here is the output:
Last login: Wed May 29 17:25:30 2019 from ovirt-engine.avinity.tv
[root@ovirt-hv-03 ~]# showmount -e 172.17.28.5
Export list for 172.17.28.5:
/ (everyone)
[root@ovirt-hv-03 ~]# ls -la /rhev/data-center/mnt/
total 0
drwxr-xr-x. 2 vdsm kvm 6 May 29 17:14 .
drwxr-xr-x. 3 vdsm kvm 17 May 29 17:11 ..
[root@ovirt-hv-03 ~]#
In addition, if it helps, here is the list of shares/mount points from Netapp side, behind the 172.17.28.5 IP:
[cid:image001.png@01D516D3.205660E0]
Kind regards
Marko Vrgotic
From: "Morris, Roy" <roy.morris(a)ventura.org>
Date: Thursday, 30 May 2019 at 00:57
To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>, "users(a)ovirt.org" <users(a)ovirt.org>
Cc: "users-request(a)ovirt.org" <users-request(a)ovirt.org>
Subject: RE: Install fresh 4.3 fails with mounting shared storage
Marko,
Can you run the following commands and let us know the results.
showmount -e 172.17.28.5
ls -la /rhev/data-center/mnt/
Best regards,
Roy Morris
From: Vrgotic, Marko <M.Vrgotic(a)activevideo.com>
Sent: Wednesday, May 29, 2019 4:07 AM
To: users(a)ovirt.org
Cc: users-request(a)ovirt.org
Subject: [External] [ovirt-users] Install fresh 4.3 fails with mounting shared storage
CAUTION: This email contains links. If it looks suspicious or is not expected, DO NOT click and immediately forward to Spam.Manager(a)ventura.org<mailto:Spam.Manager@ventura.org>.
Dear oVIrt,
We are trying to deploy new setup with Hosted-Engine , oVirt version 4.3.
Volume is on the Netapp, protocol NFS v4.
Upon populating shared storage information and path:
Please specify the storage you would like to use (glusterfs, iscsi, fc, nfs)[nfs]: nfs
Please specify the nfs version you would like to use (auto, v3, v4, v4_1)[auto]: auto
Please specify the full shared storage connection path to use (example: host:/path): 172.17.28.5:/ovirt_hosted_engine
Following is displayed on the screen:
[ INFO ] Creating Storage Domain
[ INFO ] TASK [ovirt.hosted_engine_setup : Execute just a specific set of steps]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Force facts gathering]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Check local VM dir stat]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Enforce local VM dir existence]
[ INFO ] skipping: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : include_tasks]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Obtain SSO token using username/password credentials]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch host facts]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster ID]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch cluster facts]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter facts]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter ID]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Fetch Datacenter name]
[ INFO ] ok: [localhost]
[ INFO ] TASK [ovirt.hosted_engine_setup : Add NFS storage domain]
[ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[General Exception]". HTTP response code is 400.
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault detail is \"[General Exception]\". HTTP response code is 400."}
Even with this error – storage gets mounted on the Host:
172.17.28.5:/ovirt_hosted_engine on /rhev/data-center/mnt/172.17.28.5:_ovirt__hosted__engine type nfs4 (rw,relatime,vers=4.0,rsize=65536,wsize=65536,namlen=255,soft,nosharecache,proto=tcp,timeo=600,retrans=6,sec=sys,clientaddr=172.17.28.11,local_lock=none,addr=172.17.28.5)
But playbook execution fails and we can not proceed with install.
Please advise.
Kindly awaiting your reply.
Marko Vrgotic
4 years, 11 months
Re: change he vm memoy size
by Strahil
Actually, you need to untar the OVF from the shared storage and check the configuration from the tar.
Just keep it like that (running ) and tomorrow power down and then up the HostedEngine.
Best Regards,
Strahil NikolovOn May 30, 2019 12:06, "Valkov, Alexey" <Valkov.Alexey(a)knauf.ru> wrote:
>
> Hello, Strahil. I've just tried with engine-config -s OvfUpdateIntervalInMinutes=1 systemctl restart ovirt-engine.service After that, i changed Memory Size in manager UI. And waited about 30 minutes. Then checked memSize in /var/run/ovirt-hosted-engine-ha/vm.conf (which if i right understand syncronized with ovf every minute) and saw memSize have not been changed. And Memory Size property (in manager UI) also remains initial. Thus i think that ovf dont changes. I return OvfUpdateIntervalInMinutes=60 and will wait till tomorrow, may be the setting will be magically aplyed.
>
> --
> Best regards
> Alexey
>
>> Hi Alexey,
>> How much time did you check before rebooting.
>> I have noticed ,that despite the default OVF update interval of 1 hour, it takes 5-6 hours for the engine to update the OVF.
>>
>> Best Regards,
>> Strahil Nikolov
>>
>> On May 30, 2019 10:30, "Valkov, Alexey" <Valkov.Alexey(a)knauf.ru> wrote:
>>>
>>> I try to increase memory of HE VM (oVirt 4.2.8). If i do it from manager UI, i see that hot plug works - new memory devices appear and corresponding memory increase appeares inside engine guest. But 'Memory Size' property of hosted engine (in manager UI) don't reflect that new amount of memory. Also after reboot of engine vm, memory size changes back to initial value. Is it possible to change memory size of HE vm ( as far as i know the settings stored in ovf on HE domain) and how i can make this change to be persistent.
>>>
>>> --
>>> Best regards
>>> Alexey
>>>
>> _______________________________________________
>>
>> Users mailing list --
>>
>> users(a)ovirt.org
>>
>>
>> To unsubscribe send an email to
>>
>> users-leave(a)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/IKID3B2TH3V...
>>
>>
4 years, 11 months
[ANN] oVirt 4.3.4 Third Release Candidate is now available
by Sandro Bonazzola
The oVirt Project is pleased to announce the availability of the oVirt
4.3.4 Third Release Candidate, as of May 30th, 2019.
This update is a release candidate of the fourth in a series of
stabilization updates to the 4.3 series.
This is pre-release software. This pre-release should not to be used
inproduction.
This release is available now on x86_64 architecture for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:
* Red Hat Enterprise Linux 7.6 or later
* CentOS Linux (or similar) 7.6 or later
* oVirt Node 4.3 (available for x86_64 only)
Experimental tech preview for x86_64 and s390x architectures for Fedora 28
is also included.
See the release notes [1] for installation / upgrade instructions and a
list of new features and bugs fixed.
Notes:
- oVirt Appliance is already available
- oVirt Node is already available[2]
Additional Resources:
* Read more about the oVirt 4.3.4 release highlights:
http://www.ovirt.org/release/4.3.4/
* Get more oVirt Project updates on Twitter: https://twitter.com/ovirt
* Check out the latest project news on the oVirt blog:
http://www.ovirt.org/blog/
[1] http://www.ovirt.org/release/4.3.4/
[2] http://resources.ovirt.org/pub/ovirt-4.3-pre/iso/
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>
<https://redhat.com/summit>
4 years, 11 months
oVirt 3.6 SLA and QoS algorithm
by m.isaiev＠kwebbl.com
Hello!
We are using oVirt 3.6 in our infrastructure and storage QoS in passive state (they are configured but not applie) for some of the servers. Last time we needed to activate QoS on high load servers and it caused storage load decrease. And this situation has raised some questions:
1. What happened to overlimit storage traffic, when QoS applying on high load virtual machine:
a) All over traffic is pulling into some queue, where all disk transactions can be successfully finished with QoS throughput?
b) All over-limitation data is dropped and opened transactions failed?
c) All active transactions finishes on speed beyond QoS, but all new transactions immediately start to work based on configured limits?
2. How QoS mechanism actually works? Does it use some oVirt specific functions or it uses some system features to limit storage, network or CPU usage? If system one, then the QoS are provided by libvirt (using virsh or directly) or system kernel options and which one?
Thanks in advance!
4 years, 11 months
