Bug 1072274
Summary: | Warn user if vdsm-gluster is not installed | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Rene Koch <rkoch> |
Component: | Frontend.WebAdmin | Assignee: | Shubhendu Tripathi <shtripat> |
Status: | CLOSED EOL | QA Contact: | Pavel Stehlik <pstehlik> |
Severity: | unspecified | Docs Contact: | |
Priority: | medium | ||
Version: | --- | CC: | bugs, ecohen, gklein, josh, mgoldboi, rbalakri, rkoch, sabose, sbonazzo, s.kieske, yeylon |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | gluster | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-02 10:52:33 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: |
Description
Rene Koch
2014-03-04 09:30:01 UTC
This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed. I would go further and say: why don't you prompt the user with a message which says that enabling gluster services will install the required packages on all hosts in the cluster and ask if the user agrees to this? This would be much better than an annoying warning. oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4. If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution) If it's an RFE please update the version to 4.0 if still relevant. This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4 and reopen if still an issue. |