fix: Improve output of openshift-installer progress and check #61
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
The openshift-installer requires up to 60 min to complete. You need to check manually if the install process started sucessfully or you simply wait 60 min for the results. This patch monitors the 'node-bootstrapper' request. Usually such request is raised within 6 min. If not, then this is considered as an error and the ansible playbook script exits. The openshift-installer process is not aborted! It is still running. Signed-off-by: Klaus Smolin <smolin@de.ibm.com>
Added a lowercase jinja filter because some users might type in their hostnames in all caps (like I did) in all.yaml and that causes the task 'wait for control node CSRs (retry every 30s)' to timeout even though the item it's looking for is there. Signed-off-by: Jacob Emery <jacob.emery@ibm.com>
jacobemery
force-pushed
the
improve_wait_bootstrap
branch
from
0385def
to
e2d826d
Compare
jacobemery
approved these changes
Jan 13, 2023
AmadeusPodvratnik
pushed a commit
to AmadeusPodvratnik/Ansible-OpenShift-Provisioning
that referenced
this pull request
Jan 19, 2023
The openshift-installer requires up to 60 min to complete. You need to check manually if the install process started sucessfully or you simply wait 60 min for the results. This patch monitors the 'node-bootstrapper' request. Usually such request is raised within 6 min. If not, then this is considered as an error and the ansible playbook script exits. The openshift-installer process is not aborted! It is still running. Signed-off-by: Klaus Smolin <smolin@de.ibm.com> Signed-off-by: Jacob Emery <jacob.emery@ibm.com> Co-authored-by: Jacob Emery <jacob.emery@ibm.com> Signed-off-by: Amadeus Podvratnik <pod@de.ibm.com>
AmadeusPodvratnik
pushed a commit
to AmadeusPodvratnik/Ansible-OpenShift-Provisioning
that referenced
this pull request
Jan 19, 2023
The openshift-installer requires up to 60 min to complete. You need to check manually if the install process started sucessfully or you simply wait 60 min for the results. This patch monitors the 'node-bootstrapper' request. Usually such request is raised within 6 min. If not, then this is considered as an error and the ansible playbook script exits. The openshift-installer process is not aborted! It is still running. Signed-off-by: Klaus Smolin <smolin@de.ibm.com> Signed-off-by: Jacob Emery <jacob.emery@ibm.com> Co-authored-by: Jacob Emery <jacob.emery@ibm.com> Signed-off-by: Amadeus Podvratnik <pod@de.ibm.com>
AmadeusPodvratnik
pushed a commit
to AmadeusPodvratnik/Ansible-OpenShift-Provisioning
that referenced
this pull request
Jan 19, 2023
The openshift-installer requires up to 60 min to complete. You need to check manually if the install process started sucessfully or you simply wait 60 min for the results. This patch monitors the 'node-bootstrapper' request. Usually such request is raised within 6 min. If not, then this is considered as an error and the ansible playbook script exits. The openshift-installer process is not aborted! It is still running. Signed-off-by: Klaus Smolin <smolin@de.ibm.com> Signed-off-by: Jacob Emery <jacob.emery@ibm.com> Co-authored-by: Jacob Emery <jacob.emery@ibm.com> Signed-off-by: Amadeus Podvratnik <pod@de.ibm.com>
|
🎉 This PR is included in version 1.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
jacobemery
added a commit
that referenced
this pull request
Dec 20, 2023
The openshift-installer requires up to 60 min to complete. You need to check manually if the install process started sucessfully or you simply wait 60 min for the results. This patch monitors the 'node-bootstrapper' request. Usually such request is raised within 6 min. If not, then this is considered as an error and the ansible playbook script exits. The openshift-installer process is not aborted! It is still running. Signed-off-by: Klaus Smolin <smolin@de.ibm.com> Signed-off-by: Jacob Emery <jacob.emery@ibm.com> Co-authored-by: Jacob Emery <jacob.emery@ibm.com>
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.
The openshift-installer requires up to 60 min to complete. You need to check manually if the install process started sucessfully or you simply wait 60 min for the results.
This patch monitors the 'node-bootstrapper' request. Usually such request is raised within 6 min. If not, then this is considered as an error and the ansible playbook script exits.
The openshift-installer process is not aborted! It is still running.
Signed-off-by: Klaus Smolin smolin@de.ibm.com