Bug 1203701
Summary: | Deleting all the snapshots by using "Delete All" button says "Error while executing action Delete all volume snapshots: Network error during communication with the Host." | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | RamaKasturi <knarra> |
Component: | Frontend.WebAdmin | Assignee: | Shubhendu Tripathi <shtripat> |
Status: | CLOSED DEFERRED | QA Contact: | Lucie Leistnerova <lleistne> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | --- | CC: | bugs, danken, gklein, lsurette, lsvaty, mgoldboi, rbalakri, sabose, sankarshan, sgraf, srevivo, ykaul |
Target Milestone: | --- | Keywords: | Performance |
Target Release: | --- | Flags: | ylavi:
planning_ack?
ylavi: devel_ack? lsvaty: testing_ack+ |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-12-22 06:48:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1242373 | ||
Bug Blocks: | 1187461, 1240627 |
Description
RamaKasturi
2015-03-19 13:36:13 UTC
I do not see any error/exceptions in the engine logs. This is happening only with RHEL6 nodes, on RHEL7 nodes this issue is gone. In rhel6 also I remember the snapshots actually get deleted Gluster side, only the engine command fails due to time out. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset. Please set the correct milestone or add the flag. This should be blocked on being able to set different timeout for different commands. Can you add that RFE to block this one? This bug is dependent on the ability to set time out values for vdsm calls. Moving target to 4.1.0 as dependent on an infra bug Revisit when dependent infra bug is fixed |