ID: O1-PbmlRvN
NS: ns-oi3oiebi
Region: US-West (based on node names: sealos-run-cc-us-west-worker-*)
Question: Urgent: Pod scheduling failures - Need assistance with persistent volume node affinity conflicts
Image: openlistteam/openlist:latest-lite
Respected ClawCloud Support Team,
I'm humbly requesting your assistance with a critical issue affecting my application's availability. My StatefulSet openlist-qnqzywqm has been unable to schedule for over 12 hours due to persistent volume constraints.
⚠️ Critical Concern: The application contains important user data stored in PVC vn-data-openlist-qnqzywqm-0 (3Gi, 4+ days of data). Preserving this data is my highest priority.
Current Status: Pod openlist-qnqzywqm-0 remains stuck in Pending state with these repeated errors:
Volume Node Affinity Conflict: 18-20 nodes report this error (primary concern)
Node Resource Constraints: 10-13 nodes show "Too many pods"
Node Issues: 1 node has node.kubernetes.io/unreachable taint
What I've Tried (with limited knowledge):
Added tolerations for platform taints (database.run.claw.cloud/node, devbox.sealos.io/node, etc.)
Multiple Pod deletions and rebuilds
Verified PVC remains Bound (data appears intact, which is crucial)
My Humble Assessment:
I believe the PVC pvc-8eb462c3-ee2a-4150-8938-6de9cc6defd3 may have restrictive node affinity rules, binding it to specific nodes that are now unavailable. As a user with limited platform access, I cannot investigate this further.
Kind Request for Assistance:
Could you please help with:
Data Safety First: Ensure the important data in PVC vn-data-openlist-qnqzywqm-0 is preserved and protected
Investigate PVC Affinity: Check why the volume has restrictive node placement
Node Resource Management: If target nodes are at capacity, could they be cleared or rebalanced?
Alternative Solutions: Perhaps the volume could be migrated to available nodes?
Additional Context (if helpful):
Application: OpenList (from App Store)
Running for: 3+ days without issues until now
Service port: 5244
Resource limits: 0.5 Core / 1 Gi memory
My Sincere Thanks:
I apologize for any inconvenience and truly appreciate your expertise in resolving this matter. The data preservation is particularly important to me.
With respect,
User of namespace ns-oi3oiebi