Bug 831864
Summary: | 500 Internal Server Error from utilisation graph | ||
---|---|---|---|
Product: | [Retired] Beaker | Reporter: | Dan Callaghan <dcallagh> |
Component: | reports | Assignee: | Dan Callaghan <dcallagh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 0.8 | CC: | bpeck, dcallagh, rmancy, stl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-26 06:40:57 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Dan Callaghan
2012-06-13 23:21:44 UTC
This is a regression that was introduced in commit ca896a6a for bug 797584. That commit introduced an association object SystemGroup and so Group.systems is no longer a usable join relationship. I have a feeling we hit this same problem elsewhere already, the stack trace looks very familiar... (In reply to comment #1) > I have a feeling we hit this same problem elsewhere already, the stack trace > looks very familiar... I was thinking of bug 817568, which is the same issue (joining on Group.systems) but in a different place. I've just checked all references to Group.systems and System.groups, they are not used in any other joins. We have a few places where we filter on those relationships using .contains() and .any() but it seems sqlalchemy is smart enough to figure out the right thing in those cases. On Gerrit: http://gerrit.beaker-project.org/1135 Beaker 0.9.0 has been released. |