cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Stevens <wstev...@cloudops.com>
Subject Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
Date Mon, 24 Jun 2019 15:19:57 GMT
+1 for keeping 4.11.3.0 and rereleasing...

On Mon, Jun 24, 2019, 10:38 AM Gabriel Beims Bräscher <gabrascher@gmail.com>
wrote:

> +1 on keeping the release name as 4.11.3.0.
>
> Em seg, 24 de jun de 2019 às 11:27, Wei ZHOU <ustcweizhou@gmail.com>
> escreveu:
>
> > I vote for 4.11.3.0
> >
> > -Wei
> >
> >
> >
> > Paul Angus <paul.angus@shapeblue.com> 于2019年6月24日周一 下午3:43写道:
> >
> > > Hi,
> > >
> > > Does anyone have any strong views on whether we should look to nullify
> > > 4.11.3.0 as it was never in the wild, or should be go to 4.11.3.1 ?
> > >
> > > Many thanks
> > >
> > >
> > > Paul Angus
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > paul.angus@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK
> > > @shapeblue
> > >
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: Rohit Yadav <rohit.yadav@shapeblue.com>
> > > Sent: 24 June 2019 12:13
> > > To: users@cloudstack.apache.org; dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
> > >
> > > Thanks for sharing Gregor. My/our bad, I was suspicious of how the
> > > templates were setup based on your emails and did not think what you
> > shared
> > > could be something to do with the DB upgrade path bug.
> > >
> > >
> > > Regards,
> > >
> > > Rohit Yadav
> > >
> > > Software Architect, ShapeBlue
> > >
> > > https://www.shapeblue.com
> > >
> > > ________________________________
> > > From: Riepl, Gregor (SWISS TXT) <Gregor.Riepl@swisstxt.ch>
> > > Sent: Monday, June 24, 2019 3:23:23 PM
> > > To: users@cloudstack.apache.org; dev@cloudstack.apache.org
> > > Subject: Re: [VOTE][RESULT] Apache CloudStack 4.11.3.0
> > >
> > >
> > > > https://github.com/apache/cloudstack/pull/3417
> > > >
> > > >
> > > > The issue only affects 4.11.2.0 users for which the upgrade path does
> > > > not run (a noop upgrade path runs) and it does not automatically fix
> > > > any registered 4.11.3 systemvmtemplate to be used post-upgrade. I've
> > > > mentioned workaround steps on the PR.
> > >
> > > This sounds pretty much exactly like the issue we had...
> > >
> > >
> > >
> >
> https://lists.apache.org/thread.html/3a6ba604a77c944640cb159d7a55bda2c4646afa32bd494e3072e012@%3Cdev.cloudstack.apache.org%3E
> > >
> > >
> >
> https://lists.apache.org/thread.html/94d226e7cd832cda45c877db7f3d40c4802812da1a09b14ba63ccaf7@%3Cdev.cloudstack.apache.org%3E
> > >
> > >
> >
> https://lists.apache.org/thread.html/17d603ed695ce926ced124dc99cf41102f763e9dffc4e08259d74a44@%3Cusers.cloudstack.apache.org%3E
> > >
> > > rohit.yadav@shapeblue.com
> > > www.shapeblue.com
> > > Amadeus House, Floral Street, London  WC2E 9DPUK @shapeblue
> > >
> > >
> > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message