Bug 806310
Summary: | Joining to Express Forum - error dialog. No way to join! | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | OKD | Reporter: | Garik Khachikyan <gkhachik> | ||||||||
Component: | Website | Assignee: | Clayton Coleman <ccoleman> | ||||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | urgent | ||||||||||
Version: | 2.x | CC: | ffranz, mhicks, mkoci, rmillner, sgoodwin, xtian, yujzhang | ||||||||
Target Milestone: | --- | Keywords: | Triaged | ||||||||
Target Release: | --- | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2012-04-27 20:45:45 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: | |||||||||||
Attachments: |
|
Description
Garik Khachikyan
2012-03-23 12:10:09 UTC
Created attachment 572259 [details]
screen 2
Unable to reproduce. Please confirm whether this should still be an open issue. (In reply to comment #2) hi Steve,really has this issue on product. Steps to Reproduce: 1.Go to openshift.redhat.com and sign in 2.Go to Community page and go to community/forums/express page 3.Click the "join" link on this page Actual results: An error dialog will pop up. Details please see in attachment. Created attachment 573539 [details]
screeshot1
Created attachment 573540 [details]
screenshot2
I was able to reproduce the same error with a fresh new account but not with an existing one. May be related to the permissions that are set when a new user gets created on streamline. This has been fixed in production (In reply to comment #7) Verify this bug on product, it has been fixed now, thanks. |