If you have issues with IBM FileNet® Content Manager
pods during setup by the initialization container, check for volume and folder
permissions.
About this task
When using the initialization container to set up your environment, you might encounter
permission errors. The initialization container copies JDBC drivers from the operator to the Content
Platform Engine pods. If the copy operation does not succeed, the initialization process can become
stuck.You can use the steps to check the logs and determine whether this issue is interfering
with your initialization container.
Procedure
- Get the name of the initContainer:
oc describe pod $cpe_pod_name
- Under initContainer, get the name of the job, for example:
- To see the error information, run a command like the following:
oc logs $cpe_pod_name -c cpe-copy-jdbc
You might see error information like the following
example:
[user ~]# oc logs demo-cpe-deploy-6997f7675c-mfc4h -c cpe-copy-jdbc
+ cp /opt/ansible/share/jdbc/db2/db2jcc4.jar /opt/ansible/share/jdbc/db2/db2jcc_license_cu.jar /opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides
cp: cannot create regular file '/opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides/db2jcc4.jar': Permission denied
cp: cannot create regular file '/opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides/db2jcc_license_cu.jar': Permission denied
[user ~]#
- To solve the problem, check that the permissions on your volumes and folders match the
requirements that are specified in Creating volumes and folders.
Correct permissions as needed and try
the deploy operation again.