Bug 783457

Summary: [Text] Unevaluated variables in error dialogue when activating host in active mode
Product: [Retired] oVirt Reporter: Jakub Libosvar <jlibosva>
Component: ovirt-engine-coreAssignee: Asaf Shakarchi <asaf>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: acathrow, bazulay, ecohen, iheim, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-30 12:27:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jakub Libosvar 2012-01-20 14:00:44 UTC
Description of problem:
If user clicks Activate button on host that is already Up, the error message is literally 'Cannot ${action} ${type}. Host in Up status.'

Version-Release number of selected component (if applicable):
ovirt-engine-backend-3.0.0_0001-1.2.fc16.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Have host in maintenance
2. Click activate and then again
  
Actual results:
Cannot ${action} ${type}. Host in Up status

Expected results:
Cannot activate host. Host in Up status

Additional info:
2012-01-20 15:00:24,926 INFO  [org.ovirt.engine.core.bll.HandleVdsVersionCommand] (QuartzScheduler_Worker-99) Running command: HandleVdsVersionCommand internal: true. Entities affected :  ID: 29291ea0-41ac-11e1-886e-001a4a013f0a Type: VDS
2012-01-20 15:00:25,616 WARN  [org.ovirt.engine.core.bll.ActivateVdsCommand] (http--0.0.0.0-8443-1) CanDoAction of action ActivateVds failed. Reasons:VDS_CANNOT_ACTIVATE_VDS_ALREADY_UP

Comment 1 Asaf Shakarchi 2012-07-02 15:20:23 UTC
Patch submitted:
http://gerrit.ovirt.org/#/c/5842/

Comment 2 Asaf Shakarchi 2012-07-02 19:28:35 UTC
Committed [de589fd68b5997f78]

Comment 3 Itamar Heim 2012-12-30 12:27:28 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.