coilyco-flight-deck/backend
1
0
Fork 0
Code Issues 11 Pull requests Projects Releases Packages Wiki Activity Actions

build-publish-deploy CI fails at report-status step - cannot resolve tailnet host api #3

New issue
Open
opened 2026-05-23 20:53:50 +00:00 by coilysiren · 0 comments
coilysiren commented 2026-05-23 20:53:50 +00:00
Owner
Copy link

Originally filed by @coilysiren on 2026-05-22T09:04:12Z - https://github.com/coilysiren/backend/issues/81

The build-publish-deploy workflow's final report-status-to-datastore step fails with curl exit code 6, could not resolve host api. The build, image sideload, and rollout all succeed first - the report step env shows STATUS success - only the POST to http://api/document fails. Failing consistently since about 2026-05-21 08:44, at least 3 runs: f4ad5a3 and the two pushes before it. Last green run was the PVC commit at 05:14 the same day. The CI runner joins the tailnet as tag:ci via tailscale/github-action but cannot resolve the api MagicDNS name. Likely a MagicDNS or accept-dns timing issue, or a tailnet-config regression around the same window the tailscale-operator OAuth died, see infrastructure#238. Not blocking deploys, but every push shows red. Fix idea: POST to the api node tailnet IP instead of the MagicDNS name, or add a resolve retry.

_Originally filed by @coilysiren on 2026-05-22T09:04:12Z - [https://github.com/coilysiren/backend/issues/81](https://github.com/coilysiren/backend/issues/81)_ The build-publish-deploy workflow's final report-status-to-datastore step fails with curl exit code 6, could not resolve host api. The build, image sideload, and rollout all succeed first - the report step env shows STATUS success - only the POST to http://api/document fails. Failing consistently since about 2026-05-21 08:44, at least 3 runs: f4ad5a3 and the two pushes before it. Last green run was the PVC commit at 05:14 the same day. The CI runner joins the tailnet as tag:ci via tailscale/github-action but cannot resolve the api MagicDNS name. Likely a MagicDNS or accept-dns timing issue, or a tailnet-config regression around the same window the tailscale-operator OAuth died, see infrastructure#238. Not blocking deploys, but every push shows red. Fix idea: POST to the api node tailnet IP instead of the MagicDNS name, or add a resolve retry.
coilysiren added
P2
 and removed
P1
 labels 2026-05-31 07:00:12 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
generic-modes
right-size-db-pvc
worktree-agent-a2bf119718b2a7b50
fix-sideload-image-ref
adopt-docker-save-deploy
fix/deploy-config-path
No results found.
Labels
Clear labels
  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
P0
P1
P2
P3
P4
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
coilyco-flight-deck/backend#3
No description provided.