Bug 1212741 - [New]Alert to be generated in UI when the network face with which the brick was added is down.
Summary: [New]Alert to be generated in UI when the network face with which the brick w...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: ---
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ovirt-3.6.5
: ---
Assignee: Sahina Bose
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks: rhsc_qe_tracker_everglades 1231724
TreeView+ depends on / blocked
 
Reported: 2015-04-17 09:19 UTC by RamaKasturi
Modified: 2016-03-09 09:49 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1231724 (view as bug list)
Environment:
Last Closed: 2016-03-09 09:49:23 UTC
oVirt Team: Gluster
Embargoed:
sbonazzo: ovirt-3.6.z?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?

Attachments (Terms of Use)

Description RamaKasturi 2015-04-17 09:19:33 UTC 
Description of problem:
With the gluster network for storage feature user is able to separate the management and data traffic. So when a volume is created, bricks are added to the volume using another interface leaving ovirmgmt for mangament traffic.

Now when the interface goes down with which the brick was added, UI does not mark that brick as down.

Version-Release number of selected component (if applicable):
ovirt-release-master-001-0.6.master.noarch

How reproducible:
Always

Steps to Reproduce:
1.Add a host to the UI with two interfaces.
2.Now create gluster network from UI and add this network to one of the interface using set up host networks dialog.
3. Now create a volume.
4. User will be able to see that the bricks are added using the gluster n/w.
5. Go to the system and bring down the nic which was attached to gluster n/w

Actual results:
Bricks are not marked down in the UI

Expected results:
Bricks should be marked down in the UI, as the network interface with which they were added is down.

Additional info:
Comment 1 Sahina Bose 2015-04-27 06:59:11 UTC 
Brick status can be controlled by marking the gluster network "Required" for a cluster.

What does gluster volume status return when the network interface for brick down
Comment 2 Red Hat Bugzilla Rules Engine 2015-10-19 10:58:04 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:40:41 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 Red Hat Bugzilla Rules Engine 2015-10-30 12:00:59 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 5 Sandro Bonazzola 2015-11-05 08:14:54 UTC 
oVirt 3.6.0 has been released on November 4th, re-targeting to 3.6.1 since this bug has been marked as high severity
Comment 6 Yaniv Lavi 2015-12-22 16:15:51 UTC 
3.6.1 is out, moving to 3.6.2.
Comment 7 Yaniv Lavi 2016-03-09 09:49:23 UTC 
Please reopen if you can provide the needed info.
Note You need to log in before you can comment on or make changes to this bug.