Bug 1303694

Summary:	bad string in error message when testing external provider without permissions
Product:	[oVirt] ovirt-engine	Reporter:	movciari
Component:	Frontend.WebAdmin	Assignee:	Boriso <bodnopoz>
Status:	CLOSED CURRENTRELEASE	QA Contact:	movciari
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.6.3	CC:	bodnopoz, bugs, gklein, masayag, movciari, oourfali, sbonazzo
Target Milestone:	ovirt-4.0.0-beta	Flags:	rule-engine: ovirt-4.0.0+ rule-engine: planning_ack+ rule-engine: devel_ack+ pstehlik: testing_ack+
Target Release:	4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 10:07:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description movciari 2016-02-01 16:54:18 UTC

Description of problem:
When testing the provider's liveliness while the user doesn't have the right permissions for that, the operation failed as expected but the error message has redundant underscore at the end:
"User is not authorized to perform this action_" instead of "User is not authorized to perform this action"

Version-Release number of selected component (if applicable):
3.6.3-0.1.el6

How reproducible:
always

Steps to Reproduce:
1. Have a provider (Foreman in my case)
2. Access RHEVM with a cluster admin user 
3. Test the provider

Comment 1 Eli Mesika 2016-02-02 10:33:35 UTC

Can you please attach a screenshot showing that ?

thanks

Comment 3 Sandro Bonazzola 2016-05-02 10:08:31 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 4 Gil Klein 2016-07-27 10:07:23 UTC

This bug was fixed and is slated to be in the upcoming version. As we
are focusing our testing at this phase on severe bugs, this bug was
closed without going through its verification step. If you think this
bug should be verified by QE, please set its severity to high and move
it back to ON_QA