after looking beyond the tip of my nose; this is from the changes file in the repo-branch 4.4:
Apache CloudStack CHANGES ====================================== Full release notes for each release are located in the project's documentation [website](http://docs.cloudstack.apache.org/projects/cloudstack-release-notes) Version 4.4.3 ------------- This maintenance release has the following bug fixes: Bug ID | Description CLOUDSTACK-2625, CLOUDSTACK-3401: Usage records are ordered by start_date which is not unique. CLOUDSTACK-2823: pass cmdline info to system vms for 30 times CLOUDSTACK-5446: delete all the leftover snapshots on primary storage in case of snapshot errors, after a new backup snapshot is finished CLOUDSTACK-5576: UI > IP Address > EnableVPN, DisableVPN: change label. CLOUDSTACK-5719: UI > Network > Add Guest Network > when Physical Network dropdown is changed, refresh Network Offering dropdown CLOUDSTACK-5821: systemvmiso is locked by systevmvm in hyperv CLOUDSTACK-5834: got VBD statistics from RRD CLOUDSTACK-6075: Increase the ram size for router service offering CLOUDSTACK-6172: Adding new test case to verify this fix CLOUDSTACK-6210: LDAP:listLdapUsers api throws exception when we click on "Add LDAP Account" This occurs when ldap basedn is not configured. CLOUDSTACK-6236: Fix a copy-and-paste error for decrRefCnt in VolumeDataStoreVO. (cherry picked from commit 672bb353be2f159966f351ab2de914b433a934f9) CLOUDSTACK-6261: remove the forceful timeout setting when login to NetScaler. CLOUDSTACK-6467: Add pre/post-state transition status to messages published on CLOUDSTACK-6892: use lowercase noredist, as package.sh lowercases build type CLOUDSTACK-7144: No GSLB provider is available during assigning load balancing rule CLOUDSTACK-7191: On restartNetwork destroy the VR immediatley, instead of cleanup the rules then destroy CLOUDSTACK-7293: UI: Fixed localization issues on the login page CLOUDSTACK-7302: UI: Remove Hover Interaction from breadcrumbs at top page CLOUDSTACK-7360: [vmware] Add host to existing cluster fails if the cluster is using Nexus 1000v as backend for atleast one traffic type. CLOUDSTACK-7412: Can't create proper template from VM on S3 secondary storage environment CLOUDSTACK-7415: Management server PingTask should update PingMap entry for an agent only if it is already present in the Management Server's PingMap. CLOUDSTACK-7463: UI: Domain Admin UI shows 'Add LDAP Users' button (should not be shown) CLOUDSTACK-7589: VM not Starting and always stuck in Stopped state after management server restarts. CLOUDSTACK-7595: Config parameters "job.expire.minutes" and "job.cancel.threshold.minutes" incorrectly getting multiplied by a factor of 60 CLOUDSTACK-7658: Upgrading debian packages as part of system vm template build CLOUDSTACK-7679: Bump rabbitmq client library to latest 3.4.1 CLOUDSTACK-7700: Volume Snapshot Async Job returns Success for a failed operation. CLOUDSTACK-7766: Field Validations Missing for Ingress and Egress Rules CLOUDSTACK-7837: [UI] Make the Source CIDR column wide enough to fit the CIDR value without ellipsizing CLOUDSTACK-7869: Add simulator support for findHostsForMigration API CLOUDSTACK-7871: allow VM and template details update using update APIs CLOUDSTACK-7872: network getting shutdown inspite of running VM's in the network CLOUDSTACK-7884: Cloudstack MS is not responding (happening randomly) after some restart. CLOUDSTACK-7886: cloudstackoperations like deployvm,deleteNW are failing if CS fail to contact rabbit mq server. This is happening in case of Async API calls. CLOUDSTACK-7903: Decreased minimal usage aggregation range value CLOUDSTACK-7917: Validating Load Balancer Rule when updating LB + unit test CLOUDSTACK-7950: AttachIsoCmd shoud give correct messge when trying to attach vmwaretools installer iso on non supported guestvm deployed by ISO CLOUDSTACK-7951: Limit amount of memory used by cloudstack-agent jsvc CLOUDSTACK-7954: ListTags API is ignoring the resourceID and displaying all the tags of all resources. CLOUDSTACK-7966: remove snapshot_store_ref entry, in which role is Primary, during storage GC CLOUDSTACK-7974: remove old hostname entry for a VM when adding a VM CLOUDSTACK-7986: [F5 LB] Failed to execute IPAssocCommand due to com.cloud.utils.exception.ExecutionException: Exception caught in Networking::urn:iControl:Networking/VLAN::create() CLOUDSTACK-8014: Fix NPE searching including removed templates On Wed, Feb 4, 2015 at 5:17 PM, Daan Hoogland <daan.hoogl...@gmail.com> wrote: > There is the git commit log, and Pierre-Luc created a changelog in the > release notes, but as 4.4.3 never got release I don't know if it still > exists or where > > @Pierre-Luc: is it still there? > > On Wed, Feb 4, 2015 at 5:14 PM, Andrei Mikhailovsky <and...@arhont.com> wrote: >> Daan, do you know if there is a changelog for the current 4.4.3 branch? >> Perhaps you are right and some of the issues were fixed. >> >> Andrei >> >> ----- Original Message ----- >> >>> From: "Daan Hoogland" <daan.hoogl...@gmail.com> >>> To: "dev" <dev@cloudstack.apache.org> >>> Sent: Wednesday, 4 February, 2015 4:01:55 PM >>> Subject: Re: Downgrading recommendations from 4.4.2 to 4.3.2 >> >>> Andrei, >> >>> The 4.4.2 version sysvms report version 4.4.1. Unless you bake your >>> own. I made some custom templates for xen and vmware for internal >>> use. >>> the 4.4.1 version should be fine though. >> >>> as for fix forward, going to 4.5 is an option but I meant keeping >>> your >>> own branch and cherry-picking fixes that you need until a new stable >>> release is out. >> >>> 4.4.3 was never voted in, but you could try that one >> >>> On Wed, Feb 4, 2015 at 4:47 PM, Andrei Mikhailovsky >>> <and...@arhont.com> wrote: >>> > Actually, all my systemvms and VRs are running 4.4.1 eventhough I >>> > am sure i've used the latest templates. Could someone running >>> > version 4.4.2 please verify the version of their systemvms? >>> > >>> > Kind regards >>> > >>> > ----- Original Message ----- >>> > >>> >> From: "Pierre-Luc Dion" <pd...@cloudops.com> >>> >> To: dev@cloudstack.apache.org >>> >> Sent: Wednesday, 4 February, 2015 2:09:30 PM >>> >> Subject: Re: Downgrading recommendations from 4.4.2 to 4.3.2 >>> > >>> >> Andrei, >>> > >>> >> I wouldn't recommend to downgrade, I did that in the past when we >>> >> upgraded >>> >> to 4.2.1 and I end up with even more issues. For the maintenance >>> >> mode >>> >> issue, can you verify that systemvm currently running (including >>> >> VR) >>> >> run as >>> >> 4.4.2 ? I've saw behavior like this when upgrading to 4.4.x where >>> >> CloudStack remain in Maintenance mode until all VR and system vm >>> >> run >>> >> to the >>> >> proper ACS version. This is in /etc/cloudstack of VRs, cpvm and >>> >> ssvm. >>> >> if >>> >> not at 4.4.2, try to install a new systemvm template and apply it >>> >> to >>> >> complete the upgrade of system VMs. >>> > >>> >> Hope this help and you won't have to deal with a rollback, if so, >>> >> please >>> >> share your experience >>> > >>> >> On Wed, Feb 4, 2015 at 8:51 AM, Andrei Mikhailovsky >>> >> <and...@arhont.com> >>> >> wrote: >>> > >>> >> > Daan, >>> >> > >>> >> > Do you mean that I should wait for the 4.5 branch to be out and >>> >> > try >>> >> > an >>> >> > upgrade hoping that the issues are fixed? >>> >> > >>> >> > Why do you think downgrading the database is a tricky business? >>> >> > Let's say >>> >> > I do the following: >>> >> > >>> >> > 1. Backup existing data base >>> >> > 2. Remove all virtual routers >>> >> > 3. remove the existing db (make a backup just in case). >>> >> > 4. restore db from 4.3.2 >>> >> > 5. downgrade packages >>> >> > 6. restart networking (hopefully it will recreate all virtual >>> >> > routers) >>> >> > >>> >> > Or do you think there might be some issues in this process? >>> >> > >>> >> > Thanks >>> >> > >>> >> > ----- Original Message ----- >>> >> > >>> >> > > From: "Daan Hoogland" <daan.hoogl...@gmail.com> >>> >> > > To: "dev" <dev@cloudstack.apache.org> >>> >> > > Sent: Wednesday, 4 February, 2015 12:34:08 PM >>> >> > > Subject: Re: Downgrading recommendations from 4.4.2 to 4.3.2 >>> >> > >>> >> > > Andrei, >>> >> > >>> >> > > downgrading the database is your big problem. You don't want >>> >> > > to >>> >> > > restore at this point. I would go for fix forward but that's >>> >> > > having >>> >> > > the ability to maintain my own.branch. >>> >> > >>> >> > > On Wed, Feb 4, 2015 at 1:21 PM, Andrei Mikhailovsky >>> >> > > <and...@arhont.com> wrote: >>> >> > > > >>> >> > > > >>> >> > > > Hello guys, >>> >> > > > >>> >> > > > I was hoping to get some suggestions on how to perform a >>> >> > > > downgrade >>> >> > > > from a live 4.4.2 environment back to 4.3.2. After >>> >> > > > performing >>> >> > > > an >>> >> > > > upgrade 4 days ago, I have discovered a bunch of problems >>> >> > > > with >>> >> > > > 4.4.2 release, which makes it unusable for me. Problems like >>> >> > > > CLOUDSTACK-8201, CLOUDSTACK-8210 and inability to create new >>> >> > > > instances (yet to open a support ticket) are kind of big >>> >> > > > issues >>> >> > > > for me! >>> >> > > > >>> >> > > > Prior to performing an upgrade I've backed up cloud and >>> >> > > > cloud_usage >>> >> > > > databases of version 4.3.2. I have previously downgraded ACS >>> >> > > > several times without any issues. However, i've done the >>> >> > > > downgrade >>> >> > > > a few hours after performing an upgrade. This time, it's >>> >> > > > been >>> >> > > > about 4 days since i've done the upgrade. Since then, I've >>> >> > > > restarted many networks with clean up enabled, which >>> >> > > > resulted >>> >> > > > in >>> >> > > > creation of new virtual routers. I've also created a few >>> >> > > > test >>> >> > > > vms, >>> >> > > > templates and snapshots, but I am not actually too concerned >>> >> > > > about >>> >> > > > those. >>> >> > > > >>> >> > > > What is the best route for me to do a downgrade to 4.3.2? I >>> >> > > > am >>> >> > > > planning to do it this weekend, however, I can do it sooner. >>> >> > > > Just >>> >> > > > need to make sure my ACS will not be even more broken. >>> >> > > > >>> >> > > > Many thanks >>> >> > > > >>> >> > > > Andrei >>> >> > > > >>> >> > >>> >> > > -- >>> >> > > Daan >>> >> > >> >>> -- >>> Daan > > > > -- > Daan -- Daan
