Issues identified post Casablanca release (as detailed below) have now been resolved in the Casablanca maintenance release.
Fixes for a few issues:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-1257 Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-1254 Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-1258
were released after the Casablanca release images were created. In order to test the HPA functionality, the docker manifest of the ONAP installation should be updated.
See https://onap.readthedocs.io/en/casablanca/submodules/integration.git/docs/#deploying-an-updated-docker-manifest for details on how to do this.
Use the 1.3.5 version of the SO docker images to get these fixes.
Other Known Issues:
Issues identified/fixed after the 1.3.5 docker images:
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-1306
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 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`)) ;
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SO-1262 For testing, we've followed the process described in SO How to over OOM to build the code and update the bpmn-infra pod with the new jar file.