ok that explains that I first thought it wouldn't and then that it would work. I started at master and today looked at 4.3. As soon as we have a 4.3 in one of our multi-zone envs I will verify.
On Thu, Feb 13, 2014 at 8:45 PM, Min Chen <min.c...@citrix.com> wrote: > Daan, just noticed that you are reading code from master, then your > analysis is not wrong. Edison hasn't cherry-pick his commit to master yet. > > Thanks > -min > > On 2/13/14 10:53 AM, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote: > >>I saw in code that my first analysis that this would still be a >>problem was wrong. I have not devised a way to verify yet. thanks for >>the confirmation, Min >> >>On Thu, Feb 13, 2014 at 7:47 PM, Min Chen <min.c...@citrix.com> wrote: >>> Edison has already fixed this in ACS 4.3 and master, See commit >>> >>>https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=1b064 >>>51 >>> 5ac9c7f87e1780ab2210e60723f9d541c. >>> >>> Thanks >>> -min >>> >>> On 2/12/14 8:16 AM, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote: >>> >>>>LS, >>>> >>>>It seems that when instantiating a vm from a template cloudstack tries >>>>to copy the template from a random secondary storage >>>>https://issues.apache.org/jira/browse/CLOUDSTACK-6024 >>>> >>>>the result is that the copy from secondary storage to primary fails >>>>and thus instantiation of the vm. >>>> >>>>This is in 4.2.1 but I looked into the master code and it seems to >>>>still call code that uses a random result for the origin of the >>>>template. Any of the storage guru's know if my analysis is correct and >>>>how to handle this? >>>> >>>>-- >>>>Daan >>> >> >> >> >>-- >>Daan > -- Daan
