Will, go ahead and submit to the 4.4 branch. It is opened up again for
anybody to submit fixes. I will be doing some of the remaining release
work and then start considdering a 4.4.1. To be clear, your patch
hasn't made it into 4.4.0.

On Tue, Jul 22, 2014 at 11:53 PM, Will Stevens <wstev...@cloudops.com> wrote:
> Forgive me if this is not the right place to bring this up.  If at all
> possible I would like to get the following fix into the 4.4 and 4.3.1
> branches before they are closed for good.  This fix makes the SDX usable
> again.  I have committed it to the master branch.
>
> Here are some more details: http://markmail.org/message/zcqisqm5rzre4vak
>
> Let me know if you have questions.
>
> Cheers,
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
> w cloudops.com *|* tw @CloudOps_
>
>
> On Tue, Jul 22, 2014 at 10:56 AM, Mike Tutkowski <
> mike.tutkow...@solidfire.com> wrote:
>
>> Ship it! :)
>>
>> On Tuesday, July 22, 2014, Daan Hoogland <daan.hoogl...@gmail.com> wrote:
>>
>> > this is maybe not according to proceedings as defined, but this is a
>> > result of +3 binding after more then 72 hours.
>> >
>> > anyone for drinks?
>> >
>> > On Tue, Jul 22, 2014 at 4:37 PM, Mike Tutkowski
>> > <mike.tutkow...@solidfire.com <javascript:;>> wrote:
>> > > +1
>> > >
>> > > On Tuesday, July 22, 2014, Daan Hoogland <daan.hoogl...@gmail.com
>> > <javascript:;>> wrote:
>> > >
>> > >> You are right, Sebastien. Emotion got the better of me.
>> > >>
>> > >> +1 (binding)
>> > >>
>> > >> On Tue, Jul 22, 2014 at 4:05 PM, Sebastien Goasguen <run...@gmail.com
>> > <javascript:;>
>> > >> <javascript:;>> wrote:
>> > >> > +1 on release
>> > >> >
>> > >> > ps: the vote does not have to be closed.
>> > >> >
>> > >> > On Jul 21, 2014, at 5:45 PM, Alena Prokharchyk <
>> > >> alena.prokharc...@citrix.com <javascript:;> <javascript:;>> wrote:
>> > >> >
>> > >> >> Pierre-Luc,
>> > >> >>
>> > >> >> I¹ve closed the bug as invalid. Here is the explanation why:
>> > >> >>
>> > >> >> The first attempt to upgrade failed because the new system template
>> > >> wasn't
>> > >> >> pre-downloaded prior to upgrade (the requirement reflected in
>> Release
>> > >> >> notes, for the cases when template is changed between CS versions)
>> > >> >> What should have been done to fix the problem:
>> > >> >>
>> > >> >> 1) manually roll back your DB to the pre-upgraded version (we
>> always
>> > >> >> recommend to take mysql cloud/cloud_usage db dumps prior to upgrade
>> > in
>> > >> >> case rollback is needed). Currently CS doesn't support automatic
>> > >> rollback
>> > >> >> in case of failure
>> > >> >> 2) while being on prev version, download the template
>> > >> >> 3) start management server
>> > >> >>
>> > >> >> If you attempt to start MS for the second time when the first start
>> > >> failed
>> > >> >> due to upgrade problem, w/o rolling back, the MS will try to run
>> > upgrade
>> > >> >> one more time on the partially upgraded DB. And it will fail.
>> > >> >>
>> > >> >> Please follow the steps 1-3 above to fix the problem on your
>> system.
>> > >> >>
>> > >> >> -Alena.
>> > >> >>
>> > >> >>
>> > >> >>
>> > >> >> On 7/19/14, 8:28 AM, "Pierre-Luc Dion" <pd...@cloudops.com
>> > <javascript:;>
>> > >> <javascript:;>> wrote:
>> > >> >>
>> > >> >>> Ran into issue when trying to upgrade from 4.2.1. Got the
>> following
>> > >> >>> database upgrade failure: http://pastebin.com/wkkAVYu0
>> > >> >>>
>> > >> >>> Jira: https://issues.apache.org/jira/browse/CLOUDSTACK-7140
>> > >> >>>
>> > >> >>>
>> > >> >>>
>> > >> >>> *Pierre-Luc DION*
>> > >> >>> Architecte de Solution Cloud | Cloud Solutions Architect
>> > >> >>> t 855.652.5683
>> > >> >>>
>> > >> >>> *CloudOps* Votre partenaire infonuagique* | *Cloud Solutions
>> Experts
>> > >> >>> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
>> > >> >>> w cloudops.com *|* tw @CloudOps_
>> > >> >>>
>> > >> >>>
>> > >> >>>
>> > >> >>> On Wed, Jul 16, 2014 at 8:24 AM, Daan Hoogland <
>> > >> daan.hoogl...@gmail.com <javascript:;> <javascript:;>>
>> > >> >>> wrote:
>> > >> >>>
>> > >> >>>> Hi All,
>> > >> >>>>
>> > >> >>>> I've created a 4.4.0 release, with the following artifacts up
>> for a
>> > >> >>>> vote:
>> > >> >>>>
>> > >> >>>> Git Branch and Commit SH:
>> > >> >>>>
>> > >> >>>>
>> > >> >>>>
>> > >>
>> >
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=ref
>> > >> >>>> s/heads/4.4-RC20140716T1409
>> > >> >>>> Commit: c9672d8b5710e597bca3a81a7b06dc90c7f5b1f7
>> > >> >>>>
>> > >> >>>> List of changes:
>> > >> >>>>
>> > >> >>>>
>> > >> >>>>
>> > >>
>> >
>> http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/la
>> > >> >>>> test/
>> > >> >>>>
>> > >> >>>> Source release (checksums and signatures are available at the
>> same
>> > >> >>>> location):
>> > >> >>>> https://dist.apache.org/repos/dist/dev/cloudstack/4.4.0/
>> > >> >>>>
>> > >> >>>> PGP release keys (signed using 4096R/AA4736F3):
>> > >> >>>> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>> > >> >>>>
>> > >> >>>> Vote will be open for 72 hours.
>> > >> >>>>
>> > >> >>>> For sanity in tallying the vote, can PMC members please be sure
>> to
>> > >> >>>> indicate "(binding)" with their vote?
>> > >> >>>>
>> > >> >>>> [ ] +1  approve
>> > >> >>>> [ ] +0  no opinion
>> > >> >>>> [ ] -1  disapprove (and reason why)
>> > >> >>>>
>> > >> >>>>
>> > >> >>>>
>> > >> >>>> --
>> > >> >>>> Daan
>> > >> >>>>
>> > >> >>
>> > >> >
>> > >>
>> > >>
>> > >>
>> > >> --
>> > >> Daan
>> > >>
>> > >
>> > >
>> > > --
>> > > *Mike Tutkowski*
>> > > *Senior CloudStack Developer, SolidFire Inc.*
>> > > e: mike.tutkow...@solidfire.com <javascript:;>
>> > > o: 303.746.7302
>> > > Advancing the way the world uses the cloud
>> > > <http://solidfire.com/solution/overview/?video=play>*™*
>> >
>> >
>> >
>> > --
>> > Daan
>> >
>>
>>
>> --
>> *Mike Tutkowski*
>> *Senior CloudStack Developer, SolidFire Inc.*
>> e: mike.tutkow...@solidfire.com
>> o: 303.746.7302
>> Advancing the way the world uses the cloud
>> <http://solidfire.com/solution/overview/?video=play>*™*
>>



-- 
Daan

Reply via email to