Add a boolean property to external network providers, which enables the automatic synchronization with all clusters that have that external provider as the default provider.
On import of a new network from the provider,
- the networks of the external provider will be imported to every data center
in the set of datacenters of the clusters that have that external provider
as the default provider,
- a vNIC profile will be created for every involved data center and network
- the networks will be assigned to every cluster that has that external
provider as the default provider.
- All users are allowed to use the new vNIC Profile.
The default value of the new property is 'true', that means that the auto sync is enabled by default.
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
I am currently running RHV 18.104.22.168-0.1.el7, but I do not any checkbox for enabling it. I am running the latest RHV build (BUILD VERSION: 4.2.1-5 [TARGET MILESTONE: ovirt-4.2.1] [25-01-2018])
Currently, the property is only available in rest-api and not available in webadmin. For backward compatibility, the property is set to 'disabled' by default in rest-api and webadmin. If you think the property should be available in webadmin, please create a bug with a proposed default value to track this.
Created attachment 1397090 [details]
Example to enable auto-synv on the REST-API via the oVirt python sdk
The fix for the blocker bug: https://bugzilla.redhat.com/show_bug.cgi?id=1539765 is not merged yet on the current RHV version. Could you please change the status to MODIFIED?
Verified on - 4.2.4-0.1.el7
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.
Since the problem described in this bug report should be
resolved in oVirt 4.2.4 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.