- Users - oVirt List Archives

[ANN] oVirt 4.3.5 First Release Candidate is now available
by Sandro Bonazzola 13 Jun '19

13 Jun '19

The oVirt Project is pleased to announce the availability of the oVirt 4.3.5 First Release Candidate, as of June 13th, 2019. This update is a release candidate of the fifth in a series of stabilization updates to the 4.3 series. This is pre-release software. This pre-release should not to be used in production. 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) 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.5 release highlights: http://www.ovirt.org/release/4.3.5/ * 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.5/ [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://www.redhat.com/>

1 0

Re: Memory ballon question
by Strahil 13 Jun '19

13 Jun '19

Hi Darrell, Yes , all VMs (both openSUSE and RedHat/CentOS 7) have the ovirt-guest-agent up and running. Best Regards, Strahil NikolovOn Jun 12, 2019 22:07, Darrell Budic <budic(a)onholyground.com> wrote: > > Do you have the overt-guest-agent running on your VMs? It’s required for ballooning to control allocations on the guest side. > >> On Jun 12, 2019, at 11:32 AM, Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> Hello All, >> >> as a KVM user I know how usefull is the memory balloon and how you can both increase - and also decrease memory live (both Linux & Windows). >> I have noticed that I cannot decrease the memory in oVirt. >> >> Does anyone got a clue why the situation is like that ? >> >> I was expecting that the guaranteed memory is the minimum to which the balloon driver will not go bellow, but when I put my host under pressure - the host just started to swap instead of reducing some of the VM memory (and my VMs had plenty of free space). >> >> It will be great if oVirt can decrease the memory (if the VM has unallocated memory) when the host is under pressure and the VM cannot be relocated. >> >> Best Regards, >> Strahil Nikolov >> >> _______________________________________________ >> 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/LUWCN2MLNTDJU… > >

2 1

Re: Ovirt hiperconverged setup error
by Strahil 13 Jun '19

13 Jun '19

Simone has provided you a workaround, so check his e-mail. The ansible is actually running: dig ov-node2 +short As dig is quarrying your DNS server, you need to bypass this check if you use /etc/host entries. Best Regards, Strahil NikolovOn Jun 12, 2019 21:57, PS Kazi <faruk.apsara(a)gmail.com> wrote: > > Hi, > How to check my DNS settings is ok or not for ovirt? > > On Wed, 12 Jun 2019, 6:55 pm Strahil Nikolov, <hunter86_bg(a)yahoo.com> wrote: >> >> Command run is "dig' which tries to resolve the hostname of each server. >> Do you have a DNS resolver properly configured ? >> >> Best Regards, >> Strahil Nikolov >> >> В сряда, 12 юни 2019 г., 3:59:14 ч. Гринуич-4, PS Kazi <faruk.apsara(a)gmail.com> написа: >> >> >> ovirt Node version 4.3.3.1 >> I am trying to configure 3 node Gluster storage and oVirt hosted engine but gettng following error: >> >> TASK [gluster.features/roles/gluster_hci : Check if valid FQDN is provided] **** >> failed: [ov-node-2 -> localhost] (item=ov-node-2) => {"changed": true, "cmd": ["dig", "ov-node-2", "+short"], "delta": "0:00:00.041003", "end": "2019-06-12 12:52:34.158688", "failed_when_result": true, "item": "ov-node-2", "rc": 0, "start": "2019-06-12 12:52:34.117685", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} >> failed: [ov-node-2 -> localhost] (item=ov-node-3) => {"changed": true, "cmd": ["dig", "ov-node-3", "+short"], "delta": "0:00:00.038688", "end": "2019-06-12 12:52:34.459176", "failed_when_result": true, "item": "ov-node-3", "rc": 0, "start": "2019-06-12 12:52:34.420488", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} >> failed: [ov-node-2 -> localhost] (item=ov-node-1) => {"changed": true, "cmd": ["dig", "ov-node-1", "+short"], "delta": "0:00:00.047938", "end": "2019-06-12 12:52:34.768149", "failed_when_result": true, "item": "ov-node-1", "rc": 0, "start": "2019-06-12 12:52:34.720211", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} >> >> >> Please help >> _______________________________________________ >> 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/BXMOTKHGI5TNP…

1 0

Re: Replace bad Host from a 9 Node hyperconverged setup 4.3.3
by Strahil 12 Jun '19

12 Jun '19

Hi Adrian, You have several options: A) If you have space on another gluster volume (or volumes) or on NFS-based storage, you can migrate all VMs live . Once you do it, the simple way will be to stop and remove the storage domain (from UI) and gluster volume that correspond to the problematic brick. Once gone, you can remove the entry in oVirt for the old host and add the newly built one.Then you can recreate your volume and migrate the data back. B) If you don't have space you have to use a more riskier approach (usually it shouldn't be risky, but I had bad experience in gluster v3): - New server has same IP and hostname: Use command line and run the 'gluster volume reset-brick VOLNAME HOSTNAME:BRICKPATH HOSTNAME:BRICKPATH commit' Replace VOLNAME with your volume name. A more practical example would be: 'gluster volume reset-brick data ovirt3:/gluster_bricks/data/brick ovirt3:/gluster_ ricks/data/brick commit' If it refuses, then you have to cleanup '/gluster_bricks/data' (which should be empty). Also check if the new peer has been probed via 'gluster peer status'.Check the firewall is allowing gluster communication (you can compare it to the firewalls on another gluster host). The automatic healing will kick in 10 minutes (if it succeeds) and will stress the other 2 replicas, so pick your time properly. Note: I'm not recommending you to use the 'force' option in the previous command ... for now :) - The new server has a different IP/hostname: Instead of 'reset-brick' you can use 'replace-brick': It should be like this: gluster volume replace-brick data old-server:/path/to/brick new-server:/new/path/to/brick commit force In both cases check the status via: gluster volume info VOLNAME If your cluster is in production , I really recommend you the first option as it is less risky and the chance for unplanned downtime will be minimal. The 'reset-brick' in your previous e-mail shows that one of the servers is not connected. Check peer status on all servers, if they are less than they should check for network and/or firewall issues. On the new node check if glusterd is enabled and running. In order to debug - you should provide more info like 'gluster volume info' and the peer status from each node. Best Regards, Strahil Nikolov On Jun 10, 2019 20:10, Adrian Quintero <adrianquintero(a)gmail.com> wrote: > > Can you let me know how to fix the gluster and missing brick?, > I tried removing it by going to "storage > Volumes > vmstore > bricks > selected the brick > However it is showing as an unknown status (which is expected because the server was completely wiped) so if I try to "remove", "replace brick" or "reset brick" it wont work > If i do remove brick: Incorrect bricks selected for removal in Distributed Replicate volume. Either all the selected bricks should be from the same sub volume or one brick each for every sub volume! > If I try "replace brick" I cant because I dont have another server with extra bricks/disks > And if I try "reset brick": Error while executing action Start Gluster Volume Reset Brick: Volume reset brick commit force failed: rc=-1 out=() err=['Host myhost1_mydomain_com not connected'] > > Are you suggesting to try and fix the gluster using command line? > > Note that I cant "peer detach" the sever , so if I force the removal of the bricks would I need to force downgrade to replica 2 instead of 3? what would happen to oVirt as it only supports replica 3? > > thanks again. > > On Mon, Jun 10, 2019 at 12:52 PM Strahil <hunter86_bg(a)yahoo.com> wrote: >> >> Hi Adrian, >> Did you fix the issue with the gluster and the missing brick? >> If yes, try to set the 'old' host in maintenance an

3 4

oVirt engine/engine-setup with other port than default HTTPS 443 possible?
by Dirk Rydvan 12 Jun '19

12 Jun '19

Hello, in a home lab with only one puplic IPv4-Adress is the Port 443 a very precious one. The installation of oVirt 4.3 on a single node/host with bare metal installed CentOS works well. (oVirt Cockpit and local installed engine added after installation of Centos 7.6). But it is more difficult to change the port from 443 to maybe 4443 the save the port 443. The change in: - /etc/httpd/conf/conf.d/ssl.conf - /var/lib/ovirt-engine/jboss_runtime/config/ovirt-engine.xml and - disable selinux - add 4443 to public with firewall-cmd It does not work... now I see is more difficult than I think before... A port redirection at the edge route from <public-IPv4>:4443 to <private-IPv4>:443 does also not work, because the links points all to the standard https adress without a port number. Is there a way to change the default port 443 of oVirt engine to a other port? Many Thanks in advance!

1 0

RFE: HostedEngine to use boom by default
by Strahil Nikolov 12 Jun '19

12 Jun '19

Hello All, I have seen a lot of cases where the HostedEngine gets corrupted/broken and beyond repair. I think that BOOM is a good option for our HostedEngine appliances due to the fact that it supports booting from LVM snapshots and thus being able to easily recover after upgrades or other outstanding situations. Sadly, BOOM has 1 drawback - that everything should be under a single snapshot - thus no separation of /var /log or /audit. Do you think that changing the appliance layout is worth it ? Note: I might have an unsupported layout that could cause my confusion.Is your layout a single root LV ? Best Regards,Strahil Nikolov

2 2

4K Sector Hard drive Support - oVirt 4.3.4
by nico.kruger＠darkmatter.ae 12 Jun '19

12 Jun '19

Hi Guys, 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 Thanks Nico Kruger

2 1

vNUMA question
by Matthias Leopold 12 Jun '19

12 Jun '19

Hi, when I want to use vNUMA for VMs is it necessary that the number of VM virtual sockets corresponds to the number of vNUMA nodes? concrete example: hypervisor host has 2 physical cpus VM has 2 vNUMA nodes and uses CPU pinning which distributes the VCPUs equally over both physical CPUs is it necessary for the VM to have 2 virtual sockets or is it ok for virtual socket count to be powers of 2 (eg. 16)? thanks matthias

2 1

Re: Can't bring upgraded to 4.3 host back to cluster
by Shani Leviim 12 Jun '19

12 Jun '19

Np :) On Tuesday, June 11, 2019, Artem Tambovskiy <artem.tambovskiy(a)gmail.com> wrote: > Actually, this one wasn't stupid. The host was running version 4.3.3 and > was upgraded to 4.3.4 after yum update. > And this solved the issue ... thanks a lot! > > Looing at the bugtracker (https://bugzilla.redhat.com/ > buglist.cgi?classification=oVirt&f1=flagtypes.name&o1= > substring&query_format=advanced&target_milestone=ovirt-4.3.4&v1=blocker) > I don't see a suitable bug for this. perhaps vdsmd reconfiguration + yum > upgrade + host reboot did the trick. > > Thank you very much for spending a time on this! > Regards, > Artem > > On Tue, Jun 11, 2019 at 5:19 PM Shani Leviim <sleviim(a)redhat.com> wrote: > >> A stupid one: did you try to yum update? >> >> >> >> *Regards,* >> >> *Shani Leviim* >> >> >> On Tue, Jun 11, 2019 at 5:11 PM Artem Tambovskiy < >> artem.tambovskiy(a)gmail.com> wrote: >> >>> >>> Just tried this: >>> >>> [root@ovirt1 vdsm]# vdsm-tool configure --force >>> >>> Checking configuration status... >>> >>> abrt is already configured for vdsm >>> Managed volume database is already configured >>> lvm is configured for vdsm >>> libvirt is already configured for vdsm >>> SUCCESS: ssl configured to true. No conflicts >>> Current revision of multipath.conf detected, preserving >>> >>> Running configure... >>> Reconfiguration of abrt is done. >>> Reconfiguration of passwd is done. >>> Reconfiguration of libvirt is done. >>> >>> Done configuring modules to VDSM. >>> >>> And tried to restart vdsmd - it failed again. >>> >>> [root@ovirt1 vdsm]# journalctl -xe >>> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: ovirt-ha-broker.service >>> failed. >>> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: ovirt-ha-broker.service >>> holdoff time over, scheduling restart. >>> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: Cannot add dependency job >>> for unit lvm2-lvmetad.socket, ignoring: Unit is masked. >>> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: Stopped oVirt Hosted Engine >>> High Availability Communications Broker. >>> -- Subject: Unit ovirt-ha-broker.service has finished shutting down >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit ovirt-ha-broker.service has finished shutting down. >>> Jun 11 17:07:58 ovirt1.telia.ru systemd[1]: Started oVirt Hosted Engine >>> High Availability Communications Broker. >>> -- Subject: Unit ovirt-ha-broker.service has finished start-up >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit ovirt-ha-broker.service has finished starting up. >>> -- >>> -- The start-up result is done. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: mom-vdsm.service holdoff >>> time over, scheduling restart. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Cannot add dependency job >>> for unit lvm2-lvmetad.socket, ignoring: Unit is masked. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Stopped MOM instance >>> configured for VDSM purposes. >>> -- Subject: Unit mom-vdsm.service has finished shutting down >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit mom-vdsm.service has finished shutting down. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: start request repeated too >>> quickly for supervdsmd.service >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Failed to start Auxiliary >>> vdsm service for running helper functions as root. >>> -- Subject: Unit supervdsmd.service has failed >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit supervdsmd.service has failed. >>> -- >>> -- The result is failed. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Dependency failed for >>> Virtual Desktop Server Manager. >>> -- Subject: Unit vdsmd.service has failed >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit vdsmd.service has failed. >>> -- >>> -- The result is dependency. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Dependency failed for MOM >>> instance configured for VDSM purposes. >>> -- Subject: Unit mom-vdsm.service has failed >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit mom-vdsm.service has failed. >>> -- >>> -- The result is dependency. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Job mom-vdsm.service/start >>> failed with result 'dependency'. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: Job vdsmd.service/start >>> failed with result 'dependency'. >>> Jun 11 17:07:59 ovirt1.telia.ru systemd[1]: supervdsmd.service failed. >>> >>> I also tried to enable DEBUG level but failed. >>> >>> [root@ovirt1 vdsm]# vdsm-client Host setLogLevel level=DEBUG >>> vdsm-client: Connection to localhost:54321 with use_tls=True, timeout=60 >>> failed: [Errno 111] Connection refused >>> >>> >>> Regards, >>> Artem >>> >>> >>> >>> On Tue, Jun 11, 2019 at 4:45 PM Shani Leviim <sleviim(a)redhat.com> wrote: >>> >>>> Until will get a response from Dan (maybe it's related to a network >>>> issue), I would suggest to re-configure the vdsm: >>>> vdsm-tool configure --force >>>> >>>> some further steps are available here: https://www.ovirt.org/develop/ >>>> developer-guide/vdsm/installing-vdsm-from-rpm.html# >>>> installing--configuring-vdsm >>>> >>>> Let me know if it helped. >>>> >>>> Also, can you please attach a VDSM log with DEBUG level? >>>> To do so: >>>> vdsm-client Host setLogLevel level=DEBUG >>>> >>>> >>>> *Regards,* >>>> >>>> *Shani Leviim* >>>> >>>> >>>> On Tue, Jun 11, 2019 at 3:04 PM Artem Tambovskiy < >>>> artem.tambovskiy(a)gmail.com> wrote: >>>> >>>>> Hi Shani, >>>>> >>>>> yes, you are right - I can do ssh form aby to any hosts in the >>>>> cluster. vdsm.log attached. >>>>> I have tried to restart vdsm manually and even done a host restart >>>>> several times with no success. >>>>> Host activation fails all the time ... >>>>> >>>>> Thank you in advance for your help! >>>>> Regard, >>>>> Artem >>>>> >>>>> On Tue, Jun 11, 2019 at 10:51 AM Shani Leviim <sleviim(a)redhat.com> >>>>> wrote: >>>>> >>>>>> Hi Artem, >>>>>> According to oVirt documentation [1], hosts on the same cluster >>>>>> should be reachable from one to each other. >>>>>> >>>>>> Can you please share your vdsm log? >>>>>> I suppose you do manage to ssh that inactive host (correct me if I'm >>>>>> wrong). >>>>>> While getting the vdsm log, maybe try to restart the network and >>>>>> vdsmd services on the host. >>>>>> >>>>>> Another thing you can try on the UI is putting the host on >>>>>> maintenance and then activate it. >>>>>> >>>>>> [1] https://www.ovirt.org/documentation/admin-guide/ >>>>>> chap-Clusters.html#introduction-to-clusters >>>>>> >>>>>> >>>>>> *Regards,* >>>>>> >>>>>> *Shani Leviim* >>>>>> >>>>>> >>>>>> On Mon, Jun 10, 2019 at 4:42 PM Artem Tambovskiy < >>>>>> artem.tambovskiy(a)gmail.com> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> May I ask you for and advise? >>>>>>> I'm running a small oVirt cluster and couple of months ago I decided >>>>>>> to do an upgrade from oVirt 4.2.8 to 4.3 and having an issues since that >>>>>>> time. I can only guess what I did wrong - probably one of the problems that >>>>>>> I haven't switched the cluster from iptables to firewalld. But this is just >>>>>>> my guess. >>>>>>> >>>>>>> The problem is that I have upgraded the engine and one host, and >>>>>>> then I done an upgrade of second host I can't bring it to active state. >>>>>>> Looks like VDSM can't detect the network and fails to start. I even tried >>>>>>> to reinstall the hosts from UI (I have seen that the packages being >>>>>>> installed) but again, VDSM doesn't startup at the end and reinstallation >>>>>>> fails. >>>>>>> >>>>>>> Looking at hosts process list I see script *wait_for_ipv4s* >>>>>>> hanging forever. >>>>>>> >>>>>>> vdsm 8603 1 6 16:26 ? 00:00:00 /usr/bin/python >>>>>>> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent >>>>>>> >>>>>>> *root 8630 1 0 16:26 ? 00:00:00 /bin/sh >>>>>>> /usr/libexec/vdsm/vdsmd_init_common.sh --pre-startroot 8645 8630 6 >>>>>>> 16:26 ? 00:00:00 /usr/bin/python2 /usr/libexec/vdsm/wait_for_ipv4s* >>>>>>> root 8688 1 30 16:27 ? 00:00:00 /usr/bin/python2 >>>>>>> /usr/share/vdsm/supervdsmd --sockfile /var/run/vdsm/svdsm.sock >>>>>>> vdsm 8715 1 0 16:27 ? 00:00:00 /usr/bin/python >>>>>>> /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker >>>>>>> >>>>>>> The all hosts in cluster are reachable from each other ... That >>>>>>> could be the issue? >>>>>>> >>>>>>> Thank you in advance! >>>>>>> -- >>>>>>> Regards, >>>>>>> Artem >>>>>>> _______________________________________________ >>>>>>> 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(a)ovirt.org/message/TQX3LN2TEM4DECKKUMMRCWXTRM6BGI >>>>>>> AB/ >>>>>>> >>>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> Artem >>>>> >>>> >>> >>> -- >>> Regards, >>> Artem >>> >> > > -- > Regards, > Artem > -- *Regards,* *Shani Leviim*

1 0

VM Disk Performance metrics?
by Wesley Stewart 11 Jun '19

11 Jun '19

Is there any way to get ovirt disk performance metrics into the web interface? It would be nice to see some type of IOPs data, so we can see which VMs are hitting our data stores the most. It seems you can run virt-top on a host to get some of these metrics, but it would be nice to get some sort of data in the gui. Thanks!

3 2

Can't bring upgraded to 4.3 host back to cluster
by Artem Tambovskiy 11 Jun '19

11 Jun '19

Hello, May I ask you for and advise? I'm running a small oVirt cluster and couple of months ago I decided to do an upgrade from oVirt 4.2.8 to 4.3 and having an issues since that time. I can only guess what I did wrong - probably one of the problems that I haven't switched the cluster from iptables to firewalld. But this is just my guess. The problem is that I have upgraded the engine and one host, and then I done an upgrade of second host I can't bring it to active state. Looks like VDSM can't detect the network and fails to start. I even tried to reinstall the hosts from UI (I have seen that the packages being installed) but again, VDSM doesn't startup at the end and reinstallation fails. Looking at hosts process list I see script *wait_for_ipv4s* hanging forever. vdsm 8603 1 6 16:26 ? 00:00:00 /usr/bin/python /usr/share/ovirt-hosted-engine-ha/ovirt-ha-agent *root 8630 1 0 16:26 ? 00:00:00 /bin/sh /usr/libexec/vdsm/vdsmd_init_common.sh --pre-startroot 8645 8630 6 16:26 ? 00:00:00 /usr/bin/python2 /usr/libexec/vdsm/wait_for_ipv4s* root 8688 1 30 16:27 ? 00:00:00 /usr/bin/python2 /usr/share/vdsm/supervdsmd --sockfile /var/run/vdsm/svdsm.sock vdsm 8715 1 0 16:27 ? 00:00:00 /usr/bin/python /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker The all hosts in cluster are reachable from each other ... That could be the issue? Thank you in advance! -- Regards, Artem

3 5

Failed to activate Storage Domain --- ovirt 4.2
by aminur.rahman＠iongroup.com 11 Jun '19

11 Jun '19

Hi Has anyone experiencing the following issue with Storage Domain - Failed to activate Storage Domain cLUN-R940-DC2-dstore01 -- VDSM command ActivateStorageDomainVDS failed: Storage domain does not exist: (u'1b0ef853-fd71-45ea-8165-cc6047a267bc',) Currently, the storge Domain is Inactive and strangely, the VMs are running as normal. We can't manage or extend the volume size of this storage domain. The pvscan shows as: [root@uk1-ion-ovm-18 pvscan /dev/mapper/36000d310056978000000000000000014: Checksum error at offset 4397954425856 Couldn't read volume group metadata from /dev/mapper/36000d310056978000000000000000014. Metadata location on /dev/mapper/36000d310056978000000000000000014 at 4397954425856 has invalid summary for VG. Failed to read metadata summary from /dev/mapper/36000d310056978000000000000000014 Failed to scan VG from /dev/mapper/36000d310056978000000000000000014 I have tired the following steps: 1. Restarted ovirt-engine.service 2. tried to restore the metadata using vgcfgrestore but it failed with the following error: [root@uk1-ion-ovm-19 backup]# vgcfgrestore 36000d310056978000000000000000014 Volume group 36000d310056978000000000000000014 has active volume: . WARNING: Found 1 active volume(s) in volume group "36000d310056978000000000000000014". Restoring VG with active LVs, may cause mismatch with its metadata. Do you really want to proceed with restore of volume group "36000d310056978000000000000000014", while 1 volume(s) are active? [y/n]: y /dev/mapper/36000d310056978000000000000000014: Checksum error at offset 4397954425856 Couldn't read volume group metadata from /dev/mapper/36000d310056978000000000000000014. Metadata location on /dev/mapper/36000d310056978000000000000000014 at 4397954425856 has invalid summary for VG. Failed to read metadata summary from /dev/mapper/36000d310056978000000000000000014 Failed to scan VG from /dev/mapper/36000d310056978000000000000000014 /etc/lvm/backup/36000d310056978000000000000000014: stat failed: No such file or directory Couldn't read volume group metadata from file. Failed to read VG 36000d310056978000000000000000014 from /etc/lvm/backup/36000d310056978000000000000000014 Restore failed. Please let me know if anyone knows any possible resolution. -AMinur

5 6

[ANN] oVirt 4.3.4 is now generally available
by Sandro Bonazzola 11 Jun '19

11 Jun '19

The oVirt Project is pleased to announce the general availability of oVirt 4.3.4 as of June 11th, 2019. This update is the fourth in a series of stabilization updates to the 4.3 series. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.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) Due to Fedora 28 being now at end of life this release is missing experimental tech preview for x86_64 and s390x architectures for Fedora 28. We are working on Fedora 29 and 30 support and we may re-introduce experimental support for Fedora in next release. See the release notes [1] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Node is already available[2] - oVirt Windows Guest Tools is already available[2] oVirt Guest Tools ISO has been updated including new virtio-win-prewhql drivers collection version 171, providing updated qxl-wddm-dod driver version 0.19 (see https://gitlab.freedesktop.org/spice/win32/qxl-wddm-dod/blob/master/Changel… for more information). oVirt Node and Appliance have been updated including: - oVirt 4.3.4: http://www.ovirt.org/release/4.3.4/ - Latest CentOS updates including: - CEBA-2019:1015 CentOS 7 glibc BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-May/023302.html> - CESA-2019:0809 Important CentOS 7 ovmf Security Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023280.html> - CEBA-2019:0814 CentOS 7 lvm2 BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023294.html> - CEBA-2019:0808 CentOS 7 iproute BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023288.html> - CESA-2019:1168 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2019-May/023314.html> - CEBA-2019:0807 CentOS 7 gcc BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023286.html> - CEBA-2019:0820 CentOS 7 systemd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023281.html> - CEBA-2019:0816 CentOS 7 sssd BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023283.html> - CESA-2019:1264 Important CentOS 7 libvirt Security Update <https://lists.centos.org/pipermail/centos-announce/2019-May/023319.html> - CEEA-2019:1210 CentOS 7 microcode_ctl Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-May/023311.html> - CESA-2019:1022 Important CentOS 7 python-jinja2 Security Update <https://lists.centos.org/pipermail/centos-announce/2019-May/023303.html> - CEEA-2019:0045 CentOS 7 rsync Enhancement Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023284.html> - CEBA-2019:0826 CentOS 7 scap-security-guide BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023291.html> - CEBA-2019:0819 CentOS 7 sos BugFix Update <https://lists.centos.org/pipermail/centos-announce/2019-April/023292.html> - latest CentOS Virt and Storage SIG updates: - CESA-2019:1179 CentOS Virt SIG - Errata and Security Advisory 2019:1179 Important Upstream details at : https://access.redhat.com/errata/RHSA-2019:1179 - ansible-2.8.1: https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.… - glusterfs-5.6: https://docs.gluster.org/en/latest/release-notes/5.6/ - cockpit 193: https://cockpit-project.org/blog/cockpit-193.html 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/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>

1 0

Replace bad Host from a 9 Node hyperconverged setup 4.3.3
by adrianquintero＠gmail.com 10 Jun '19

10 Jun '19

Anybody have had to replace a failed host from a 3, 6, or 9 node hyperconverged setup with gluster storage? One of my hosts is completely dead, I need to do a fresh install using ovirt node iso, can anybody point me to the proper steps? thanks,

6 15

Re: run ovirt without firewalld
by Strahil 10 Jun '19

10 Jun '19

Then ... You have no choice , but to enable firewalld via a cron job or systemd service. I think Sahina and/or Sandro can hint you how to proceed . Best Regards, Strahil Nikolov On Jun 10, 2019 20:02, Chris Boon <cpjboon(a)gmail.com> wrote: > > yeah i noticed the same, HostedEngine doesn't want to migrate or start due to disabled firewalld. > But some organizations have a company policy not to run firewalls on servers, only edge firewalls. > So automation tools disable firewalld :( > > best regards, > Chris > _______________________________________________ > 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/JQOROLNXKSQHT…

1 0

Re: Replace bad Host from a 9 Node hyperconverged setup 4.3.3
by Strahil 10 Jun '19

10 Jun '19

Hi Adrian, Did you fix the issue with the gluster and the missing brick? If yes, try to set the 'old' host in maintenance and then forcefully remove it from oVirt. If it succeeds (and it should), then you can add the server back and then check what happens. Best Regards, Strahil NikolovOn Jun 10, 2019 18:12, Adrian Quintero <adrianquintero(a)gmail.com> wrote: > > Ok I have tried reinstalling the server from scratch with a different name and IP address and when trying to add it to cluster I get the following error: > > Event details > ID: 505 > Time: Jun 10, 2019, 10:00:00 AM > Message: Host myshost2.virt.iad3p installation failed. Host myhost2.mydomain.com reports unique id which already registered for myhost1.mydomain.com > > I am at a loss here, I don't have a brand new server to do this and in need to re-use what I have. > > > From the oVirt engine log (/var/log/ovirt-engine/engine.log): > 2019-06-10 10:57:59,950-04 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-37744) [9b88055] EVENT_ID: VDS_INSTALL_FAILED(505), Host myhost2.mydomain.com installation failed. Host myhost2.mydomain.com reports unique id which already registered for myhost1.mydomain.com > > So in the /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-20190610105759-myhost2.mydomain.com-9b88055.log of the ovirt engine I see that the host deploy is running the following command to identify the system, if this is the case then it will never work :( because it identifies each host using the system uuid. > > dmidecode -s system-uuid > b64d566e-055d-44d4-83a2-d3b83f25412e > > > Any suggestions? > > Thanks > > On Sat, Jun 8, 2019 at 11:23 AM Adrian Quintero <adrianquintero(a)gmail.com> wrote: >> >> Leo, >> I did try putting it under maintenance and checking to ignore gluster and it did not work. >> Error while executing action: >> -Cannot remove host. Server having gluster volume. >> >> Note: the server was already reinstalled so gluster will never see the volumes or bricks for this server. >> >> I will rename the server to myhost2.mydomain.com and try to replace the bricks hopefully that might work, however it would be good to know that you can re-install from scratch an existing cluster server and put it back to the cluster. >> >> Still doing research hopefully we can find a way. >> >> thanks again >> >> Adrian >> >> >> >> >> On Fri, Jun 7, 2019 at 2:39 AM Leo David <leoalex(a)gmail.com> wrote: >>> >>> You will need to remove the storage role from that server first ( not being part of gluster cluster ). >>> I cannot test this right now on production, but maybe putting host although its already died under "mantainance" while checking to ignore guster warning will let you remove it. >>> Maybe I am wrong about the procedure, can anybody input an advice helping with this situation ? >>> Cheers, >>> >>> Leo >>> >>> >>> >>> >>> On Thu, Jun 6, 2019 at 9:45 PM Adrian Quintero <adrianquintero(a)gmail.com> wrote: >>>> >>>> I tried removing the bad host but running into the following issue , any idea?

2 1

Re: run ovirt without firewalld
by Strahil 10 Jun '19

10 Jun '19

I remember a case where my HostedEngine couldn't start due to disqbled firewalld. I'd recommend you to keep it running , as it will only be benefitial . Best Regards, Strahil NikolovOn Jun 8, 2019 13:38, Chris Boon <cpjboon(a)gmail.com> wrote: > > Hello, > > When i deploy and use oVirt 4.3, is firewalld really needed on hypervisors or can oVirt 4.3 run and function with a disabled firewalld? > > Regards, > Chris > _______________________________________________ > 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/7G4KQQCEVIXCK…

2 1

Erro seabios ovirt
by LIONS TECNOLOGIA 10 Jun '19

10 Jun '19

Please! I am a beginner in ovirt and I installed a single server, I am with the following problem, when I open the virtual machine console screen, it shows this black screen attached, I would like to know how to solve this problem.

2 1

Re: Failed to activate Storage Domain --- ovirt 4.2
by Eyal Shenitzky 10 Jun '19

10 Jun '19

Nir, can you please have a look? On Mon, Jun 10, 2019 at 2:29 PM Aminur Rahman <aminur.rahman(a)iongroup.com> wrote: > Hi Eyal > > > > We’re using: > > > > ovirt-engine-4.2.8.2-1.el7.noarch > > vdsm-client-4.20.46-1.el7.noarch > > > > Thanks > > *Aminur Rahman* > > aminur.rahman(a)iongroup.com > > *t* > > +44 20 7398 0243 <+44%2020%207398%200243> > > *m* > > +44 7825 780697 <+44%207825%20780697%3c> > > iongroup.com <https://www.iongroup.com> > > > > *From:* Eyal Shenitzky <eshenitz(a)redhat.com> > *Sent:* 10 June 2019 07:20 > *To:* Aminur Rahman <aminur.rahman(a)iongroup.com>; Nir Soffer < > nsoffer(a)redhat.com> > *Cc:* users <users(a)ovirt.org> > *Subject:* Re: [ovirt-users] Failed to activate Storage Domain --- ovirt > 4.2 > > > > Hi Aminur, > > > > Can you please send the engine and vdsm versions? > > > > > > On Fri, Jun 7, 2019 at 5:03 PM <aminur.rahman(a)iongroup.com> wrote: > > Hi > Has anyone experiencing the following issue with Storage Domain - > > Failed to activate Storage Domain cLUN-R940-DC2-dstore01 -- > VDSM command ActivateStorageDomainVDS failed: Storage domain does not > exist: (u'1b0ef853-fd71-45ea-8165-cc6047a267bc',) > > Currently, the storge Domain is Inactive and strangely, the VMs are > running as normal. We can't manage or extend the volume size of this > storage domain. The pvscan shows as: > [root@uk1-ion-ovm-18 pvscan > /dev/mapper/36000d310056978000000000000000014: Checksum error at offset > 4397954425856 > Couldn't read volume group metadata from > /dev/mapper/36000d310056978000000000000000014. > Metadata location on /dev/mapper/36000d310056978000000000000000014 at > 4397954425856 has invalid summary for VG. > Failed to read metadata summary from > /dev/mapper/36000d310056978000000000000000014 > Failed to scan VG from /dev/mapper/36000d310056978000000000000000014 > > I have tired the following steps: > 1. Restarted ovirt-engine.service > 2. tried to restore the metadata using vgcfgrestore but it failed with the > following error: > > [root@uk1-ion-ovm-19 backup]# vgcfgrestore > 36000d310056978000000000000000014 > Volume group 36000d310056978000000000000000014 has active volume: . > WARNING: Found 1 active volume(s) in volume group > "36000d310056978000000000000000014". > Restoring VG with active LVs, may cause mismatch with its metadata. > Do you really want to proceed with restore of volume group > "36000d310056978000000000000000014", while 1 volume(s) are active? [y/n]: y > /dev/mapper/36000d310056978000000000000000014: Checksum error at offset > 4397954425856 > Couldn't read volume group metadata from > /dev/mapper/36000d310056978000000000000000014. > Metadata location on /dev/mapper/36000d310056978000000000000000014 at > 4397954425856 has invalid summary for VG. > Failed to read metadata summary from > /dev/mapper/36000d310056978000000000000000014 > Failed to scan VG from /dev/mapper/36000d310056978000000000000000014 > /etc/lvm/backup/36000d310056978000000000000000014: stat failed: No such > file or directory > Couldn't read volume group metadata from file. > Failed to read VG 36000d310056978000000000000000014 from > /etc/lvm/backup/36000d310056978000000000000000014 > Restore failed. > > Please let me know if anyone knows any possible resolution. > > -AMinur > _______________________________________________ > 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/ > <https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > <https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt…> > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/W2JP7ZO5XMV66… > <https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovi…> > > > > > -- > > Regards, > > Eyal Shenitzky > -- Regards, Eyal Shenitzky

1 0

oVirt survey - May 2019
by Sandro Bonazzola 10 Jun '19

10 Jun '19

As we continue to develop oVirt 4.3 and future releases, the Development and Integration teams at Red Hat would value insights on how you are deploying the oVirt environment. Please help us to hit the mark by completing this short survey. Survey will close on June 7th. If you're managing multiple oVirt deployments with very different use cases or very different deployments you can consider answering this survey multiple times. Please note the answers to this survey will be publicly accessible. This survey is under oVirt Privacy Policy available at https://www.ovirt.org/site/privacy-policy.html The survey is available here: https://forms.gle/8uzuVNmDWtoKruhm8 -- 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>

1 1

Re: [ovirt-devel] cannot add host (oVirt 4.3.3.7)
by Nir Soffer 10 Jun '19

10 Jun '19

On Sun, Jun 9, 2019 at 9:15 PM Hetz Ben Hamo <hetz(a)hetz.biz> wrote: Moving to users list, devel list is for discussion about oVirt development, not troubleshooting. I'm trying to add a new host to oVirt. The main host is Xeon E5 while the > new host is AMD Ryzen 5. > > The main host is running oVirt 4.3.3 and the new node is a minimal install > of CentOS 7.6 (1810) with all the latest updates. > Which engine version? on which OS? I'm enclosing the log files. it complains that it cannot get the oVirt > packages, perhaps wrong channel(?). Looking at the log, it's trying to use > minidnf. I don't think CentOS 7 supports DNF.. > Did you install ovirt-release43 rpm before adding the host? https://ovirt.org/download/ Nir

3 4

Re: Clusters run virtual machines or Red Hat Gluster Storage Servers
by Strahil 10 Jun '19

10 Jun '19

OVirt + Gluster is called 'Hyperconverged' setup and it supports only replica3 or a 'replica3 arbiter1' volumes. Vmware VSAN is another popular Hyperconverged Setup but requires a lot of licenses. The CPU and Disk resources are plenty on virtualization Hosts and this setup allows you to save space by removal of the iSCSI/NFS/SAN dedicated system. The setup is quite popular and it works quite well, but requires a 10G network (as load balancing smaller NICs is very hard ) - if performance is required, while even a 1 gbit/s NIC is possible to be used. Note: 1gbit/s will provide no more than 87 MB/s on gluster level for all your VMs , which is very poor. If you have 4 hosts -> one of them will not be in the gluster setup, or you will have 2 separate gluster volumes like this: oVirt1- Replica for volume A oVirt2- Replica for volume A , arbiter for volume B oVirt3 - Replica for volume B,arbiter for volume A oVirt4 - Replica for volume B Then you add them as hosts in your oVirt setup. Best Regards, Strahil NikolovOn Jun 10, 2019 05:29, xilazz(a)126.com wrote: > > Hi, everybody. When I was looking at the administrator's manual, it prompted Clusters run virtual machines or Red Hat Gluster Storage Servers. These two purposes are mad exclusive: > Virtualization and storage hosts together. When I configured the cluster, I said that the glusterfs and virt I saw were alternatives to the two checkboxes. > I would like to ask what happens when glusterfs and virt are in the same cluster? > How can I use hosted engine when I have four nodes? > Thank you very much for your reply. > _______________________________________________ > 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/CZR73TNWNRE5L…

2 1

Clusters run virtual machines or Red Hat Gluster Storage Servers
by xilazz＠126.com 10 Jun '19

10 Jun '19

Hi, everybody. When I was looking at the administrator's manual, it prompted Clusters run virtual machines or Red Hat Gluster Storage Servers. These two purposes are mad exclusive: Virtualization and storage hosts together. When I configured the cluster, I said that the glusterfs and virt I saw were alternatives to the two checkboxes. I would like to ask what happens when glusterfs and virt are in the same cluster? How can I use hosted engine when I have four nodes? Thank you very much for your reply.

1 0

run ovirt without firewalld
by Chris Boon 08 Jun '19

08 Jun '19

Hello, When i deploy and use oVirt 4.3, is firewalld really needed on hypervisors or can oVirt 4.3 run and function with a disabled firewalld? Regards, Chris

1 0

oVirt hosted engine lost superblocks, need to recover data - 4.1
by marcushershberger＠locl.net 07 Jun '19

07 Jun '19

I have been working on this a few days now, though no solution seems to have emerged. I have an oVirt 4.1 hosted engine that is now failing to boot except into emergency mode. When xfs_repair is run, it gives an error saying that the primary and secondary superblocks are bad. Earlier this week, I was trying to install engine-backup because there were problems with the root partition being full. I was working on resolving dependencies for engine-backup when the hosted engine became unresponsive with an output about gov0 (which I believe is related to gluster), and I have not been able to boot it correctly since then. I am able to mount /var, and I have access to it, but that is not true for the root partition. What are some suggestions for recovering the data on the root partition? Thanks!

1 0