Troubleshooting

Procedure

1. Run the following command to check the build status:

   $ oc get build buildah-build-kata -o jsonpath='{.status.reason}'

2. To fix this issue, update the runtimeClassName to use only lowercase alphanumeric characters, dots (.), or hyphens (-), and ensure it begins and ends with an alphanumeric character.

   The following example output displays the invalid names:

Procedure

1. Run the following command to examine the pod events:

   $ oc describe pod <build-pod-name>

2. Identify any FailedScheduling events, which often result from the following scenarios:

   • The Build validation only checks string format, a name that is syntactically valid but refers to a missing RuntimeClass will fail during scheduling. Run the following command to verify the resource exists:

     $ oc get runtimeclass kata

   • The targeted nodes must have the Kata runtime properly installed. Confirm the KataConfig status and node readiness:

     $ oc get kataconfig -o yaml

     Check status.installationStatus to ensure the installation on worker nodes was successful.

   • The operator-managed kata runtimeClass applies a node-role.kubernetes.io/kata-oc: "" selector. If your build configuration defines additional selectors, they must intersect with the runtimeClass requirements. Verify node labels:

     $ oc get nodes --show-labels | grep kata

Procedure

1. Run the following command to check the BuildRun status message:

   $ oc get buildrun <buildrun-name> -o jsonpath='{.status.conditions[0].message}'

2. To resolve this issue, use one of the following methods:

   1. Define the runtimeClassName directly within the inline spec.build.spec block:

      apiVersion: shipwright.io/v1beta1
      kind: BuildRun
      spec:
        build:
          spec:
            # ... source and strategy fields ...
            runtimeClassName: kata

   2. Reference a standalone Build by name to use the override field:

      apiVersion: shipwright.io/v1beta1
      kind: BuildRun
      spec:
        build:
          name: buildah-build-kata
        runtimeClassName: kata

Procedure

1. Confirm the operator is active:

   $ oc get csv -n openshift-sandboxed-containers-operator

2. Check the KataConfig installation status:

   $ oc get kataconfig -o jsonpath='{.items[0].status.installationStatus}'

3. Ensure all worker nodes have completed the mandatory reboot process.