The following table lists the issues you might encounter and the suggested actions for working on these issues. If the problem persists, contact your NetIQ representative.
|
Issue |
Suggested action |
|---|---|
|
When you are running the deploy.yml for the first time in your deployment, you will see the following message indicating that the Docker images are not present on the target nodes. For example, if you are deploying the Core DNS container, you will see the following error: fatal: [<ip address/DNS>]: FAILED! => {"changed": true, "cmd": "docker images | grep coredns | grep 1.8.0", "delta": "0:00:00.914078", "end": "msg": "non-zero return code", "rc": 1, "start": "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} |
There is no workaround at this time. However, you can ignore the message and proceed with the deployment. This does not cause any loss in functionality. |
|
The container deployment fails when the IP address is already in use by a different container across your network. The following exception is reported on the console. fatal: [<ip address/DNS>]: FAILED! => {"changed": false, "msg": "Error starting container b1eb07f42cf6bd63787ae6167f5e3a0f7cbee0f8be80a5764bcc7c7f9d6b96b1: 403 Client Error for http+docker://localhost/v1.40/containers/b1eb07f42cf6bd63787ae6167f5e3a0f7cbee0f8be80a5764bcc7c7f9d6b96b1/start: Forbidden (\"Address already in use\")"} |
Assign a different IP address for the container. |
|
After deploying the Identity Applications container, when you log in to the Identity Manager Dashboard and navigate to the Tasks page, the Dashboard does not fetch the list of tasks as expected. The following error is reported in the catalina.out file. SEVERE [main] org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource Unable to process web resource [/WEB-INF/classes/com/microfocus/idm/nrf/resources/NRFRsrc_fr.class] for annotations java.io.EOFException at java.io.DataInputStream.readFully(DataInputStream.java:197) at java.io.DataInputStream.readUTF(DataInputStream.java:609) at java.io.DataInputStream.readUTF(DataInputStream.java:564) at org.apache.tomcat.util.bcel.classfile.ConstantUtf8.getInstance(ConstantUtf8.java:36) at org.apache.tomcat.util.bcel.classfile.Constant.readConstant(Constant.java:79) at org.apache.tomcat.util.bcel.classfile.ConstantPool.<init>(ConstantPool.java:53) at org.apache.tomcat.util.bcel.classfile.ClassParser.readConstantPool(ClassParser.java:174) at org.apache.tomcat.util.bcel.classfile.ClassParser.parse(ClassParser.java:83) at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2351) at org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:2250) at org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:2244) at org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:2244) at org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:2244) at org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:2244) at org.apache.catalina.startup.ContextConfig.processAnnotationsWebResource(ContextConfig.java:2244) at org.apache.catalina.startup.ContextConfig.processClasses(ContextConfig.java:1397) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1302) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:985) |
To workaround this issue, perform the following steps:
|