Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
4.3.0
-
None
-
Security Level: Public (Anyone can view this level - this is the default.)
-
None
Description
We use a custom SSL certificate that had been installed before the upgrade.
After upgrading from 4.2.1 to 4.3 the console proxy did not work due to a wrong SSL url being generated:
https://1-2-3-4.*.ssl.example.com instead of https://1-2-3-4.ssl.example.com
We fixed this by altering these settings to remove "*."
secstorage.ssl.cert.domain
consoleproxy.url.domain
These settings were altered during the upgrade, and they actually break it.
2014-03-27 14:46:45,429 DEBUG [utils.db.ScriptRunner] (main:null) UPDATE `cloud`.`configuration` SET value = CONCAT("*.",(SELECT `temptable`.`value` FROM (SELECT * FROM `cloud`.`configuration` WHERE `name`="consoleproxy.url.domain") AS `temptable` WHERE `temptable`.`name`="consoleproxy.url.domain")) WHERE `name`="consoleproxy.url.domain"
2014-03-27 14:46:45,441 DEBUG [utils.db.ScriptRunner] (main:null) UPDATE `cloud`.`configuration` SET `value` = CONCAT("*.",(SELECT `temptable`.`value` FROM (SELECT * FROM `cloud`.`configuration` WHERE `name`="secstorage.ssl.cert.domain") AS `temptable` WHERE `temptable`.`name`="secstorage.ssl.cert.domain")) WHERE `name`="secstorage.ssl.cert.domain"
The SQL can be found in this file:
/usr/share/cloudstack-management/setup/db/schema-421to430.sql
Please fix this!
Thanks,
Remi