Some checks failed
API CI / API Lint (push) Successful in 47s
API CI / API Type Check (push) Failing after 47s
API CI / API Test (push) Successful in 1m0s
API CI / API Build (push) Failing after 50s
API CI / Build Docker Image (push) Has been skipped
Build Crossplane Provider / build (push) Failing after 5m51s
CD Pipeline / Deploy to Staging (push) Failing after 29s
CI Pipeline / Lint and Type Check (push) Failing after 36s
CI Pipeline / Build (push) Has been skipped
CI Pipeline / Test Backend (push) Failing after 1m33s
CI Pipeline / Test Frontend (push) Failing after 30s
CI Pipeline / Security Scan (push) Failing after 1m16s
Crossplane Provider CI / Go Test (push) Failing after 3m23s
Crossplane Provider CI / Go Lint (push) Failing after 7m27s
Crossplane Provider CI / Go Build (push) Failing after 3m27s
Deploy to Staging / Deploy to Staging (push) Failing after 30s
Portal CI / Portal Lint (push) Failing after 21s
Portal CI / Portal Type Check (push) Failing after 21s
Portal CI / Portal Test (push) Failing after 21s
Portal CI / Portal Build (push) Failing after 22s
Test Suite / frontend-tests (push) Failing after 30s
Test Suite / api-tests (push) Failing after 49s
Test Suite / blockchain-tests (push) Failing after 30s
Type Check / type-check (map[directory:. name:root]) (push) Failing after 23s
Type Check / type-check (map[directory:api name:api]) (push) Failing after 21s
Type Check / type-check (map[directory:portal name:portal]) (push) Failing after 19s
Validate Configuration Files / validate (push) Failing after 1m52s
CD Pipeline / Deploy to Production (push) Has been skipped
Co-authored-by: Cursor <cursoragent@cursor.com>
2.7 KiB
2.7 KiB
Ceph OSD Creation Issues - Summary
Date: 2025-12-13
Status: 🔍 ISSUES IDENTIFIED - NEEDS DIAGNOSIS
Issues Identified
1. OSD Creation Hanging/Timeout
Symptom: ceph-volume lvm create hangs at "osd new" step
Root Causes (likely):
- ❌ Bootstrap keyring missing - Cannot authenticate with cluster
- ❌ Ceph cluster not accessible - RADOS timeout errors
- ❌ Monitor connectivity issues - Cannot reach Ceph monitors
2. Bootstrap Keyring Issue
Error:
unable to find a keyring on /etc/pve/priv/ceph.client.bootstrap-osd.keyring
RADOS timed out (error connecting to the cluster)
Possible Locations:
/var/lib/ceph/bootstrap-osd/ceph.keyring(standard)/etc/pve/priv/ceph.client.bootstrap-osd.keyring(Proxmox)
Status: Unknown - needs verification
3. Ceph Cluster Connectivity
Issue: Commands timeout when trying to connect to cluster
Possible Causes:
- Monitors not running
- Network connectivity issues
- Firewall blocking ports
- Cluster configuration issues
Diagnostic Steps
Run these commands on R630-01 to diagnose:
Quick Check
# 1. Check Ceph health (does it respond?)
ceph health
# 2. Check monitors
ceph mon stat
# 3. Check bootstrap keyring
ls -la /var/lib/ceph/bootstrap-osd/ceph.keyring
ls -la /etc/pve/priv/ceph.client.bootstrap-osd.keyring
# 4. Check if pveceph available
which pveceph
Full Diagnostic
# Run comprehensive diagnostic
bash /tmp/diagnose-ceph-issues.sh
Likely Solutions
Solution 1: Use pveceph (If Proxmox-Managed)
If pveceph is available:
for drive in sdc sdd sde sdf sdg sdh; do
pveceph create /dev/$drive
done
Solution 2: Fix Bootstrap Keyring
If cluster is accessible:
# Get bootstrap keyring
mkdir -p /var/lib/ceph/bootstrap-osd
ceph auth get client.bootstrap-osd -o /var/lib/ceph/bootstrap-osd/ceph.keyring
# Then create OSDs
for drive in sdc sdd sde sdf sdg sdh; do
ceph-volume lvm create --data /dev/$drive
done
Solution 3: Fix Cluster Connectivity
If cluster is not accessible:
- Check monitor services
- Check network connectivity
- Check firewall rules
- Fix connectivity issues
- Then retry OSD creation
Current State
- ✅ 6x 250GB drives: Wiped and ready
- ❌ OSD creation: Hanging due to authentication/connectivity
- 🔍 Root cause: Needs diagnosis
Next Action
Run diagnostic script to understand the issue:
# On R630-01
bash /tmp/diagnose-ceph-issues.sh
This will show:
- Ceph cluster status
- Bootstrap keyring locations
- Monitor connectivity
- Service status
- Network connectivity
Then we can apply the appropriate fix.
Last Updated: 2025-12-13