scruffydude/homelab
Watch
1
0
Fork
You've already forked homelab
 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Point the code-server-update Fabric job at code2 on optibcc #74

Merged
scruffydude merged 1 commit from fix/code-server-update-job-code2 into main 2026-10-19 13:39:29 -04:00
Conversation 0 Commits 1 Files changed 1 +5 -4
Nimby commented 2026-10-19 13:38:20 -04:00
Collaborator
Copy link

Retargets the code-server-update Fabric job after the 2026-10-13 move of code-server to optibcc.

Why: the last run, on 2026-09-12, failed: the deploy returned rc=4 because channel100 was unreachable. The spec still points every preflight, postflight, log and verify step at channel100 (192.168.30.12) and the old code-server container. Separately, the windows-desktop-wsl worker's checkout is on 2302bc6 (2026-09-14), from before the cutover. Its group_vars would deploy code-server to channel100 and could bring the retired instance back.

Changes

  • SSH probes now go to director@192.168.30.22 (optibcc), and container references now use code2.
  • A new first collect step fast-forwards the worker to origin/main (clean tree required). It uses the same pattern as astr-deploy.

Validation

  • agent_runner.py validate --host-config examples/agent-hosts/homelab.json passes.
  • The worker can reach optibcc over SSH and sees code2, and its origin (Forgejo) returns main at 64298e9.
  • Live today: code2 is healthy on 4.141.0-ls369 and returns HTTP 302.

After merge: dispatch code-server-update from the Fabric dashboard. Then check deploy_exit_code=0 with an optibcc PLAY RECAP, and that code2 is still healthy.

🤖 Generated with Claude Code

Retargets the `code-server-update` Fabric job after the 2026-10-13 move of code-server to optibcc. **Why:** the last run, on 2026-09-12, failed: the deploy returned rc=4 because channel100 was unreachable. The spec still points every preflight, postflight, log and verify step at channel100 (`192.168.30.12`) and the old `code-server` container. Separately, the `windows-desktop-wsl` worker's checkout is on `2302bc6` (2026-09-14), from before the cutover. Its group_vars would deploy code-server to **channel100** and could bring the retired instance back. **Changes** - SSH probes now go to `director@192.168.30.22` (optibcc), and container references now use `code2`. - A new first collect step fast-forwards the worker to `origin/main` (clean tree required). It uses the same pattern as `astr-deploy`. **Validation** - `agent_runner.py validate --host-config examples/agent-hosts/homelab.json` passes. - The worker can reach optibcc over SSH and sees `code2`, and its `origin` (Forgejo) returns main at `64298e9`. - Live today: code2 is healthy on 4.141.0-ls369 and returns HTTP 302. After merge: dispatch `code-server-update` from the Fabric dashboard. Then check `deploy_exit_code=0` with an optibcc PLAY RECAP, and that code2 is still healthy. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Point the code-server-update Fabric job at code2 on optibcc
All checks were successful
CI Pipeline / Validate Ansible Syntax (pull_request) Successful in 1m28s
Details
CI Pipeline / Validate Ansible Syntax (push) Successful in 1m27s
Details
CI Pipeline / Test Ansible Playbooks (Syntax Only) (pull_request) Successful in 48s
Details
CI Pipeline / Python Tests (pull_request) Successful in 21s
Details
CI Pipeline / Test Ansible Playbooks (Syntax Only) (push) Successful in 45s
Details
CI Pipeline / Python Tests (push) Successful in 24s
Details
fc52346a74 
The job still probed channel100 (192.168.30.12) and the old
`code-server` container after the 2026-10-13 cutover, so its health
checks would hit the retired host. Retarget them to optibcc/code2.

Also fast-forward the worker's checkout before deploying (same as
astr-deploy): windows-desktop-wsl was on a pre-cutover commit whose
group_vars still deploy code-server to channel100.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scruffydude deleted branch fix/code-server-update-job-code2 2026-10-19 13:39:29 -04:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
scruffydude/homelab!74
No description provided.