Errors in CASE prerequisites or airgap.sh script (offline only)

If you have an error in the CASE prerequisites or airgap.sh script, you must edit the CASE.

Symptom

CASE prerequisite fails as check is invalid.

For example, your CASE prereq.yaml is set up as:

oc:
  metadata:
    description: "Client has oc version 4.4.0 or greater"
  command: "oc"
  versionArgs: "version --client"
  versionRegex: "Client Version: 4.[4-9]*.[0-9]*"

However the tooling returns the following: Clientversion: v3.8.0+2091.cec7f90e0db0b99281c8a3d75573b652de2297e8

In this example, the prerequisite cannot be met as the command returns a different version format than what is set up in CASE prerequisite.

Solution

Perform the following steps to fix the CASE:

  1. Download and extract the CASE.
  2. Modify the files (for example, remove a prerequisite from prereq.yaml)
  3. Specify the directory containing the extracted CASE on oc ibm-pak commands with the —tolerance 1 flag. The tolerance flag specifies oc ibm-pak not to validate the signature on the CASEs.
  4. To reference the .tgz file directly, run the following command:
export CASE_ARCHIVE=$CASE_NAME-$CASE_VERSION.tgz
export OFFLINEDIR=$HOME/offline
export CASE_LOCAL_PATH=$OFFLINEDIR/$CASE_ARCHIVE
  1. To reference the .tgz file in an expanded location where updates have been made, run the following command:
cd $OFFLINEDIR
tar -xvf $OFFLINEDIR/$CASE_NAME-$CASE_VERSION.tgz
<edit file(s) directed by product teams or support>
export CASE_LOCAL_PATH=$OFFLINEDIR/$CASE_NAME-$CASE_VERSION

The path is now expanded to the CASE source ($CASE_LOCAL_PATH) and the tolerance flag must be specified if updates to the CASE content are made.