...
After deploying, with 1.3.5 images, there will still be a problem. The 'homing_instances' table is not created in the SO database.
The so-catalog-db-adapter and so-openstack-adapter pods will be in a CrashLoopBackup state. The workaround is to create it manually. Once this is done, the pods will start to run normally.
The SQL commands to do so create the table are:
use catalogdb;
CREATE TABLE IF NOT EXISTS `homing_instances` (
`SERVICE_INSTANCE_ID` varchar(50) NOT NULL,
`CLOUD_OWNER` VARCHAR(200) NOT NULL,
`CLOUD_REGION_ID` VARCHAR(200) NOT NULL,
`OOF_DIRECTIVES` longtext NULL DEFAULT NULL,
PRIMARY KEY (`SERVICE_INSTANCE_ID`)
) ;