Re: [ovirt-users] Seamless SAN HA failovers with oVirt?
Thanks for the replies, all! Yep, Chris is right. TrueNAS HA is active/passive and there isn't a way around that when failing between heads. Sven: In my experience with iX support, they have directed me to reboot the active node to initiate failover. There's "hactl takeover" and "hactl giveback" commends, but reboot seems to be their preferred method. VMs going into a paused state and resuming when storage is back online sounds great. As long as oVirt's pause/resume isn't significantly slower than the 30-or-so seconds the TrueNAS takes to complete its failover, that's a pretty tolerable interruption for my needs. So my next questions are: 1) Assuming the SAN failover DOES work correctly, can anyone comment on their experience with oVirt pausing/thawing VMs in an NFS-based active/passive SAN failover scenario? Does it work reliably without intervention? Is it reasonably fast? 2) Is there anything else in the oVirt stack that might cause it to "freak out" rather than gracefully pause/unpause VMs? 2a) Particularly: I'm running hosted engine on the same TrueNAS storage. Does that change anything WRT to timeouts and oVirt's HA and fencing and sanlock and such? 2b) Is there a limit to how long oVirt will wait for storage before doing something more drastic than just pausing VMs? -- Matthew Trent Network Engineer Lewis County IT Services 360.740.1247 - Helpdesk 360.740.3343 - Direct line From: users-boun...@ovirt.org on behalf of Chris Adams Sent: Tuesday, June 6, 2017 7:21 AM To: users@ovirt.org Subject: Re: [ovirt-users] Seamless SAN HA failovers with oVirt? Once upon a time, Juan Pablo said: > Chris, if you have active-active with multipath: you upgrade one system, > reboot it, check it came active again, then upgrade the other. Yes, but that's still not how a TrueNAS (and most other low- to mid-range SANs) works, so is not relevant. The TrueNAS only has a single active node talking to the hard drives at a time, because having two nodes talking to the same storage at the same time is a hard problem to solve (typically requires custom hardware with active cache coherency and such). You can (and should) use multipath between servers and a TrueNAS, and that protects against NIC, cable, and switch failures, but does not help with a controller failure/reboot/upgrade. Multipath is also used to provide better bandwidth sharing between links than ethernet LAGs. -- Chris Adams ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Seamless SAN HA failovers with oVirt?
I'm using two TrueNAS HA SANs (FreeBSD-based ZFS) to provide storage via NFS to 7 oVirt boxes and about 25 VMs. For SAN system upgrades I've always scheduled a maintenance window, shut down all the oVirt stuff, upgraded the SANs, and spun everything back up. It's pretty disruptive, but I assumed that was the thing to do. However, in talking with the TrueNAS vendor they said the majority of their customers are using VMWare and they almost always do TrueNAS updates in production. They just upgrade one head of the TrueNAS HA pair then failover to the other head and upgrade it too. There's a 30-ish second pause in I/O while the disk arrays are taken over by the other HA head, but VMWare just tolerates it and continues without skipping a beat. They say this is standard procedure in the SAN world and virtualization systems should tolerate 30-60 seconds of I/O pause for HA failovers seamlessly. It sounds great to me, but I wanted to pick this lists' brain -- is anyone doing this with oVirt? Are you able to failover your HA SAN with 30-60 seconds of no I/O without oVirt freaking out? If not, are there any tunables relating to this? I see the default NFS mount options look fairly tolerant (proto=tcp,timeo=600,retrans=6), but are there VDSM or sanlock or some other oVirt timeouts that will kick in and start putting storage domains into error states, fencing hosts or something before that? I've never timed anything, but I want to say my past experience is that ovirt hosted engine started showing errors almost immediately when we've had SAN issues in the past. Thanks! -- Matthew Trent Network Engineer Lewis County IT Services ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] SR-IOV: "ethX" interfaces not getting cleaned-up and virtio stops working
I've been experimenting with SR-IOV. I have a network with two vNIC profiles, one for passthrough and one for virtio. Per this video: https://www.youtube.com/watch?v=A-MROZ8D06Y I think I should be able to do "mixed mode" using SR-IOV and virtio on the same physical NIC. It does work, initially. But if I flip the VM between the two vNIC profiles, eventually the virtio one stops passing traffic. And I've noticed the Network Interfaces tab on that host shows an increasing number of eth0, eth1, eth2, eth3 interfaces, all with the MAC address of the VM. An equal number of interfaces has been deducted from the p3p1_x VF list. I'm guessing this is related...? See attached screenshot. This is a Dell R530 and the NIC is an Intel X540. OS Version: RHEL - 7 - 2.1511.el7.centos.2.10 Kernel Version: 3.10.0 - 327.13.1.el7.x86_64 KVM Version: 2.3.0 - 31.el7_2.7.1 LIBVIRT Version: libvirt-1.2.17-13.el7_2.4 VDSM Version: vdsm-4.17.23.2-1.el7 -- Matthew Trent Network Engineer Lewis County IT Services___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Master Doamin - Ovirt 3.6 - hoted engine
Thanks! I'm suffering from this issue as well. Did you have to manually copy some data to the other store or anything? Or is this the full procedure, start to finish? -- Matthew Trent Network Engineer Lewis County IT Services 360.740.1247 - Helpdesk 360.740.3343 - Direct line From: users-boun...@ovirt.org on behalf of Dariusz Kryszak Sent: Friday, February 26, 2016 2:12 AM To: Simone Tiraboschi Cc: users Subject: Re: [ovirt-users] Master Doamin - Ovirt 3.6 - hoted engine OK. I've made it procedure: 1. backup hosted engine config engine-backup --mode=backup --file=engine_`date +%Y%m%d_%H%M%S`.bck - -log=engine_`date +%Y%m%d_%H%M%S`.log 2. on the hypervisor hosted-engine --set-maintenance --mode=global 3. on the management host systemctl stop ovirt-engine.service 4. on the management host su - postgres psql \c engine --- tu have to find maualy valuses but master always has storage_domain_type=0 UPDATE storage_domain_static SET storage_domain_type=(select storage_domain_type from storage_domain_static where storage_name='hosted_storage') WHERE storage_name='DS_MAIN' UPDATE storage_domain_static SET _update_date=(select _update_date from storage_domain_static where storage_name='hosted_storage') WHERE storage_name='DS_MAIN' UPDATE storage_domain_static SET storage_domain_type=1 WHERE storage_name='hosted_storage'; UPDATE storage_domain_static SET _update_date=null WHERE storage_name='hosted_storage'; 5. on the management host systemctl start ovirt-engine.service 6. on the hypervisor hosted-engine --set-maintenance --mode=none end. enjoy :-) On Fri, 2016-02-26 at 09:17 +0100, Simone Tiraboschi wrote: > > > On Thu, Feb 25, 2016 at 10:03 PM, Dariusz Kryszak < > dariusz.krys...@gmail.com> wrote: > > > > > > > > > > On Tue, 2016-02-23 at 17:13 +0100, Simone Tiraboschi wrote: > > > > > > > > > On Tue, Feb 23, 2016 at 4:19 PM, Dariusz Kryszak < > > > dariusz.krys...@gmail.com> wrote: > > > > Hi folks, > > > > I have a question about master domain when I'm using hosted > > engine > > > > deployment. > > > > At the beginning I've made deployment on NUC (small home > > > > installation) with hosted engine on the nfs share from NUC > > host. > > > > I've configured FS gluster on the same machine and used it for > > > > master domain and iso domain. Lets say All-in-ONE. > > > > After reboot happened something strange. Log says that master > > > > domain is not available and has to become on the > > hosted_storage. > > > > This is not ok in my opinion. I know that behavior because > > master > > > > doamin is not available, has been migrated to other shareable > > (in > > > > this case hosted_domain is nfs ). > > > > Do you thing, that should be locked in this particular case > > means > > > > when available is only hosted_storage? Right now it is not > > possible > > > > to change this situation because hosted engine resides on the > > > > hosted_storage. I Can't migrate it. > > > > > > > > > > > It could happen only after the hosted-engine storage domain got > > > imported by the engine but to do that you need an additional > > storage > > > domain which will become the master storage domain. > > > In the past we had a bug that let you remove the last regular > > storage > > > domain and it the case the hosted-engine would become the master > > > storage domain and as you pointed out that was an issue. > > > https://bugzilla.redhat.com/show_bug.cgi?id=1298697 > > > > > > Now it should be fixed. If it just happened again just because > > you > > > gluster regular storage domain wasn't available is not really > > fixed. > > > Adding Roy here. > > > Dariusz, which release are you using? > > > > Regarding to the ovirt version. > > 1. ovirt manager > > ovirt-engine-setup - oVirt Engine Version: 3.6.2.6-1.el7.centos > The patch that should address that issue is here: > https://gerrit.ovirt.org/#/c/53208/ > > But you'll find it only in 3.6.3; it wasn't available at 3.6.2.6 > time. > > Recovering from the condition you reached is possible but it requires > a few manual actions. > If your instance was almost empty redeploying is also an (probably > easier) option. > > > > # uname -a > > Linux ovirtm.stylenet 3.10.0-327.10.1.el7.x86_64 #1 SMP Tue Feb 16 > > 17:03:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linu
Re: [ovirt-users] Dumb question: exclamation mark next to VM?
?When I upgraded to 3.6.1 (I think), I had exclamation points on several VMs, and hovering over (or looking at the bottom of the VM's General tab) gave a message about time zone mis-match. After 3.6.2, the message about time zone mis-match is gone, but the exclamation points remain. -- Matthew Trent Network Engineer Lewis County IT Services 360.740.1247 - Helpdesk 360.740.3343 - Direct line From: users-boun...@ovirt.org on behalf of Charles Kozler Sent: Thursday, February 4, 2016 7:46 AM To: Joe DiTommasso Cc: users Subject: Re: [ovirt-users] Dumb question: exclamation mark next to VM? You cant see my mouse (because scrot removes it when you take a picture) but it is hovering over the ! and it says up (almost like it thinks im over the green arrow but I'm not) http://i.imgur.com/5u2Yvay.png To that end I cannot see what the issue is On Thu, Feb 4, 2016 at 10:43 AM, Joe DiTommasso mailto:jd...@domeyard.com>> wrote: If you mouse over the exclamation mark, you should get a tooltip that tells you what it's complaining about. I've got it on pretty much all my VMs, it's an issue with the timezone for me. On Thu, Feb 4, 2016 at 10:41 AM, Charles Kozler mailto:char...@fixflyer.com>> wrote: I have this too. Thank you, I was going to email about this as well http://i.imgur.com/cZ6P5dp.png On Thu, Feb 4, 2016 at 10:38 AM, Chris Adams mailto:c...@cmadams.net>> wrote: I set up a new oVirt 3.6.2 cluster on CentOS 7.2 (everything up to date as of yesterday). I created a basic CentOS 7.2 VM with my local customizations, created a template from it, and then created a VM from that template. That new VM has an exclamation mark next to it in the web GUI (between the up arror for "running" and the "server" icon). Usually I would expect that means something is wrong or needs attention, but I can't find anything to fix/address/etc. (no messages in the Alerts, nothing odd in the Events, etc.). What does the exclamation mark mean, and how do I clear it? -- Chris Adams mailto:c...@cmadams.net>> ___ Users mailing list Users@ovirt.org<mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users -- Charles Kozler Vice President, IT Operations FIX Flyer, LLC 225 Broadway | Suite 1600 | New York, NY 10007 1-888-349-3593 http://www.fixflyer.com<http://fixflyer.com> NOTICE TO RECIPIENT: THIS E-MAIL IS MEANT ONLY FOR THE INTENDED RECIPIENT(S) OF THE TRANSMISSION, AND CONTAINS CONFIDENTIAL INFORMATION WHICH IS PROPRIETARY TO FIX FLYER LLC. ANY UNAUTHORIZED USE, COPYING, DISTRIBUTION, OR DISSEMINATION IS STRICTLY PROHIBITED. ALL RIGHTS TO THIS INFORMATION IS RESERVED BY FIX FLYER LLC. IF YOU ARE NOT THE INTENDED RECIPIENT, PLEASE CONTACT THE SENDER BY REPLY E-MAIL AND PLEASE DELETE THIS E-MAIL FROM YOUR SYSTEM AND DESTROY ANY COPIES. ___ Users mailing list Users@ovirt.org<mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users -- Charles Kozler Vice President, IT Operations FIX Flyer, LLC 225 Broadway | Suite 1600 | New York, NY 10007 1-888-349-3593 http://www.fixflyer.com<http://fixflyer.com> NOTICE TO RECIPIENT: THIS E-MAIL IS MEANT ONLY FOR THE INTENDED RECIPIENT(S) OF THE TRANSMISSION, AND CONTAINS CONFIDENTIAL INFORMATION WHICH IS PROPRIETARY TO FIX FLYER LLC. ANY UNAUTHORIZED USE, COPYING, DISTRIBUTION, OR DISSEMINATION IS STRICTLY PROHIBITED. ALL RIGHTS TO THIS INFORMATION IS RESERVED BY FIX FLYER LLC. IF YOU ARE NOT THE INTENDED RECIPIENT, PLEASE CONTACT THE SENDER BY REPLY E-MAIL AND PLEASE DELETE THIS E-MAIL FROM YOUR SYSTEM AND DESTROY ANY COPIES. ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Mixing CPU types
Sure would be a nice feature, though! It would simplify things for those of us who build out of re-purposed Windows servers (still a lot of life left in them for Linux applications!) and end up with a mix of CPUs. For most of my VMs I don't need the latest and greatest CPU features, but being able to consolidate my hosts into fewer clusters would be really useful. Like you said, oVirt already allows mixing CPU generations by selecting the lowest common denominator CPU type -- as long as you stick to Intel or AMD. It's a similar scenario, and the KVM stuff seems well established. Just expose some additional "generic" CPU types, per the KVM docs, and allow mixed clusters... -- Matthew Trent Network Engineer Lewis County IT Services 360.740.1247 - Helpdesk 360.740.3343 - Direct line From: Martin Polednik Sent: Wednesday, February 3, 2016 11:43 PM To: Matthew Trent Cc: Yaniv Kaul; users@ovirt.org Subject: Re: [ovirt-users] Mixing CPU types - Original Message ----- > From: "Matthew Trent" > To: "Yaniv Kaul" > Cc: users@ovirt.org > Sent: Wednesday, February 3, 2016 8:10:35 PM > Subject: Re: [ovirt-users] Mixing CPU types > > ?Actually it works great! It's been supported by KVM for a while now. I had > one Proxmox cluster with a mix of AMD and Intel and migrated KVM VM's > between them frequently. OpenStack (KVM) and VMWare support this as well. > > > The trick is to expose a virtual CPU with a common set of features to the > VMs. KVM handles the rest. From the KVM FAQ: > > http://www.linux-kvm.org/page/FAQ#Does_KVM_support_live_migration_from_an_AMD_host_to_an_Intel_host_and_back.3F That is pretty much what libvirt does. The sandy-bridge, haswell and other cpu's that we expose are not really a CPUs, but sets of flags (called baseline CPUs in libvirt's terminology). Afaik there should be no issue running cluster with both CPU vendors, the problem is lack of testing on devel side as we mostly run single vendor clusters everywhere. > "Does KVM support live migration from an AMD host to an Intel host and back? > > > Yes. There may be issues on 32-bit Intel hosts which don't support NX (or > XD), but for 64-bit hosts back and forth migration should work well. > Migration of 32-bit guests should work between 32-bit hosts and 64-bit > hosts. If one of your hosts does not support NX, you may consider disabling > NX when starting the guest on a NX-capable system. You can do it by passing > "-cpu qemu64,-nx" parameter to the guest." > > -- > Matthew Trent > Network Engineer > Lewis County IT Services > 360.740.1247 - Helpdesk > 360.740.3343 - Direct line ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Mixing CPU types
?Actually it works great! It's been supported by KVM for a while now. I had one Proxmox cluster with a mix of AMD and Intel and migrated KVM VM's between them frequently. OpenStack (KVM) and VMWare support this as well. The trick is to expose a virtual CPU with a common set of features to the VMs. KVM handles the rest. From the KVM FAQ: http://www.linux-kvm.org/page/FAQ#Does_KVM_support_live_migration_from_an_AMD_host_to_an_Intel_host_and_back.3F "Does KVM support live migration from an AMD host to an Intel host and back? Yes. There may be issues on 32-bit Intel hosts which don't support NX (or XD), but for 64-bit hosts back and forth migration should work well. Migration of 32-bit guests should work between 32-bit hosts and 64-bit hosts. If one of your hosts does not support NX, you may consider disabling NX when starting the guest on a NX-capable system. You can do it by passing "-cpu qemu64,-nx" parameter to the guest." -- Matthew Trent Network Engineer Lewis County IT Services 360.740.1247 - Helpdesk 360.740.3343 - Direct line From: Yaniv Kaul Sent: Tuesday, February 2, 2016 2:17 PM To: Matthew Trent Cc: users@ovirt.org Subject: Re: [ovirt-users] Mixing CPU types On Mon, Feb 1, 2016 at 9:13 PM, Matthew Trent mailto:matthew.tr...@lewiscountywa.gov>> wrote: Though our new oVirt setup is better in most ways, cross-CPU-type migration is one of the features I miss from Proxmox. KVM supports mixed-CPU migration for a while now, even between AMD and Intel. http://www.linux-kvm.org/page/Migration I highly doubt the above works in real life scenarios. Y. I'm using a bunch of re-purposed servers with a mix of AMD and Intel. I separate them into clusters, as noted, but it sure would be nice to be able to live migrate between them. :) -- Matthew Trent Network Engineer Lewis County IT Services > Hi Rene, > > Thank you very much for coming back to me. > > That's perfect then and answers my questions exactly. > > Much appreciated. > > Regards. > >Neil Wilson. > > >On Wed, Jan 27, 2016 at 1:57 PM, René Koch rk-it.at<http://rk-it.at>> wrote: >> >> Hi Neil, >> >> You can mix cpu types (but not AMD and Intel) if you leave the cluster >> level at the lowest cpu level. >> I personally don't mix cpu levels if possible, but instead create own >> clusters for each cpu type in order to be able to use the newest cpu >> features... >> >> >> Regards, >> René >> >> >> On 01/27/2016 12:53 PM, Neil wrote: >> >> Hi guys, >> >> I currently have an oVirt 3.5 cluster with Sandy Bridge Xeon CPU's, and I >> need to add a new host for more RAM and vCPU's, however the new Xeon e5 >> cpu's are Haswell based. >> >> Can I mix CPU types (Haswell and Sandy Bridge) in my cluster and will I be >> able to migrate between my hosts? >> >> I'm guessing that for this to work I'll need to leave my "CPU type" set to >> Sandy Bridge, will the Haswell based CPU be compatible with my cluster, but >> just run without any Haswell type features? >> >> Apologies if this is a dumb question or if it's been answered before. >> >> Thank you. >> >> Regards. >> >> Neil Wilson >> ___ Users mailing list Users@ovirt.org<mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Mixing CPU types
Though our new oVirt setup is better in most ways, cross-CPU-type migration is one of the features I miss from Proxmox. KVM supports mixed-CPU migration for a while now, even between AMD and Intel. http://www.linux-kvm.org/page/Migration I'm using a bunch of re-purposed servers with a mix of AMD and Intel. I separate them into clusters, as noted, but it sure would be nice to be able to live migrate between them. :) -- Matthew Trent Network Engineer Lewis County IT Services > Hi Rene, > > Thank you very much for coming back to me. > > That's perfect then and answers my questions exactly. > > Much appreciated. > > Regards. > >Neil Wilson. > > >On Wed, Jan 27, 2016 at 1:57 PM, René Koch wrote: >> >> Hi Neil, >> >> You can mix cpu types (but not AMD and Intel) if you leave the cluster >> level at the lowest cpu level. >> I personally don't mix cpu levels if possible, but instead create own >> clusters for each cpu type in order to be able to use the newest cpu >> features... >> >> >> Regards, >> René >> >> >> On 01/27/2016 12:53 PM, Neil wrote: >> >> Hi guys, >> >> I currently have an oVirt 3.5 cluster with Sandy Bridge Xeon CPU's, and I >> need to add a new host for more RAM and vCPU's, however the new Xeon e5 >> cpu's are Haswell based. >> >> Can I mix CPU types (Haswell and Sandy Bridge) in my cluster and will I be >> able to migrate between my hosts? >> >> I'm guessing that for this to work I'll need to leave my "CPU type" set to >> Sandy Bridge, will the Haswell based CPU be compatible with my cluster, but >> just run without any Haswell type features? >> >> Apologies if this is a dumb question or if it's been answered before. >> >> Thank you. >> >> Regards. >> >> Neil Wilson >> ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 7.2 and oVirt 3.6.0 => 3.6.1
Yes! That did it. All the errors are gone, and HA seems to be functioning normally. Thanks much! -- Matthew Trent Network Engineer Lewis County IT Services ? From: Simone Tiraboschi Sent: Thursday, December 17, 2015 4:50 PM To: Matthew Trent Cc: users@ovirt.org Subject: Re: [ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 7.2 and oVirt 3.6.0 => 3.6.1 On Fri, Dec 18, 2015 at 12:32 AM, Matthew Trent mailto:matthew.tr...@lewiscountywa.gov>> wrote: (Sorry if this reply doesn't thread properly. Just subscribed to reply to this topic.) I'm also experiencing this issue. Just upgraded to the latest packages and both ovirt-ha-agent and ovirt-ha-broker pause for a long time when being started, then timeout with errors. Please try manually reverting this patch https://gerrit.ovirt.org/#/c/50662/ by removing the lines that start with PIDFile= from /usr/lib/systemd/system/ovirt-ha-broker.service and /usr/lib/systemd/system/ovirt-ha-agent.service Then systemctl daemon-reload and restart the services [root@ovirt2 ~]# systemctl start ovirt-ha-broker Job for ovirt-ha-broker.service failed because a timeout was exceeded. See "systemctl status ovirt-ha-broker.service" and "journalctl -xe" for details. [root@ovirt2 ~]# systemctl start ovirt-ha-agent Job for ovirt-ha-agent.service failed because a timeout was exceeded. See "systemctl status ovirt-ha-agent.service" and "journalctl -xe" for details. Dec 17 15:27:53 ovirt2 systemd: Failed to start oVirt Hosted Engine High Availability Communications Broker. Dec 17 15:27:53 ovirt2 systemd: Unit ovirt-ha-broker.service entered failed state. Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service failed. Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service holdoff time over, scheduling restart. Dec 17 15:27:53 ovirt2 systemd: Starting oVirt Hosted Engine High Availability Communications Broker... Dec 17 15:27:53 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker: [ OK ] Dec 17 15:27:53 ovirt2 systemd: PID 21125 read from file /run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie. Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service stop-final-sigterm timed out. Killing. Dec 17 15:29:22 ovirt2 systemd: Failed to start oVirt Hosted Engine High Availability Monitoring Agent. Dec 17 15:29:22 ovirt2 systemd: Unit ovirt-ha-agent.service entered failed state. Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service failed. Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service holdoff time over, scheduling restart. Dec 17 15:29:23 ovirt2 systemd: ovirt-ha-broker.service start operation timed out. Terminating. Dec 17 15:29:24 ovirt2 systemd: Failed to start oVirt Hosted Engine High Availability Communications Broker. Dec 17 15:29:24 ovirt2 systemd: Unit ovirt-ha-broker.service entered failed state. Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service failed. Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High Availability Monitoring Agent... Dec 17 15:29:24 ovirt2 systemd-ovirt-ha-agent: Starting ovirt-ha-agent: [ OK ] Dec 17 15:29:24 ovirt2 systemd: PID 21288 read from file /run/ovirt-hosted-engine-ha/agent.pid does not exist or is a zombie. Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service holdoff time over, scheduling restart. Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High Availability Communications Broker... Dec 17 15:29:25 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker: [ OK ] Dec 17 15:29:25 ovirt2 systemd: PID 21304 read from file /run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie. -- Matthew Trent Network Engineer Lewis County IT Services 360.740.1247 - Helpdesk 360.740.3343 - Direct line ___ Users mailing list Users@ovirt.org<mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] ovirt-ha-broker issue after upgrade CentOS 7.1 => 7.2 and oVirt 3.6.0 => 3.6.1
(Sorry if this reply doesn't thread properly. Just subscribed to reply to this topic.) I'm also experiencing this issue. Just upgraded to the latest packages and both ovirt-ha-agent and ovirt-ha-broker pause for a long time when being started, then timeout with errors. [root@ovirt2 ~]# systemctl start ovirt-ha-broker Job for ovirt-ha-broker.service failed because a timeout was exceeded. See "systemctl status ovirt-ha-broker.service" and "journalctl -xe" for details. [root@ovirt2 ~]# systemctl start ovirt-ha-agent Job for ovirt-ha-agent.service failed because a timeout was exceeded. See "systemctl status ovirt-ha-agent.service" and "journalctl -xe" for details. Dec 17 15:27:53 ovirt2 systemd: Failed to start oVirt Hosted Engine High Availability Communications Broker. Dec 17 15:27:53 ovirt2 systemd: Unit ovirt-ha-broker.service entered failed state. Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service failed. Dec 17 15:27:53 ovirt2 systemd: ovirt-ha-broker.service holdoff time over, scheduling restart. Dec 17 15:27:53 ovirt2 systemd: Starting oVirt Hosted Engine High Availability Communications Broker... Dec 17 15:27:53 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker: [ OK ] Dec 17 15:27:53 ovirt2 systemd: PID 21125 read from file /run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie. Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service stop-final-sigterm timed out. Killing. Dec 17 15:29:22 ovirt2 systemd: Failed to start oVirt Hosted Engine High Availability Monitoring Agent. Dec 17 15:29:22 ovirt2 systemd: Unit ovirt-ha-agent.service entered failed state. Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service failed. Dec 17 15:29:22 ovirt2 systemd: ovirt-ha-agent.service holdoff time over, scheduling restart. Dec 17 15:29:23 ovirt2 systemd: ovirt-ha-broker.service start operation timed out. Terminating. Dec 17 15:29:24 ovirt2 systemd: Failed to start oVirt Hosted Engine High Availability Communications Broker. Dec 17 15:29:24 ovirt2 systemd: Unit ovirt-ha-broker.service entered failed state. Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service failed. Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High Availability Monitoring Agent... Dec 17 15:29:24 ovirt2 systemd-ovirt-ha-agent: Starting ovirt-ha-agent: [ OK ] Dec 17 15:29:24 ovirt2 systemd: PID 21288 read from file /run/ovirt-hosted-engine-ha/agent.pid does not exist or is a zombie. Dec 17 15:29:24 ovirt2 systemd: ovirt-ha-broker.service holdoff time over, scheduling restart. Dec 17 15:29:24 ovirt2 systemd: Starting oVirt Hosted Engine High Availability Communications Broker... Dec 17 15:29:25 ovirt2 systemd-ovirt-ha-broker: Starting ovirt-ha-broker: [ OK ] Dec 17 15:29:25 ovirt2 systemd: PID 21304 read from file /run/ovirt-hosted-engine-ha/broker.pid does not exist or is a zombie. -- Matthew Trent Network Engineer Lewis County IT Services 360.740.1247 - Helpdesk 360.740.3343 - Direct line ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
