Skip to content

Conversation

@sebsoto
Copy link
Contributor

@sebsoto sebsoto commented Jul 31, 2025

Attempts to fix an issue where Windows Server 2019 machines were not having a running SSH server due to network instability.

Attempts to fix an issue where Windows Server 2019 machines were not
having a running SSH server due to network instability.
@openshift-ci openshift-ci bot requested a review from mansikulkarni96 July 31, 2025 00:11
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 31, 2025
@sebsoto sebsoto changed the title Retry SSH server initialization OCPBUGS-58282: Retry SSH server initialization Jul 31, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jul 31, 2025
@openshift-ci-robot
Copy link

@sebsoto: This pull request references Jira Issue OCPBUGS-58282, which is invalid:

  • expected the bug to target the "4.20.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Attempts to fix an issue where Windows Server 2019 machines were not having a running SSH server due to network instability.

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
Copy link
Contributor Author

sebsoto commented Jul 31, 2025

/test ci/prow/azure-e2e-operator ci/prow/azure-e2e-upgrade

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 31, 2025

@sebsoto: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test aws-e2e-operator
/test azure-e2e-operator
/test azure-e2e-upgrade
/test ci-bundle-wmco-bundle
/test gcp-e2e-operator
/test images
/test lint
/test nutanix-e2e-operator
/test platform-none-vsphere-e2e-operator
/test security
/test unit
/test vsphere-disconnected-e2e-operator
/test vsphere-e2e-operator
/test vsphere-proxy-e2e-operator
/test wicd-unit-vsphere

Use /test all to run all jobs.

In response to this:

/test ci/prow/azure-e2e-operator ci/prow/azure-e2e-upgrade

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.

@sebsoto
Copy link
Contributor Author

sebsoto commented Jul 31, 2025

/test azure-e2e-operator azure-e2e-upgrade

@sebsoto
Copy link
Contributor Author

sebsoto commented Jul 31, 2025

/retest-required

}
catch {
$attempt++
Start-Sleep -Seconds 5
Copy link
Contributor

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.

Copy link
Contributor

@jrvaldes jrvaldes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 31, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 31, 2025

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sebsoto
Copy link
Contributor Author

sebsoto commented Jul 31, 2025

/test azure-e2e-operator azure-e2e-upgrade

2 similar comments
@sebsoto
Copy link
Contributor Author

sebsoto commented Jul 31, 2025

/test azure-e2e-operator azure-e2e-upgrade

@sebsoto
Copy link
Contributor Author

sebsoto commented Aug 1, 2025

/test azure-e2e-operator azure-e2e-upgrade

@sebsoto
Copy link
Contributor Author

sebsoto commented Aug 1, 2025

/override ci/prow/nutanix-e2e-operator ci/prow/vsphere-disconnected-e2e-operator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 1, 2025

@sebsoto: Overrode contexts on behalf of sebsoto: ci/prow/nutanix-e2e-operator, ci/prow/vsphere-disconnected-e2e-operator

In response to this:

/override ci/prow/nutanix-e2e-operator ci/prow/vsphere-disconnected-e2e-operator

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.

@sebsoto
Copy link
Contributor Author

sebsoto commented Aug 1, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Aug 1, 2025
@openshift-ci-robot
Copy link

@sebsoto: This pull request references Jira Issue OCPBUGS-58282, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

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:

/jira refresh

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 1, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 1, 2025

@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.

@openshift-merge-bot openshift-merge-bot bot merged commit f21188c into openshift:master Aug 1, 2025
18 checks passed
@openshift-ci-robot
Copy link

@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:

Attempts to fix an issue where Windows Server 2019 machines were not having a running SSH server due to network instability.

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
Copy link
Contributor Author

sebsoto commented Aug 5, 2025

/cherry-pick release-4.19

@openshift-cherrypick-robot

@sebsoto: new pull request created: #3139

In response to this:

/cherry-pick release-4.19

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants