Bug 1583516
| Summary: | [AutoDefine] - The external sync of the AutoSyncCommand attaching all external_networks to all clusters type | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Michael Burman <mburman> | ||||
| Component: | BLL.Network | Assignee: | Ales Musil <amusil> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.2.3.5 | CC: | alkaplan, amarchuk, bugs, danken, myakove | ||||
| Target Milestone: | ovirt-4.2.5 | Flags: | rule-engine:
ovirt-4.2+
|
||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-engine-4.2.5.2_SNAPSHOT-79.gffafd93.0.scratch.master.el7ev.noarch.rpm | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-07-31 15:32:02 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1530027 | ||||||
| Attachments: |
|
||||||
|
Description
Michael Burman
2018-05-29 07:23:08 UTC
Created attachment 1445194 [details]
engine log
It is a bit problematic to solve the bug. We don't have an indication whether the network was auto-defined or not. Once auto-syncing, the network is added to all the clusters that have the provider defined. We don't have a way to differentiate between a regular network to a one that was auto-defined. Let's schedule a meeting to decide how to solve the issue. One possibility may be to change the requirements and define the auto-defined network in all the clusters and not just the ovs ones. Meanwhile, moving the bug to 4.2.5. Another option is to change the auto sync provider process so that external networks with a physical network will be automatically attached only to ovs clusters. (In reply to Alona Kaplan from comment #3) > Another option is to change the auto sync provider process so that external > networks with a physical network will be automatically attached only to ovs > clusters. That is actually what we have discussed with Dominik and I am trying to implement this. FailedQa on - 4.2.5.2_SNAPSHOT-76.g2d45cde.0.scratch.master.el7ev 2d45cde is https://code.engineering.redhat.com/gerrit/#/c/143700/ which is upstream 20e078765 which is ovirt-engine-4.2.5.1 which is does not have the code yet. This is a bug in the nightly builds: 4.2.5.2_SNAPSHOT-76.g2d45cde.0.scratch.master.el7ev is based on a code that is older than that of ovirt-engine-4.2.5.1_SNAPSHOT-75.gde294d4.0.scratch.master (9199da9 restapi: Fix APIv3 deprecated/removed message) comment 6 is incorrect. build: post ovirt-engine-4.2.5.1 is three commits after restapi: Fix APIv3 deprecated/removed as is evident on https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/heads/ovirt-engine-4.2 Verified on - 4.2.5.2_SNAPSHOT-79.gffafd93.0.scratch.master.el7ev This bugzilla is included in oVirt 4.2.5 release, published on July 30th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.5 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. |