Hi Daan, It was the importing of a standard template added via the UI. I will re-try again today to ensure it wasn't a networking fault (unlikely) but the messages about the host disconnecting randomly does have me concerned.
I was using the system vm template from jenkins. http://jenkins.buildacloud.org/view/4.4/job/cloudstack-4.4-systemvm64/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-4.4-2014-11-24-xen.vhd.bz2 On 25 November 2014 at 10:11, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > Thanks Lucian, I am not sure what Ians failing scenario is? It might > be the download process that is failing and it might be the starting. > > On Tue, Nov 25, 2014 at 11:05 AM, Nux! <n...@li.nux.ro> wrote: > > I'll upgrade my test setup (4.4.1) today and get back to you. > > > > Do I need a new systemvm or can I just leave the old one from 4.4.1 in > place? > > > > -- > > Sent from the Delta quadrant using Borg technology! > > > > Nux! > > www.nux.ro > > > > ----- Original Message ----- > >> From: "Daan Hoogland" <daan.hoogl...@gmail.com> > >> To: "dev" <dev@cloudstack.apache.org>, "Ian Duffy" <i...@ianduffy.ie> > >> Sent: Tuesday, 25 November, 2014 09:37:36 > >> Subject: Re: [ACS44]release 4.4.2 release candidate RC20141121T0341 (#2) > > > >> Anybody else seeing this? > >> > >> @Ian, please confirm this is a regression compared to 4.4.1. Ans can > >> you describe the scenario/is this a regular template test or a > >> systemvm template? > >> > >> I will not regard this a blocker without confirmation. We have enough > >> +1 binding but I will extend voting a bit. > >> > >> Daan > >> > >> On Mon, Nov 24, 2014 at 8:01 PM, Ian Duffy <i...@ianduffy.ie> wrote: > >>> +0 (Don't want to get in the way...) > >>> > >>> Tested with my standard automated virtualised cloudstack environment. > >>> > >>> Failed to import a template successfully. The template downloaded, it > hung > >>> on installing template for awhile eventually got an error of "Failed > post > >>> download script: timeout" > >>> > >>> The logs repeat the following over and over: > >>> > >>> INFO [c.c.a.m.AgentManagerImpl] (AgentMonitor-1:ctx-0209bee9) Found > the > >>> following agents behind on ping: [1] > >>> INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-12:ctx-c5084767) > >>> Investigating why host 1 has disconnected with event PingTimeout > >>> INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-12:ctx-c5084767) The > state > >>> determined is Up > >>> INFO [c.c.a.m.AgentManagerImpl] (AgentTaskPool-12:ctx-c5084767) Agent > is > >>> determined to be up and running > >>> WARN [c.c.a.m.DirectAgentAttache] (DirectAgentCronJob-15:ctx-b3fbf6da) > >>> Unable to get current status on 1(localhost.localdomain) > >>> > >>> I don't appear to have any network issues with the hypervisor from the > >>> management server. The system vms booted up just fine and look healthy. > >>> > >>> The API params for configuring xenserver advanced networking tags are > still > >>> different thus breaking marvin. > > -- > Daan >
