Bug 1326146

Summary: In horizon, when going to Identity and clicking the project without admin privileges will result in being logged out
Product: Red Hat OpenStack Reporter: David Hill <dhill>
Component: python-django-horizonAssignee: Itxaka <iserrano>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: high Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: akaris, aortega, athomas, dhill, dmaley, iserrano, jliberma, mrunge, srevivo, yjog
Target Milestone: asyncKeywords: ZStream
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-2015.1.3-2.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-01 12:28:42 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:

Description David Hill 2016-04-11 23:15:00 UTC
Description of problem:
In horizon, when going to Identity and clicking the project without admin privileges will result in being logged out

The following patch seems to be fixing it:
https://review.openstack.org/#/c/283011/

Version-Release number of selected component (if applicable):


How reproducible:
Everytime

Steps to Reproduce:
1. Create a user test in tenant test 
2. Go in dashboard, click identity then the project name
3.

Actual results:
Logged out

Expected results:
Display nothing or not clickable.

Additional info:
This cannot be reproduced with RHOSP 8.

Comment 3 David Hill 2016-04-26 23:24:59 UTC
We confirm this patch solves the issue.

Comment 11 Itxaka 2016-05-09 10:06:12 UTC
There is 3 patches involved that could fix this issue:

Replace default user model PK:
https://review.openstack.org/#/c/222478/


doa does not work with mysql (introduced by the patch above):
https://review.openstack.org/#/c/228024/


This one is a simple change to the default local_settings.py.example, so its not really needed as a patch as it can be applied manually to the local_settings.py configuration

Use the User model from d-o-a:
https://review.openstack.org/#/c/222480/




Looking at this patches, they were all done against Liberty, and in this case we are talking about Kilo. There is a possibility of breaking more stuff by introducing them into a stable branch.

Would be good to deploy the patches manually first to see if this solves the customer issue before proceeding further.

Thanks.

Comment 12 Itxaka 2016-05-09 10:50:29 UTC
Im thinking, that as this is a different issue altogether it would be better to open a different case for it as to make it easier to reference the issue and not pollute the original issue, which from my POV is solved.

What do you think?

Comment 13 Andreas Karis 2016-05-09 14:29:46 UTC
Hi, I looked at https://bugzilla.redhat.com/show_bug.cgi?id=1218894 and don't really understand the last part about failed qa for python-django-horizon-2015.1.3-2.el7ost 

Is it possible that this version of openstack auth fixed the issue? "python-django-openstack-auth-1.2.0-6.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report"

FYI, I openend BZ 1334405  in order to continue work on this.

Regards,

Andreas

Comment 14 Itxaka 2016-05-09 14:40:21 UTC
Thanks Andreas.

That package is for fedora only, I submited the backports downstream to our RHOS package and Im in the middle of testing them.

Unfortunately I have no idea what the other bug report (https://bugzilla.redhat.com/show_bug.cgi?id=1218894) stands with the failed QA, but that should not affect the patches to RHOS.

Thanks for opening the other bug, will link all patches to that one.

Comment 16 Ido Ovadia 2016-05-22 12:30:07 UTC
Verified
========
python-django-horizon-2015.1.3-3.el7ost.noarch

Comment 18 errata-xmlrpc 2016-06-01 12:28:42 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1197