Bug 1341719 - SetupNetworks - Wrong ip on moved network
Summary: SetupNetworks - Wrong ip on moved network
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.0.0-rc
: 4.0.0
Assignee: Alona Kaplan
QA Contact: Meni Yakove
Depends On:
TreeView+ depends on / blocked
Reported: 2016-06-01 15:03 UTC by Alona Kaplan
Modified: 2016-07-05 07:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-07-05 07:41:04 UTC
oVirt Team: Network
rule-engine: ovirt-4.0.0+
rule-engine: planning_ack+
danken: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
oVirt gerrit 58472 0 ovirt-engine-4.0 MERGED webadmin: attachment with no reported configuration is Synced 2016-06-01 15:32:08 UTC

Description Alona Kaplan 2016-06-01 15:03:16 UTC
Description of problem:
When moving a network from a nic to another nic and then opening the edit dialog, the ip config disappears (should move with the network to a new nic)
However, when clicking ok on the setup networks dialog, the correct ip is actually set on the nic
So the bug is only with the display of the edit dialog.

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

How reproducible: 100%

Steps to Reproduce:
1. Open the setup network dialog.
2. Set the ip of the network to be static, ip -
3. Move a network from one nic to another.
3. Open the edit dialog of the network.
4. Click ok on the setup network dialog.

Actual results:
3. The edit dialog doesn't show the ip is static and
4. The actual value set on the network is ip static -

Expected results:
3. The edit dialog shows the ip is static and

Additional info:

Comment 1 Michael Burman 2016-06-07 09:28:01 UTC
Verified on -

Comment 2 Sandro Bonazzola 2016-07-05 07:41:04 UTC
oVirt 4.0.0 has been released, closing current release.

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