Bug 1121388
| Summary: | Missing error message for CANNOT_FORCE_SELECT_SPM_VDS_ALREADY_SPM | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Moti Asayag <masayag> | ||||
| Component: | ovirt-engine-core | Assignee: | Tal Nisan <tnisan> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Carlos Mestre González <cmestreg> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.5 | CC: | acanan, amureini, bugs, ecohen, gklein, iheim, rbalakri, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.5.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | ovirt-3.5.0_rc1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-10-17 12:20:25 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Artear a talk with Tal, the fix is disabling the "Select as SPM" button in the webui when the host is already the SPM. That works for RC1 (ovirt-engine-3.5.0-0.0.master.20140804172041.git23b558e.el6.noarch) Additional note: CANNOT_FORCE_SELECT_SPM_VDS_ALREADY_SPM shows proper message [Cannot force select SPM. The Host 10.34.62.206 is already SPM or contending.] throught REST-API. oVirt 3.5 has been released and should include the fix for this issue. |
Created attachment 919358 [details] missing error Description of problem: The webadmin doesn't translate the error code into a proper message Version-Release number of selected component (if applicable): commit 11b2a8bc15acc7186504fb5da3d021451381d73f How reproducible: always Steps to Reproduce: 1. Select a host as SPM while it is already selected as SPM. 2. 3. Actual results: see screenshot Expected results: an error should be properly translated Additional info: the relevant translation is missing from AppErrors.java