POC Troubleshooting
Every command install.sh runs, and its output, is in install.log in the bundle folder. After a fix, run ./install.sh again; every step is safe to repeat. If you set another namespace=, use it in place of kfuse in the kubectl -n kfuse commands below. The README.md in the bundle folder lists the errors for your bundle.
Tools, license, and input
| Symptom | Fix |
|---|---|
|
Install the tools, then run |
The license check fails with |
|
|
The organization can’t change after installation. Use that organization’s |
A value is rejected with |
Backspace or the arrow keys left invisible characters in it. Type it again without editing. |
|
Renew your TLS certificate, replace the files, then run |
Sign-in and permissions
| Symptom | Fix |
|---|---|
Resources created in the wrong account, or permission errors right after the static IP was created |
You were signed in to another account. |
A permission check reports missing permissions or roles |
Use an identity with the permissions in POC Permissions, then run |
AWS: |
Your AWS sign-in expired. Run |
AWS: |
The permission check itself needs that action. Add it to your identity, use an admin role, or add |
AWS: |
|
Google Cloud: |
Run |
Google Cloud: |
Sign in again and check Select all on the Google sign-in page. |
Google Cloud: |
Run |
Azure: |
Ask a subscription Owner to add the roles it names to the condition, or to grant |
|
A proxy or firewall on your side blocks the cluster’s API endpoint. |
New cluster
| Symptom | Fix |
|---|---|
Apply fails with a quota error |
Raise the vCPU quota for the region. See POC Permissions. |
AWS: |
The region has no Elastic IPs left; the install needs two. Check with |
AWS: |
The region’s first availability zone doesn’t offer it. Pick another region. |
Google Cloud: |
Pick another zone in the region that offers N4. All four |
Azure: |
Neither the v5 nor the v7 size is offered in that zone, or both are blocked for your subscription. Pick another region or zone, or ask Azure support to enable a size. |
|
Put the old value back, or uninstall and install again. |
|
A cloud bundle always creates a new cluster. To install on a cluster you already have, run |
|
An earlier bundle installed on an existing cluster from this folder. Remove it with |
|
|
Existing cluster
| Symptom | Fix |
|---|---|
|
Sign in to your cloud and refresh your kubeconfig, then run |
|
|
|
Use a kubeconfig context with |
|
Label and taint a node for Kloudfuse, then run |
|
The table under the message lists them. Move them off the node with |
|
|
|
This folder’s install is on another cluster. Run |
|
A storage class can’t be changed once it exists, and |
Kloudfuse and HTTPS
| Symptom | Fix |
|---|---|
Pods in |
|
|
Something wasn’t ready within 30 minutes. |
|
Kloudfuse is installed, but its address doesn’t answer yet. |
|
|
Disks (PVCs) stuck |
The disk driver isn’t running. On AWS, check |
|
Expected on a first install: Let’s Encrypt checked before the load balancer was ready. The script asks again by itself, up to 4 times, 2 minutes apart. |
Certificate |
The DNS name doesn’t resolve to the static IP yet, or port 80 is blocked from the internet. |
The wait for |
cert-manager isn’t creating the certificate. Check that it runs, with Gateway API support: |
|
A cert-manager that was already on the cluster can’t issue the certificate. Turn on its Gateway API support ( |
Browser certificate warning |
With Let’s Encrypt, the certificate isn’t issued yet. With your own certificate, it doesn’t cover the DNS name, or the certificate file is missing the intermediate certificates. |
After installation
| Symptom | Fix |
|---|---|
Lost the admin password |
|
Alert emails don’t arrive |
The SMTP host, port, or password is wrong, or the port is 25. If they arrive in spam, the from address isn’t set up for your mail server (SPF, DKIM). |
|
It was edited, or the settings changed. Answer Yes to replace it (the old one is backed up), or No to stop with nothing changed. Put lasting changes in the settings or in |
|
A newer bundle changed this install, and an older one can’t safely run on it. Run |
Azure: Pinot restarts with an access error on the storage account |
The storage account key was rotated. Run |
|
Run |
|
Kloudfuse’s load balancer still uses the static IP. Run |
AWS: |
A load balancer is left over. Delete it in the AWS console (tag |