-
Notifications
You must be signed in to change notification settings - Fork 74
OCPBUGS-58282: Retry SSH server initialization #3135
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
Conversation
Attempts to fix an issue where Windows Server 2019 machines were not having a running SSH server due to network instability.
|
@sebsoto: This pull request references Jira Issue OCPBUGS-58282, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test ci/prow/azure-e2e-operator ci/prow/azure-e2e-upgrade |
|
@sebsoto: The specified target(s) for Use In 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-sigs/prow repository. |
|
/test azure-e2e-operator azure-e2e-upgrade |
|
/retest-required |
| } | ||
| catch { | ||
| $attempt++ | ||
| Start-Sleep -Seconds 5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider adding a log message here to track this edge case and its frequency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jrvaldes, sebsoto The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test azure-e2e-operator azure-e2e-upgrade |
2 similar comments
|
/test azure-e2e-operator azure-e2e-upgrade |
|
/test azure-e2e-operator azure-e2e-upgrade |
|
/override ci/prow/nutanix-e2e-operator ci/prow/vsphere-disconnected-e2e-operator |
|
@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/nutanix-e2e-operator, ci/prow/vsphere-disconnected-e2e-operator In 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-sigs/prow repository. |
|
/jira refresh |
|
@sebsoto: This pull request references Jira Issue OCPBUGS-58282, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request. In 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@sebsoto: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
|
@sebsoto: Jira Issue OCPBUGS-58282: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-58282 has been moved to the MODIFIED state. In 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/cherry-pick release-4.19 |
|
@sebsoto: new pull request created: #3139 In 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-sigs/prow repository. |
Attempts to fix an issue where Windows Server 2019 machines were not having a running SSH server due to network instability.