It seems to me that this patch will fix 1989, not 1987.
Thanks
-min

On 4/11/13 6:24 PM, "Marcus Sorensen" <shadow...@gmail.com> wrote:

>Does it fix 1989, or perhaps both?
>
>https://issues.apache.org/jira/browse/CLOUDSTACK-1989
>On Apr 11, 2013 7:08 PM, "Min Chen" <min.c...@citrix.com> wrote:
>
>> Hi Ryan,
>>
>>         Maybe I overlooked something, but I could not understand how
>>your
>> patch
>> is fixing CLOUDSTACK-1987. It would be appreciated if you can address my
>> comment in that patch.
>>
>>         Thanks
>>         -min
>>
>> On 4/11/13 5:52 PM, "Prachi Damle" <prachi.da...@citrix.com> wrote:
>>
>> >Hi Ryan,
>> >
>> >Yes Sure, my bad,  will look at the patch first.
>> >
>> >Thanks,
>> >Prachi
>> >
>> >-----Original Message-----
>> >From: Ryan Dietrich [mailto:r...@betterservers.com]
>> >Sent: Thursday, April 11, 2013 5:46 PM
>> >To: dev@cloudstack.apache.org
>> >Subject: Re: [ACS41] Help needed clearing bugs!
>> >
>> >Could you look at this first?
>> >
>> >https://reviews.apache.org/r/10426/
>> >
>> >On Apr 11, 2013, at 6:25 PM, Prachi Damle <prachi.da...@citrix.com>
>> wrote:
>> >
>> >> I will take a look at CLOUDSTACK-1987.
>> >>
>> >> -Prachi
>> >>
>> >> -----Original Message-----
>> >> From: Edison Su [mailto:edison...@citrix.com]
>> >> Sent: Thursday, April 11, 2013 5:17 PM
>> >> To: dev@cloudstack.apache.org
>> >> Subject: RE: [ACS41] Help needed clearing bugs!
>> >>
>> >> Probably, it's a setup issue, e.g openvswitch doesn't work. I'll
>>take a
>> >>look QA's environment, if it's still there.
>> >>
>> >>> -----Original Message-----
>> >>> From: Marcus Sorensen [mailto:shadow...@gmail.com]
>> >>> Sent: Thursday, April 11, 2013 5:12 PM
>> >>> To: dev@cloudstack.apache.org
>> >>> Subject: Re: [ACS41] Help needed clearing bugs!
>> >>>
>> >>> I haven't even touched openvswitch, or I'd take a look at 1978. Is
>> >>> that a prerequisite for duplicating the issue?
>> >>> On Apr 11, 2013 3:41 PM, "Kelven Yang" <kelven.y...@citrix.com>
>>wrote:
>> >>>
>> >>>> about CLOUDSTACK-1978, it looks like the problem at hypervsor host
>> >>>> side, the hypervisor host is either failed to setup the VNC
>> >>>> listening interface or failed to configure firewall properly, could
>> >>>> KVM developer pick this up(I assume it is KVM hypervisor)?
>> >>>>
>> >>>> Kelven
>> >>>>
>> >>>> On 4/11/13 2:11 PM, "Chip Childers" <chip.child...@sungard.com>
>> wrote:
>> >>>>
>> >>>>> Hi all,
>> >>>>>
>> >>>>> I need your help clearing out the following bugs...  if you have
>> >>>>> one assigned to you, please see if you can get it completed.  If
>> >>>>> you have any time available, and think you can help resolve one of
>> >>>>> the unassigned ones, please jump in!  We're obviously behind the
>> >>>>> schedule that we set for ourselves, so I'd love to see the
>> >>>>> community come together for a final push to get 4.1.0 out the
>>door.
>> >>>>>
>> >>>>> CLOUDSTACK-2007 Release Notes failing to build on jenkins.cs.o
>> >>>>> Currently unassigned - Joe looked into it, and he thinks this is a
>> >>>>> build server issue.  Can someone please take a look?
>> >>>>>
>> >>>>> CLOUDSTACK-1934 NPE with listSupportedNetworkServices after
>>upgrade
>> >>>>> from
>> >>>>> 4.0 to 4.1 (Ubuntu MS)
>> >>>>> Unassigned
>> >>>>>
>> >>>>> CLOUDSTACK-1978 openvswitch - unable to start console session for
>> >>>>> SSVM CPVM user VMs Unassigned
>> >>>>>
>> >>>>> CLOUDSTACK-1987 Deleted service offerings owned by a domain show
>>up
>> >>>>> to domain users Unassigned
>> >>>>>
>> >>>>> CLOUDSTACK-1997 Upload and Document IPV6 specific system
>>templates.
>> >>>>> Unassigned - Who wants to host the template (wido?), and then we
>> >>>>> need to add it to the IPv6 docs.
>> >>>>>
>> >>>>> Last but not least, we still need to wrap up any final docs
>> >>>>> (including Release Notes, which I consider a blocker right now).
>> >>>>> Joe, do you want / need help with the Release Notes?  Other doc
>> >>>>> folks, anything that's in progress that we can get over the line
>> >>>>> would be appreciated.  The same goes for translations that may be
>> >>> outstanding...
>> >>>>>
>> >>>>> Let's get 4.1.0 out!
>> >>>>>
>> >>>>> -chip
>> >>>>
>> >>>>
>> >
>>
>>

Reply via email to