I still see this issue on master build , where after executing cloudstack-setup-databases DB version is still pointing to 4.0.0.
I have logged the following bug to track this issue: CLOUDSTACK-2052 - After executing cloudstack-setup-databases , DB version is still pointing to 4.0.0. -Thanks Sangeetha -----Original Message----- From: Alex Huang [mailto:alex.hu...@citrix.com] Sent: Thursday, March 21, 2013 11:56 AM To: dev@cloudstack.apache.org; cloudstack-...@incubator.apache.org Subject: RE: CLOUDSTACK-1747: fresh deploydb bug in 4.1 requires cherry-pick commits from master > -----Original Message----- > From: rohityada...@gmail.com [mailto:rohityada...@gmail.com] On Behalf > Of Rohit Yadav > Sent: Wednesday, March 20, 2013 11:27 PM > To: cloudstack-...@incubator.apache.org > Subject: Re: CLOUDSTACK-1747: fresh deploydb bug in 4.1 requires > cherry- pick commits from master > > On Thu, Mar 21, 2013 at 1:54 AM, Alex Huang <alex.hu...@citrix.com> > wrote: > > Hi everyone, > > > > We had a discussion on irc. > > > > To implement something intermediary will be around the same effort > > as > finishing the job and there are various reasons why just running the > create- schema.sql and update*.sql is not enough. So we should just > decide on finishing the job in 4.1 or document the behavior. > > > > Any input on which way we should take. > > > > The engineer in me says just finish the job. It's obviously working > > in dev > setup on master so the risk of this introducing bugs is very low. If > someone knows why it's difficult to change in cloud-setup-databases > script, please speak up. > > Alex asks why it is difficult to change in cloud-setup-database script? Rohit, Actually, I really just meant was there technical challenges in updating the script that was already looked into. Sounds like from your reply there isn't. Appreciate your work on the various parts. It was excellent. Good luck on your next venture. --Alex
