Fix TeslaMate DB corruption and Rook-Ceph reconcile hang

- Scale CNPG pg-teslamate to 1 instance: on-disk storage corruption
  (corrupted sequences, system catalog indexes) means replicas cloned
  via pg_basebackup inherit corruption and can't open any database.
  Primary works from cached catalogs. Sequences already rebuilt live.

- Remove talos-cp-02 from Rook-Ceph nodes list: ceph-volume inventory
  hangs on BIOS partition via nsenter lvs in host namespace. Talos
  read-only /etc prevents LVM filter fix. OSD 1 keeps running from
  its existing deployment.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Scooby Husky
2026-03-14 14:53:31 -05:00
co-authored by Claude Opus 4.6
parent 8df30c11ee
commit 2643d5e0bf
2 changed files with 4 additions and 4 deletions
+1 -1
View File
@@ -5,7 +5,7 @@ metadata:
namespace: teslamate namespace: teslamate
spec: spec:
imageName: ghcr.io/cloudnative-pg/postgresql:16 imageName: ghcr.io/cloudnative-pg/postgresql:16
instances: 2 instances: 1
# Resource limits to prevent OOM # Resource limits to prevent OOM
resources: resources:
+3 -3
View File
@@ -120,6 +120,9 @@ cephClusterSpec:
memory: "50Mi" memory: "50Mi"
# Storage configuration - explicit nodes with passthrough NVMe # Storage configuration - explicit nodes with passthrough NVMe
# NOTE: talos-cp-02 excluded from nodes list because ceph-volume inventory
# hangs on its BIOS partition (lvs kernel I/O hang via nsenter on Talos).
# OSD 1 (nvme1n1) continues running from its existing deployment.
storage: storage:
useAllNodes: false useAllNodes: false
useAllDevices: false useAllDevices: false
@@ -127,9 +130,6 @@ cephClusterSpec:
- name: "talos-cp-01" - name: "talos-cp-01"
devices: devices:
- name: "nvme0n1" - name: "nvme0n1"
- name: "talos-cp-02"
devices:
- name: "nvme1n1"
- name: "talos-cp-03" - name: "talos-cp-03"
devices: devices:
- name: "nvme0n1" - name: "nvme0n1"