Cloudkit issues on GCP

• Cloudkit produces logs that detail any errors or issues encountered during the provisioning and configuration process. Review the logs to identify any specific errors or issues that may be causing problems.
• Review the cloudkit inputs to ensure that all values are set correctly.

Error waiting to create Router: Error waiting for Creating Router: Quota 'ROUTERS' exceeded.  Limit: 20.0 globally.

Credential issues

• Check your GCP credentials. Ensure that the GCP credentials used to provision resources through cloudkit are valid and have the appropriate permissions. Verify this by checking the GCP credential JSON file used by cloudkit and confirming that they have the necessary permissions.

  google: could not find default credentials. See https://cloud.google.com/docs/authentication/external/set-up-adc for more information

Transient network errors

• Cluster creation failure due to transient network errors:
  1. In some circumstances it might be possible to encounter latent network issues may be encountered while deploying new cluster resources.
  2. If this is encountered, rerun the ./cloudkit command with the same parameters.
  3. The cloudkit logs might list something like:

     Error waiting for instance to create: error while retrieving operation: Get \"https://compute.googleapis.com/compute/v1/projects/<PROJECT_ID>/zones/us-east1-b/operations/operation-1696304597507-1111111-e49f6fc6-a5b7ecc4?alt=json&prettyPrint=false\": http2: client connection lost

  4. If the problem still persists after rerunning the command, delete the existing cluster and create a new cluster.
• If an IBM Storage Scale related problem is suspected, collect data by running a gpfs.snap. Upload this gpfs.snap to the IBM Storage Scale support ticket that is opened.
• Plan your network infrastructure to ensure a reliable communication between installer node and cloud. In jump host based connectivity, it could take little longer for ssh to reach the node, if there is a network drop, it is recommended to re-run.

Error: Failed to load plugin schemas
Error: while loading schemas for plugin components: Failed to obtain schema: Could not load the schema for provider

The cloudkit delete cluster command might encounter failures for the following reasons:

• If any GCP resources have been provisioned into the VPC outside of the cloudkit, the cloudkit delete command will be unable to delete these manually created resources. In this case, all resources created outside of the cloudkit must be deleted manually before the cloudkit delete operation can be executed.

I: Destroy all remote objects managed by terraform (instance_template) configuration.
I: Destroy all remote objects managed by terraform (bastion_template) configuration.
I: Destroy all remote objects managed by terraform (vpc_template) configuration.
E: Delete cluster received error: exit status 1

Credential issues

• Check for errors in cloudkit logs. Cloudkit produces logs that detail any errors or issues encountered during the provisioning and configuration process. Review the logs to identify any specific errors or issues that may be causing problems.
• If the logs indicate a failure in accessing the IBM Storage Scale management GUI, ensure that the credentials provided for accessing the GUI are correct and rerun if necessary after rectifying the credentials.

Cluster creation failure due to transient network errors:

1. In some circumstances it might be possible to encounter latent network issues may be encountered while deploying new cluster resources.
2. If this is encountered, rerun the ./cloudkit command with the same parameters.
3. The cloudkit logs might list something like:

   "Failed to connect to the host via ssh: Connection timed out during banner exchange"

Credential issues

• Check for errors in cloudkit logs. Cloudkit produces logs that detail any errors or issues encountered during the provisioning and configuration process. Review the logs to identify any specific errors or issues that may be causing problems.
• If the logs indicate a failure in accessing the IBM Storage Scale management GUI, ensure that the credentials provided for accessing the GUI are correct and rerun if necessary after rectifying the credentials.

Cluster creation failure due to transient network errors:

1. In some circumstances it might be possible to encounter latent network issues when deploying new cluster resources.
2. If this is encountered, rerun the ./cloudkit command with the same parameters.
3. The cloudkit logs might list something like:

   "Failed to connect to the host via ssh: Connection timed out during banner exchange"