SSH Keypair Issue When Scaling Out SOACS Instance
(Doc ID 2879635.1)
Last updated on JUNE 29, 2022
Applies to:SOA Suite Cloud Service - Version N/A to N/A
Information in this document applies to any platform.
Attempting to scale out a single-node instance of SOACS to make it a two-node cluster through the SOA PaaS console. It failed with the following error:
May 25, 2022 7:24:48 PM UTC Started scaling operation on service [<HOST_NAME>] in identity domain [idcs-d6ec2b861ccd40799ebc6fbd00078bbf].
May 25, 2022 7:27:43 PM UTC Completed scaling operation on service [<HOST_NAME>] in domain [idcs-d6ec2b861ccd40799ebc6fbd00078bbf].
May 25, 2022 7:30:36 PM UTC Started operation to check provisioning status on the VMs for [WLS]
May 25, 2022 7:51:33 PM UTC Service has returned the following error(s) for service component [WLS]: [<JCS-ERR-20426> : Provisioning failed on host(s)<HOST_NAME> <JCS-ERR-20425> : <Provisioning check failed to execute check_logs.py on host<HOST_NAME> : Permission denied (publickey,gssapi-keyex,gssapi-with-mic). >].
May 25, 2022 7:51:33 PM UTC PSM-LCM-01101 Unable to provision service. One or more components could not be configured. See additional errors for more details.
May 25, 2022 7:51:55 PM UTC Submitted scale in job to clean up resources for the failed scale out operation.
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