Bug 1173540
Summary: | No timeout and error status when optimizer machine is blocked by iptables from engine machine | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Lukas Svaty <lsvaty> |
Component: | ovirt-optimizer | Assignee: | Martin Sivák <msivak> |
Status: | CLOSED ERRATA | QA Contact: | Shira Maximov <mshira> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.5.0 | CC: | dfediuck, gklein, juwu, mavital, msivak |
Target Milestone: | ovirt-3.6.0-rc | ||
Target Release: | 3.6.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | ovirt-optimizer-0.9 | Doc Type: | Bug Fix |
Doc Text: |
Previously, the default configuration for jQuery requests did not time out. If incoming and outgoing connections to the Optimizer machine were blocked from the Manager, there were no indications that the connections were blocked. With this update, the UI plug-in reports an error if the Optimizer machine can not be reached within 60 seconds.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-09 20:21:38 UTC | Type: | Bug |
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: | |||
Bug Blocks: | 1232536 |
Description
Lukas Svaty
2014-12-12 11:51:26 UTC
3.5.1 is already full with bugs (over 80), and since none of these bugs were added as urgent for 3.5.1 release in the tracker bug, moving to 3.5.2 verified on : Red Hat Enterprise Virtualization Manager Version: 3.6.0-0.18.el6 Hi Martin, I have updated the doc text. The original doc text said time out is 30 seconds but the gerrit commit said 60 seconds so I've changed the doc text to 60 seconds. Please have a look and let me know if it is correct. Cheers, Julie Ack. But shouldn't the sentence about blocked connections use plural? "were blocked?" Thanks for reviewing the doc text. Fixed. Cheers, Julie 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. https://rhn.redhat.com/errata/RHBA-2016-0427.html |