[
https://issues.apache.org/jira/browse/CLOUDSTACK-4065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730904#comment-13730904
]
Alena Prokharchyk commented on CLOUDSTACK-4065:
-----------------------------------------------
Angie, its a diff bug. Please file it separately.
> [ Upgrade ] 3.0.7 GA -> 4.2 fail - advance zone SG enabled guest networks
> same VLAN different subnet
> --------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4065
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4065
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: MS 10.223.195.62 build 3.0.7 GA upgrade
> campo 4.2 build CloudPlatform-4.2-324-rhel6.3.tar.gz
> host 10.223.51.3 XS 6.1
> Reporter: angeline shen
> Assignee: Alena Prokharchyk
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: cloud-backup.dmp, cloud-backup.dmp, cloud-backup.sql,
> cloud-backup.sql, cloud-usage-backup.dmp, cloud-usage-backup.dmp,
> cloud-usage-backup.sql, cloud-usage-backup.sql, management-server.log.gz,
> management-server.log.gz
>
>
> MS 10.223.195.62 build 3.0.7 GA upgrade 4.2 build host
> 10.223.51.3 XS 6.1
> 1. MS install 3.0.7 GA,
> 2. create advanced zone with SG
> 3. create several networks with different subnets and same vlan
> vlan GW start IP end
> IP
> ----------------------------------------------------------------------------------------------------------
> guest network 1250 10.223.125.1 10.223.125.13 10.223.125.18
>
> 1250-66to68 1250 10.223.125.65 10.223.125.66 10.223.125.68
> 1250-130to132 1250 10.223.125.129 10.223.125.130 10.223.125.132
> 4. start VMs on each of these networks
> 125.18 125.16 125.14 125.68 125.67 125.131
> 125.132
> no ingress or egress rules :
> VMs can ssh + ping other VMs in all subnets
> VMs can egress internet
> add ingress TCP icmp egress TCP egress
> 5. make sure VM work well
> 6. upgrade to 4.2 FAIL:
> LB health check states (in sec)')
> 2013-08-03 20:58:18,463 DEBUG [utils.db.ScriptRunner] (Timer-1:null) INSERT
> IGNORE INTO `cloud`.`configuration` VALUES ('Snapshots', 'DEFAULT',
> 'SnapshotManager', 'KVM.snapshot.enabled', 'false', 'whether snapshot is
> enabled for KVM hosts')
> 2013-08-03 20:58:18,471 DEBUG [upgrade.dao.Upgrade410to420] (Timer-1:null)
> Ignoring zone 1 with hypervisor type XenServer
> 2013-08-03 20:58:18,492 ERROR [cloud.upgrade.DatabaseUpgradeChecker]
> (Timer-1:null) Unable to upgrade the database
> com.cloud.utils.exception.CloudRuntimeException: Unable to create placeholder
> nics
> at
> com.cloud.upgrade.dao.Upgrade410to420.createPlaceHolderNics(Upgrade410to420.java:769)
> at
> com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:79)
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:264)
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
> at
> com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
> at
> com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
> at java.util.TimerThread.mainLoop(Timer.java:534)
> at java.util.TimerThread.run(Timer.java:484)
> Caused by: java.sql.SQLException: Field 'default_nic' doesn't have a default
> value
> at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1074)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4074)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4006)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2468)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2629)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2719)
> at
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
> at
> com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2450)
> at
> com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2371)
> at
> com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2355)
> at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
> at
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
> at
> com.cloud.upgrade.dao.Upgrade410to420.createPlaceHolderNics(Upgrade410to420.java:764)
> ... 7 more
> 2013-08-03 20:58:18,493 DEBUG [db.Transaction.Transaction] (Timer-1:null)
> Rolling back the transaction: Time = 3269 Name =
> -CloudStartupServlet$1.run:52-TimerThread.mainLoop:534-TimerThread.run:484;
> called by
> -Transaction.rollback:896-Transaction.removeUpTo:839-Transaction.close:663-DatabaseUpgradeChecker.upgrade:293-DatabaseUpgradeChecker.check:389-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:54-TimerThread.mainLoop:534-TimerThread.run:484
> 2013-08-03 20:58:18,495 ERROR [utils.component.ComponentContext]
> (Timer-1:null) System integrity check failed. Refuse to startup
>
--
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
