Unable to create Sandbox on IBM Cloud

1. Save the WaziSandboxSystem resource YAML to a file sandbox.yaml.
2. Delete the WaziSandboxSystem resource that fails by following the instructions that are described in the Deleting a sandbox instance.

apiVersion: sandbox.wazi.ibm.com/v1alpha1
kind: WaziSandboxSystem
metadata:
  name: your-sandbox-name
spec:
  zpdt:
    secretName: your-sandbox-secret
    configMap:
      create: true
      licenseServer: your-license-server
      sftpHost: your-sftp-server
      sftpPort: 22
      sftpUser: sftp-user
      sftpPath: /path/to/adcd
  zVolumes:
    existingClaimName: your-sandbox-storage

If the dynamic configuration is not being used, skip to Create a PersistentVolumeClaim if required. Otherwise, use the following steps to create a ConfigMap.

1. Create a file configmap.yaml by using the following template.

   apiVersion: v1
   kind: ConfigMap
   metadata:
     name: sandbox-fix-init-config
   data:
     licenseServer: ls.example.com
     sftpHost: sftp.example.com
     sftpPort: ‘22’
     sftpUser: example-user
     sftpPath: /path/to/adcd
   

2. Change the values in the configmap.yaml to match the values in the spec.configMap from the sandbox.yaml. If the sftpPort does not appear in the sandbox.yaml, you can leave the value as 22.
3. Save the configmap.yaml.
4. Submit the configmap.yaml to your namespace by using the OpenShift web console or by using the following command.

   oc create -f configmap.yaml

5. Edit the sandbox.yaml.
6. In the spec.configMap section, delete all existing keys.
7. In the spec.configMap section, add the key and value: name: sandbox-fix-init-config.
   Note: If you changed the metadata.name field in the template, use the new name here as well.
8. Save the sandbox.yaml.

apiVersion: sandbox.wazi.ibm.com/v1alpha1
kind: WaziSandboxSystem
metadata:
  name: your-sandbox-name
spec:
  zVolumes:
    size: 300Gi
    storageClassName: ""
  zpdt:
    secretName: your-sandbox-secret
    configMap:
      name: your-sandbox-config

If a dynamic storage is not being used, spec.zVolumes.existingClaimName will be set, skip to Create a WaziSandboxVolumeCopy request. Otherwise, use the following steps to create a PersistentVolumeClaim.

1. Create a file pvc.yaml by using the following template.

   kind: PersistentVolumeClaim
   apiVersion: v1
   metadata:
     name: sandbox-fix-init-storage
   spec:
     storageClassName: VALUE_FROM_SANDBOX_YAML
     resources:
       requests:
         storage: SIZE_FROM_SANDBOX_YAML
     selector:
       matchExpressions:
         - key: ZVOLUMES_SELECTOR_LABEL_FROM_SANDBOX_YAML
           operator: In
           values: [ ZVOLUMES_SELECTOR_VALUE_FROM_SANDBOX_YAML
     accessModes:
       - ReadWriteOnce
     volumeMode: Filesystem
   

2. Change the VALUE_FROM_SANDBOX_YAML to the spec.zVolumes.storageClassName value from the sandbox.yaml. Or, change it to be “” if no such value exits in the sandbox.yaml.
3. Change the SIZE_FROM_SANDBOX_YAML to the spec.zVolumes.size value from the sandbox.yaml.
4. If the sandbox.yaml includes a spec.zVolumes.selector section, change the ZVOLUMES_SELECTOR_LABEL_FROM_SANDBOX_YAML to the spec.zVolumes.selector.label value and to the spec.zVolumes.selector.value value from the sandbox.yaml. Otherwise, delete the spec.selector section from the pvc.yaml.
5. Save the pvc.yaml.
6. Submit the pvc.yaml to your namespace by using the OpenShift web console or by using the following command.

   oc create -f pvc.yaml

7. Edit the sandbox.yaml.
8. In the spec.zVolumes section, delete all existing keys.
9. In the spec.zVolumes section, add the key and value: existingClaimName: sandbox-fix-init-storage.
   Note: If you changed the metadata.name field in the template, use the new name here as well.
10. Save the sandbox.yaml.

1. Create a file volcopy.yaml by using the following template.

   apiVersion: sandbox.wazi.ibm.com/v1alpha1
   kind: WaziSandboxVolumeCopy
   metadata:
     name: sandbox-fix-init-copy
   spec:
     source:
       type: sftp
       existingConfigName: CONFIGMAP_NAME_FROM_SANDBOX_YAML
       secretName: SECRETNAME_FROM_SANDBOX_YAML
     destination:
       existingClaimName: ZVOLUMES_EXISTINGCLAIMNAME_FROM_SANDBOX_YAML
     imagePullSecrets:
       - name: PULL_SECRET_NAME_FROM_SANDBOX_YAML
   

2. Change the CONFIGMAP_NAME_FROM_SANDBOX_YAML to spec.zpdt.configMap.name value from the sandbox.yaml.
3. Change the SECRETNAME_FROM_SANDBOX_YAML to spec.zpdt.secretName value from the sandbox.yaml.
4. Change the ZVOLUMES_EXISTINGCLAIMNAME_FROM_SANDBOX_YAML to spec.zVolumes.existingClaimName value from the sandbox.yaml.
5. If the sandbox.yaml includes an imagePullSecrets section, change the PULL_SECRET_NAME_FROM_SANDBOX_YAML to the value from the sandbox.yaml. Otherwise, delete the imagePullSecrets section.
6. Save the volcopy.yaml.
7. Submit the volcopy.yaml to your namespace by using the OpenShift web console or by using the following command.

   oc create -f volcopy.yaml

8. Wait for the Job that is created by this request to complete. Verify that the job is completed successfully by drilling down from the Job to the Pod. Check the status on the Overview tab and log file on the Logs tab to verify that the job was able to correctly copy all z/OS volume files.