- Users - oVirt List Archives

Support and suggestions for 10/25 GbE cards
by Gianluca Merlo 17 Jul '19

17 Jul '19

Hello everyone, I am in the hardware selection phase for an oVirt cluster which has a requirement for 10/25 GbE connectivity. Does anyone have any advice on which adapters are better supported and working on oVirt Node? The choice I have is between: - Intel XXV710 - Mellanox ConnectX-4 It is my first foray into this tier of connectivity, so pardon the naivety of the question. I would just like to hear suggesions from the experience any of you may have had in the field, so I can be better prepared and know which kind of problems I may run into, and if choosing a specific card over the other can spare me some. Thank you in advance for your help Gianluca

1 0

hosted engine, Hyperconverged recovery
by William Kwan 17 Jul '19

17 Jul '19

Hi, I need some direction to make sure we won't make more mistake in recovering a 3-node self hosted engine with Gluster. Someone carelessly, very, wiped out the first few MB of the LVM PV on one node. We changed the quorum and brought up the Gluster and oVirt. We ran vgcfgrestore on the 'bad node' and we can run pvscan, vgscan and lvscan to see the LV's. What should I do next to prevent more damage or corrupt the glusterfs on the other two nodes? Will this work? mkfs the LV's bring up gluster run gluster sync <goodNode>? ThanksWill

3 2

VM says paused, but does not appear to be.
by Jacob Green 17 Jul '19

17 Jul '19

I have a Fibre Channel back end for my oVirt cluster, and one of my VMS is saying "paused due to lack of storage space", however I can confirm that the back end storage has plenty of space and the VM itself does not appear to be paused. I can SSH the VM and perform tasks on the VM. So I am trying to figure out why it would say that, and how to clear it. Also have 20 something other VMS on this cluster and no errors like this on those. I am running engine 4.3.3.7-1.el7 Also I do not fully understand this chart, what I can tell you is that the top storage domain is my Fibre Channel storage, and it has plenty of available space, 35%-40% free And lastly this is what a df -h looks like on the given VM. If anyone has some insight on to what might cause this let me know and ill chase it down. Thank you

1 0

Re: Hardware Used
by Strahil 17 Jul '19

17 Jul '19

As far as I know several orgs are using AMD Ryzen CPUs with oVirt. Ryzen CPUs are quite nice from price/performance perspective. Best Regards, Strahil NikolovOn Jul 17, 2019 15:04, Michal Skrivanek <michal.skrivanek(a)redhat.com> wrote: > > > >> On 16 Jul 2019, at 15:10, Adrian Odendaal <adrian(a)quodes.co.za> wrote: >> > No well we saw that only CPU’s are supported. > > So we want to find out what hardware we need in order to progress. > > Servers with the needed CPU architecture. > > Not sure what you’re looking for. A developer kind of answer - you got that already. If you want anything better I suggest you talk to a vendor who sells oVirt for a living and help you with the right architecture fitting your needs. > List of certified Intel CPUs for RHEL (and hence CentOS) is here [1] and here[2]. We also support IBM POWER8 and POWER9, and if you wanna start something really big, IBM zSystem mainframes as a tech preview;-) > > Thanks, > michal > > [1] https://access.redhat.com/support/policy/intel > [2] https://access.redhat.com/support/policy/amd > >> >> Kind Regards >> >> >> <bcard.jpg> >> >> >> >> >> >> Legal Disclaimer:

2 1

Re: Hardware Used
by Emil Natan 17 Jul '19

17 Jul '19

I think the right place for this question is the ovirt users mailing list. Added. On Mon, Jul 15, 2019 at 10:28 AM <adrian(a)quodes.co.za> wrote: > Hi All > > We are looking into setting up a highly scalable and HA Ovirt > infrastructure but I see only some CPU's are supported. Is this only for th > Hypervisors or for the entire cluster? > _______________________________________________ > Infra mailing list -- infra(a)ovirt.org > To unsubscribe send an email to infra-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/infra@ovirt.org/message/X5MMJXN67LMBC… > -- Emil Natan RHV/CNV DevOps

3 6

Re: UI exception when changing Cluster in New VM window
by Strahil 17 Jul '19

17 Jul '19

Dear Sharon, I think you mean Marko Vrgotic. Best Regards, Strahil NikolovOn Jul 10, 2019 14:19, Sharon Gratch <sgratch(a)redhat.com> wrote: > > Hi Strahil, > > Based on the stuck trace in the UI log that you sent, I am pretty sure that this UI exception was already fixed on https://gerrit.ovirt.org/#/c/99463/ for oVirt 4.3.4. > So please follow Michal's suggestion to install latest 4.3.5 version for overcoming this issue. > > Thanks, > Sharon > > On Tue, Jul 9, 2019 at 8:19 PM Michal Skrivanek <michal.skrivanek(a)redhat.com> wrote: >> >> can you please try that on 4.3.5 and if it persist open a bug with that ui.log attached? >> >> thanks, >> michal >> >>> On 5 Jul 2019, at 16:06, Vrgotic, Marko <M.Vrgotic(a)activevideo.com> wrote: >>> >>> Hi Strahil, >>> >>> I tried what you said and I am still getting an exception. >>> >>> Correct me if I am wrong, but my expectation is following, when creating new VM: >>> Select cluster >>> Whether I want to use template or create brand new VM from scratch, list of templates and everything else specific to cluster I selected should be loaded >>> >>> Instead, I get the exception and have to refresh/reload the page. >>> >>> In short, when creating new VM, I am currently locked to a default loaded cluster, which in my case is avshared1. >>> >>> To give you bit more insight into configuration, here are the cluster details: >>> >>> <image001.png> >>> >>> Per cluster:

2 1

Re: ovirt_disk and ubuntu issues
by Vrgotic, Marko 16 Jul '19

16 Jul '19

Dear oVIrt, Even though I would like to get some insight into what could be reason this is no working, I did find a workaround: Instead of trying to get Ubuntu disk specified with ovirt_disk size, I used qemu-img resize to increase the disk size before importing it to oVIrt. This works, but it still going to present the problem if User eventually wants to increase for example disk from 40GBto 80GB. Kindly awaiting your reply. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic Sr. System Engineer @ System Administration m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> From: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com> Date: Wednesday, 10 July 2019 at 16:19 To: "users(a)ovirt.org" <users(a)ovirt.org> Subject: ovirt_disk and ubuntu issues Dear oVirt, I am downloading the ubuntu cloud image 16.04 and or 18.04: - name: "Download base cloud image from server" get_url: url: "{{ image_url }}" checksum: "sha256:{{ image_checksum }}" validate_certs: yes dest: "/tmp/{{ inventory_hostname_short }}.qcow2" delegate_to: localhost creating a 40GB HDD and attaching image to it: - name: "Create oVirt disk with base image (with 40Gb allocated)" ovirt_disk: name: "{{ inventory_hostname_short }}" interface: virtio size: 40GiB format: cow upload_image_path: "/tmp/{{ inventory_hostname_short }}.qcow2" storage_domain: ovirt_production wait: true delegate_to: localhost creating VM afterwards: - name: "Create new Ubuntu VMs from cloud image" delegate_to: localhost ovirt_vm: auth: "{{ ovirt_auth }}" name: "{{ inventory_hostname_short }}" disks: - name: "{{ inventory_hostname_short }}" graphical_console: protocol: vnc serial_console: true usb_support: true soundcard_enabled: false operating_system: "{{ operating_system_type }}" type: server nics: - name: nic1 profile_name: tenant1 interface: virtio nic_on_boot: true cloud_init: host_name: "{{ inventory_hostname }}" user_name: ubuntu authorized_ssh_keys: "{{ ssh_agent_pubkeys.stdout }}" state: "running" cluster: "{{ ovirt_cluster }}" when: inventory_hostname in groups['ubuntu-baker'] When VM gets created, I can see in oVIrt VM details disk created is 40GB. Executing df -h, gives me following: root@av3-ubuntu-18-base:/home/ubuntu# df -h Filesystem Size Used Avail Use% Mounted on udev 447M 0 447M 0% /dev tmpfs 92M 696K 92M 1% /run /dev/vda1 2.0G 1.3G 706M 65% / tmpfs 460M 0 460M 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 460M 0 460M 0% /sys/fs/cgroup /dev/vda15 105M 3.6M 101M 4% /boot/efi tmpfs 92M 0 92M 0% /run/user/1000 Initially I thought growpart or resize2fs is not triggered, but then running dmesg or fdisk /dev/vda, told me that physical disk size is still only size of the downloaded ubuntu cloud image. Disk /dev/vda: 2.2 GiB, 2361393152 bytes, 4612096 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Is this related to ovirt_disk module, or ubuntu and ovirt_disk, since I do not have this behavior with CentOS 7 images? Can you advise how to proceed, in case I am missing some configuration parameter or command to be run? The following Ubuntu images are used: ubuntu-16: image_url=https://cloud-images.ubuntu.com/xenial/current/xenial-server-clou… image_checksum=fda868058586b129c7fdb6472fe575e911f7c67551a6dc75966f2ec02201bdae ubuntu-18: image_url=https://cloud-images.ubuntu.com/bionic/current/bionic-server-clou… image_checksum=7d2b90022a169119d7726c0fefa1713acbead7cc36d282c879896fd89c5a6663 Kindly awaiting your reply. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic Sr. System Engineer @ System Administration m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> tel. +31 (0)35 677 4131

2 4

Moving Hosted Engine Storage
by Dan Poltawski 16 Jul '19

16 Jul '19

Hello, I've read various posts[1] on this list, but I must confess that I am still not entirely clear on the process for moving a hosted engine to a new storage domain (in my case I want to move from an existing NFS server to a new iSCSI target). Some of what i've read make me slightly concerned it's a risky operation and in my situation I am just prototyping and retaining the existing engine will be saving some time rather than mission critical. Is anyone able to outline the steps to me? thanks, Dan [1] https://lists.ovirt.org/pipermail/users/2017-June/082466.html ________________________________ The Networking People (TNP) Limited. Registered office: Network House, Caton Rd, Lancaster, LA1 3PE. Registered in England & Wales with company number: 07667393 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

2 1

Re: Update 4.2.8 --> 4.3.5
by Strahil 16 Jul '19

16 Jul '19

I'm addding gluster-users as I'm not sure if you can go gluster v3 -> v6 directly. Theoretically speaking , there should be no problem - but I don't know if you will observe any issues. @Gluster-users, Can someone share their thoughts about v3 to v6 migration ? Best Regards, Strahil NikolovOn Jul 11, 2019 14:05, Christoph Köhler wrote: > > Hello! > > We have a 4.2.8 environment with some managed gluster-volumes as storage > domains and we want to go up to 4.3.5. > > How is that procedure especially with the gluster nodes in ovirt that > are running 3.12.15? My fear is on the jump to gluster 6. Do the cluster > work if the first node (of three) is upgraded? And what about the > sequence - first the hypervisors or first gluster nodes? > > Is there anyone who had done this? > > Greetings! > Christoph Köhler > _______________________________________________ > 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/VWFS6YUKA77VP…

3 2

Can't oepn console to VM
by csi-laser＠cisco.com 16 Jul '19

16 Jul '19

Hi, When trying to open a console for my VM , I'm getting this error : [cid:image001.png@01D53732.4E21AD20] Can you please help ? Thanks in advance

1 1

VM status codes
by Mitja Mihelič 15 Jul '19

15 Jul '19

Hi! We are graphing certain parameters we collect from the engine database. We use following query to get the count of running VMs: select count(*),cluster.name as cluster from vms, cluster where vms.cluster_id = cluster.cluster_id and vms.status = 1 group by cluster; It would help extremely if we knew what the numeric VM status codes mean. For example, I know that "status = 1" means the VM is running. The ones we can cause through the web interface are easy enough to figure out. But there are error states, that cannot be produced by standard use. For instance, when the event log says "VM foobar has been paused due to storage I/O problem." the following states get set in the DB (Query used: select * from vm_dynamic where vm_guid =(select vm_guid from vm_static where vm_name = 'foobar';): status | 4 exit_status | 0 pause_status | 2 guest_agent_status | 0 What do they mean? If you could point me to a table somewhere with the state descriptions it would be extremely helpful. Kind regards, Mitja Mihelič

2 2

SSH Authorized_keys
by Vrgotic, Marko 15 Jul '19

15 Jul '19

Dear oVIrt, Would it be possible to utilize SSH Pub key from User config [cid:image001.png@01D53B2B.0E387070] In such a way that it is offered or autoloaded into Cloud-init SSH Authorized keys field when exists? This would bring one less action required before VM can be created. Kindly awaiting your reply. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic

1 0

Re: ovirt-engine-appliance ova
by Strahil 15 Jul '19

15 Jul '19

Exactly. Ovirt (and RHV respectively) can be installed as: 1. VM in an oVirt Cluster 2. Separate machine(s) In point 2 , the Virt admin should take care about the high availability of the engine. So, you can install CentOS7 and then deploy the engine's software ontop of it. Extracting the OVA will not provide you with fully working engine, as the deployment scripts on the hosts will not inject the necessary data on remote system. (Only on local) Best Regards, Strahil NikolovOn Jul 15, 2019 04:08, Jingjie Jiang <jingjie.jiang(a)oracle.com> wrote: > > > On 7/13/2019 6:28 AM, Strahil Nikolov wrote: > > I still don't get why you need the OVA . > Are you trying to extract and put it into another virtualization. If this is your intention - better install it as if it was a standalone engine. > > Yes, I am trying to build ova with different OS. > > What do you mean install it as standalone engine? > > install VM first then install as ovirt engine? > > > Thanks, > > Jingjie > > >> >> Best Regards, >> Strahil Nikolov. >> >> В петък, 12 юли 2019 г., 21:48:35 ч. Гринуич+3, Jingjie Jiang <jingjie.jiang(a)oracle.com> написа: >> >> >> Hi Strahil, >> >> Thanks for your reply. >> >> Can you share the procedure of creating ovirt-engine-appliance ova? >> >> >> Thanks, >> >> Jingjie >> >> >> On 7/12/19 12:52 AM, Strahil wrote: >> >> Based on my experience - the OVA contains the xml and the actual disk of the hosted engine. >> Then the deployment starts locally the VM and populates the necessary data in it >> Once it's over , the deployment shuts down and copies the disk of that local VM, undefines it and then ovirt's ha agents are being configured - so they can mount the shared storage and power up the VM (special tar /OVMF/ file on shared storage has the agent configuration file). >> >> So , in the ova there should be a template VM + the xml config (cpus, ram, devices, etc) . >> I would be surprised if there is something else in it. >> >> Best Regards, >> Strahil Nikolov >> >> On Jul 11, 2019 23:39, Jingjie Jiang <jingjie.jiang(a)oracle.com> wrote:

1 0

Add Instance_type option for VM Portal
by Vrgotic, Marko 15 Jul '19

15 Jul '19

Dear oVIrt, We are relying on Templates more and more, which is great. Images/templates built using “official” cloud images usually have 1CPU and 1GB of RAM. Using this feature via Administration portal is super, since we can attach Instance_type to template to provide sufficient CPU and RAM, regardless of via UI or using Ansible. Would it be possible to consider adding Instance_Type option to Create New VM options in VM Portal? Haven’t tested yet, but is Instance_type supported via ovirt_vm ansible module, in case of EndUser privileges? Kindly awaiting your reply. — — — Met vriendelijke groet / Kind regards, Marko Vrgotic Sr. System Engineer @ System Administration m.vrgotic(a)activevideo.com<mailto:m.vrgotic@activevideo.com> tel. +31 (0)35 677 4131 ActiveVideo BV Mediacentrum 3741 Joop van den Endeplein 1 1217 WJ Hilversum

1 0

iptables with 4.3+?
by Jordan Conway 15 Jul '19

15 Jul '19

Hello, I'm working on migrating an existing ovirt setup to a new hosted-engine setup and I've been seeing messages about iptables support being deprecated and slated to be removed. Can I continue using iptables to manage the firewalls on my ovirt hosts if I don't care about allowing ovirt to configure the firewalls? We manage all of our machines with puppet and iptables is deeply integrated into this. It would be non-trivial to migrate to firewalld support. As it stands I already manage the firewall rules for our ovirt hosts with puppet and iptables and have always ignored the "Automatically Configure Firewall" option when adding new hosts. Will this continue to work? Also with hosted engine, I had to cowboy enable firewalld to get the engine installed, but now that I've got a cluster up and running with hosted engine enabled on several hosts, can I just switch back from firewalld to iptables assuming I've got all the correct ports open? Thank you, Jordan Conway

4 3

Re: ovirt-engine-appliance ova
by Strahil 15 Jul '19

15 Jul '19

Based on my experience - the OVA contains the xml and the actual disk of the hosted engine. Then the deployment starts locally the VM and populates the necessary data in it Once it's over , the deployment shuts down and copies the disk of that local VM, undefines it and then ovirt's ha agents are being configured - so they can mount the shared storage and power up the VM (special tar /OVMF/ file on shared storage has the agent configuration file). So , in the ova there should be a template VM + the xml config (cpus, ram, devices, etc) . I would be surprised if there is something else in it. Best Regards, Strahil NikolovOn Jul 11, 2019 23:39, Jingjie Jiang <jingjie.jiang(a)oracle.com> wrote: > > Hi Strahil, > > Yes, you are right. > > After install ovirt-engine-appliance rpm, the ova file will be save at /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.3-20190610.1.el7.ova > > I was trying to understand what the ova file included. > > I thought it only has the CentOS7.6. > > I observed that ovirt-engine was installed during "host-engine --deploy" > > Is ovirt-engine-appliance-4.3-20190610.1.el7.ova only used for deploy host-engine? > > Is there a document about how to generate? > > > Thanks, > > Jingjie > > > On 7/11/19 4:20 PM, Strahil Nikolov wrote: > > If I'm not wrong, this rpm is being downloaded to one of the hosts during self-hosted engine's deployment. > Why would you try to import a second self-hosted engine ? > > Best Regards, > Strahil Nikolov > > > В четвъртък, 11 юли 2019 г., 22:37:56 ч. Гринуич+3, <jingjie.jiang(a)oracle.com> написа: > > > Hi, > Can someone tell me how to generate ovirt-engine-appliance ova file in ovirt-engine-appliance-4.3-20190610.1.el7.x86_64.rpm? > I tried to import ovirt-engine-appliance ova(ovirt-engine-appliance-4.3-20190610.1.el7.ova) from ovirt-engine, but I got error as following: > Failed to load VM configuration from OVA file: /var/tmp/ovirt-engine-appliance-4.2-20190121.1.el7.ova > > I guess ovirt-engine-appliance-4.2-20190121.1.el7.ova has more than CentOS7.6. > > Thanks, > Jingjie > _______________________________________________ > 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/EP2BMVXRXUM6F…" rel="nofollow" target="_blank" moz-do-not-send="true">https://lists.ovirt.org/archives/list/users@o

3 3

hosted engine installation on iscsi multipath/mpath device fails
by Michael Frank 14 Jul '19

14 Jul '19

Dear all, since several days i try to install the hosted engine initially to an iscsi multipath device without success. Some information on the environment: - Ovirt Version 4.3.3 - using two 10gbe interfaces as single lacp - bond for the ovirtmgmt interface - using two 10gbe storage interfaces on each hypervisor for iscsi storage -- each storage interface is configured without any lacp bonding or 802.1q tagging, etc (on the switches the vlan is configured; port based vlan) -- each storage interface lives in a serarate vlan were also the iscsi target is available, the iscsi target has 4x10ge interfaces -- so; each storage interface is connected to a iscsi target through a different vlan The documentation here is for me unclear: https://ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engi… <https://ovirt.org/documentation/self-hosted/chap-Deploying_Self-Hosted_Engi…> >Note: To specify more than one iSCSI target, you must enable multipathing before deploying the self-hosted engine. There is also a Multipath >Helper tool that generates a script to install and configure multipath with different options. This indicates for me that it should be possbile to install the HE directly on the /dev/mapper/mpath device which is availibale when I have prepared the host accordingly before installing the HE (log in to multiple iscsi targets, create proper multipath,conf, etc) - right ? I login to the two iscsi targets and get in sum 8 pathes, 4 from each interface and iscsi target. I have then the mpath device on the hypervisor available and i can mount the mpath device and put (test) data on it. In the cockpit interface the mount can also be activated and is recognized correctly. multipathd -ll and lsblk looks good. Everything seems to be fine. But when I run the "hosted-engine" --deploy, the last option while running the assistant is to enter the iscsi data. So, basically i just want to define my mpath device - when entering the data for one of my iscsi target I can see the 4 pathes of the single target, and when i choose the path where the "lun" is finally available it fails. I think in general this option is not that what i want to have here for using the multipath device. I' m lost - what is the usual way to install the HE on a mutlipath device ? Do I have to change the configuration of the storage interfaces or the iscsi network design? - Are bond interfaces for these iscsi connections mandatory ? Did I missed something obvious ? Can I put in my multipath data into the answerfile somehow to get rid of the last step of the assistant ? Is it not possible in general ?? : https://bugzilla.redhat.com/show_bug.cgi?id=1193961 <https://bugzilla.redhat.com/show_bug.cgi?id=1193961> Sorry in advance for the long mail .... 1!^^ br, michael

1 0

Re: System unable to recover after a crash
by Strahil 13 Jul '19

13 Jul '19

Hi Carl, I'd recommend you to avoid DNS & DHCP unless you oVirt infra consistes of hundreds of servers. It is far more reliable to use static IPs + /etc/hosts . As you could 'ssh' to the engine, check the logs - there should be a clue why it failed. Most probably it's related to the DNS/IP used. I think the devs can tell their opinion on Monday. Best Regards, Strahil NikolovOn Jul 13, 2019 15:08, carl langlois <crl.langlois(a)gmail.com> wrote: > > Hi > Thanks for the info. There have been some progress with the situation. So to make the story as short as possible we are in a process of changing our range of IP addresse to 10.8.X.X to 10.16.X.X for all of the ovirt infra. This implies a new DHCP server, new switchs etc etc. For now we went back to our old IP address ranges because we were not able to stabilize the system. > > So the last status using our new range of addresses was that gluster was all fine, the hosted engine domaine was moutning okey. I suspect DNS table was not properly updated.. but i am not 100% sure. But if we tried to used the new range of adrreses everything seems to be fine except that the hosted-engine always fail the "liveliness check" after going up. I was not able to solve this situation so i went back to our previous DHCP server. > > So i am not sure what is missing for the hosted-engine to use the DHCP server. Is there any hardcode config in the hosted-egnine that need to be updated when chaging DHCP server(i.e new address with the same hostname, new gateway..) > > More info on the test i did with the new DHCP server -- > All node have name resolution working. I am able to ssh to the hosted-engine > > Any suggestions will be appreciated as i am out of idea for now. Do i need to redo some sort of setup in the engine to take into account the range of address/new gateway? There is also a LDAP server access configure in the engine for username mapping.. > Carl > > > > > On Sat, Jul 13, 2019 at 6:31 AM Strahil Nikolov <hunter86_bg(a)yahoo.com> wrote: >> >> Can you mount the volume manually at another location ? >> Also, have you done any changes to Gluster ? >> >> Please provide "gluster volume info engine" . I have noticed the following in your logs: option 'parallel-readdir' is not recognized >> >> Best Regards, >> Strahil Nikolov >> >> В петък, 12 юли 2019 г., 22:30:41 ч. Гринуич+3, carl langlois <crl.langlois(a)gmail.com> написа: >> >> >> Hi , >> >> I am in state where my system does not recover from a major failure. I have pinpoint the probleme to be that the hosted engine storage domain is not able to mount >> >> I have a glusterfs containing the storage domain. but when it attempt to mount glusterfs to /rhev/data-center/mnt/glusterSD/ovhost1:_engine i get >> >> +------------------------------------------------------------------------------+ >> [2019-07-12 19:19:44.063608] I [rpc-clnt.c:1986:rpc_clnt_reconfig] 0-engine-client-2: changing port to 49153 (from 0) >> [2019-07-12 19:19:55.033725] I [fuse-bridge.c:4205:fuse_init] 0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.24 kernel 7.22 >> [2019-07-12 19:19:55.033748] I [fuse-bridge.c:4835:fuse_graph_sync] 0-fuse: switched to graph 0 >> [2019-07-12 19:19:55.033895] I [MSGID: 108006] [afr-common.c:537

1 0

Does Ovirt 4.3.4 have support for NFS 4/4.1/4.2 or pNFS
by Erick Perez 13 Jul '19

13 Jul '19

I have read the archives and the most recent discussion was 5 years ago. So I better ask again. My NAS runs Centos with NFS4.2 (and I am testing Ganesha in another server) Does Ovirt 4.3.4 have support for NFS 4/4.1/4.2 or pNFS Specially version 4.2 due to: Server-Side Copy: NFSv4.2 supports copy_file_range() system call, which allows the NFS client to efficiently copy data without wasting network resources. But this will only happen if the Ovirt (which I know is Centos based) supports NFS 4.2. Not sure If I update the NFS toolset on the Ovirt install, it will break something or worst.

3 2

System unable to recover after a crash
by carl langlois 13 Jul '19

13 Jul '19

Hi , I am in state where my system does not recover from a major failure. I have pinpoint the probleme to be that the hosted engine storage domain is not able to mount I have a glusterfs containing the storage domain. but when it attempt to mount glusterfs to /rhev/data-center/mnt/glusterSD/ovhost1:_engine i get +------------------------------------------------------------------------------+ [2019-07-12 19:19:44.063608] I [rpc-clnt.c:1986:rpc_clnt_reconfig] 0-engine-client-2: changing port to 49153 (from 0) [2019-07-12 19:19:55.033725] I [fuse-bridge.c:4205:fuse_init] 0-glusterfs-fuse: FUSE inited with protocol versions: glusterfs 7.24 kernel 7.22 [2019-07-12 19:19:55.033748] I [fuse-bridge.c:4835:fuse_graph_sync] 0-fuse: switched to graph 0 [2019-07-12 19:19:55.033895] I [MSGID: 108006] [afr-common.c:5372:afr_local_init] 0-engine-replicate-0: no subvolumes up [2019-07-12 19:19:55.033938] E [fuse-bridge.c:4271:fuse_first_lookup] 0-fuse: first lookup on root failed (Transport endpoint is not connected) [2019-07-12 19:19:55.034041] W [fuse-resolve.c:132:fuse_resolve_gfid_cbk] 0-fuse: 00000000-0000-0000-0000-000000000001: failed to resolve (Transport endpoint is not connected) [2019-07-12 19:19:55.034060] E [fuse-bridge.c:900:fuse_getattr_resume] 0-glusterfs-fuse: 2: GETATTR 1 (00000000-0000-0000-0000-000000000001) resolution failed [2019-07-12 19:19:55.034095] W [fuse-resolve.c:132:fuse_resolve_gfid_cbk] 0-fuse: 00000000-0000-0000-0000-000000000001: failed to resolve (Transport endpoint is not connected) [2019-07-12 19:19:55.034102] E [fuse-bridge.c:900:fuse_getattr_resume] 0-glusterfs-fuse: 3: GETATTR 1 (00000000-0000-0000-0000-000000000001) resolution failed [2019-07-12 19:19:55.035596] W [fuse-resolve.c:132:fuse_resolve_gfid_cbk] 0-fuse: 00000000-0000-0000-0000-000000000001: failed to resolve (Transport endpoint is not connected) [2019-07-12 19:19:55.035611] E [fuse-bridge.c:900:fuse_getattr_resume] 0-glusterfs-fuse: 4: GETATTR 1 (00000000-0000-0000-0000-000000000001) resolution failed [2019-07-12 19:19:55.047957] I [fuse-bridge.c:5093:fuse_thread_proc] 0-fuse: initating unmount of /rhev/data-center/mnt/glusterSD/ovhost1:_engine The message "I [MSGID: 108006] [afr-common.c:5372:afr_local_init] 0-engine-replicate-0: no subvolumes up" repeated 3 times between [2019-07-12 19:19:55.033895] and [2019-07-12 19:19:55.035588] [2019-07-12 19:19:55.048138] W [glusterfsd.c:1375:cleanup_and_exit] (-->/lib64/libpthread.so.0(+0x7e25) [0x7f51cecb3e25] -->/usr/sbin/glusterfs(glusterfs_sigwaiter+0xe5) [0x5632143bd4b5] -->/usr/sbin/glusterfs(cleanup_and_exit+0x6b) [0x5632143bd32b] ) 0-: received signum (15), shutting down [2019-07-12 19:19:55.048150] I [fuse-bridge.c:5852:fini] 0-fuse: Unmounting '/rhev/data-center/mnt/glusterSD/ovhost1:_engine'. [2019-07-12 19:19:55.048155] I [fuse-bridge.c:5857:fini] 0-fuse: Closing fuse connection to '/rhev/data-center/mnt/glusterSD/ovhost1:_engine'. [2019-07-12 19:19:56.029923] I [MSGID: 100030] [glusterfsd.c:2511:main] 0-/usr/sbin/glusterfs: Started running /usr/sbin/glusterfs version 3.12.11 (args: /usr/sbin/glusterfs --volfile-server=ovhost1 --volfile-server=ovhost2 --volfile-server=ovhost3 --volfile-id=/engine /rhev/data-center/mnt/glusterSD/ovhost1:_engine) [2019-07-12 19:19:56.032209] W [MSGID: 101002] [options.c:995:xl_opt_validate] 0-glusterfs: option 'address-family' is deprecated, preferred is 'transport.address-family', continuing with correction [2019-07-12 19:19:56.037510] I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2019-07-12 19:19:56.039618] I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with index 2 [2019-07-12 19:19:56.039691] W [MSGID: 101174] [graph.c:363:_log_if_unknown_option] 0-engine-readdir-ahead: option 'parallel-readdir' is not recognized [2019-07-12 19:19:56.039739] I [MSGID: 114020] [client.c:2360:notify] 0-engine-client-0: parent translators are ready, attempting connect on transport [2019-07-12 19:19:56.043324] I [MSGID: 114020] [client.c:2360:notify] 0-engine-client-1: parent translators are ready, attempting connect on transport [2019-07-12 19:19:56.043481] I [rpc-clnt.c:1986:rpc_clnt_reconfig] 0-engine-client-0: changing port to 49153 (from 0) [2019-07-12 19:19:56.048539] I [MSGID: 114020] [client.c:2360:notify] 0-engine-client-2: parent translators are ready, attempting connect on transport [2019-07-12 19:19:56.048952] I [rpc-clnt.c:1986:rpc_clnt_reconfig] 0-engine-client-1: changing port to 49153 (from 0) Final graph: without this mount point the ha-agent is not starting. the volume seem to be okey Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick ovhost1:/gluster_bricks/data/data 49152 0 Y 7505 Brick ovhost2:/gluster_bricks/data/data 49152 0 Y 3640 Brick ovhost3:/gluster_bricks/data/data 49152 0 Y 6329 Self-heal Daemon on localhost N/A N/A Y 7712 Self-heal Daemon on ovhost2 N/A N/A Y 4925 Self-heal Daemon on ovhost3 N/A N/A Y 6501 Task Status of Volume data ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: engine Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick ovhost1:/gluster_bricks/engine/engine 49153 0 Y 7514 Brick ovhost2:/gluster_bricks/engine/engine 49153 0 Y 3662 Brick ovhost3:/gluster_bricks/engine/engine 49153 0 Y 6339 Self-heal Daemon on localhost N/A N/A Y 7712 Self-heal Daemon on ovhost2 N/A N/A Y 4925 Self-heal Daemon on ovhost3 N/A N/A Y 6501 Task Status of Volume engine ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: iso Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick ovhost1:/gluster_bricks/iso/iso 49154 0 Y 7523 Brick ovhost2:/gluster_bricks/iso/iso 49154 0 Y 3715 Brick ovhost3:/gluster_bricks/iso/iso 49154 0 Y 6349 Self-heal Daemon on localhost N/A N/A Y 7712 Self-heal Daemon on ovhost2 N/A N/A Y 4925 Self-heal Daemon on ovhost3 N/A N/A Y 6501 Task Status of Volume iso ------------------------------------------------------------------------------ There are no active volume tasks Status of volume: vmstore Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick ovhost1:/gluster_bricks/vmstore/vmsto re 49155 0 Y 7532 Brick ovhost2:/gluster_bricks/vmstore/vmsto re 49155 0 Y 3739 Brick ovhost3:/gluster_bricks/vmstore/vmsto re 49155 0 Y 6359 Self-heal Daemon on localhost N/A N/A Y 7712 Self-heal Daemon on ovhost2 N/A N/A Y 4925 Self-heal Daemon on ovhost3 N/A N/A Y 6501 Task Status of Volume vmstore ------------------------------------------------------------------------------ There are no active volume tasks I am not sure what to look for at this point Any help would be really appreciated. Thanks Carl

3 3

"Actual timezone in guest doesn't match configuration" for Windows VMs since guest agent 4.3
by Matthias Leopold 12 Jul '19

12 Jul '19

Hi, the oVirt guest agent seems to report DST configuration for the timezone since version 4.3 (of the guest agent). this results in "Actual timezone in guest doesn't match configuration" messages in the UI for windows VMs because the timezone field can't be matched with oVirt configuration anymore (no DST flag). to me this looks like a bug. shall I report it? I know there was a similar thread at the beginning of May, but there was no solution mentioned. Matthias

2 3

An error has occurred during installation of Host
by lliujd＠gmail.com 11 Jul '19

11 Jul '19

Hello everyone, I have installed an 'oVirt Engine' by 'yum install ovirt-engine' and the engine runs fine after 'engine-setup'. But when I trying to add node host,some error occurred: 1st: An error has occurred during installation of Host node02: Yum Cannot queue package dmidecode: 'ascii' codec can't encode characters in position 143-147: ordinal not in range(128). 2ed: An error has occurred during installation of Host node02: Failed to execute stage 'Environment packages setup': 'ascii' codec can't encode characters in position 143-147: ordinal not in range(128). 3rd: Host node02 installation failed. Command returned failure code 1 during SSH session 'root@node02'. On host node02,package dmidecode has been installed: rpm -qa | grep dmidecode python-dmidecode-3.12.2-3.el7.x86_64 dmidecode-3.1-2.el7.x86_64 anyone can help ? Thanks !

2 2

Update 4.2.8 --> 4.3.5
by Christoph Köhler 11 Jul '19

11 Jul '19

Hello! We have a 4.2.8 environment with some managed gluster-volumes as storage domains and we want to go up to 4.3.5. How is that procedure especially with the gluster nodes in ovirt that are running 3.12.15? My fear is on the jump to gluster 6. Do the cluster work if the first node (of three) is upgraded? And what about the sequence - first the hypervisors or first gluster nodes? Is there anyone who had done this? Greetings! Christoph Köhler

1 0

Re: VM Migrations Failing
by Strahil 11 Jul '19

11 Jul '19

Power down the VM and reduce the memory a little bit but keep the maximum memory value the same or larger. Then power it up and extend the ram to the same value the VM had. It's a wild guess... So don't expect miracles. Best Regards, Strahil NikolovOn Jul 10, 2019 18:21, Michael Watters <wattersm(a)watters.ws> wrote: > > I need to migrate running VMs from one host in our cluster to another > however the task keeps failing any time I start a migration. The engine > logs show a few different errors as follows. > > 2019-07-10 09:53:19,440-04 ERROR > [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] > (ForkJoinPool-1-worker-2) [] Migration of VM 'vm1' to host > 'ovirt-node-production3' failed: VM destroyed during the startup. > > 2019-07-10 09:53:06,542-04 ERROR > [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] > (default task-51) [c1daf639-ff39-4397-b1bf-09426cacf72d] EVENT_ID: > VM_MIGRATION_FAILED(65), Migration failed due to a failed validation: > [Cannot migrate VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host ovirt-node-production3 did > not satisfy internal filter Memory.] (VM: vm2, Source: > ovirt-node-production2). > > I also checked the vdsm.log on the destination host which is showing an > error like this. > > ERROR (jsonrpc/2) [virt.vm] > (vmId='f5bb25a8-3176-40b6-b21b-f07ed1089b27') Alias not found for device > type balloon during migration at destination host (vm:5562) > > Does anybody know how to resolve this? The destination host is able to > run VMs and I've been able to move a few VMs by shutting down and doing > a restart however I'd like to do a live migration if possible. > > > > > > _______________________________________________ > 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/AWOTK2Q7OJGJX…

2 1

Manual Migration not working and Dashboard broken after 4.3.4 update
by Neil 11 Jul '19

11 Jul '19

Hi guys. I have two problems since upgrading from 4.2.x to 4.3.4 First issue is I can no longer manually migrate VM's between hosts, I get an error in the ovirt GUI that says "Could not fetch data needed for VM migrate operation" and nothing gets logged either in my engine.log or my vdsm.log Then the other issue is my Dashboard says the following "Error! Could not fetch dashboard data. Please ensure that data warehouse is properly installed and configured." If I look at my ovirt-engine-dwhd.log I see the following if I try restart the dwh service... 2019-07-09 11:48:04|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|0 hoursToKeepHourly|720 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|60 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.3.0 dwhAggregationDebug|false dwhUuid|dca0ebd3-c58f-4389-a1f8-6aecc20b1316 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** 2019-07-09 11:48:10|ETL Service Stopped 2019-07-09 11:49:59|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|0 hoursToKeepHourly|720 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|60 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.3.0 dwhAggregationDebug|false dwhUuid|dca0ebd3-c58f-4389-a1f8-6aecc20b1316 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** 2019-07-09 11:52:56|ETL Service Stopped 2019-07-09 11:52:57|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|0 hoursToKeepHourly|720 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|60 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.3.0 dwhAggregationDebug|false dwhUuid|dca0ebd3-c58f-4389-a1f8-6aecc20b1316 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** 2019-07-09 12:16:01|ETL Service Stopped 2019-07-09 12:16:45|ETL Service Started ovirtEngineDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbJdbcConnection|jdbc:postgresql://localhost:5432/ovirt_engine_history?sslfactory=org.postgresql.ssl.NonValidatingFactory hoursToKeepDaily|0 hoursToKeepHourly|720 ovirtEngineDbPassword|********************** runDeleteTime|3 ovirtEngineDbJdbcConnection|jdbc:postgresql://localhost:5432/engine?sslfactory=org.postgresql.ssl.NonValidatingFactory runInterleave|60 limitRows|limit 1000 ovirtEngineHistoryDbUser|ovirt_engine_history ovirtEngineDbUser|engine deleteIncrement|10 timeBetweenErrorEvents|300000 hoursToKeepSamples|24 deleteMultiplier|1000 lastErrorSent|2011-07-03 12:46:47.000000 etlVersion|4.3.0 dwhAggregationDebug|false dwhUuid|dca0ebd3-c58f-4389-a1f8-6aecc20b1316 ovirtEngineHistoryDbDriverClass|org.postgresql.Driver ovirtEngineHistoryDbPassword|********************** I have a hosted engine, and I have two hosts and my storage is FC based. The hosts are still running on 4.2 because I'm unable to migrate VM's off. I have plenty resources available in terms of CPU and Memory on the destination host, and my Cluster version is set to 4.2 because my hosts are still on 4.2 I have recently upgraded from 4.1 to 4.2 and then I upgraded my hosts to 4.2 as well, but I can't get my hosts to 4.3 because of the above migration issue. Below my ovirt packages installed... ovirt-ansible-cluster-upgrade-1.1.13-1.el7.noarch ovirt-ansible-disaster-recovery-1.1.4-1.el7.noarch ovirt-ansible-engine-setup-1.1.9-1.el7.noarch ovirt-ansible-hosted-engine-setup-1.0.20-1.el7.noarch ovirt-ansible-image-template-1.1.11-1.el7.noarch ovirt-ansible-infra-1.1.12-1.el7.noarch ovirt-ansible-manageiq-1.1.14-1.el7.noarch ovirt-ansible-repositories-1.1.5-1.el7.noarch ovirt-ansible-roles-1.1.6-1.el7.noarch ovirt-ansible-shutdown-env-1.0.3-1.el7.noarch ovirt-ansible-vm-infra-1.1.18-1.el7.noarch ovirt-cockpit-sso-0.1.1-1.el7.noarch ovirt-engine-4.3.4.3-1.el7.noarch ovirt-engine-api-explorer-0.0.5-1.el7.noarch ovirt-engine-backend-4.3.4.3-1.el7.noarch ovirt-engine-cli-3.6.9.2-1.el7.centos.noarch ovirt-engine-dbscripts-4.3.4.3-1.el7.noarch ovirt-engine-dwh-4.3.0-1.el7.noarch ovirt-engine-dwh-setup-4.3.0-1.el7.noarch ovirt-engine-extension-aaa-jdbc-1.1.10-1.el7.noarch ovirt-engine-extensions-api-impl-4.3.4.3-1.el7.noarch ovirt-engine-metrics-1.3.3.1-1.el7.noarch ovirt-engine-restapi-4.3.4.3-1.el7.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch ovirt-engine-setup-4.3.4.3-1.el7.noarch ovirt-engine-setup-base-4.3.4.3-1.el7.noarch ovirt-engine-setup-plugin-cinderlib-4.3.4.3-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.3.4.3-1.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.3.4.3-1.el7.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.3.4.3-1.el7.noarch ovirt-engine-setup-plugin-websocket-proxy-4.3.4.3-1.el7.noarch ovirt-engine-tools-4.3.4.3-1.el7.noarch ovirt-engine-tools-backup-4.3.4.3-1.el7.noarch ovirt-engine-ui-extensions-1.0.5-1.el7.noarch ovirt-engine-vmconsole-proxy-helper-4.3.4.3-1.el7.noarch ovirt-engine-webadmin-portal-4.3.4.3-1.el7.noarch ovirt-engine-websocket-proxy-4.3.4.3-1.el7.noarch ovirt-engine-wildfly-15.0.1-1.el7.x86_64 ovirt-engine-wildfly-overlay-15.0.1-1.el7.noarch ovirt-guest-agent-common-1.0.16-1.el7.noarch ovirt-guest-tools-iso-4.3-3.el7.noarch ovirt-host-deploy-common-1.8.0-1.el7.noarch ovirt-host-deploy-java-1.8.0-1.el7.noarch ovirt-imageio-common-1.5.1-0.el7.x86_64 ovirt-imageio-proxy-1.5.1-0.el7.noarch ovirt-imageio-proxy-setup-1.5.1-0.el7.noarch ovirt-iso-uploader-4.3.1-1.el7.noarch ovirt-js-dependencies-1.2.0-3.1.el7.centos.noarch ovirt-provider-ovn-1.2.22-1.el7.noarch ovirt-release41-4.1.9-1.el7.centos.noarch ovirt-release42-4.2.8-1.el7.noarch ovirt-release43-4.3.4-1.el7.noarch ovirt-vmconsole-1.0.7-2.el7.noarch ovirt-vmconsole-proxy-1.0.7-2.el7.noarch ovirt-web-ui-1.5.2-1.el7.noarch python2-ovirt-engine-lib-4.3.4.3-1.el7.noarch python2-ovirt-host-deploy-1.8.0-1.el7.noarch python2-ovirt-setup-lib-1.2.0-1.el7.noarch python-ovirt-engine-sdk4-4.3.1-2.el7.x86_64 [root@dell-ovirt ~]# rpm -qa | grep postgre rh-postgresql10-postgresql-contrib-10.6-1.el7.x86_64 rh-postgresql10-postgresql-10.6-1.el7.x86_64 postgresql-libs-9.2.24-1.el7_5.x86_64 collectd-postgresql-5.8.1-4.el7.x86_64 postgresql-server-9.2.24-1.el7_5.x86_64 rh-postgresql10-postgresql-server-10.6-1.el7.x86_64 rh-postgresql95-postgresql-9.5.14-1.el7.x86_64 rh-postgresql95-postgresql-contrib-9.5.14-1.el7.x86_64 postgresql-jdbc-9.2.1002-6.el7_5.noarch rh-postgresql10-runtime-3.1-1.el7.x86_64 rh-postgresql95-postgresql-libs-9.5.14-1.el7.x86_64 rh-postgresql10-postgresql-libs-10.6-1.el7.x86_64 postgresql-9.2.24-1.el7_5.x86_64 rh-postgresql95-runtime-2.2-2.el7.x86_64 rh-postgresql95-postgresql-server-9.5.14-1.el7.x86_64 I'm also seeing a strange error on my hosts when I log in showing... node status: DEGRADED Please check the status manually using `nodectl check` [root@host-a ~]# nodectl check Status: FAILED Bootloader ... OK Layer boot entries ... OK Valid boot entries ... OK Mount points ... OK Separate /var ... OK Discard is used ... OK Basic storage ... OK Initialized VG ... OK Initialized Thin Pool ... OK Initialized LVs ... OK Thin storage ... FAILED - It looks like the LVM layout is not correct. The reason could be an incorrect installation. Checking available space in thinpool ... OK Checking thinpool auto-extend ... FAILED - In order to enable thinpool auto-extend,activation/thin_pool_autoextend_threshold needs to be set below 100 in lvm.conf vdsmd ... OK I'm running CentOS Linux release 7.6.1810 (Core) These are my package versions on my hosts... [root@host-a ~]# rpm -qa | grep -i ovirt ovirt-release41-4.1.9-1.el7.centos.noarch ovirt-hosted-engine-ha-2.2.19-1.el7.noarch ovirt-host-deploy-1.7.4-1.el7.noarch ovirt-node-ng-nodectl-4.2.0-0.20190121.0.el7.noarch ovirt-vmconsole-host-1.0.6-2.el7.noarch ovirt-provider-ovn-driver-1.2.18-1.el7.noarch ovirt-engine-appliance-4.2-20190121.1.el7.noarch ovirt-release42-4.2.8-1.el7.noarch ovirt-release43-4.3.4-1.el7.noarch python-ovirt-engine-sdk4-4.2.9-2.el7.x86_64 cockpit-ovirt-dashboard-0.11.38-1.el7.noarch ovirt-imageio-daemon-1.4.6-1.el7.noarch ovirt-host-4.2.3-1.el7.x86_64 ovirt-setup-lib-1.1.5-1.el7.noarch ovirt-node-ng-image-update-4.2.8-1.el7.noarch ovirt-imageio-common-1.4.6-1.el7.x86_64 ovirt-vmconsole-1.0.6-2.el7.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch ovirt-host-dependencies-4.2.3-1.el7.x86_64 ovirt-release-host-node-4.2.8-1.el7.noarch cockpit-machines-ovirt-193-2.el7.noarch ovirt-hosted-engine-setup-2.2.33-1.el7.noarch [root@host-a ~]# rpm -qa | grep -i vdsm vdsm-http-4.20.46-1.el7.noarch vdsm-common-4.20.46-1.el7.noarch vdsm-network-4.20.46-1.el7.x86_64 vdsm-jsonrpc-4.20.46-1.el7.noarch vdsm-4.20.46-1.el7.x86_64 vdsm-hook-ethtool-options-4.20.46-1.el7.noarch vdsm-hook-vhostmd-4.20.46-1.el7.noarch vdsm-python-4.20.46-1.el7.noarch vdsm-api-4.20.46-1.el7.noarch vdsm-yajsonrpc-4.20.46-1.el7.noarch vdsm-hook-fcoe-4.20.46-1.el7.noarch vdsm-hook-openstacknet-4.20.46-1.el7.noarch vdsm-client-4.20.46-1.el7.noarch vdsm-gluster-4.20.46-1.el7.x86_64 vdsm-hook-vmfex-dev-4.20.46-1.el7.noarch I am seeing the following error every minute or so in my vdsm.log as follows.... 2019-07-09 12:50:31,543+0200 WARN (qgapoller/2) [virt.periodic.VmDispatcher] could not run <function <lambda> at 0x7f52b01b85f0> on ['9a6561b8-5702-43dc-9e92-1dc5dfed4eef'] (periodic:323) Then also under /var/log/messages.. Jul 9 12:57:48 host-a ovs-vsctl: ovs|00001|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) I'm not using ovn so I'm guessing this can be ignored. If I search for ERROR or WARN in my logs nothing relevant is logged Any suggestions on what to start looking for please? Please let me know if you need further info. Thank you. Regards. Neil Wilson

4 9