Bug 1178507
Summary: | [Network Custom Properties] Removal of an unmanaged network doesn't clear its properties | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | GenadiC <gcheresh> |
Component: | ovirt-engine | Assignee: | Martin Mucha <mmucha> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | GenadiC <gcheresh> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.5.0 | CC: | bazulay, danken, gklein, lpeer, lsurette, mburman, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi |
Target Milestone: | ovirt-3.6.0-rc3 | Flags: | ylavi:
Triaged+
|
Target Release: | 3.6.0 | ||
Hardware: | x86_64 | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-20 01:11:49 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: | 1136329, 1246060 | ||
Bug Blocks: |
Description
GenadiC
2015-01-04 12:40:11 UTC
And a related but different bug - it's possible to supply network custom properties to a host interface via the Setup Networks API even if no network is attached to it (according to what I saw on your setup... I vaguely remember writing code to block this, but anyway...). Once 1136329 will be implemented custom properties will be stored in network attachments and the bug will be solved by cascading network delete. Other thoughts on this matter: There are 2 types of custom properties: 1. Some custom properties (e.g. bridging opts) are persistent on the VDSM side and some of them being reported back to the engine, though engine ignores that. 2. Any other non-persistent & not reported custom properties being stored in engine DB only. IMHO, all persistent properties should be reported by VDSM to engine as they are host configuration and might be configured manually by a user (not through engine). Engine should track them for sync/un-sync decision. Verified on - 3.6.0.2-0.1.el6 and vdsm-4.17.10-5.el7ev.noarch |