I assigned it to myself. As for the question from Chip. This change is not intended for 4.1 so I removed the 4.1 fixed version in the bug.
This change is intended to get prepared for continuing changes we started on javelin. It basically puts most of our system vms as services that cloud-engine helps to provide. There was no code change but moving directories tends to cause big code merge problems if done late so I do it early for 4.2. There's probably due to some of that path problem Marcus was talking about that cause this bug. Will take a look. --Alex > -----Original Message----- > From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf > Of Rohit Yadav > Sent: Thursday, February 14, 2013 9:23 AM > To: cloudstack-dev@incubator.apache.org > Cc: Alex Huang > Subject: Re: [BLOCKER] SystemVMs come up but don't have agent running > > On Thu, Feb 14, 2013 at 8:23 PM, Chip Childers > <chip.child...@sungard.com> wrote: > > On Thu, Feb 14, 2013 at 05:02:17PM +0530, Nitin Mehta wrote: > >> I am facing this issue as well. > >> > >> On 14/02/13 4:53 PM, "Rohit Yadav" <bhais...@apache.org> wrote: > >> > >> >I mentioned in a recent thread about build failure about this blocker, > >> >and wanted to confirm. > >> > > >> >Looks like this is an issue and not just for me: > >> >A fresh deployment of basic zone would start systemvms and they are > >> >shown as running but they don't have any agent running on them, nor I > >> >found any iso attached. The bug was introduced around the time when > >> >the build was broken, when console-proxy was refactored and moved to > >> >services/ > >> > > >> >commit 4869f0cacfc1319ac725e35ac4ebd1b59da8e5e1 > >> >Author: Alex Huang <alex.hu...@citrix.com> > >> >Date: Tue Feb 12 15:59:02 2013 -0800 > >> > > >> > Moved console-proxy into services > >> > > >> >commit 2293caa32e4387d7c71c1d4f677e3015856eff0a > >> >Author: Alex Huang <alex.hu...@citrix.com> > >> >Date: Tue Feb 12 15:58:38 2013 -0800 > >> > > >> > > >> > moved console proxy into services directory. no code change > >> > > >> >BUG: https://issues.apache.org/jira/browse/CLOUDSTACK-1273 > >> >NOTE: This is not an issue on 4.1, just on master branch > >> > > >> >Regards. > >> > >> > > > > Alex - That was a pretty large code move. Can you share a bit more > > about what it was for? > > > > Rohit - I see you opened a bug and assigned to yourself. Are you good > > with fixing it? > > First of all YES I think I can do anything as long as any man can do > it. Challenges excite me :) But, no I did not assign it to anyone, > it's still unassigned: > https://issues.apache.org/jira/browse/CLOUDSTACK-1273 > > Regards. > > > > > -chip
