Bug 883879 - engine [TEXT]: error message for failing mount on posix domain is not clear
Summary: engine [TEXT]: error message for failing mount on posix domain is not clear
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.1.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.3.0
Assignee: Maor
QA Contact: Dafna Ron
URL:
Whiteboard: storage
: 664216 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-05 13:47 UTC by Dafna Ron
Modified: 2016-02-10 20:22 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: Storage
Target Upstream Version:
Embargoed:
scohen: Triaged+

Attachments (Terms of Use)
logs (503.10 KB, application/x-gzip)
2012-12-05 13:47 UTC, Dafna Ron 		no flags Details
View All

Description Dafna Ron 2012-12-05 13:47:51 UTC 
Created attachment 658205 [details]
logs

Description of problem:

I think that this error presented to user in a dialogue is not very clear. 

Error: Cannot add Storage. Internal error, Storage Connection doesn't exist.

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

si24.5

How reproducible:

100%

Steps to Reproduce:
1. open the new posix domain dialoge
2.  put wrong parameters in the dialogue
3. press OK
  
Actual results:

Error: Cannot add Storage. Internal error, Storage Connection doesn't exist.

Expected results:

since its posix and we can fail on different things we need a general user friendly message for any failure. this error is not very clear or true. 
 
Additional info: logs
Comment 2 Maor 2013-01-16 19:56:49 UTC 
Should this message still change? since this bug is related to other command that should be fixed before it.
Comment 3 Ayal Baron 2013-01-27 10:28:54 UTC 
(In reply to comment #2)
> Should this message still change? since this bug is related to other command
> that should be fixed before it.

With the fix for bug 815083 will users still be able to reach this error?
Comment 4 Maor 2013-02-20 23:08:56 UTC 
(In reply to comment #3)
> (In reply to comment #2)
> > Should this message still change? since this bug is related to other command
> > that should be fixed before it.
> 
> With the fix for bug 815083 will users still be able to reach this error?

Depends on the fix.
Comment 5 Ayal Baron 2013-03-06 21:32:14 UTC 
(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > Should this message still change? since this bug is related to other command
> > > that should be fixed before it.
> > 
> > With the fix for bug 815083 will users still be able to reach this error?
> 
> Depends on the fix.

The fix is in, does it take care of this scenario or not?
Comment 6 Maor 2013-03-13 17:43:18 UTC 
*** Bug 664216 has been marked as a duplicate of this bug. ***
Comment 7 Vered Volansky 2013-03-18 10:31:33 UTC 
Bz 883877 will fix the general exception issue once solved. Issue here will probably persist, though should be easier to resolve.
Comment 8 Maor 2013-06-05 16:00:10 UTC 
It seems that BZ883877 already fixed this issue.
The message for mount problem is :"Error while executing action Add Storage Connection: Problem while trying to mount target"
Moving to ON_QA to be verified
Comment 9 Dafna Ron 2013-06-10 11:44:21 UTC 
verified on is1

vdsm: 

MountError: (32, ";mount: unknown filesystem type 'bla'\n")

engine: 

posix failed because of error code 477 and error message is: problemwhiletryingtomounttarget

UI: 

Error while executing action Add Storage Connection: Problem while trying to mount target
Comment 10 Itamar Heim 2014-01-21 22:23:43 UTC 
Closing - RHEV 3.3 Released
Comment 11 Itamar Heim 2014-01-21 22:24:49 UTC 
Closing - RHEV 3.3 Released
Comment 12 Itamar Heim 2014-01-21 22:28:24 UTC 
Closing - RHEV 3.3 Released
Note You need to log in before you can comment on or make changes to this bug.