Open Rickkwa opened 8 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
What happened?
This is a continuation of #10313.
When
roles/kubespray-defaults/tasks/fallback_ips.yml
runs on a inventory with an unreachable host, it'll exit the entire play after thesetup
task, withNO MORE HOSTS LEFT
.What did you expect to happen?
I expect the entire
kubespray-defaults
role to finish running, but it exits the play after the single task.How can we reproduce it (as minimally and precisely as possible)?
Minimal inventory
And then this minimal playbook
Execute with
ansible-playbook -i hosts.ini bug.yml
OS
Version of Ansible
Tried both:
and
Version of Python
Python 3.9.18
Version of Kubespray (commit)
66eaba377
Network plugin used
calico
Full inventory with variables
See "How can we reproduce it" section. Just that inventory, no variables.
Command used to invoke ansible
See "How can we reproduce it" section
Output of ansible run
Anything else we need to know
In the PR #10601, it added
ignore_unreachable: true
. That made it so the Play Recap hadignored=1
instead ofunreachable=1
. But ultimately it doesn't solve the issue of the play exiting early.