Bug 1255590

Summary: Gluster: Variables in an error message are not replaced when it is shown on screen
Product: [oVirt] ovirt-engine Reporter: Yuko Katabami <ykatabam>
Component: Frontend.WebAdminAssignee: Sahina Bose <sabose>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: medium    
Version: ---CC: amarchuk, amureini, bugs, gklein, lsurette, mgoldboi, rbalakri, sabose, sasundar, sbonazzo, srevivo, ykaul
Target Milestone: ovirt-4.0.2Flags: rule-engine: ovirt-4.0.z+
rule-engine: planning_ack+
sabose: devel_ack+
sasundar: testing_ack+
Target Release: 4.0.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-25 12:16:27 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:
Attachments:
Description Flags
error message with variables none

Description Yuko Katabami 2015-08-21 04:21:25 UTC
Created attachment 1065435 [details]
error message with variables

Description of problem:
While translating/reviewing, we found the following message shown on the screen without having those variable replaced with the actual values:

Cannot ${action} ${type}. No up server found in ${clusterName}.

Version-Release number of selected component (if applicable): 3.6


How reproducible:


Steps to Reproduce:
1. Login to Web Admin Portal
2. Click Volumes tab and select a volume
3. Click Geo-Replication sub tab
4. Click Sync action button

Actual results:
Message is shown without having the variables replaced

Expected results:
Variables should be replaced with actual values

Additional info:
Screenshot attached

Comment 1 Red Hat Bugzilla Rules Engine 2015-10-19 11:02:51 UTC
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.

Comment 2 Sandro Bonazzola 2015-10-26 12:44:23 UTC
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Comment 3 Red Hat Bugzilla Rules Engine 2015-12-11 02:23:41 UTC
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.

Comment 4 Sandro Bonazzola 2016-05-02 10:02:39 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 5 Yaniv Lavi 2016-05-23 13:17:54 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 6 Yaniv Lavi 2016-05-23 13:21:52 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 7 Sandro Bonazzola 2016-07-12 10:02:15 UTC
Moving back to post since this bug is targeted to 4.0.1 but referenced patches are not included in 4.0.1 branch. Please check this bug status and eventually re-target to 4.0.2

Comment 8 SATHEESARAN 2016-08-22 17:28:35 UTC
Tested with RHGS 3.1.3 ( vdsm-4.17.33-1.el7rhgs ) and RHV 4.0.2-7 by adding RHGS node to 3.6 cluster

1. Created a volume
2. Moved all the RHGS node in the cluster in to MAINTENANCE state
3. Select the volume, click on 'geo-replication' tab and select the operation as 'sync'

Observer the error dialog mentioning correct response - "Error while executing action: Cannot refresh Geo-replication session. No up server found in RHGS_Cluster_1."