Bug 799969
Summary: | [RFE] Improve flow in engine when vdsm service is restarted on the SPM | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | David Jaša <djasa> |
Component: | ovirt-engine | Assignee: | Allon Mureinik <amureini> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.1.0 | CC: | acathrow, amureini, bazulay, djasa, iheim, jkt, lpeer, nsoffer, Rhev-m-bugs, yeylon |
Target Milestone: | --- | Keywords: | FutureFeature, Improvement, Reopened |
Target Release: | 3.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | storage | ||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-04 09:16:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Jaša
2012-03-05 14:16:28 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug. Please try to reproduce this again with current release, and provide engine and vdms logs. I tried 3.3 in various parts of cycle and my impression is that workaround were applied throughout the stack such as vdsm service (re)start over ssh. All of those do not resolve however the simple case of issuing "shutdown -h now" on SPM host - the host never lets know to engine or peers that it's going down so SPM status remains forever. |