my-homelab-configs/infra/jeannie-explain/findings.tsv

7.3 KiB

1patternmeaningdiagnose_commandsjeannie_fix_commandsother_fix_commandsriskauto_fixnotes
2unsupported template variableGenerated docs found a template placeholder that render-docs does not support../jeannie validatenoneEdit README.md.tmpl or scripts/render-docslownoUsually a docs/template mismatch rather than an infrastructure issue.
3generated README.md is staleREADME.md does not match README.md.tmpl rendering../jeannie validatenonescripts/render-docslowcandidateA future docs-render Jeannie command could safely wrap this.
4missing_resource_policyWorkloads are missing resource requests or limits, so capacity planning is unreliable../jeannie resource-budget;./jeannie capacitynoneEdit app manifests or Helm valuesmediumnoAdd requests first, then limits for workloads you own.
5missing requestsOne or more containers do not declare CPU or memory requests../jeannie resource-budget --details;./jeannie capacitynoneEdit app manifests or Helm valuesmediumnoStart with application namespaces before system namespaces.
6missing limitsOne or more containers do not declare CPU or memory limits../jeannie resource-budget --details;./jeannie capacitynoneEdit app manifests or Helm valuesmediumnoLimits are useful but can cause throttling; set them deliberately.
7resource policyCapacity or resource policy needs attention../jeannie resource-budget;./jeannie capacitynoneEdit infra/resource-budgets.yml or app manifestsmediumnoDo not hide pressure by only changing the budget file.
8diskpressureA Kubernetes node reports disk pressure../jeannie capacity;./jeannie doctor-clusternoneClean images/logs or expand storagehighnoDiskPressure can evict pods and should be handled quickly.
9memorypressureA Kubernetes node reports memory pressure../jeannie capacity;./jeannie doctor-clusternoneReduce workloads or add worker capacityhighnoCheck whether Debian is carrying app pods.
10notreadyA Kubernetes node is not Ready../jeannie doctor-cluster;./jeannie workers list./jeannie start-clusternonehighnoOnly start/recreate workers after checking node state.
11problem podsPods are Pending, CrashLooping, failing image pulls, or otherwise unhealthy../jeannie status;./jeannie doctor-clusternonekubectl describe/logs for the affected podmediumnoUse namespace and pod name from the original output.
12crashloopbackoffA pod is repeatedly crashing../jeannie doctor-clusternonekubectl logs/describe for the podmediumnoLook for config, secret, dependency, or command errors.
13imagepullbackoffA pod cannot pull its image../jeannie doctor-clusternoneCheck registry, image tag, platform, and pull secretsmediumnoThis often means a tag/platform mismatch or registry reachability issue.
14errimagepullA pod cannot pull its image../jeannie doctor-clusternoneCheck registry, image tag, platform, and pull secretsmediumnoThis often means a tag/platform mismatch or registry reachability issue.
15kubernetes api unavailableThe Kubernetes API is not reachable../jeannie doctor-cluster;./jeannie start-cluster./jeannie start-clusternonehighnoStarting the cluster is explicit; do not do it automatically.
16connection refusedA service endpoint is refusing connections../jeannie status;./jeannie doctor-cluster;./jeannie doctor-edgenoneCheck the named service/container/podmediumnoUse the host and port in the original output.
17timed outA service or DNS query timed out../jeannie status;./jeannie doctor-rpi;./jeannie doctor-edgenoneCheck routing, firewall, DNS, or service healthmediumnoTimeouts often point to routing/firewall/service-down issues.
18no servers could be reachedDNS queries are failing../jeannie doctor-rpi;./jeannie status./jeannie rpi-servicesnonemediumnoRPi service redeploys can restart DNS; run explicitly.
19piholePi-hole DNS or web health needs attention../jeannie doctor-rpi;./jeannie status./jeannie rpi-servicesnonemediumnoCheck DNS before redeploying to avoid extending an outage.
20unboundUnbound recursive DNS health needs attention../jeannie doctor-rpi./jeannie rpi-servicesnonemediumnoPi-hole should still have fallback DNS if configured.
21uptime kumaUptime Kuma health or monitor coverage needs attention../jeannie doctor-rpi;./jeannie route-inventory./jeannie rpi-servicesnonelownoMonitor seeding can be rerun, but verify credentials/config first.
22giteaGitea local, SSH, or public route health needs attention../jeannie doctor-gitea;./jeannie status./jeannie deploy-gitea;./jeannie bootstrap-gitea-repononemediumnoDeploy/bootstrap can change repo service state.
23http 404A route answered but the expected path was not found../jeannie doctor-edge;./jeannie route-inventorynoneCheck ingress, reverse proxy path, and app root URLmediumno404 can mean path rewrite or app sub-path mismatch.
24http 502The reverse proxy cannot reach the backend../jeannie doctor-edge;./jeannie statusnoneCheck backend service, Traefik, edge proxy, and routeshighno502 is usually backend unreachable or unhealthy.
25certificateTLS certificate, expiry, or public HTTPS validation needs attention../jeannie cert-check;./jeannie doctor-edge./jeannie plan edge;./jeannie upnonemediumnoEdge apply can affect public routing, so keep it explicit.
26duckdns-to-ociPublic DNS does not point where the inventory expects../jeannie cert-check;./jeannie doctor-edgenoneUpdate DuckDNS or edge inventorymediumnoDNS drift can break public routes and cert issuance.
27tailscaleTailscale IP, route acceptance, or peer reachability needs attention../jeannie status;./jeannie doctor-edge;./jeannie doctor-rpinoneCheck tailscale status/routes on the named hostmediumnoTailscale ACL/route changes should be deliberate.
28docker rootDocker root path is not where expected../jeannie status;./jeannie preflight./jeannie fix-debian-docker-rootnonemediumnoDocker root migration is stateful; verify host before running.
29pimox storagePimox storage is missing, wrong, or unhealthy../jeannie preflight;./jeannie doctor-clusternoneCheck pvesm status and opi5_ssd mounthighnoStorage mistakes can break or strand VM disks.
30backupBackup freshness or restore drill readiness needs attention../jeannie backup-status;./jeannie recover-plan./jeannie backup-gitea;./jeannie state-backup;./jeannie drill-restorenonemediumnoBackups are safer than restores, but keep drills explicit.
31restore drillRestore drill reports are missing or stale../jeannie backup-status;./jeannie recover-plan./jeannie drill-restore;./jeannie drill-gitea-restore;./jeannie drill-pihole-restorenonemediumnoDrills can be noisy and should be run intentionally.
32argocdArgo CD sync or health needs attention../jeannie gitops-status;./jeannie status./jeannie appsnonemediumnoApp deployment can change workloads.
33outofsyncAn Argo CD app differs from Git../jeannie gitops-status./jeannie appsnonemediumnoConfirm desired branch before syncing.
34degradedAn Argo CD app or workload is degraded../jeannie gitops-status;./jeannie statusnoneCheck app events/logsmediumnoFix depends on the degraded app.
35edgePublic edge routing or OCI edge service needs attention../jeannie doctor-edge;./jeannie cert-check./jeannie plan edge;./jeannie upnonehighnoEdge fixes can affect internet-facing access.
36securitySecurity policy or defensive scan needs attention../jeannie security-scan;./jeannie tailnet-policy-checknoneReview reported policy or findingmediumnoDo not let AI auto-remediate security policy yet.