Bug 1749316
| Summary: | [restraint] ERROR: Socket I/O timed out | ||
|---|---|---|---|
| Product: | [Retired] Restraint | Reporter: | Ales Zelinka <azelinka> |
| Component: | general | Assignee: | Carol Bouchard <cbouchar> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 0.1.39 | CC: | asavkov, bpeck, breilly, cbeer, cbouchar, jtluka, kzhang, liali, lzachar, mastyk, xiawu, yfu |
| Target Milestone: | 0.1.43 | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-13 18:23:48 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Ales Zelinka
2019-09-05 11:06:06 UTC
Hello Carol, can you please take a look into this issue? You may experience this during your patches. I'm suspicious this issue is related to sshlib; however, I wanted to spend more time testing my theory. Hi, We got several RHEL-8.2 userspace gating tests failed because of this "Socket I/O timed out" error. We have to trigger gating tests again manually to unblock developer tagging packages to RHEL-8.2 release. For example: Beaker job: https://beaker.engineering.redhat.com/jobs/3929699 Task T:103015482: http://lab-02.rhts.eng.pek2.redhat.com/beaker/logs/tasks/103015+/103015482/harness.log .... Installed: kernel-kernel-kdump-crash-sysrq-c-3.0-15.noarch Complete! ** Preparing metadata ** Refreshing peer role hostnames ** ERROR: Socket I/O timed out ** Completed Task : 103015482 ... Can I know when this could be fixed? Or is there a way to workaround this error? Thanks, Emma We will ship this to upstream probably within 1/2 weeks. *** Bug 1779033 has been marked as a duplicate of this bug. *** Hi there, We have gating job failed as this problem very often, for example: https://beaker.engineering.redhat.com/jobs/3951456 https://beaker.engineering.redhat.com/jobs/3951092 https://beaker.engineering.redhat.com/jobs/3949809 https://beaker.engineering.redhat.com/jobs/3949776 https://beaker.engineering.redhat.com/jobs/3949556 (from last night to now) Once gating job failed, it will block the whole workflow for not only one team, we have to retest, but retest may have the same problem. I am not pushing, just hope this issue can be fixed ASAP, Thanks! Best regards Yanan Fu Hi, we are working on in. PEK2 is affected more than just Socket I/O. (In reply to Martin Styk 🤦♂️ from comment #8) > Hi, > > we are working on in. > > PEK2 is affected more than just Socket I/O. HI, How soon will the fix be applied in our product environment? If you are too busy investigating the PEK2 lab slowness issue, is there someone else who can fasten deploying the socket I/O issue fix? Thanks! Patch is merged already. I will speak today with my colleagues. If they want to add anything else into new restraint release. Otherwise, I will tag it and ship it. |