Bug 1539765
| Summary: | Auto-Sync - network rename on provider does not trigger rename in engine | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Mor <mkalfon> | ||||
| Component: | BLL.Network | Assignee: | Dominik Holler <dholler> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | future | CC: | bugs, danken, dholler, myakove, ylavi | ||||
| Target Milestone: | ovirt-4.2.4 | Flags: | rule-engine:
ovirt-4.2+
ylavi: exception+ |
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-engine-4.2.4 | Doc Type: | Enhancement | ||||
| Doc Text: |
Feature: External network rename on provider is reflected in engine
Reason: The name of an external network in engine should be consistent with the name of the same network on the provider.
Result: Renaming an external network on the provider is reflected in engine.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-06-26 08:44:18 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: | 1511823 | ||||||
| Attachments: |
|
||||||
Dominik, Just to clear something, do we allow to rename the ovn network via the engine or not? currently it's possible to do so via the engine(we have no validation for it) and after the sync the name of the ovn network returns to the origin, is that the expected behaviour in such case? (In reply to Michael Burman from comment #1) > Dominik, > Just to clear something, do we allow to rename the ovn network via the > engine or not? currently it's possible to do so via the engine(we have no > validation for it) and after the sync the name of the ovn network returns to > the origin, is that the expected behaviour in such case? This is the expected behavior in the current ovirt-4.2. In ovirt-4.3 the renaming is already blocked. If ovirt-4.3's behavior should be backported to ovirt-4.2, a new bug is required. Verified on - 4.2.4-0.1.el7 (In reply to Dominik Holler from comment #2) > (In reply to Michael Burman from comment #1) > > Dominik, > > Just to clear something, do we allow to rename the ovn network via the > > engine or not? currently it's possible to do so via the engine(we have no > > validation for it) and after the sync the name of the ovn network returns to > > the origin, is that the expected behaviour in such case? > > This is the expected behavior in the current ovirt-4.2. In ovirt-4.3 the > renaming is already blocked. If ovirt-4.3's behavior should be backported to > ovirt-4.2, a new bug is required. We decided that we would like to have in 4.2 as well. BZ 1583486 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. |
Created attachment 1387836 [details] ovirt-provider-ovn engine logs Description of problem: When renaming existing network in the provider, auto-sync does not update the network name in engine. Version-Release number of selected component (if applicable): RHV 4.2.1.3-0.1.el7 How reproducible: 100% Steps to Reproduce: 1. Create network on provider 'OVN_NET'. 2. Wait for auto-sync cycle. 3. Update the network name to 'OVN_NET_NEW'. Actual results: Engine still shows the obsolete network name - 'OVN_NET'. Expected results: Engine should update the name field of the oVirt network. Additional info: Look for 'sample_network_*' (wildcard) in the logs.