A quick workaround is to disable the zone before rebooting the host. -----Original Message----- From: Nux! [mailto:n...@li.nux.ro] Sent: Thursday, December 18, 2014 4:16 AM To: dev@cloudstack.apache.org Subject: Re: Reboot of single hypervisor in zone leads to management network exhaustion
Heh :-) There is a workaround, but this should get addressed in the code: if your only hypervisor is down, stop trying to spin up system vms. Any takers? -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "sebgoa" <run...@gmail.com> > To: dev@cloudstack.apache.org > Sent: Thursday, 18 December, 2014 08:52:22 > Subject: Re: Reboot of single hypervisor in zone leads to management network > exhaustion > On Dec 18, 2014, at 12:43 AM, Nux! <n...@li.nux.ro> wrote: > >> I hit this with 4.4.2 and KVM. >> >> The same problem is described here by Daniel, more than a year ago. >> https://issues.apache.org/jira/browse/CLOUDSTACK-4735 >> >> Any tips on what to remove from the DB without killing it softly? > > Just put the Fugees very loud and it should work :) > > Merry christmas. > >> >> Lucian >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! > > www.nux.ro
