[ovirt-users] Re: VM memory decrease

2020-11-26 Thread Erez Zarum
I think i'm answering my self :)
I noticed "mom.Controllers.Balloon - INFO - Ballooning guest" message in the 
mom.log.
So best option to remove this and keep High Performance is disabling Memory 
Ballooning.
___
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/VLNN72BEK6IAJGOW5BDKAPJNXZRCJYYV/


[ovirt-users] VM memory decrease

2020-11-26 Thread Erez Zarum
I have an 8 node cluster running oVirt 4.4.2, i have noticed lately that some 
VMs started to have their memory decrease.
For example a VM that was configured to have 32GB memory without any notice 
were had their memory decrease to about 4GB, if i restart the VM the VM comes 
up with the correct memory but shortly after it decreases again.

The VM configuration has:
Memory Size: 32768 MB
Maximum Memory: 131072 MB
Physical Memory Guaranteed: 1024 MB

It's worth mentioning that those are Linux VMs which are provisioned through 
Foreman, Windows VMs are not provisioned from Foreman and their "Memory Size" 
is identical to "Physical Memory Guaranteed", so far i have not observed a 
Windows VM with this behaviour, though there might be some that i haven't 
caught.
Is there a possibility the cause for this issue is by having "Physical Memory 
Guaranteed" set to this low?


___
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/6I2P5ODKFF7UZN2HGIA526IRDCDH5DXP/


[ovirt-users] Re: multiple new networks

2020-10-21 Thread Erez Zarum
I'm not sure if 4.3 supports it, but in 4.4 you can create a network LABEL and 
attach that LABEL to the host interface, later you can add a new network and 
LABEL that network, it will be automatically added to the host/interface where 
that LABEL is attached.
Example:
Create a LABEL named: MYLABEL
Attach "MYLABEL" LABEL to a Host interface, let's say bond0.
You will now have "MYLABEL" attached to bond0.
Create a new network, fill all the settings (VM Network, VLAN tag, etc..) but 
you will also be able to choose to add a LABEL, add "MYLABEL".
After doing this the network will be automatically created on bond0.

You can automate the task of adding "MYLABEL" to bond0 on all the hosts using 
the API or manually just once.
___
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/WPJ4ETWB46N7G7WI5US423DZUYWYKHTE/


[ovirt-users] Re: Upgrade oVirt Host from 4.4.0 to 4.4.2 fails

2020-10-02 Thread Erez Zarum
Seems the problem, atleast part of it (because still, it doesn't get to the 
part of creating the imgbase layer) is related to the /tmp/yum_updates file.
/usr/share/ovirt-engine/ansible-runner-service-project/project/roles/ovirt-host-check-upgrade/tasks/main.yml
yum check-update -q | cut -d ' ' -f1 | sed '/^$/d' >> /tmp/yum_updates
For some reason it also lists those packages:
gluster-ansible-cluster.src
gluster-ansible-infra.src
gluster-ansible-maintenance.src
gluster-ansible-roles.src

Which do not exists, those are source RPMs, so the ansible playbook for the 
host upgrade fails.

I did a quick workaround and added an "egrep -v src"
yum check-update -q | egrep -v src | cut -d ' ' -f1 | sed '/^$/d' >> 
/tmp/yum_updates

So now the ansible-playbook doesn't fail, it does says the upgrade was 
successful the host reboots, but it doesn't get upgraded.

Also, i noticed that the playbook does make sure that the dnf cache is up to 
date (update_cache is set to true) when first checking the ovirt-host package, 
but it also does this for every single package in the task after, so there's no 
need for update_cache there.

As a workaround to upgrade to 4.4.2 i have to reinstall every host with oVirt 
node 4.4.2 as it seems the upgrade process is broken.
___
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/GMZ5WLCYMFDSFBNTXFNOZU6ANYESSQ4H/


[ovirt-users] Re: Upgrade oVirt Host from 4.4.0 to 4.4.2 fails

2020-10-02 Thread Erez Zarum
It's not related, i have no multipath devices and i don't get into an emergency 
mode.
___
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/HT6RWSLJB5ERLCQOUJKOBNAY7UTK5XDW/


[ovirt-users] Re: Upgrade oVirt Host from 4.4.0 to 4.4.2 fails

2020-10-02 Thread Erez Zarum
Nope, i already tried it :(
The Prepare NGN fails always after ansible-dnf check "virt-v2v" package.
___
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/IYHH4RD24K4TYBIDO5WLPL2KMGCBRGDM/


[ovirt-users] Upgrade oVirt Host from 4.4.0 to 4.4.2 fails

2020-10-02 Thread Erez Zarum
Hey,
Bunch of hosts installed from oVirt Node Image, i have upgraded the self-hosted 
Engine successfully.
I have ran Check Upgrade on one of the hosts and it was entitled for an upgrade.
I use the UI to let it Upgrade, after multiple retries it always fails on 
"Prepare NGN host for upgrade."
so i chose another host as a test.
I have set the Host into Maintenance and let all the VMs migrate successfully.
made sure i do have the latest 4.4.2 repo (it was 4.4.0) yum install 
https://resources.ovirt.org/pub/yum-repo/ovirt-release44.rpm
And issued "dnf upgrade"
Installing:
 ovirt-openvswitch 
 replacing  openvswitch.x86_64 2.11.1-5.el8
 ovirt-openvswitch-ovn 
 replacing  ovn.x86_64 2.11.1-5.el8
 ovirt-openvswitch-ovn-host
 replacing  ovn-host.x86_64 2.11.1-5.el8
 ovirt-python-openvswitch  
 replacing  python3-openvswitch.x86_64 2.11.1-5.el8
Upgrading:
 ovirt-node-ng-image-update-placeholder
Installing dependencies:
 openvswitch2.11   
 ovirt-openvswitch-ovn-common  
 ovn2.11   
 ovn2.11-host  
 python3-openvswitch2.11   
Installing weak dependencies:
 network-scripts-openvswitch   
 network-scripts-openvswitch2.11   

It was very quick, but nothing else happened, I did try to reboot the host but 
I still see the host as oVirt 4.4.0 and as expected it still says that an 
update is available.
___
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/WL67T6DNFNS3QOZ2ZHK75JXTCWHIECFD/


[ovirt-users] Re: Windows TimeZone UTC

2020-08-04 Thread Erez Zarum
This does not set to UTC inside the guest, i have not checked this on Linux, 
but on Windows the guest uses: "Monrovia, Reykjavik".
Why not give the user to option to add a custom one?
___
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/BRPMEK4PNQLPW3EDBJSLDUOFZUWR2SUD/


[ovirt-users] Re: Windows TimeZone UTC

2020-07-26 Thread Erez Zarum
Hey Liran,
I still don't understand from those resources how can i add an "extra" timezone 
that is not "compiled" into Engine?
Is there a possibility you can write one here? I fear to mess up the 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/4TJBJEW5QF74EKOBEX5TBH2VHSYRSISR/


[ovirt-users] Re: Windows TimeZone UTC

2020-07-22 Thread Erez Zarum
I ran into this link while searching, how can i change it using engine-config? 
I see no reference there.

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


[ovirt-users] Windows TimeZone UTC

2020-07-20 Thread Erez Zarum
The Engine has the TimeZone types compiled, this may be an issue when one wants 
to configure a Windows Machine to use UTC as a Timezone instead of GMT.
Using GMT sets the Windows VM to "London, Dublin" time which may cause issues 
with daylight saving for some users.
There should be an option to supply our own Timezone or the least, make sure it 
is indeed coordinated with what Windows supports.
___
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/XZ6KQWPMSH6U5P57KL2Y2WN6KPVHO43L/


[ovirt-users] Re: iSCSI multipath with separate subnets... still not possible in 4.4.x?

2020-07-20 Thread Erez Zarum
I think there's a misunderstanding behind the name, what happens is the 
following:
When you deploy the hosted-engine you can choose only one target and path 
probably, so it uses the "default" interface, this is also true when you run a 
scan/discovery.
As example, if using a standard iSCSI configuration (best practice is also 
having a different network switches, etc.. which i show in this example, but it 
works well even if you don't have), you will probably have two interfaces, each 
in his own Fault Domain, so let's say we have eth3 as FD1 and eth4 as FD2.
Subnets:
 FD1 = 192.168.100.0/24
 FD2 = 192.168.200.0/24
You will then create a logical network for each of those Fault Domains, so FD1 
and FD2, make sure those are only attached and are not marked as VM network and 
are not "Required".
After that, you will have to attach those logical networks to the hosts and 
configure their IP.
For example on host1:
 We attach FD1 to eth3 and give it 192.168.100.11/24
 We attach FD2 to eth4 and give it 192.168.200.11/24
Note that i did not specify any gateway, It's a simple Layer2 configuration.
You will have to do this for each host (you can use ansible for automation 
which makes it very simple).
After you have attached you first Storage Domain using iSCSI and did the 
procedure above you will under the Datacenter a new Tab named "iSCSI 
Multipathing" the name is confusing because it does not control the Multipath, 
configuration of the Multipath should be done by referencing to the vendor best 
practice and configure it under "/etc/multipath/conf.d" because the VDSM 
override /etc/multipath.conf
In the "iSCSI Multipathing" section you will need to add those two Fault 
Domains.
So for FD1 you will need to select the logical network we created earlier named 
"FD1" and then select the appropriate targets related to it only!, do the same 
for FD2.
What happens behind the scene is that VDSM configure iSCSI (oVirt/RHEL uses 
libiscsi).
You can observe that two interfaces were created, eth3 and eth4: "iscsiadm -m 
iface"
Then look at the sessions: "iscsiadm -m session"
Easiest way around is just seeing what was created in the "/var/lib/iscsi" 
folder: "find /var/lib/iscsi"
You will see how VDSM configured iSCSI to interact with the targets, it tells 
it to use those specific interfaces to those specific targets.
you can observe a session "iscsiadm -m session -r1 -P3" to get more details.
So what really happened now is that VDSM will take care of making sure iSCSI 
works on each host, it will automatically login to the targets using those 
interfaces.

I do agree the name "Multipathing" is confusing. 

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


[ovirt-users] Re: Failed to upload ISO oVirt 4.4.0 - imageio unable to verify certificate

2020-07-10 Thread Erez Zarum
Replying to myself again, i managed to "solve" this.
in /etc/ovirt-imageio/conf.d/50-engine.conf it uses the key_file and cert_file 
of the apache by default.
For the CA cert it is indeed using the apache-ca.pem as expected (?), it seems 
to use the same CA when trying to reach the VDSM imageio daemon running on each 
host for obvious reasons those are two different CA, the apache-ca.pem is used 
by the Engine "frontend".
Changing the ca_file to /etc/pki/ovirt-engine/ca.pem and restart the imageio 
daemon on the ovirt-engine solved this issue.
The information here: http://ovirt.github.io/ovirt-imageio/overview.html is 
misleading.
___
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/FUV7B43YSWAG6E3VO3IEXXJLDJ3DJWND/


[ovirt-users] Re: Failed to upload ISO oVirt 4.4.0 - imageio unable to verify certificate

2020-07-10 Thread Erez Zarum
There is a lot of misinformation, I don't have the ovirt-imageio-proxy service 
and only ovirt-imageio, can i assume this is the same?
I have tried to follow every workaround i have found (including many bugs that 
were closed) but none helped me to solve it.
I can confirm that this worked well in 4.3.10.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MIBC72NTFPF36I2O57R42HYH3CBFNYEO/


[ovirt-users] Failed to upload ISO oVirt 4.4.0 - imageio unable to verify certificate

2020-07-10 Thread Erez Zarum
I have changed the Engine SSL certificate with our own certificates (using 
FreeIPA), i have followed the procedure described in the documents carefully 
and it is indeed working well.
I haven now tried to upload an ISO and it fails, using "test connection" says 
the connection to the imageio service is ok, but when the upload starts it 
fails.
I can see those errors in the ovirt-imageio daemon log file.
2020-07-10 06:00:48,386 ERROR   (Thread-11) [http] Server error
Traceback (most recent call last):
  File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/http.py", 
line 699, in __call__
self.dispatch(req, resp)
  File "/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/http.py", 
line 744, 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 66, in put
backends.get(req, ticket, self.config),
  File 
"/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/__init__.py",
 line 53, in get
cafile=config.tls.ca_file)
  File 
"/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", 
line 48, in open
secure=options.get("secure", True))
  File 
"/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", 
line 63, in __init__
options = self._options()
  File 
"/usr/lib64/python3.6/site-packages/ovirt_imageio/_internal/backends/http.py", 
line 364, in _options
self._con.request("OPTIONS", self.url.path)
  File "/usr/lib64/python3.6/http/client.py", line 1254, in request
self._send_request(method, url, body, headers, encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1300, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1249, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
  File "/usr/lib64/python3.6/http/client.py", line 1036, in _send_output
self.send(msg)
  File "/usr/lib64/python3.6/http/client.py", line 974, in send
self.connect()
  File "/usr/lib64/python3.6/http/client.py", line 1422, 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)

Looking at old posts here, i have also tried:
keytool -importcert -trustcacerts -keystore /etc/pki/ovirt-engine/.truststore 
-storepass mypass -file /etc/pki/ovirt-engine/apache-ca.pem
And restarted both the ovirt-imageio service and the ovirt-engine service, it 
didn't help.
___
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/6PZXUXSZLT2LFWXHGG3E5QSSJYQWHUB6/


[ovirt-users] oVirt 4.4.0, slave interfaces are down after a reboot

2020-07-07 Thread Erez Zarum
Fresh installation of oVirt 4.4.0 (using the ISO), after restarting an host, 
the host comes up but the slave interfaces of a bond remains in down state.
The only way to bring it up is to login via IPMI and restart the 
"NetworkManager" service.
Weird thing, after this, the host says that it's network is out of sync, this 
happens on a network that is marked as "migration network", what is out of sync 
is the gateway.
I have restart the host again (this happens on all hosts) and i can see that 
after a restart the NetworkManager state (nmcli c show bond0.421 as example) 
does not list the routes, after syncing the routes are there.
___
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/45JF643HPJOG62FJ3M3Y5CIYVO5RZ75M/


[ovirt-users] Running Self Hosted-Engine on the same iSCSI target as other Storage Domains

2020-07-07 Thread Erez Zarum
We are using Dell SC (Storage) with iSCSI with oVirt, it is impossible to 
create a new Target Portal with a specific LUN so it's impossible to isolate 
the SE LUN from other LUNs that are in use by other Storage Domains.
According to the documentations this is not a best practice, while searching i 
ran into that specific issue but it seems to be solved.
Is it still by best practice when using oVirt 4.4 to use a whole different 
target for the SE? If it is not possible giving the current envrionment 
restrictions is the only option for us is to attach a few disks to each servers 
and create a small gluster cluster (volume) just for the SE?
___
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/G5TORMHOP6KBCJ3ZOGD22OWTYFCYSTRQ/


[ovirt-users] Re: VDSM not binding on IPv4 after ovirt-engine restart

2020-06-30 Thread Erez Zarum
> On Tue, Jun 30, 2020 at 6:13 PM Erez Zarum  
> Thanks for sharing the details.
> 
> 
> Why do you think the host does not listen to IPv4 anymore?
> Can you please share the output of
> "nc -vz  10.46.20.23 54321"
> executed on engine VM or another host?
$ nc -vz 10.46.20.23 54321
Ncat: Version 7.50 ( https://nmap.org/ncat )
Ncat: Connected to 10.46.20.23:54321.
Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds.

Seems like it does work.
___
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/RHLCN4RMUZHMWSAR63OBMUKZJGNEYLYR/


[ovirt-users] VDSM not binding on IPv4 after ovirt-engine restart

2020-06-30 Thread Erez Zarum
While troubleshooting a fresh installation of (after a failed one) that caused 
all the hosts but the one running the hosted-engine to become in “Unassigned” 
state I noticed that the ovirt-engine complains about not being able to contact 
the VDSM.
I noticed that VDSM has stopped listening on IPv4.

I didn’t disable any IPv6 as it states not to disable it on hosts that are 
capable running the hosted-engine  and it seems that the reason behind it is 
that the hosted-engine talks to the host it runs on through “localhost”, this 
also explains why the host which the hosted-engine runs on is “OK”.

Below is from a host that does not run the hosted-engine:
# ss -atn | grep 543
LISTEN 0  5*:54322*:*
ESTAB  0  0  127.0.0.1:54792  127.0.0.1:54321
ESTAB  0  0  127.0.0.1:54798  127.0.0.1:54321
LISTEN 0  5 [::]:54321 [::]:*
ESTAB  0  0   [:::127.0.0.1]:54321   
[:::127.0.0.1]:54798
ESTAB  0  0   [:::127.0.0.1]:54321   
[:::127.0.0.1]:54792
ESTAB  0  0[::1]:54321[::1]:50238
ESTAB  0  0[::1]:50238[::1]:54321

Below is from a host that runs the hosted-engine at the moment:
# ss -atn | grep 543
LISTEN 0  5*:54322*:*
LISTEN 0  5 [::]:54321 [::]:*
ESTAB  0  0[::1]:51230[::1]:54321
ESTAB  0  0[::1]:54321[::1]:51242
ESTAB  0  0 [:::10.46.20.23]:54321 
[:::10.46.20.20]:45706
ESTAB  0  0 [:::10.46.20.23]:54321 
[:::10.46.20.20]:45746
ESTAB  0  0[::1]:51240[::1]:54321
ESTAB  0  0[::1]:54321[::1]:51230
ESTAB  0  0[::1]:51242[::1]:54321
ESTAB  0  0[::1]:54321[::1]:51240

The hosted-engine IP is 10.46.20.20 and the host is 10.46.20.23.

/etc/hosts on all hosts:
127.0.0.1  localhost localhost.localdomain localhost4 
localhost4.localdomain4
::1localhost localhost.localdomain localhost6 
localhost6.localdomain6

Perhaps this is relevant but all hosts are enrolled into IDM (FreeIPA) and as 
an outcome they all have a DNS record and a PTR record as well as the 
ovirt-engine VM.

# cat /etc/vdsm/vdsm.conf
[vars]
ssl = true
ssl_ciphers = HIGH:!aNULL
ssl_excludes = OP_NO_TLSv1,OP_NO_TLSv1_1

[addresses]
management_port = 54321

I have tried adding “management_ip = 0.0.0.0” but then it only binds to IPv4 
and yet, the host still shows as Unassigned, sometimes it switches to 
“NonResponsive” and trying to “Reinstall” the host fails, the ovirt-engine 
complains it can't contact/reach the VDSM, while using netcat from the 
ovirt-engine it works.

I have KSM and Memory Ballooning enabled on the Cluster as well.

oVirt 4.3.10 installed on CentOS 7.8.2003
The self-hosted Engine runs on an external GlusterFS, before reinstalling 
everything (fresh start of OS, etc..) I tried iSCSI as well.


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


[ovirt-users] VDSM can't see StoragePool

2020-06-25 Thread Erez Zarum
I have a Self-hosted Engine running on iSCSI as well as couple of Storage 
domains using iSCSI, both the SE and those Storage Domains uses the same target 
portals (two).
I can see the iSCSI sessions and multipath working well from the Host point of 
view.
Yesterday after doing a restart for the “ovirt-engine” all the hosts besides 
the one that runs the SE and the SPM went into “Unassigned” mode with an error 
stating the ovirt-engine can’t communicate with the hosts.
Network wise, everything is good, I can reach all the ports, all the network is 
well configured, so I ruled this.
Looking at the VDSM logs on those “Unassigned” hosts it looks like the VDSM 
can’t find the Storage Pool.

(vmrecovery) [vdsm.api] START getConnectedStoragePoolsList(options=None) 
from=internal, task_id=217ec32b-591c-4376-8dc0-8d62200557ee (api:48)
(vmrecovery) [vdsm.api] FINISH getConnectedStoragePoolsList return={'poollist': 
[]} from=internal, task_id=217ec32b-591c-4376-8dc0-8d62200557ee (api:54)
(vmrecovery) [vds] recovery: waiting for storage pool to go up (clientIF:723)

If I look at the VDSM logs on the host where the SE and SPM is running, no 
issues there and the node appears up (green) in the ovirt-engine UI.

I managed to set the hosted-engine to maintenance, shut it down and then start 
it again on another Host, when it starts on that Host, the host goes “green” 
and if the SPM stays on the previous host, I have two hosts working and the 
rest remains “Unassigned”.

All the “ovirt-ha-agent”/”ovirt-ha-broker” services seems ok, I restarted them, 
I also tried to restart the VDSM on the hosts with no luck.
I have the VMs still running, I did shutdown one host (even used the “SSH 
restart” from the WebUI) to see if that helps, it came back and still went into 
“Unassigned”.

It seems like the hosts can’t see the Storage pool.

Where should I start to troubleshoot this?

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


[ovirt-users] Migration of self Hosted Engine from iSCSI to Gluster/NFS

2020-06-24 Thread Erez Zarum
I was looking for a “complete” best practice to migrate a self-hosted engine 
running currently on an iSCSI LUN to a Gluster of NFS storage domain
oVirt version 4.3.10

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/67TIOC6NZV732WQMMTTRUVVHCSM3CPDS/


[ovirt-users] Re: New VM from Template and Storage size

2020-06-16 Thread Erez Zarum
It is reasonable flow that you inherit the configuration from the template, but 
you can change most of the settings during the creation of the VM, I just don't 
understand why not to be able to change the disk size and name.
Why disk size? You can say the same thing with any other settings, so just make 
a template for any different setting you need for different VMs based on that 
same OS.
This flow of changing the disk size is supported in any other platforms take a 
few, OpenStack, VMWare, Xen and any other Cloud providers.
I don't see a reason why to do this in two API calls, one for VM creation and 
then another one for just expanding the disk size.
I do understand if you create a VM based on a thin template which is just a 
link that there's no other way.
Another "issue" is that it creates the new of the new disk for the VM based on 
the template name instead of "vmname_Disk1" etc...
I have a customer with many different disk sizes, varying from 50GB up to 
200GB, If I go and create a template for an OS based on that, I will probably 
have 10 templates, it's not scalable if you need to just modify something in 
the template as well.

So the only option right now is to use OpenStack Glance for saving images or 
create a new feature in Foreman/Satelite for that.

On 16/06/2020, 20:53, "Nir Soffer"  wrote:

On Tue, Jun 16, 2020 at 5:32 PM Erez Zarum  wrote:
>
> Hey,
>
> I have created a template that the disk is a thick (raw) with a size of 
15GB.
>
> I am trying to create a VM from that template but having the disk with a 
much larger size, both template and the VM are set to use thick and I create  
the new VM with the clone option, so there’s no link between the new VM and the 
template.
>
> So far the only solution I managed to find is to adjust the size after 
creating the VM.

This looks like reasonable flow. You create the vm from a template, so
you inherit the
disk size from the template. Then you modify the disk to the required size.

> For example, this situation causes a problematic step when using 
Foreman/Satelite as trying to provision a VM based on a template but with 
different size for the OS disk.

Why is this problematic?

> I assume that one of the ways to solve it is to convert the template 
somehow into an “image”? like using OpenStack Glance as a place to store 
“templates” as images? Any other way besides using Glance?

If you always need to resize the template, why not create another
templated with the right
size based on this template?

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/46IFRJCTZNZZHRYVDIYGVJFBNSOJNPVX/


[ovirt-users] New VM from Template and Storage size

2020-06-16 Thread Erez Zarum
Hey,
I have created a template that the disk is a thick (raw) with a size of 15GB.
I am trying to create a VM from that template but having the disk with a much 
larger size, both template and the VM are set to use thick and I create  the 
new VM with the clone option, so there’s no link between the new VM and the 
template.
So far the only solution I managed to find is to adjust the size after creating 
the VM.
For example, this situation causes a problematic step when using 
Foreman/Satelite as trying to provision a VM based on a template but with 
different size for the OS disk.

I assume that one of the ways to solve it is to convert the template somehow 
into an “image”? like using OpenStack Glance as a place to store “templates” as 
images? Any other way besides using Glance?

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/5K3OSY2SLB3BOOXIBAKQHT77VP5YZ4RZ/


[ovirt-users] Re: oVirt 4.4 Self-hosted Engine and Intel Skylake CPUs

2020-06-16 Thread Erez Zarum
Thanks, so during an upgrade from 4.3.10 to 4.4 there should not be any issues 
as I have already established a Cluster and a CPU type?

On 15/06/2020, 23:01, "Anton Gonzalez"  wrote:

Hey. Yup, this is a known issue. You can reference the following threads:

https://lists.ovirt.org/archives/list/users@ovirt.org/thread/KZHDCDE6JYADDMFSZD6AXYBP6SPV4TGA/

https://lists.ovirt.org/archives/list/users@ovirt.org/thread/5LBCJGWTVRVTEWC5VSDQ2OINQ3OHKQ7K/
___
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/BY77QHD4TXXEUFCQWBOYLRQUSYSAE5P5/
___
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/4KPUBEJMGA7OBF5XALZHQCNJ6DFJGUQV/


[ovirt-users] oVirt 4.4 Self-hosted Engine and Intel Skylake CPUs

2020-06-15 Thread Erez Zarum
Hey,
I was trying to install oVirt with SE on a node that has Intel Skylake CPU
(Intel Xeon Gold 6238R CPU to be precise) which by Intel supports TSX.
When the SE was provisioned as a local VM all was working well, it was
using a different CPU type for local provisioning.
After the local SE VM was migrated to the shared Storage (iSCSI) and was
configured, it failed to start.
When checking the XML (and vm.conf) that was created and provided to
libvirt I noticed it uses the "Secure Intel Skylake" type CPU
with +tsx-ctrl as a required flag.
My assumption as this is a fresh install of oVirt with SE is that the newly
created Cluster was set to this CPU compatibility.
This specific CPU by Intel does not expose any tsx flags, while it does
indeed support TSX libvirt has no way of knowing it, more strange, some
other CPUs from that same range/models do expose the tsx flag.
I have tried to set the kernel cmdline to tsx=yes|auto|off and none of
those helped.
The quick solution was to start the engine manually by editing the XML file
(hosted-engine --vm-shutdown and then start it with libvirt) and change the
Cluster CPU type and the HostedEngine CPU type as well to "Intel Skylake"
and then start it (hosted-engine --vm-start)
Another solution which i haven't tried is to get the correct string from
the oVirt-Engine API of the non-secure Intel Skylake CPU and hardcode it
into the cpu_model fact in the SE ansible role (task).
At the end i opted not to try any workaround and decided to go on with
oVirt 4.3 which went smooth, it chose "Intel Skylake Server IBRS SSBD MDS
Family" as the Cluster CPU compatibility and installation went without any
errors/issues.
1) What will happen if i decide to upgrade to 4.4? I will first have to
reinstall a node with CentOS 8 and then migrate the HostedEngine to there
as well, will it keep the current cluster CPU type or will it try to
upgrade and these fail the upgrade?
2) Are you aware of this situation? I understand this is a new solution
because you had to update everytime the CPU databases but on the other
hand, Intel is not helping here by not being strict about exposing the tsx
flags, perhaps the best will be to let the user chose which CPU type use on
the first Cluster created by the SE ansible role? (As far as i remember,
this was available in the previous versions of oVirt)

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