raymonvdm opened a new issue #2804: Upgrade issue 4.10.0 to 4.11.0 URL: https://github.com/apache/cloudstack/issues/2804 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ UI ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ Upgrade from 4.10.0 to 4.11.0 fails with different issues ~~~ ##### CONFIGURATION <!-- Information about the configuration if relevant, e.g. basic network, advanced networking, etc. N/A otherwise --> ~~~ No networking issues yet ~~~ ##### OS / ENVIRONMENT <!-- Information about the environment if relevant, N/A otherwise --> ~~~ Ubuntu 14.04 VM running cloudstack management agent. 2 x Ubuntu 14.04 and 16.04 running KVM as HyperVisors ~~~ ##### SUMMARY <!-- Explain the problem/feature briefly --> ~~~ During the upgrade from 4.10 to 4.11 the database upgrade fails with the message logid:) Unable to upgrade the database com.cloud.utils.exception.CloudRuntimeException: 4.11.0.0KVM SystemVm template not found. Cannot upgrade system Vms Second run same error. I have followed these instructions and it looks like a naming issue in the new templates. http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.11/upgrade/upgrade-4.10.html I managed to recover by checking the .sql file https://github.com/apache/cloudstack/blob/3109c590e3d69de83a114ed6fdb12b706e46a7f3/engine/schema/resources/META-INF/db/schema-41000to41100.sql The database upgrade seems to be working and after adding the upgrade statement in the version table the UI is working again. But when clicking Account i get the following database error ~~~ ~~~ DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@600d2498: SELECT user_view.id, user_view.uuid, user_view.username, user_view.password, user_view.firstname, user_view.lastname, user_view.email, user_view.state, user_view.api_key, user_view.secret_key, user_view.created, user_view.removed, user_view.timezone, user_view.registration_token, user_view.is_registered, user_view.incorrect_login_attempts, user_view.account_id, user_view.account_uuid, user_view.account_name, user_view.account_type, user_view.account_role_id, user_view.domain_id, user_view.domain_uuid, user_view.domain_name, user_view.domain_path, user_view.job_id, user_view.job_uuid, user_view.job_status, user_view.default, user_view.source FROM user_view WHERE user_view.account_id = 2 AND user_view.removed IS NULL ~~~ ##### STEPS TO REPRODUCE <!-- For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate. For new features, show how the feature would be used. --> <!-- Paste example playbooks or commands between quotes below --> ~~~ ~~~ <!-- You can also paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> ~~~ ~~~ ##### ACTUAL RESULTS <!-- What actually happened? --> <!-- Paste verbatim command output between quotes below --> ~~~ ~~~
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
