Created attachment 614409 [details] screencap: blank browser window Description of problem: Dashboard does not load following login and org selection Version-Release number of selected component (if applicable): v1.1 [root@qeblade41 conf]# rpm -qa |grep katello katello-qpid-broker-key-pair-1.0-1.noarch katello-cli-common-1.1.8-4.el6cf.noarch katello-common-1.1.12-7.el6cf.noarch katello-configure-1.1.9-3.el6cf.noarch katello-certs-tools-1.1.8-1.el6cf.noarch katello-glue-candlepin-1.1.12-7.el6cf.noarch katello-1.1.12-7.el6cf.noarch katello-qpid-client-key-pair-1.0-1.noarch katello-glue-pulp-1.1.12-7.el6cf.noarch katello-all-1.1.12-7.el6cf.noarch katello-candlepin-cert-key-pair-1.0-1.noarch katello-cli-1.1.8-4.el6cf.noarch katello-selinux-1.1.1-1.el6cf.noarch How reproducible: occasionally Steps to Reproduce: 1. Login 2. Select org 3. observe blank browser screen hung on URL https://.../katello/notices/get_new?_=1348059796717 4. dashboard does not load Actual results: dashboard does not load. blank browser screen hung on URL https://.../katello/notices/get_new?_=1348059796717 Expected results: display dashboard Additional info: Note: httpd.conf (attached) has been edited to allow for co-install of SystemEngine and CloudEngine on same bare metal box.
Created attachment 614410 [details] katello-debug logs
Created attachment 614411 [details] edited httpd.conf to allow for co-install of SystemEngine and CloudEngine
This is happening for me too. How reproducible: Always. Steps to Reproduce: 1. Login 2. Open two browser windows. 3. Click logout in ONE browser window. 4. Wait with the other browser window open for the polling to notices to happen (default is 120 seconds). 5. Close browser window and log back in. 6. Observe blank browser screen hung on URL https://.../katello/notices/get_new?_=1348059796717
The solution here would be to not allow users to be redirected to /notices/get_new after login.
Pull request: https://github.com/Katello/katello/pull/1300
Katello commit: 33805e20e28ad60516856b740d780c0c3d4c8686
getting rid of 6.0.0 version since that doesn't exist
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM. If this is a mistake feel free to re-open.