Siebel Cloud Manager: Greenfield Deployment Failing At Check ORM Stack Job Execution Status with Error: 400-InvalidParameter, Cannot access Object Storage using the subnet with the following OCID
(Doc ID 3013509.1)
Last updated on APRIL 04, 2024
Applies to:
Siebel CRM - Version 24.1 to 24.2 [Release V17]Information in this document applies to any platform.
Symptoms
When performing a Greenfield deployment using Siebel Cloud Manager (SCM), the deployment fails and the following error is seen in the payload response:
"stages": [
...
{
"end_time": "Wed, 16 Mar 2024 16:24:06 +0000",
"log_api_link": "http://<Siebel Cloud Name IP>:16690/api/v1/environments/<Env ID>/logs/check-orm-stack",
"log_location": "/home/opc/siebel/<Env ID>/logs/stack.log",
"name": "Check ORM stack job execution status",
"previous_status": "",
"stage_description": "Check ORM stack job execution status",
"stage_name": "check-orm-stack",
"start_time": "Wed, 16 Mar 2024 16:24:05 +0000",
"status": "failed"
},
The issue can be reproduced at will with the following steps:
1. Perform greenfield deployment by executing POST call to Siebel Cloud Manager: http://<Siebel Cloud Name IP>:16690/api/v1/environments/
2. Get selflink URL from POST request response
3. Check Deployment Status using a GET request using selflink URL, example: http://<Siebel Cloud Name IP>:16690/api/v1/environments/<Env ID>
4. Check through the response to see if "stage_name": "check-orm-stack", failed
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |