Sangeetha Hariharan created CLOUDSTACK-1811:
-----------------------------------------------
Summary: Upgrade 4.0->4.1 - When upgrade scripts fail , component
loading continues and management server starts.
Key: CLOUDSTACK-1811
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1811
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Management Server
Affects Versions: 4.1.0
Environment: Upgrade from 4.0 -> 4.1
Reporter: Sangeetha Hariharan
Assignee: Kelven Yang
Fix For: 4.1.0
Upgrade 4.0 -> 4.1 - When upgrade scripts fail , component loading continues
and management server starts.
Steps to reproduce the problem:
1. Install and configure 4.0 setup
2. Create 4.1 repo and update the packages to 4.1
3. Tried to start Management server.
DB updgrade fails ( tracked in cloudstack-1804) and we see the version in DB
is still at 4.0. In spite of DB upgrade failing , management server process
starts up.
Also we are able to log in to the management server as admin user but we are
not presented with the dashboard view and user is presented with the following
error message - "The given command does not exist or it is not available for
user"
Expected Behavior:
Management server should not start in case of encountering DB upgrade failures.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
