Bug 2100417
| Summary: | Improve error message for timeout deploy error. | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Pavol Brilla <pbrilla> |
| Component: | ovirt-host-deploy-ansible | Assignee: | Dana <delfassy> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavol Brilla <pbrilla> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.5.1 | CC: | bugs, dfodor, mperina |
| Target Milestone: | ovirt-4.5.2 | Flags: | mperina:
ovirt-4.5+
|
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-30 08:47:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Pavol Brilla
2022-06-23 10:14:00 UTC
Does the log contain information, which task hanged (or which was the last one executed)? That's probably the first pointer to start debugging why it took so long, no? Or anything else missing? The case we're discussing is when the tasks themselves were executed, but the timeout occurred before all of the tasks were parsed # ls -l /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20220810220427-HOSTNAME-637f56b0-7243-45f4-829b-31a3a7c12000.log -rw-r--r--. 1 ovirt ovirt 2003867 Aug 10 22:06 /var/log/ovirt-engine/host-deploy/ovirt-host-deploy-ansible-20220810220427-HOSTNAME-637f56b0-7243-45f4-829b-31a3a7c12000.log Deploy is writing to deploy log file continuously and I see much more detail information about tasks after timeout. Verified on Software Version:4.5.2-0.3.el8ev This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |