fix(vm_workload_showroom): publish runner port to bastion host for FTL health check#73
Merged
Merged
Conversation
…L health check The vm_runtime_automation_load_test role checks http://localhost:<port>/health from the bastion host. PR #63 replaced the old ansible_runner_api_service.j2 (which had `ports: - "8501:80"`) with service_runtime_automation.j2 which dropped the ports section entirely. Without the port binding, localhost:8501 on the bastion is unreachable and every FTL E2E load test fails at the health check with Connection refused. Add ports back, mapping the configurable runner port to the same port on the bastion host so both the FTL health check and traefik routing work.
prakhar1985
added a commit
that referenced
this pull request
Jun 17, 2026
…t for FTL health check Reverts #73
prakhar1985
added a commit
that referenced
this pull request
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What broke and why
PR #63 replaced
ansible_runner_api_service.j2withservice_runtime_automation.j2. The old template had:The new template dropped the
ports:section entirely — only traefik labels remain.The
vm_runtime_automation_load_testrole (used for FTL E2E load testing) curlshttp://localhost:<port>/healthdirectly on the bastion host. Without the port binding, the container's port 8501 is only reachable inside the podman network via traefik, not from the host. Every FTL health check times out withConnection refused.The fix
Add
ports:back toservice_runtime_automation.j2, mapping the configurable_runner_portto the same port on the bastion host:This restores the direct host-side accessibility needed by
vm_runtime_automation_load_testwhile keeping traefik routing intact.Verified on
aap2-prod-us-east-2, GUIDn6xxdcurl http://localhost:8501/health→ 200 after fix appliedDiff
ansible_runner_api_service.j2)service_runtime_automation.j2) — before this PRports:"8501:80"ports:missing =localhost:8501unreachable from bastion = FTL load test fails on every VM-based lab.cc @andrew-jones — introduced in #63