Files
Sankofa/docs/vm/MONITORING_SUMMARY.md
defiQUG 33d50fb91e
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
chore: consolidate local WIP (repo cleanup 20260707)
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-07 09:41:34 -07:00

86 lines
2.2 KiB
Markdown

# VM Deployment Monitoring Summary
**Date**: 2025-12-13
**Status**: 🟡 **MONITORING IN PROGRESS - AUTHENTICATION ISSUE DETECTED**
---
## Current Status
### Provider
- **Status**: Running (1/1 Ready)
- **Image**: crossplane-provider-proxmox:latest
- **Token Auth**: Detected in logs ("Using token authentication")
- **Issue**: Still getting "invalid PVE ticket" errors
### VMs
- **Total**: 30
- **Deployed in K8s**: 30
- **Created on Proxmox**: 0 (blocked by authentication errors)
---
## Issue Identified
### Authentication Errors
**Symptom**: "401 permission denied - invalid PVE ticket"
**Frequency**: All node health checks failing
**Impact**: VM creation blocked - cannot proceed past health check
### Root Cause Analysis
1. Token authentication is being detected in logs ✅
2. Token format appears correct: `tokenid=token`
3. Cookie header implementation is correct ✅
4. But API calls still fail with "invalid PVE ticket" ❌
### Possible Causes
1. Token might be expired or invalid
2. Token permissions might be insufficient
3. Token format might need adjustment
4. Provider might not be using latest code (unlikely - pod restarted)
---
## Monitoring Commands
### Real-Time Monitoring
```bash
# Watch all VMs
kubectl get proxmoxvm -A -w
# Continuous monitor
./scripts/continuous-monitor.sh 30
# View provider logs
kubectl logs -n crossplane-system -l app=crossplane-provider-proxmox -f
```
### Check Authentication Status
```bash
# Count authentication errors
kubectl logs -n crossplane-system -l app=crossplane-provider-proxmox --since=5m | grep -i "invalid PVE ticket" | wc -l
# Check token authentication usage
kubectl logs -n crossplane-system -l app=crossplane-provider-proxmox --since=5m | grep "Using token authentication" | wc -l
```
---
## Next Steps
1. ⚠️ **URGENT**: Fix token authentication issue
- Verify token is valid and not expired
- Check token permissions
- Test token manually with curl
- Verify token format is correct
2. Monitor VM creation once authentication is fixed
3. Verify VMs are being created on Proxmox
4. Post-deployment verification
---
**Last Updated**: 2025-12-13
**Status**: 🟡 **MONITORING - AUTHENTICATION ISSUE BLOCKING DEPLOYMENT**