Bug 844660 - [oVirt-node]Previous nic info still exist in Status page after configured another nic with vlanid
Summary: [oVirt-node]Previous nic info still exist in Status page after configured ano...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-node
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Fabian Deutsch
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 894059
TreeView+ depends on / blocked
 
Reported: 2012-07-31 10:01 UTC by haiyang,dong
Modified: 2016-04-26 19:52 UTC (History)
13 users (show)

Fixed In Version: 2.6.0
Clone Of:
Environment:
Last Closed: 2013-02-05 16:19:23 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
Screenshot of Status page (86.44 KB, image/png)
2012-07-31 10:01 UTC, haiyang,dong
no flags Details

Description haiyang,dong 2012-07-31 10:01:15 UTC
Created attachment 601499 [details]
Screenshot of Status page

Description of problem:
Configure one nic by using "DHCP" Protocol with vlanid, then choose another nic different from the previous,configure the network with the same action,
after that,  the previous nic info(p3p1.20 Disabled) still exist in the Networking filed of Status page

Version-Release number of selected component (if applicable):
ovirt-node-iso-2.5.0-2.0.fc17

How reproducible:
100%

Steps to Reproduce:
1. Install ovirt-node-iso-2.5.0-2.0.fc17.
2. Configure one nic with setting like below:
VLAN yes
IPv4 dhcp.
3.Choose another nic different from the previous,configure the networking with setting like step 2.
4.Focus on Status page(Screenshot of Status page.png).

Actual results:
Networking field display disabled nic info(p3p1.20 Disabled) in Status page after configured another nic with vlanid

Expected results:
Networking field should only display enabled nic info in Status page after configured another nic with vlanid

Additional info:

No this issue when configuring nic without vlan id.

Comment 1 Fabian Deutsch 2013-02-05 16:19:01 UTC
Should be fixed with the new UI in 2.6.0

Comment 2 Fabian Deutsch 2013-02-05 16:19:23 UTC
Should be fixed with the new UI in 2.6.0


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