-
Notifications
You must be signed in to change notification settings - Fork 83
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
frankmit11
wants to merge
36
commits into
IBM:main
Choose a base branch
from
frankmit11:fix/bastion-host-error
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
Kvm ocp upc enhancements
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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 thehost: 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
anddestroy-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 unlessuse_internal_bastion == true
. I believe the same issue will occur for theadd-new-compute-node
code path as well, so I made some changes there as well.