Bug 1636758
| Summary: | PrepareImageVDSCommand fails - Unable to update the image info - VDSM (vdsm.Scheduler) [Executor] Worker blocked | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Avihai <aefrat> | ||||||
| Component: | BLL.Storage | Assignee: | Tal Nisan <tnisan> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Lucie Leistnerova <lleistne> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.2.6.2 | CC: | aefrat, bugs, eshames, lsvaty, mperina, nsoffer, pkliczew, reliezer, tnisan | ||||||
| Target Milestone: | --- | Keywords: | Automation | ||||||
| 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: | 2019-01-14 09:06:47 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Avihai
2018-10-07 12:42:16 UTC
Created attachment 1491323 [details]
Full engine logs for several TC's with the failiure
Seems like more of an infra issue since the workers are blocked see similar bug: https://bugzilla.redhat.com/show_bug.cgi?id=1653258 Correct worker is blocked due to sdc module. We can assume that thread executor is broken because a thread was stuck due to the code running inside. From my perspective the storage code should handle it and make sure a worker won't get stuck. Avihay, worker blocked is not a bug in storage (or other system). When you have issues with block workers you need to check what is blocking the workers. Please attach these logs to the bug: - sanlock.log - /var/log/messages And output of: - grep WARN vdsm.log Most likely the storage (NFS?) is not responding, this can quickly block all workers in the system. (In reply to Nir Soffer from comment #6) > Avihay, worker blocked is not a bug in storage (or other system). When you > have issues with > block workers you need to check what is blocking the workers. Can you be more specific on what exactly to check? > Please attach these logs to the bug: > - sanlock.log > - /var/log/messages > > And output of: > - grep WARN vdsm.log > > Most likely the storage (NFS?) is not responding, this can quickly block all > workers in the > system. Nir, It's been almost 3 months since this bug was opened and obviously, by now I do not have the requested logs. We(QE) will try to see if this bug reproduces in our latest runs and will provide new logs once it reoccurs. Elad, please tell notify if you encounter this issue during automation Tier3 runs. Avihay, without the logs we cannot do anything. Please close as insifficient data and reopen with proper logs if this happen again. (In reply to Nir Soffer from comment #8) > Avihay, without the logs we cannot do anything. Please close as insifficient > data and reopen with proper logs if this happen again. I leave it up to you as the developer to close it with whatever reason you see fit. |