Bug 105378
Summary: | Session#flushAll mistakenly things a 1..1 association isn't set | ||
---|---|---|---|
Product: | [Retired] Red Hat Web Application Framework | Reporter: | Daniel Berrangé <berrange> |
Component: | persistence | Assignee: | Archit Shah <archit.shah> |
Status: | CLOSED WONTFIX | QA Contact: | Jon Orris <jorris> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | nightly | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-11-10 21:03:46 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 108447 |
Description
Daniel Berrangé
2003-09-25 15:54:00 UTC
The bug reported is actually a bug masking a known lacking feature. The reported bug that is causing the error reported is fixed in 37186. That changes the code that checks flushability to use the correct metadata. With that fix, the error you will get is a foreign key violation. The engine is confused by the loop of 1..1 relationships. According to the metadata, the link must exist for the "provider" object to exist. And the "provider" object, as part of the key of the link must exist for the link to exist. Only by looking at the physical metadata and determining that the "provider" object can be created in the database without the link can this use case work. |