Bug 1609658 - [UI] - Edit External networks - All external networks are set as connected to physical network
Summary: [UI] - Edit External networks - All external networks are set as connected t...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.2.5.1
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ovirt-4.3.0
: 4.3.0
Assignee: Ales Musil
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-30 06:33 UTC by Michael Burman
Modified: 2019-02-13 07:48 UTC (History)
1 user (show)

Fixed In Version: ovirt-engine-4.3.0_alpha
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-13 07:48:06 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.3+


Attachments (Terms of Use)
record (3.16 MB, application/x-gzip)
2018-07-30 06:33 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 94604 0 master MERGED webadmin: Check external network connection to physical network 2018-10-03 06:52:49 UTC

Description Michael Burman 2018-07-30 06:33:02 UTC
Created attachment 1471420 [details]
record

Description of problem:
[UI] - Edit External networks  - All external networks are set as connected to physical network.

It's a UI bug, all external networks are set with connect to physical network, even if not created with this property.

Version-Release number of selected component (if applicable):
4.2.6_SNAPSHOT-84.gad3de30.0.scratch.master.el7ev

How reproducible:
100%

Steps to Reproduce:
1. Create new ovn network on ovn provider - Don't check the 'connect to physical network' checkbox
2. Edit the network

Actual results:
The 'connect to physical network' checkbox is checked

Expected results:
If 'connect to physical network' checkbox wasn't set on network creation, then it shouldn't appear as checked on the edit network flow.

Comment 1 Michael Burman 2018-10-08 06:30:55 UTC
Verified on - 4.3.0-0.0.master.20181007173621.git678f1a8.el7

Comment 2 Sandro Bonazzola 2018-11-02 14:30:48 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.7 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.

Comment 3 Sandro Bonazzola 2018-11-02 15:05:41 UTC
Closed by mistake, moving back to qa -> verified

Comment 4 Sandro Bonazzola 2019-02-13 07:48:06 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


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