Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[IBM Cloud] Network issues on Windows: connectex: A connection attempt failed because the connected party did not properly respond after a period of time #6838

Closed
rm3l opened this issue May 23, 2023 · 3 comments
Closed

[IBM Cloud] Network issues on Windows: connectex: A connection attempt failed because the connected party did not properly respond after a period of time #6838

rm3l opened this issue May 23, 2023 · 3 comments
Labels
area/infra Issues or PRs related to setting up or fixing things in infrastructure. Mostly CI infrastructure. area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering area/Windows Issues or PRs specific to Windows kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.

Comments

@rm3l
Copy link
Member

rm3l commented May 23, 2023

/kind bug
/area testing
/area infra
/area Windows

Seeing these issues again with the testing infrastructure:

  [oc] ''Unable to connect to the server: dial tcp 149.81.180.114:30329: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Observed on:
@openshift-ci openshift-ci bot added kind/bug Categorizes issue or PR as related to a bug. area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering area/infra Issues or PRs related to setting up or fixing things in infrastructure. Mostly CI infrastructure. area/Windows Issues or PRs specific to Windows labels May 23, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label May 23, 2023
This was referenced May 23, 2023
Merged
Merged
Merged
This was referenced May 31, 2023
Merged
Merged
@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 22, 2023
@github-actions
Copy link
Contributor

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 21, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Sep 21, 2023
@rm3l
Copy link
Member Author

rm3l commented Sep 21, 2023

Not observed recently. Will reopen if it occurs again in the future.

@rm3l rm3l closed this as not planned Won't fix, can't repro, duplicate, stale Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/infra Issues or PRs related to setting up or fixing things in infrastructure. Mostly CI infrastructure. area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering area/Windows Issues or PRs specific to Windows kind/bug Categorizes issue or PR as related to a bug. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
Projects
odo Project
Archived in project
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rm3l