Bug 1420856
Summary: | If the first OSP tenant returned to cloudforms is disabled , Cloudforms will fail to authenticate against openstack | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Felix Dewaleyne <fdewaley> | ||||
Component: | Providers | Assignee: | Marek Aufart <maufart> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Omri Hochman <ohochman> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 5.7.0 | CC: | fdewaley, jfrey, jhardy, obarenbo, slucidi, tzumainn | ||||
Target Milestone: | GA | Flags: | okolisny:
needinfo+
|
||||
Target Release: | cfme-future | ||||||
Hardware: | All | ||||||
OS: | All | ||||||
Whiteboard: | openstack | ||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-09-13 18:38:15 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | Openstack | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Felix Dewaleyne
2017-02-09 16:08:31 UTC
Please assess the importance of this issue and update the priority accordingly. Somewhere it was missed in the bug triage process. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#priority for a reminder on each priority's definition. If it's something like a tracker bug where it doesn't matter, please set it to Low/Low. Added 5 disabled tenants. Refresh is fast and successful. Verified in 5.8.2.0 and RHOS 11. Felix, it looks like this is fixed in the current release - is it okay to close this BZ? (In reply to Tzu-Mainn Chen from comment #8) > Felix, it looks like this is fixed in the current release - is it okay to > close this BZ? 5.8.2.0 isn't out right now - this was not tested against 5.8.1.5 but 5.8.2.0. Sorry for repeating, this should have been resolved in the current release - is it okay to close this BZ? Thanks! |