Bug 1023878 - [RFE] It would be better if pop-up warning info if user did not select any nic when configure bond
Summary: [RFE] It would be better if pop-up warning info if user did not select any ni...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact: Virtualization Bugs
URL:
Whiteboard: node
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-28 08:06 UTC by cshao
Modified: 2016-02-10 20:07 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-29 09:04:10 UTC
oVirt Team: Node
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description cshao 2013-10-28 08:06:09 UTC 
Description of problem:
[RFE] It would be better if pop-up warning info if user did not select any nic when configure bond.

As we know, the user needs select one nic at least when configure bond, but actually, bonding still can be configured even if user did not choose any nic.

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

How reproducible:
100%

Steps to Reproduce:
1. Install rhevh-6.5-20131024.1.0
2. Enter network page.
3. Create bond without any nic.
4. Click save button.

Actual results:
Bond is successfully configured even if user did not choose any nic.

Expected results:
It would be better if pop-up warning info if user did not select any nic when configure bond.

Additional info:
Comment 2 RHEL Program Management 2013-11-01 08:25:38 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 4 Itamar Heim 2014-06-29 09:04:10 UTC 
assuming we'll be removing all our own logic in next-gen
Note You need to log in before you can comment on or make changes to this bug.