Bug 481773
Summary: | Your Grid Jobs tab does not agree with Jobs tab | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Matthew Farrellee <matt> |
Component: | cumin | Assignee: | Justin Ross <jross> |
Status: | CLOSED NOTABUG | QA Contact: | Frantisek Reznicek <freznice> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 1.1 | CC: | esammons, iboverma, jross |
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: | 2009-02-23 20:22:03 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: |
Description
Matthew Farrellee
2009-01-27 15:03:34 UTC
This can probably be explained by a pool misconfiguration. There were 2 pools with the same name. This raises a question of the Home view vs the Grid view if the Grid view defaults to a pool that does not have the data visible in the Home view. Right. The pool view is, naturally, scoped by a pool id. The user job view is not. I think a "pool" column is therefore in order on the user job table so one can distinguish, and navigate from that column to a particular pool. In subsequent discussion (at the f2f) we decided we didn't want the pool info before the non-admin user. Closing this as it arose due to a configuration problem. |