Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1552062

Summary: [UI] New provider with type External Network Provider requires auto-sync to be enabled
Product: [oVirt] ovirt-engine Reporter: Mor <mkalfon>
Component: BLL.NetworkAssignee: Dominik Holler <dholler>
Status: CLOSED CURRENTRELEASE QA Contact: Mor <mkalfon>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.2.2CC: bugs, dholler, lveyde, mburman
Target Milestone: ovirt-4.2.2Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.2.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:01:48 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
screenshot none

Description Mor 2018-03-06 12:33:00 UTC
Created attachment 1404778 [details]
screenshot

Description of problem:
When adding a new External Network Provider, UI requires to check the 'Automatic Synchronization' option. Adding new External Network Provider with auto-sync off is a valid use case, hence this value should not be mandatory.

Version-Release number of selected component (if applicable):
RHV 4.2.2.2-0.1.el7

How reproducible:
100%

Steps to Reproduce:
1. Try to add new provider with External Network Provider type. Do not mark the 'Automatic Synchronization' checkbox.

Actual results:
When you press OK, it doesn't complete the add action.

Expected results:
Should complete the action.

Additional info:
This is also relevant for OpenStack Networking provider type.

Comment 1 Mor 2018-03-18 07:34:52 UTC
Verified on:
RHV 4.2.2.4-0.1.el7

Comment 2 Sandro Bonazzola 2018-03-29 11:01:48 UTC
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 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.