Fix deploy host key verification failure #4

Merged
kglitchy merged 1 commit from fix/deploy-host-key-checking into main 2026-06-05 22:37:38 +00:00
Owner

The deploy pipeline failed with Host key verification failed after the inventory's StrictHostKeyChecking=accept-new was removed. The ephemeral runner has no persistent known_hosts, so default strict checking rejects the host every run.

Fix: set host_key_checking = False in the deploy task's throwaway ansible.cfg — a deploy-environment concern, kept out of the committed inventory. Restores the TOFU posture the inventory previously had. The check/test pipeline is unaffected (no SSH).

The deploy pipeline failed with `Host key verification failed` after the inventory's `StrictHostKeyChecking=accept-new` was removed. The ephemeral runner has no persistent `known_hosts`, so default strict checking rejects the host every run. Fix: set `host_key_checking = False` in the deploy task's throwaway `ansible.cfg` — a deploy-environment concern, kept out of the committed inventory. Restores the TOFU posture the inventory previously had. The check/test pipeline is unaffected (no SSH).
Disable host key checking in the deploy pipeline
All checks were successful
Pipelines as Code CI / glitches-chat-test Success
a5376d0731
The ephemeral deploy runner has no known_hosts, so strict checking
rejected the host every run after the inventory ssh args were dropped.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Author
Owner

Pipelines as Code CI/glitches-chat-test-pjr4s is running.

Starting Pipelinerun glitches-chat-test-pjr4s in namespace glitches-chat-pipelines

You can monitor the execution using the Tekton Dashboard PipelineRun viewer or through the command line by
using the tkn CLI with the following command:

tkn pr logs -n glitches-chat-pipelines glitches-chat-test-pjr4s -f

Pipelines as Code CI/glitches-chat-test-pjr4s is running. Starting Pipelinerun <b>[glitches-chat-test-pjr4s](https://tekton.corp.mulliken.net/#/namespaces/glitches-chat-pipelines/pipelineruns/glitches-chat-test-pjr4s)</b> in namespace <b>glitches-chat-pipelines</b> You can monitor the execution using the [Tekton Dashboard](https://tekton.corp.mulliken.net/#/namespaces/glitches-chat-pipelines/pipelineruns/glitches-chat-test-pjr4s) PipelineRun viewer or through the command line by using the [tkn](https://tekton.dev/docs/cli/#installation) CLI with the following command: <code>tkn pr logs -n glitches-chat-pipelines glitches-chat-test-pjr4s -f</code>
Author
Owner

Pipelines as Code CI/glitches-chat-test-pjr4s has successfully validated your commit.


Task Statuses:

StatusDurationName
Succeeded 25 seconds

fetch-repository

Succeeded 43 seconds

Static checks

Pipelines as Code CI/glitches-chat-test-pjr4s has <b>successfully</b> validated your commit. <ul> <li><b>Namespace</b>: <a href="https://tekton.corp.mulliken.net/#/namespaces/glitches-chat-pipelines/pipelineruns">glitches-chat-pipelines</a></li> <li><b>PipelineRun:</b> <a href="https://tekton.corp.mulliken.net/#/namespaces/glitches-chat-pipelines/pipelineruns/glitches-chat-test-pjr4s">glitches-chat-test-pjr4s</a></li> </ul> <hr> <h4>Task Statuses:</h4> <table> <tr><th>Status</th><th>Duration</th><th>Name</th></tr> <tr> <td>Succeeded</td> <td>25 seconds</td><td> [fetch-repository](https://tekton.corp.mulliken.net/#/namespaces/glitches-chat-pipelines/pipelineruns/glitches-chat-test-pjr4s?pipelineTask=fetch-repository) </td></tr> <tr> <td>Succeeded</td> <td>43 seconds</td><td> [Static checks](https://tekton.corp.mulliken.net/#/namespaces/glitches-chat-pipelines/pipelineruns/glitches-chat-test-pjr4s?pipelineTask=check) </td></tr> </table>
Sign in to join this conversation.
No reviewers
No labels
No milestone
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
kglitchy/glitches.chat!4
No description provided.