>> >>enance release we will like to avoid schema >> changes as much as possible. > >it sounds like a pretty big issue IMHO, if not even a security risk.
Schema changes are bit messy in a maintenance release as it will require changes to upgrade script etc. We can put the fix in 4.3 and document this as known issue in 4.2.1 > >In addition there was this bug: >https://issues.apache.org/jira/browse/CLOUDSTACK-5214 > >reported by milamber on 4.2.1 upgrade. He raise it as a blocker. > >if both need a db schema fix, then maybe we need to bite the bullet... CLOUDSTACK-5214: Checked the ticket the fix does not require a schema change it just requires a check. Milamber has already verified the fix, it would be great if he can commit the fix. > >> >> A temporary fix (i.e. Till we fix schema in next big release) could mean >> fetching vpc list for a user from vpc table and then use the vpc ids to >> get the acls. *Marcus* you want to try out this fix ? >> >> -abhi >>
