Bug 1558054
| Summary: | Adding a new external network fails during auto-sync is running | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Dominik Holler <dholler> |
| Component: | BLL.Network | Assignee: | Dominik Holler <dholler> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.2.2 | CC: | bugs, danken, mburman |
| Target Milestone: | ovirt-4.2.3 | Flags: | rule-engine:
ovirt-4.2+
rule-engine: exception+ |
| Target Release: | 4.2.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.2.3 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: The access to an external network provider is enforced to be serialized be non-blocking locking.
Consequence: If an external network is added, removed or imported during the automatic synchronization of the same network provider is running, the adding, removing or importing is failing with a message like:
"Cannot add Network. Related operation on provider with the id c38a67ec-0b48-4e6f-be85-70c700df5483 is currently in progress. Please try again later." because of the automatic synchronization holds the lock.
Fix: Use blocking locks to Import, Add and Remove external networks.
Result: Network is added successfully after the sync is finished.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-05-10 06:32:52 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: | |||
|
Description
Dominik Holler
2018-03-19 14:12:51 UTC
Verified on - 4.2.3-0.1.el7 This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.3 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. |