Ops Center LDOM Deployment - ERROR java.io.IOException: Unable to create installadm service <HOSTNAME>_xxxx
(Doc ID 1515074.1)
Last updated on DECEMBER 28, 2020
Applies to:
Enterprise Manager Ops Center - Version 12.3.0 to 12.4.0 [Release 12.0]Information in this document applies to any platform.
Symptoms
The issue is that the LDOM is created but the manifest creation step is failing during the provisioning step.
For example when Installation Plan fails on OPS Proxy with
Task : Configure Install Server
Task Run ID : 98230
Target : <IP>
Status : ROLLBACK_SUCCESS
Result : Cleanup completed for client '<HOSTNAME>'.
Logs :
04/29/2015 02:42:35 PM CEST INFO Invoking the prepare method of this target. (15018)
04/29/2015 02:42:35 PM CEST INFO Successfully constructed client override information for <MAC>
04/29/2015 02:42:35 PM CEST INFO Task is posted to the Proxy Controller (<HOSTNAME>-d7399c78), from the Enterprise Controller. (15011)
04/29/2015 02:42:36 PM CEST INFO Task is received by the Proxy Controller. (15012)
04/29/2015 02:42:36 PM CEST INFO Successfully got client information: <HOSTNAME>
04/29/2015 02:42:36 PM CEST INFO Start enabling Client ID: <MAC>
04/29/2015 02:42:36 PM CEST INFO Successfully got profile information: <HOSTNAME>
04/29/2015 02:42:36 PM CEST INFO Successfully got payload information: <HOSTNAME>
04/29/2015 02:42:36 PM CEST INFO Successfully got the client override information: <HOSTNAME>
04/29/2015 02:42:36 PM CEST INFO Starting configuration of client: <HOSTNAME>
04/29/2015 02:42:36 PM CEST INFO Start configuring client '<HOSTNAME>' using Auto Install..
04/29/2015 02:42:41 PM CEST ERROR java.io.IOException: Unable to create installadm service <HOSTNAME>_oc_solaris_sparc_2. Output from command
04/29/2015 02:42:41 PM CEST ERROR at com.sun.hss.services.osdeployment.impl.ai.CreateServiceExecutor.createService(CreateServiceExecutor.java:47)
04/29/2015 02:42:41 PM CEST ERROR at com.sun.hss.services.osdeployment.impl.ai.InstallAdmExecutor.createService(InstallAdmExecutor.java
Changes
A previously deployed LDOM guest <HOSTNAME> was removed to try to fix a VNIC problem. Subsequent re-deployments of this LDOM (using the same name: <HOSTNAME>) are failing at the "installadm create-manifest" phase.
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 |
Changes |
Cause |
Solution |