If the OIG domain creation fails when running create-domain.sh, run the following to diagnose the issue:
Run the following command to diagnose the create domain job:
$ kubectl logs <job_name> -n <domain_namespace>
For example:
$ kubectl logs governancedomain-create-fmw-infra-sample-domain-job-9wqzb -n oigns
Also run:
$ kubectl describe pod <job_domain> -n <domain_namespace>
For example:
$ kubectl describe pod governancedomain-create-fmw-infra-sample-domain-job-9wqzb -n oigns
Using the output you should be able to diagnose the problem and resolve the issue.
Clean down the failed domain creation by following steps 1-4 in Delete the OIG domain home. Then recreate the PC and PVC then execute the OIG domain creation steps again.
If any of the above commands return the following error:
Failed to start container "create-fmw-infra-sample-domain-job": Error response from daemon: error while creating mount source path
'/scratch/OIGDockerK8S/governancedomainpv ': mkdir /scratch/OIGDockerK8S/governancedomainpv : permission denied
then there is a permissions error on the directory for the PV and PVC and the following should be checked:
a) The directory has 777 permissions: chmod -R 777 <work directory>/governancedomainpv.
b) If it does have the permissions, check if an oracle user exists and the uid and gid equal 1000, for example:
$ uid=1000(oracle) gid=1000(spg) groups=1000(spg),59968(oinstall),8500(dba),100(users),1007(cgbudba)
Create the oracle user if it doesn’t exist and set the uid and gid to 1000.
c) Edit the <work directory>/weblogic-kubernetes-operator/kubernetes/samples/scripts/create-oim-domain-pv-pvc/create-pv-pvc-inputs.yaml and add a slash to the end of the directory for the weblogicDomainStoragePath parameter:
weblogicDomainStoragePath: /scratch/OIGDockerK8S/governancedomainpv/
Clean down the failed domain creation by following steps 1-4 in Delete the OIG domain home. Then recreate the PC and PVC and then execute the OIG domain creation steps again.