Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix/bastion host error #271

Open
wants to merge 36 commits into
base: main
Choose a base branch
from

Conversation

frankmit11
Copy link

@frankmit11 frankmit11 commented Jul 3, 2024

It is not safe to assume the bastion host is something that can be accessed by Ansible if use_internal_bastion == false.

In my environment, I'm not using a bastion node at all. As a result, when running the destroy playbook, 04-destroy.yaml, the playbook prematurely fails because it cannot reach the host: bastion since a bastion is not defined in my inventory file.

As a quick and ugly fix I have been commenting out the bastion section of the destroy-computes and destroy-controls playbooks to get around this problem. Hopefully this PR resolves this problem for good, my updates don't try to access any bastion hosts unless use_internal_bastion == true. I believe the same issue will occur for the add-new-compute-node code path as well, so I made some changes there as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant