Hi Bobby,
I checked the 4.5-4.11 upgrade environment, due to the nature of how static checker with commands.properties work, admins will be required to add/update new API/ACLs in the commands.properties file. Adding the following to commands.properties file and restarting mgmt server fixes the issue: quotaIsEnabled=15 Please continue testing, thanks. - Rohit <https://cloudstack.apache.org> ________________________________ From: Boris Stoyanov <boris.stoya...@shapeblue.com> Sent: Wednesday, January 17, 2018 6:54:28 PM To: us...@cloudstack.apache.org Cc: dev@cloudstack.apache.org Subject: Re: [VOTE] Apache Cloudstack 4.11.0.0 (LTS) I think I’ve hit a blocker when upgrading to 4.11 Here’s the jira id: https://issues.apache.org/jira/browse/CLOUDSTACK-10236 I’ve upgraded from 4.5 to 4.11, then I’ve logged in with admin and got session expired immediately. Regards, Boris Stoyanov boris.stoya...@shapeblue.com www.shapeblue.com<http://www.shapeblue.com> 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue rohit.ya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue On 17 Jan 2018, at 8:42, Tutkowski, Mike <mike.tutkow...@netapp.com<mailto:mike.tutkow...@netapp.com>> wrote: Hi everyone, For the past couple days, I have been running the KVM managed-storage regression-test suite against RC1. With the exception of one issue (more on this below), all of these tests have passed. Tomorrow I plan to start in on the VMware-related managed-storage tests. Once I’ve completed running those, I expect to move on to the XenServer-related managed-storage tests. I ran these XenServer and VMware tests just prior to RC1 being created, so I suspect all of those tests will come back successful. Now, with regards to the one issue I found on KVM with managed storage: It relates to a new feature whereby you can online migrate the storage of a VM from NFS or Ceph to managed storage. During the code-review process, I made a change per a suggestion and it introduced an issue with this feature. The solution is just a couple lines of code and only impacts this one use case. If you are testing this release candidate and don’t really care about this particular feature, it should not at all impact your ability to test RC1. Thanks! Mike On Jan 15, 2018, at 4:33 AM, Rohit Yadav <ro...@apache.org<mailto:ro...@apache.org>> wrote: Hi All, I've created a 4.11.0.0 release, with the following artifacts up for testing and a vote: Git Branch and Commit SH: https://gitbox.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.11.0.0-RC20180115T1603 Commit: 1b8a532ba52127f388847690df70e65c6b46f4d4 Source release (checksums and signatures are available at the same location): https://dist.apache.org/repos/dist/dev/cloudstack/4.11.0.0/ PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884): https://dist.apache.org/repos/dist/release/cloudstack/KEYS The 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) Additional information: For users' convenience, I've built packages from 1b8a532ba52127f388847690df70e65c6b46f4d4 and published RC1 repository here: http://cloudstack.apt-get.eu/testing/4.11-rc1 The release notes are still work-in-progress, but the systemvmtemplate upgrade section has been updated. You may refer the following for systemvmtemplate upgrade testing: http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/latest/index.html 4.11 systemvmtemplates are available from here: https://download.cloudstack.org/systemvm/4.11/ Regards, Rohit Yadav
