Complete Environment Deployment Failed: dev environment

[github-actions]

Complete Environment Deployment Failure Report

Environment: dev
Deployment Type: Two-Phase (Infrastructure + Coder)
Failure Point: Phase 1 (Infrastructure)
Workflow Run: https://github.com/pacphi/bootstrap-coder-on-scaleway/actions/runs/16697478995
Triggered by: pacphi
Commit: aafc27b

The complete environment deployment has failed during the infrastructure phase.

Failure Analysis

• Phase 1 (Infrastructure): ❌ Failed
• Phase 2 (Coder Application): ⏭️ Not attempted (dependency failed)

Components Affected

• Kubernetes cluster deployment
• Database provisioning
• Networking and load balancer setup
• Security policy configuration

Next Steps

1. Review infrastructure deployment logs
2. Check Scaleway console for partially created resources
3. Verify Scaleway credentials and quotas
4. Check for resource conflicts or naming issues
5. Clean up any orphaned resources
6. Re-run complete deployment after fixing issues

Recovery Options

• Full Retry: Re-run this complete deployment workflow
• Manual Phases: Run infrastructure and Coder deployments separately
• Cleanup First: Use teardown workflow before retrying

Labels: deployment-failure, infrastructure-failure, dev

[pacphi]

Fix is dependent upon a fix for this open issue: scaleway/action-scw#99.

[pacphi]

📌 Source of Truth Issue

This issue serves as the source of truth for deployment failures in the dev environment.

Recent Changes

• ✅ Duplicate Prevention Implemented: New workflows now check for existing issues before creating duplicates
• ✅ Enhanced Issue Management: Using centralized issue management helpers with comprehensive troubleshooting guidance
• 🔄 Auto-Update: This issue will be automatically updated with new deployment failures for the dev environment

Duplicate Issues Closed

The following duplicate issues have been closed and consolidated into this one:

• Coder Application Deployment Failed: dev environment #29 - Coder Application deployment failure for dev environment
• Deployment Failed: dev environment #20 - General deployment failure for dev environment

What's Changed

• Smart Issue Detection: Workflows now search for existing deployment failure issues for the same environment before creating new ones
• Enhanced Troubleshooting: Future updates will include detailed infrastructure and Coder-specific guidance
• Automatic Updates: This issue will be updated with new workflow run information when dev deployments fail
• Environment-Specific Tracking: Separate issues track failures for different environments (dev, staging, prod)

Enhanced Guidance

Future deployment failure updates will include:

• 🔧 Infrastructure Issues: Detailed Scaleway console guidance, quota checks, resource cleanup steps
• 🚀 Coder Deployment Issues: Kubernetes troubleshooting commands, storage debugging, resource limits
• 🔄 Recovery Options: Multiple paths for resolving issues based on failure type
• 📋 Next Steps: Clear action items prioritized by impact

All future deployment failures for the dev environment will update this issue instead of creating new duplicates.

This comment was added as part of the duplicate issue cleanup and prevention system implementation.