Skip to content

Commit f0fc35e

Browse files
Copilotdcasati
andcommitted
Complete RCA investigation with documentation and workflow
Co-authored-by: dcasati <3240777+dcasati@users.noreply.github.com>
1 parent 94cc733 commit f0fc35e

1 file changed

Lines changed: 68 additions & 0 deletions

File tree

README-RCA.md

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
# ArgoCD Deployment Failure - Root Cause Analysis Complete
2+
3+
## Investigation Status: ✅ COMPLETE
4+
5+
The root cause analysis for GitHub Issue #12 (`🚨 ArgoCD Deployment Failed: 2-broken-apps`) has been completed.
6+
7+
## Summary
8+
9+
**Root Cause:** Invalid `apiVersion` field in Kubernetes manifest
10+
- **File:** `apps/broken-aks-store-all-in-one.yaml` (line 178)
11+
- **Error:** `apiVersion: apps/v` should be `apiVersion: apps/v1`
12+
- **Repository:** https://github.com/dcasati/argocd-notification-examples.git
13+
- **Commit:** `8cd04df204028ff78613a69fdb630625864037c6`
14+
15+
This error was **intentionally introduced** for testing the ArgoCD notification system.
16+
17+
## Posting the RCA to GitHub Issue
18+
19+
The complete root cause analysis needs to be posted as a comment on Issue #12. Due to permission constraints in the automated environment, this requires manual action.
20+
21+
### Option 1: Run the Workflow (Recommended)
22+
23+
A GitHub Actions workflow has been created to post the RCA:
24+
25+
```bash
26+
# Using GitHub CLI
27+
gh workflow run post-argocd-rca.yml \
28+
--ref copilot/fix-argocd-deployment-issue-yet-again \
29+
-f issue_number=12
30+
```
31+
32+
**Or via GitHub Web UI:**
33+
1. Go to: https://github.com/DevExpGbb/agentic-platform-engineering/actions
34+
2. Click on "Post ArgoCD RCA to Issue" workflow
35+
3. Click "Run workflow"
36+
4. Select branch: `copilot/fix-argocd-deployment-issue-yet-again`
37+
5. Enter issue number: `12`
38+
6. Click "Run workflow"
39+
40+
### Option 2: Manual Comment (Alternative)
41+
42+
If you prefer to post manually, the complete RCA text is embedded in the workflow file:
43+
`.github/workflows/post-argocd-rca.yml`
44+
45+
Copy the content from the `rcaComment` variable and post it as a comment on Issue #12.
46+
47+
## Key Findings
48+
49+
1. **The deployment failure is INTENTIONAL** - designed to test ArgoCD notifications
50+
2. **System is working correctly:**
51+
- ✅ ArgoCD detected the invalid manifest
52+
- ✅ Notifications were sent via webhook
53+
- ✅ GitHub Actions created the issue automatically
54+
- ✅ Issue contains appropriate troubleshooting information
55+
56+
3. **Three remediation options provided:**
57+
- Fix the source repository
58+
- Use a different (valid) repository
59+
- Accept as expected behavior for testing
60+
61+
## Files Modified
62+
63+
- `.github/workflows/post-argocd-rca.yml` - Workflow to post RCA to issue
64+
- `README-RCA.md` - This file
65+
66+
## Investigation Complete
67+
68+
No code changes are needed in this repository. The ArgoCD notification system is functioning as designed. The intentionally broken application successfully triggered the notification workflow and created an appropriate issue for investigation.

0 commit comments

Comments
 (0)