Bug 1221463 - [New] - Display proper error message in UI when one of the step in the brick create fails.
Summary: [New] - Display proper error message in UI when one of the step in the brick ...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: ---
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.0.0-alpha
: ---
Assignee: Timothy Asir
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks: rhsc_qe_tracker_everglades
TreeView+ depends on / blocked
 
Reported: 2015-05-14 05:47 UTC by RamaKasturi
Modified: 2023-09-14 02:59 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-12 12:08:59 UTC
oVirt Team: Gluster
Embargoed:
ylavi: ovirt-4.0.0?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?


Attachments (Terms of Use)

Description RamaKasturi 2015-05-14 05:47:37 UTC
Description of problem:
When user tries to create a brick and if create brick fails to mount the volume or add entry in /etc/fstab  UI displays Internal Engine error , instead it should display proper error message.

Version-Release number of selected component (if applicable):
ovirt-engine-3.6.0-0.0.master.20150429182702.git939c2e8.el6.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a brick in the UI
2. Do not remove the /etc/fstab enrty.
3. remove all the other pv,vg,lv and umount the brick.
4. Now try to create another brick with the same mount point which is in /etc/fstab.

Actual results:
UI displays an internal engine error.

Expected results:
UI should display proper error message

Additional info:

Comment 1 Ramesh N 2015-05-27 11:31:43 UTC
Looks like VDSM is not raising any proper exceptions for failure in brick creation. It always fails arbitrarily with some unknown error/exception. 

Tim: Please fix the issue and let me know, so that I can test the engine code with the exceptions.

Comment 2 Red Hat Bugzilla Rules Engine 2015-10-19 10:50:52 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 3 Sandro Bonazzola 2015-10-26 12:39:33 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 4 Sandro Bonazzola 2015-11-05 08:22:26 UTC
oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high

Comment 5 Red Hat Bugzilla Rules Engine 2015-11-09 13:24:11 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 6 Sahina Bose 2015-12-10 10:44:25 UTC
Ramesh, have the patches for this gone into 3.6?

Comment 7 Yaniv Lavi 2015-12-22 16:16:17 UTC
3.6.1 is out, moving to 3.6.2.

Comment 8 Sahina Bose 2016-03-09 09:54:40 UTC
Kasturi, do you still face this issue?

Comment 9 Sahina Bose 2016-04-12 12:08:59 UTC
Exception handling is present on master branch - and will be available in 4.0 builds

Comment 10 Red Hat Bugzilla 2023-09-14 02:59:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.