Bug 1298703
Summary: | Unable to See/Access “My Services” after a Provisioning Event. | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | John Prause <jprause> |
Component: | Appliance | Assignee: | Gregg Tanzillo <gtanzill> |
Status: | CLOSED NOTABUG | QA Contact: | Shveta <sshveta> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.5.0 | CC: | abellott, cpelland, dajohnso, dsimmons, gtanzill, jhardy, jocarter, jvlcek, kbrock, kmorey, obarenbo |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.5.6 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | service:catalog | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1297539 | Environment: | |
Last Closed: | 2016-10-10 14:28:17 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: | |||
Bug Depends On: | 1297539, 1299493 | ||
Bug Blocks: |
Comment 1
John Prause
2016-01-18 14:00:40 UTC
Keenan, Is the PR [1] that address the upstream clone of this bug in 5.5.z? If so then this BZ should be moved to post. see: https://bugzilla.redhat.com/show_bug.cgi?id=1297539#c5 [1] https://github.com/ManageIQ/manageiq/pull/6209 Keenan, Is the PR [1] that address the upstream clone of this bug in 5.5.z? If so then this BZ should be moved to post. see: https://bugzilla.redhat.com/show_bug.cgi?id=1297539#c5 [1] https://github.com/ManageIQ/manageiq/pull/6209 Hard to know if this is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1297539 It looks very similar. I'm guessing that not properly setting tags/group(tenant) is the number one reason for stuff like this to disappear. And Jeff even said this is what was happening in the PR. I can vouch that the ownership doesn't get set until later in the discovery process. Not that long of a lag, but a bit. I'd venture to say this need not be resolved in 5.5 Also, if this were indeed still broken, many people would be complaining about it. I think this can be closed. And I think it has been fixed per the PR you mentioned. |