Bug 1609658

Summary: [UI] - Edit External networks - All external networks are set as connected to physical network
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Ales Musil <amusil>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: low Docs Contact:
Priority: low    
Version: 4.2.5.1CC: bugs
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3+
Target Release: 4.3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 07:48:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
record none

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.