Bug 1119699
Summary: | ovirt-ha-agent dead but subsys locked | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | ovirt-hosted-engine-ha | Assignee: | Jiri Moskovcak <jmoskovc> |
Status: | CLOSED ERRATA | QA Contact: | Nikolai Sednev <nsednev> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.0 | CC: | aburden, alukiano, dfediuck, gklein, iheim, jmoskovc, mavital, nsednev, sbonazzo, sherold |
Target Milestone: | --- | Keywords: | Rebase, Triaged, ZStream |
Target Release: | 3.4.2 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | sla | ||
Fixed In Version: | Doc Type: | Rebase: Bug Fixes Only | |
Doc Text: |
Rebase package(s) to version: 1.1.5
Highlights and important bug fixes:
The rebase just drop patches included in the rpm, now included in the source tarball.
Other bugs addressed in the rebase will be attached to the errata.
About this bug (leaving to Jiri to complete):
Previously, ovirt-ha-agent did not always wait long enough before attempting to connect to storage, which would result in a failure to connect. Now, the wait time is configurable so that the agent will wait long enough, and will retry if necessary, to successfully connect to storage.
|
Story Points: | --- |
Clone Of: | 1097767 | Environment: | |
Last Closed: | 2014-09-04 12:47:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1097767 | ||
Bug Blocks: | 1123858 |
Comment 2
Nikolai Sednev
2014-08-12 18:04:16 UTC
Cause: agent doesn't wait long enough for vdsm to connect the storage Consequence: agent tries to access the storage before it's ready Fix: wait longer and retry a few times (this is configurable in case some systems needs a different grace time) Result: agent waits long enough and the storage is successfully connected (note: yes, this is similar to 1119702, but the fix was on a different place) Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1155.html |