nvazquez commented on issue #6074: URL: https://github.com/apache/cloudstack/issues/6074#issuecomment-1063245051
Yes @AlexanderKgr I have seen that - have also been investigating why your database contains that column if version 4.16.0 does not contain it and was introduced only on 4.16.1. Found this PR which introduced the constraint that is blocking you from removing the column: https://github.com/apache/cloudstack/pull/5541/files#diff-c3fcc536a9c25282503a8d8f0c07b5320ab9c6ffea9e199bafdba6e306f0aa8bR796. But this PR was reverted(https://github.com/apache/cloudstack/pull/5665) and not included on 4.16.0. It seems like you were not using the 4.16.0 release packages but a development version. This is not included on 4.16.0: ```` ALTER TABLE cloud.vm_work_job ADD CONSTRAINT vm_work_job_step_and_objects UNIQUE KEY (step,vm_instance_id,secondary_object); ```` Anyways, to revert this constraint I would suggest the following SQL and then retry dropping the column: ```` ALTER TABLE cloud.vm_work_job DROP CONSTRAINT vm_work_job_step_and_objects; ```` Let us know if that fixes the problem, after dropping the column you should be able to upgrade -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
