[jira] [Created] (CLOUDSTACK-9916) Database upgrade script from: 4.9.2 to 10.0.0 (master) fails

["Steven Varco (JIRA)" <ji...@apache.org>]

Steven Varco created CLOUDSTACK-9916:
----------------------------------------

             Summary: Database upgrade script from: 4.9.2 to 10.0.0 (master) fails
                 Key: CLOUDSTACK-9916
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9916
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: cloudstack-agent
    Affects Versions: Future
            Reporter: Steven Varco


To test the upcoming 10.0.0 Version of CloudStack, I have built the code from the master branch and created RPMs out of that.

After upgrading the cloudstack-agent with:
{noformat}yum localinstall cloudstack-common-4.10.0.-1.el7.centos.x86_64.rpm cloudstack-agent-4.10.0.-1.el7.centos.x86_64.rpm {noformat}
I can see that the database upgrade script is being invoked:
{noformat}
2017-05-03 16:52:03,745 INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (localhost-startStop-1:null) (logid:) Running system integrity checker com.cloud.upgrade.DatabaseUpgradeChecker@45dcbe55
2017-05-03 16:52:03,747 INFO  [c.c.u.DatabaseUpgradeChecker] (localhost-startStop-1:null) (logid:) Grabbing lock to check for database upgrade.
2017-05-03 16:52:04,057 INFO  [c.c.u.DatabaseUpgradeChecker] (localhost-startStop-1:null) (logid:) DB version = 4.9.2 Code Version = 4.10.0
2017-05-03 16:52:04,057 INFO  [c.c.u.DatabaseUpgradeChecker] (localhost-startStop-1:null) (logid:) Database upgrade must be performed from 4.9.2 to 4.10.0
2017-05-03 16:52:04,060 DEBUG [c.c.u.DatabaseUpgradeChecker] (localhost-startStop-1:null) (logid:) Running upgrade NoopDbUpgrade to upgrade from 4.9.2-4.10.0 to 4.10.0
2017-05-03 16:52:04,171 INFO  [c.c.u.DatabaseUpgradeChecker] (localhost-startStop-1:null) (logid:) Cleanup upgrade NoopDbUpgrade to upgrade from 4.9.2-4.10.0 to 4.10.0.
2017-05-03 16:52:04,362 DEBUG [c.c.u.DatabaseUpgradeChecker] (localhost-startStop-1:null) (logid:) Upgrade completed for version 4.10.0
{noformat}
Then after the upgrade I get the following in the error log:
{noformat}2017-05-03 16:53:38,560 WARN  [o.a.c.s.m.c.ResourceApplicationContext] (localhost-startStop-1:null) (logid:) Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Failed to start bean 'cloudStackLifeCycle'; nested exception is com.cloud.utils.exception.CloudRuntimeException: DB Exception on: com.mysql.jdbc.JDBC4PreparedStatement@7db43ded: SELECT network_offerings.id, network_offerings.name, network_offerings.unique_name, network_offerings.display_text, network_offerings.nw_rate, network_offerings.mc_rate, network_offerings.traffic_type, network_offerings.specify_vlan, network_offerings.system_only, network_offerings.service_offering_id, network_offerings.tags, network_offerings.default, network_offerings.availability, network_offerings.state, network_offerings.removed, network_offerings.created, network_offerings.guest_type, network_offerings.dedicated_lb_service, network_offerings.shared_source_nat_service, network_offerings.specify_ip_ranges, network_offerings.sort_key, network_offerings.uuid, network_offerings.redundant_router_service, network_offerings.conserve_mode, network_offerings.elastic_ip_service, network_offerings.eip_associate_public_ip, network_offerings.elastic_lb_service, network_offerings.inline, network_offerings.is_persistent, network_offerings.egress_default_policy, network_offerings.concurrent_connections, network_offerings.keep_alive_enabled, network_offerings.supports_streched_l2, network_offerings.supports_public_access, network_offerings.internal_lb, network_offerings.public_lb FROM network_offerings WHERE network_offerings.unique_name = _binary'System-Public-Network'  AND network_offerings.removed IS NULL  ORDER BY RAND() LIMIT 1{noformat}

If I then run the mentioned mysql statement:
{noformat}
mysql -ucloud
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 49
Server version: 5.5.52-MariaDB MariaDB Server

MariaDB [(none)]> use cloud
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
MariaDB [cloud]> SELECT network_offerings.id, network_offerings.name, network_offerings.unique_name, network_offerings.display_text, network_offerings.nw_rate, network_offerings.mc_rate, network_offerings.traffic_type, network_offerings.specify_vlan, network_offerings.system_only, network_offerings.service_offering_id, network_offerings.tags, network_offerings.default, network_offerings.availability, network_offerings.state, network_offerings.removed, network_offerings.created, network_offerings.guest_type, network_offerings.dedicated_lb_service, network_offerings.shared_source_nat_service, network_offerings.specify_ip_ranges, network_offerings.sort_key, network_offerings.uuid, network_offerings.redundant_router_service, network_offerings.conserve_mode, network_offerings.elastic_ip_service, network_offerings.eip_associate_public_ip, network_offerings.elastic_lb_service, network_offerings.inline, network_offerings.is_persistent, network_offerings.egress_default_policy, network_offerings.concurrent_connections, network_offerings.keep_alive_enabled, network_offerings.supports_streched_l2, network_offerings.supports_public_access, network_offerings.internal_lb, network_offerings.public_lb FROM network_offerings WHERE network_offerings.unique_name = _binary'System-Public-Network'  AND network_offerings.removed IS NULL  ORDER BY RAND() LIMIT 1;

ERROR 1054 (42S22): Unknown column 'network_offerings.supports_public_access' in 'field list'
{noformat}

I can verify that the column: "network_offerings.supports_public_access" is not there.

Since 10.0.0 is not released yet, I would like to ask, if this is a known issue already?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)