[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-14 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363792#comment-16363792
 ] 

ASF subversion and git services commented on CLOUDSTACK-10285:
--

Commit 3109c590e3d69de83a114ed6fdb12b706e46a7f3 in cloudstack's branch 
refs/heads/master from [~rohithsharma]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=3109c59 ]

CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users (#2452)

4.10.0.0 users when upgrade to 4.11.0.0 may face db related
discrepancies due to some PRs that got merged without moving their sql
changes to 4.10->4.11 upgrade path. The 4.10.0.0 users can run those
missing sql statements manually and then upgrade to 4.11.0.0, since a
workaround like this is possible this ticket is not marked a blocker. In
4.11.1.0+, we'll move those changes from 4.9.3.0->4.10.0.0 upgrade path
to 4.10.0.0->4.11.0.0 upgrade path. Ideally we should not be doing this,
but this will fix issues for a future 4.10.0.0 user who may want to
upgrade to 4.11.1.0 or 4.12.0.0+.

Signed-off-by: Rohit Yadav 

> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-14 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363786#comment-16363786
 ] 

ASF subversion and git services commented on CLOUDSTACK-10285:
--

Commit 3109c590e3d69de83a114ed6fdb12b706e46a7f3 in cloudstack's branch 
refs/heads/4.11 from [~rohithsharma]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=3109c59 ]

CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users (#2452)

4.10.0.0 users when upgrade to 4.11.0.0 may face db related
discrepancies due to some PRs that got merged without moving their sql
changes to 4.10->4.11 upgrade path. The 4.10.0.0 users can run those
missing sql statements manually and then upgrade to 4.11.0.0, since a
workaround like this is possible this ticket is not marked a blocker. In
4.11.1.0+, we'll move those changes from 4.9.3.0->4.10.0.0 upgrade path
to 4.10.0.0->4.11.0.0 upgrade path. Ideally we should not be doing this,
but this will fix issues for a future 4.10.0.0 user who may want to
upgrade to 4.11.1.0 or 4.12.0.0+.

Signed-off-by: Rohit Yadav 

> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-14 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16363788#comment-16363788
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

rhtyd commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 
4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-365567472
 
 
   Merged based on code reviews and test results.


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16362154#comment-16362154
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

rhtyd commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 
4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-365236093
 
 
   Thanks @ustcweizhou for your lgtm. I'll wait for others for their 
feedback/review.
   @ernjvr I think we can merge this PR first and you can modify/make the 
changes idempotent using the macros you've defined in your PR.


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361998#comment-16361998
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

ernjvr commented on a change in pull request #2452: CLOUDSTACK-10285: Fix db 
upgrade failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#discussion_r167792319
 
 

 ##
 File path: engine/schema/resources/META-INF/db/schema-41000to41100.sql
 ##
 @@ -546,3 +546,24 @@ ALTER TABLE cloud.ldap_trust_map ADD COLUMN account_id 
BIGINT(20) DEFAULT 0;
 ALTER TABLE cloud.ldap_trust_map DROP FOREIGN KEY fk_ldap_trust_map__domain_id;
 DROP INDEX uk_ldap_trust_map__domain_id ON cloud.ldap_trust_map;
 CREATE UNIQUE INDEX uk_ldap_trust_map__bind_location ON ldap_trust_map 
(domain_id, account_id);
+
+CREATE TABLE IF NOT EXISTS `cloud`.`netscaler_servicepackages` (
+  `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
+  `uuid` varchar(255) UNIQUE,
+  `name` varchar(255) UNIQUE COMMENT 'name of the service package',
+  `description` varchar(255) COMMENT 'description of the service package',
+  PRIMARY KEY  (`id`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+
+CREATE TABLE IF NOT EXISTS `cloud`.`external_netscaler_controlcenter` (
+  `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
+  `uuid` varchar(255) UNIQUE,
+  `username` varchar(255) COMMENT 'username of the NCC',
+  `password` varchar(255) COMMENT 'password of NCC',
+  `ncc_ip` varchar(255) COMMENT 'IP of NCC Manager',
+  `num_retries` bigint unsigned NOT NULL default 2 COMMENT 'Number of retries 
in ncc for command failure',
+  PRIMARY KEY  (`id`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+
+ALTER TABLE `cloud`.`sslcerts` ADD COLUMN `name` varchar(255) NULL default 
NULL COMMENT 'Name of the Certificate';
 
 Review comment:
   if pull request https://github.com/apache/cloudstack/pull/2449 gets approved 
and merged, we can make this add column statement idempotent afterwards


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361930#comment-16361930
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

ustcweizhou commented on a change in pull request #2452: CLOUDSTACK-10285: Fix 
db upgrade failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#discussion_r167781635
 
 

 ##
 File path: engine/schema/resources/META-INF/db/schema-41000to41100.sql
 ##
 @@ -546,3 +546,24 @@ ALTER TABLE cloud.ldap_trust_map ADD COLUMN account_id 
BIGINT(20) DEFAULT 0;
 ALTER TABLE cloud.ldap_trust_map DROP FOREIGN KEY fk_ldap_trust_map__domain_id;
 DROP INDEX uk_ldap_trust_map__domain_id ON cloud.ldap_trust_map;
 CREATE UNIQUE INDEX uk_ldap_trust_map__bind_location ON ldap_trust_map 
(domain_id, account_id);
+
+CREATE TABLE IF NOT EXISTS `cloud`.`netscaler_servicepackages` (
+  `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
+  `uuid` varchar(255) UNIQUE,
+  `name` varchar(255) UNIQUE COMMENT 'name of the service package',
+  `description` varchar(255) COMMENT 'description of the service package',
+  PRIMARY KEY  (`id`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+
+CREATE TABLE IF NOT EXISTS `cloud`.`external_netscaler_controlcenter` (
+  `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
+  `uuid` varchar(255) UNIQUE,
+  `username` varchar(255) COMMENT 'username of the NCC',
+  `password` varchar(255) COMMENT 'password of NCC',
+  `ncc_ip` varchar(255) COMMENT 'IP of NCC Manager',
+  `num_retries` bigint unsigned NOT NULL default 2 COMMENT 'Number of retries 
in ncc for command failure',
+  PRIMARY KEY  (`id`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+
+ALTER TABLE `cloud`.`sslcerts` ADD COLUMN `name` varchar(255) NULL default 
NULL COMMENT 'Name of the Certificate';
 
 Review comment:
   @rhtyd thanks for your explanation. 
   LGTM now.


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16361539#comment-16361539
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade 
failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-365082774
 
 
   Trillian test result (tid-2254)
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 23691 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2452-t2254-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
   Smoke tests completed. 65 look OK, 2 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_04_rvpc_privategw_static_routes | `Failure` | 277.99 | 
test_privategw_acl.py
   test_hostha_enable_ha_when_host_in_maintenance | `Error` | 3.43 | 
test_hostha_kvm.py
   


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360867#comment-16360867
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade 
failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364954377
 
 
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been 
kicked to run smoke tests


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360865#comment-16360865
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

rhtyd commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 
4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364954204
 
 
   @blueorangutan test


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360777#comment-16360777
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade 
failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364930948
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1710


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360754#comment-16360754
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade 
failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364907238
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1709


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360756#comment-16360756
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade 
failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364923692
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360753#comment-16360753
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade 
failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364901557
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360752#comment-16360752
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

rhtyd commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 
4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364923525
 
 
   @blueorangutan package


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360748#comment-16360748
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

rhtyd commented on a change in pull request #2452: CLOUDSTACK-10285: Fix db 
upgrade failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#discussion_r167555229
 
 

 ##
 File path: engine/schema/resources/META-INF/db/schema-41000to41100.sql
 ##
 @@ -546,3 +546,24 @@ ALTER TABLE cloud.ldap_trust_map ADD COLUMN account_id 
BIGINT(20) DEFAULT 0;
 ALTER TABLE cloud.ldap_trust_map DROP FOREIGN KEY fk_ldap_trust_map__domain_id;
 DROP INDEX uk_ldap_trust_map__domain_id ON cloud.ldap_trust_map;
 CREATE UNIQUE INDEX uk_ldap_trust_map__bind_location ON ldap_trust_map 
(domain_id, account_id);
+
+CREATE TABLE IF NOT EXISTS `cloud`.`netscaler_servicepackages` (
+  `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
+  `uuid` varchar(255) UNIQUE,
+  `name` varchar(255) UNIQUE COMMENT 'name of the service package',
+  `description` varchar(255) COMMENT 'description of the service package',
+  PRIMARY KEY  (`id`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+
+CREATE TABLE IF NOT EXISTS `cloud`.`external_netscaler_controlcenter` (
+  `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
+  `uuid` varchar(255) UNIQUE,
+  `username` varchar(255) COMMENT 'username of the NCC',
+  `password` varchar(255) COMMENT 'password of NCC',
+  `ncc_ip` varchar(255) COMMENT 'IP of NCC Manager',
+  `num_retries` bigint unsigned NOT NULL default 2 COMMENT 'Number of retries 
in ncc for command failure',
+  PRIMARY KEY  (`id`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+
+ALTER TABLE `cloud`.`sslcerts` ADD COLUMN `name` varchar(255) NULL default 
NULL COMMENT 'Name of the Certificate';
 
 Review comment:
   The assumption is it won't exist in before 4.11.0.0 release. Users of 
4.9.3.0 or earlier will get this change when they upgrade to 4.11.0.0 but 
4.10.0.0 users won't. See the dev/user ML for the discussion/proposal. But I 
see what you mean, the query is not idempotent which perhaps @ernjvr and 
@borisstoyanov may help improve.


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360673#comment-16360673
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

ustcweizhou commented on a change in pull request #2452: CLOUDSTACK-10285: Fix 
db upgrade failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#discussion_r167540175
 
 

 ##
 File path: engine/schema/resources/META-INF/db/schema-41000to41100.sql
 ##
 @@ -546,3 +546,24 @@ ALTER TABLE cloud.ldap_trust_map ADD COLUMN account_id 
BIGINT(20) DEFAULT 0;
 ALTER TABLE cloud.ldap_trust_map DROP FOREIGN KEY fk_ldap_trust_map__domain_id;
 DROP INDEX uk_ldap_trust_map__domain_id ON cloud.ldap_trust_map;
 CREATE UNIQUE INDEX uk_ldap_trust_map__bind_location ON ldap_trust_map 
(domain_id, account_id);
+
+CREATE TABLE IF NOT EXISTS `cloud`.`netscaler_servicepackages` (
+  `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
+  `uuid` varchar(255) UNIQUE,
+  `name` varchar(255) UNIQUE COMMENT 'name of the service package',
+  `description` varchar(255) COMMENT 'description of the service package',
+  PRIMARY KEY  (`id`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+
+CREATE TABLE IF NOT EXISTS `cloud`.`external_netscaler_controlcenter` (
+  `id` bigint unsigned NOT NULL AUTO_INCREMENT COMMENT 'id',
+  `uuid` varchar(255) UNIQUE,
+  `username` varchar(255) COMMENT 'username of the NCC',
+  `password` varchar(255) COMMENT 'password of NCC',
+  `ncc_ip` varchar(255) COMMENT 'IP of NCC Manager',
+  `num_retries` bigint unsigned NOT NULL default 2 COMMENT 'Number of retries 
in ncc for command failure',
+  PRIMARY KEY  (`id`)
+) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+
+ALTER TABLE `cloud`.`sslcerts` ADD COLUMN `name` varchar(255) NULL default 
NULL COMMENT 'Name of the Certificate';
 
 Review comment:
   Is it possible that `name` field already exists in `sslcerts` table ?
   If yes, upgrade will fail here.
   


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360668#comment-16360668
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade 
failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364907238
 
 
   Packaging result: ✔centos6 ✔centos7 ✔debian. JID-1709


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360644#comment-16360644
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

blueorangutan commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade 
failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-364901557
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0

2018-02-12 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16360643#comment-16360643
 ] 

ASF GitHub Bot commented on CLOUDSTACK-10285:
-

rhtyd opened a new pull request #2452: CLOUDSTACK-10285: Fix db upgrade failure 
for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452
 
 
   4.10.0.0 users when upgrade to 4.11.0.0 may face db related
   discrepancies due to some PRs that got merged without moving their sql
   changes to 4.10->4.11 upgrade path. The 4.10.0.0 users can run those
   missing sql statements manually and then upgrade to 4.11.0.0, since a
   workaround like this is possible this ticket is not marked a blocker. In
   4.11.1.0+, we'll move those changes from 4.9.3.0->4.10.0.0 upgrade path
   to 4.10.0.0->4.11.0.0 upgrade path. Ideally we should not be doing this,
   but this will fix issues for a future 4.10.0.0 user who may want to
   upgrade to 4.11.1.0 or 4.12.0.0+.
   
   The failure hit is missing column `service_package_id`.
   Issue was caused primarily due to `884606f77be7621944d2f315fd8eabe8884c45d9`.
   
   Pinging for review - @PaulAngus @borisstoyanov @DaanHoogland @wido @karuturi 
@sateesh-chodapuneedi and others.
   
   @blueorangutan package


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:
us...@infra.apache.org


> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -
>
> Key: CLOUDSTACK-10285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Rohit Yadav
>Assignee: Rohit Yadav
>Priority: Critical
> Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)