- Users - oVirt List Archives

ovirt 4.3.3 SELINUX issue
by Strahil Nikolov 14 May '19

14 May '19

Hello All, I want to warn you that selinux-policy & selinux-policy-targeted with version '3.13.1-229.el7_6.12' cause an issue with my HostedEngine where I got "Login incorrect" screen of death. I have also raised a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1710083 If you want to test your luck, increase the default grub timeout in "/etc/default/grub" to 15 and rebuild the grub menu via 'grub2-mkconfig -o /boot/grub2/grub.cfg' If the issue occurs to you - just append 'enforcing=0' to your kernel and the issue will be over.Of course, you can always rollback either from a rescue DVD or from the running 'enforcing=0' system. Best Regards,Strahil Nikolov

1 0

oVirt and Windows NFS
by ron＠prgstudios.com 14 May '19

14 May '19

Hi Everyone - Greetings from Detroit Michigan! Has anyone had any luck with using oVirt to connect to a Windows Server running an NFS service? I've made several attempts so far and am having problems getting the two to work together. I was hoping someone had some hints (besides the obvious "use Linux" bit). Thanks! Ron

3 2

Is teamd supported on 4.3?
by Valentin Bajrami 14 May '19

14 May '19

Hello guys, Next week, I'm planning to deploy ovirt-node 4.3 on a few hosts. I've been running bonds for the past years but I'd like to know if teaming (teamd) is also supported with this version. My current package version(s): OS Version: | RHEL - 7 - 6.1810.2.el7.centos OS Description: | oVirt Node 4.3.1 Kernel Version: | 3.10.0 - 957.5.1.el7.x86_64 KVM Version: | 2.12.0 - 18.el7_6.3.1 LIBVIRT Version: | libvirt-4.5.0-10.el7_6.4 VDSM Version: | vdsm-4.30.9-1.el7 SPICE Version: | 0.14.0 - 6.el7_6.1 GlusterFS Version: | glusterfs-5.3-2.el7 CEPH Version: | librbd1-10.2.5-4.el7 Open vSwitch Version: | openvswitch-2.10.1-3.el7 Kernel Features: | PTI: 1, IBRS: 0, RETP: 1 VNC Encryption: | Disabled Is anyone running teamd on this version ? Thanks in advance -- Kind regards / Met vriendelijke groet, Valentin Bajrami Target Holding

2 4

botched 3.6 -> 4.0/1/2 upgrade, how to recover
by Axel.Thimm＠01lgc.com 14 May '19

14 May '19

Hello, an old 3.6 self-hosted one-system installation was half upgraded to 4.0 and I took on the task to continue upgrading it. I managed to setup a new engine and upgraded step by step until 4.2 where the host needs to be upgraded. During that time the host was "non-responsive", but I though that this had to do with the upgrade process. Upon trying to upgrade the host the setup broke to pieces. I tried to downgrade everything and restart the old engine to no avail. I now try the way forward to try to start the new engine or create a complete new one, I don;t care much about the old engine's inherited information - all I need to to resurrect the VMs again. At the end of the day the setup is supposed to migrate to a three system hyperconverged setup anyway. How should I proceed to get a working state that fires up the VMs? Is it safe to install a hosted engine from scratch and reattach the domain? Probably the VM configuration will be lost and I will have to puzzle together the disks. I still have the 3.6 engine's backup file, if that is of any help. Should I perhaps recreate a 4.0 engine with that file and try to continue from there? I guess all information on which VMs are attached to which images etc are in the DB of the engine, so I either have to get this info off the 3.6 backup or wire them up again by inspection. BTW this is not a pure ovirt, but an RHV with self-evaluation support, but I believe that any pure ovirt solution will apply. Many thanks in advance.

5 10

Re: Is teamd supported on 4.3?
by Strahil 14 May '19

14 May '19

I'm using teaming and I don't see issues. Just cannot control the teaming device. Best Regards, Strahil NikolovOn May 13, 2019 22:26, Dominik Holler <dholler(a)redhat.com> wrote: > > On Mon, 13 May 2019 15:30:11 +0200 > Valentin Bajrami <valentin.bajrami(a)target-holding.nl> wrote: > > > Hello guys, > > > > Next week, I'm planning to deploy ovirt-node 4.3 on a few hosts. I've > > been running bonds for the past years but I'd like to know if teaming > > (teamd) is also supported with this version. > > > > No, unfortunately not. > May I ask why you want to use teaming instead of bonding? > > > > My current package version(s): > > > > OS Version: | RHEL - 7 - 6.1810.2.el7.centos > > OS Description: | oVirt Node 4.3.1 > > Kernel Version: | 3.10.0 - 957.5.1.el7.x86_64 > > KVM Version: | 2.12.0 - 18.el7_6.3.1 > > LIBVIRT Version: | libvirt-4.5.0-10.el7_6.4 > > VDSM Version: | vdsm-4.30.9-1.el7 > > SPICE Version: | 0.14.0 - 6.el7_6.1 > > GlusterFS Version: | glusterfs-5.3-2.el7 > > CEPH Version: | librbd1-10.2.5-4.el7 > > Open vSwitch Version: | openvswitch-2.10.1-3.el7 > > Kernel Features: | PTI: 1, IBRS: 0, RETP: 1 > > VNC Encryption: | Disabled > > > > Is anyone running teamd on this version ? > > > > Thanks in advance > > > _______________________________________________ > 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/XVFQQWUJK3QTV…

3 2

Ovirt Node transfer to New Engine (it is possible)
by IT INFRA 14 May '19

14 May '19

Hi, It is possible to transfer my node to other ovirt engine (new 4.3) here's the scenario. Old Server: (no internet prod) Engine (ovirt 4.1) - Hardware failure No possible recovery Node1 (node 4.1) Node2 (node 4.1) New Server Engine (Ovirt 4.3) *note have full backup of old engine 4.1 version\ * can't re install using yum install http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm (no more link available) any possible solution on this.. Thanks,

1 1

A "memory" issue when trying to start VM on oVirt 4.3
by Vrgotic, Marko 14 May '19

14 May '19

Dear oVirt, We are running 4.3.3 oVirt with SHE on three CentOS nodes for HA – with NFS storage. We also have two Local Storage DCs managed by same SHE. [cid:image001.png@01D50A59.F4276FD0] The issue we are reporting was present on 4.3.2 as well. The memory usage on both hosts (third one is in maintenance mode) does not go above 45%: [cid:image002.png@01D50A59.F4276FD0] I have also attached the UI Dashboard screenshot. However, when trying to start one VM: [cid:image003.png@01D50A59.F4276FD0] Engine reports that there is not enough memory and writes the following in the engine.log: 2019-05-14 11:23:10,809Z INFO [org.ovirt.engine.core.bll.RunVmCommand] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] Lock Acquired to object 'EngineLock:{exclusiveLocks='[13b2299f-b4b4-48e4-b2f9-09450eff235d=VM]', sharedLocks=''}' 2019-05-14 11:23:10,819Z INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] START, IsVmDuringInitiatingVDSCommand( IsVmDuringInitiatingVDSCommandParameters:{vmId='13b2299f-b4b4-48e4-b2f9-09450eff235d'}), log id: 5f80129f 2019-05-14 11:23:10,819Z INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 5f80129f 2019-05-14 11:23:10,833Z INFO [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] Candidate host 'ovirt-staging-hv-01' ('d81b296a-f3b2-49ea-9b4d-04c90f3508e9') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'Memory' (correlation id: null) 2019-05-14 11:23:10,833Z INFO [org.ovirt.engine.core.bll.scheduling.SchedulingManager] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] Candidate host 'ovirt-staging-hv-02' ('f4fdeccd-4cf4-4ed7-9eb1-d98ac65c4ce6') was filtered out by 'VAR__FILTERTYPE__INTERNAL' filter 'Memory' (correlation id: null) 2019-05-14 11:23:10,838Z ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] EVENT_ID: USER_FAILED_RUN_VM(54), Failed to run VM csm2-216-d due to a failed validation: [Cannot run VM. There is no host that satisfies current scheduling constraints. See below for details:, The host ovirt-staging-hv-01 did not satisfy internal filter Memory because its available memory is too low (0 MB) to run the VM., The host ovirt-staging-hv-01 did not satisfy internal filter Memory because its available memory is too low (0 MB) to run the VM.] (User: admin@internal-authz). 2019-05-14 11:23:10,838Z WARN [org.ovirt.engine.core.bll.RunVmCommand] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] Validation of action 'RunVm' failed for user admin@internal-authz. Reasons: VAR__ACTION__RUN,VAR__TYPE__VM,SCHEDULING_ALL_HOSTS_FILTERED_OUT,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-staging-hv-01,$filterName Memory,$availableMem 0,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL,VAR__FILTERTYPE__INTERNAL,$hostName ovirt-staging-hv-02,$filterName Memory,$availableMem 0,VAR__DETAIL__NOT_ENOUGH_MEMORY,SCHEDULING_HOST_FILTERED_REASON_WITH_DETAIL 2019-05-14 11:23:10,838Z INFO [org.ovirt.engine.core.bll.RunVmCommand] (default task-14) [63aa9817-80fd-4b18-8c86-26c910a2954a] Lock freed to object 'EngineLock:{exclusiveLocks='[13b2299f-b4b4-48e4-b2f9-09450eff235d=VM]', sharedLocks=''}' Current memory optimization is set to “None” Please let me know if you need additional log files. Kindly awaiting your reply. Marko Vrgotic Sr. System Engineer

1 0

Re: oVirt and Windows NFS
by Strahil 14 May '19

14 May '19

Get a vanilla CentOS7 and try to access the shares to Windows. Is windows in AD ? Best Regards, Strahil NikolovOn May 14, 2019 01:31, ron(a)prgstudios.com wrote: > > Hi Everyone - Greetings from Detroit Michigan! > > Has anyone had any luck with using oVirt to connect to a Windows Server running an NFS service? > > I've made several attempts so far and am having problems getting the two to work together. I was hoping someone had some hints (besides the obvious "use Linux" bit). > > Thanks! > > Ron > _______________________________________________ > 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/BH4KT3ODZYEGT…

1 0

Re: Gluster volume heals and after 5 seconds has /dom_md/ids dirty again
by Strahil 14 May '19

14 May '19

I have just noticed this behaviour. I stopped and redesigned my brick (addded vdo layer) and after the heal (1000+ entries got sync) the dom_ids need healing. Running 'gluster volume heal volume_name full' heals the file and 1 min later it happens again. I will try to do a rolling reboot and see if the issues got fixes. Best Regards, Strahil NikolovOn May 13, 2019 18:14, Darrell Budic <budic(a)onholyground.com> wrote: > > I see this sometimes after rebooting a server, and it usually stops happening, generally within a few hours, I’ve never tracked it down further. Don’t know for sure, but I assume it’s related to healing and goes away once everything syncs up. > > Occasionally it turns out to be a communications problem between servers (usually an update to something screws up my firewall), so I always check my peer status when I see it and make sure all servers are talking to each other. > > > On May 13, 2019, at 4:13 AM, Andreas Elvers <andreas.elvers+ovirtforum(a)solutions.work> wrote: > > > > I restored my engine to a gluster volume named :/engine on a three node hyperconverged oVirt 4.3.3.1 cluster. Before restoring I was checking the status of the volumes. They were clean. No heal entries. All peers connected. gluster volume status looked good. Then I restored. This went well. The engine is up. But the engine gluster volume shows entries on node02 and node03. The engine was installed to node01. I have to deploy the engine to the other two hosts to reach full HA, but I bet maintenance is not possible until the volume is healed. > > > > I tried "gluster volume heal engine" also with added "full". The heal entries will disappear for a few seconds and then /dom_md/ids will pop up again. The __DIRECT_IO_TEST__ will join later. The split-brain info has no entries. Is this some kind of hidden split brain? Maybe there is data on node01 brick which got not synced to the other two nodes? I can only speculate. Gluster docs say: this should heal. But it doesn't. I have two other volumes. Those are fine. One of them containing 3 VMs that are running. I also tried to shut down the engine, so no-one was using the volume. Then heal. Same effect. Those two files will always show up. But none other. Heal can always be started successfully from any of the participating nodes. > > > > Reset the volume bricks one by one and cross fingers? > > > > [root@node03 ~]# gluster volume heal engine info > > Brick node01.infra.solutions.work:/gluster_bricks/engine/engine > > Status: Connected > > Number of entries: 0 > > > > Brick node02.infra.solutions.work:/gluster_bricks/engine/engine > > /9f4d5ae9-e01d-4b73-8b6d-e349279e9782/dom_md/ids > > /__DIRECT_IO_TEST__ > > Status: Connected > > Number of entries: 2 > > > > Brick node03.infra.solutions.work:/gluster_bricks/engine/engine > > /9f4d5ae9-e01d-4b73-8b6d-e349279e9782/dom_md/ids > > /__DIRECT_IO_TEST__ > > Status: Connected > > Number of entries: 2 > > _______________________________________________ > > 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/L3YCRPRAGPUMB… > _______________________________________________ > 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/6XOCRXRCQOUKE…

1 0

Gluster volume heals and after 5 seconds has /dom_md/ids dirty again
by Andreas Elvers 14 May '19

14 May '19

I restored my engine to a gluster volume named :/engine on a three node hyperconverged oVirt 4.3.3.1 cluster. Before restoring I was checking the status of the volumes. They were clean. No heal entries. All peers connected. gluster volume status looked good. Then I restored. This went well. The engine is up. But the engine gluster volume shows entries on node02 and node03. The engine was installed to node01. I have to deploy the engine to the other two hosts to reach full HA, but I bet maintenance is not possible until the volume is healed. I tried "gluster volume heal engine" also with added "full". The heal entries will disappear for a few seconds and then /dom_md/ids will pop up again. The __DIRECT_IO_TEST__ will join later. The split-brain info has no entries. Is this some kind of hidden split brain? Maybe there is data on node01 brick which got not synced to the other two nodes? I can only speculate. Gluster docs say: this should heal. But it doesn't. I have two other volumes. Those are fine. One of them containing 3 VMs that are running. I also tried to shut down the engine, so no-one was using the volume. Then heal. Same effect. Those two files will always show up. But none other. Heal can always be started successfully from any of the participating nodes. Reset the volume bricks one by one and cross fingers? [root@node03 ~]# gluster volume heal engine info Brick node01.infra.solutions.work:/gluster_bricks/engine/engine Status: Connected Number of entries: 0 Brick node02.infra.solutions.work:/gluster_bricks/engine/engine /9f4d5ae9-e01d-4b73-8b6d-e349279e9782/dom_md/ids /__DIRECT_IO_TEST__ Status: Connected Number of entries: 2 Brick node03.infra.solutions.work:/gluster_bricks/engine/engine /9f4d5ae9-e01d-4b73-8b6d-e349279e9782/dom_md/ids /__DIRECT_IO_TEST__ Status: Connected Number of entries: 2

3 11