-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Bug 1796627: cmd/openshift-install/create: add env var to preserve bootstrap #2935
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
Bug 1796627: cmd/openshift-install/create: add env var to preserve bootstrap #2935
Conversation
ae3c7cc to
0f39302
Compare
|
We need this option for troubleshooting failure on disconnected environments where we are unable to further troubleshoot failed deployment because the bootstrap is not longer there. |
|
Hmm if the cluster bootstrap succeeds I don't see how keeping the bootstrap is useful? |
|
I have had many occasions where bootstrap succeeds, but installation failed and it would be useful to examine the bootstrap node. Yesterday we had an issue with machine-config-operator rendering different manifests on bootstrap vs the cluster but the bootstrap had already been removed so we couldn’t examine why. |
|
@abhinavdahiya would you be in support of this being available as an installer build time option? (never to be represented in product docs) |
|
We've discussed the need for this and have arrived at the conclusion that we'd accept an environment variable that preserved bootstrap host and emitted warnings advising that this is intended only for debugging purposes and poses a risk to cluster stability. Similar to the warning emitted when the release image is overridden via env var. Would you be interested in updating your work for that or would you prefer someone from Installer team take that on? |
Sure, thanks - I'll update the PR this afternoon. |
0f39302 to
645095a
Compare
For a variety of reasons, it may be useful to keep the bootstrap VM around for debugging. My general approach has been to interrupt the installer before it has a chance to delete the bootstrap VM. If the environment variable OPENSHIFT_INSTALL_PRESERVE_BOOTSTRAP is set to any value, the installer will not delete the bootstrap.
645095a to
e3b65eb
Compare
|
@sdodson PTAL |
|
@stbenjam Thanks, while we don't intend to allow this to enter into CI jobs because we don't wish for CI to diverge from normal customer workflows, we will likely enable this via clusterbot. Does |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I believe so, any terraform resources that still exist should get destroyed - but I haven't tested yet. |
|
/lgtm |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
21 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@stbenjam: All pull requests linked via external trackers have merged. Bugzilla bug 1796627 has been moved to the MODIFIED state. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@stbenjam: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/cherry-pick release-4.3 |
|
@sdodson: new pull request created: #3053 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
For a variety of reasons, it may be useful to keep the bootstrap VM
around for debugging. My general approach has been to interrupt the
installer before it has a chance to delete the bootstrap VM.
If the environment variable OPENSHIFT_INSTALL_PRESERVE_BOOTSTRAP is set
to any value, the installer will not delete the bootstrap.