login as admin to projects fails

[koren]

create project:
1)login as admin.
2)add project, add admin as member to that project.
3)logout

recreate bug:
2.1)login as admin.
2.2)from "projects" on top left choose the project.
2.3)you are "unauthorized" and sent out ....
2.4)try login again (no change to url) - unsuccessful ...
2.5)change url back to root level, login again, and you are now authorized inside the project.

repeat 2.1 to 2.5 many times ....same results

[Steve Martinelli (stevemar)]

sounds like you're using horizon, so i'm adding them as well. are there any logs from keystone or horizon that show the error?

[Steve Martinelli (stevemar)]

also, which version of openstack are you using? can you attach any config files (the horizon and keystone config files) with passwords and sensitive information removed

[koren (korenlev)]

can be easily re-produced ....
effected versions ( the ones tested and verified) " juno,kilo,liberty
just follow steps above and get some logs from ur systems.

2016-04-16 23:44 GMT+03:00 Steve Martinelli <email address hidden>:

> sounds like you're using horizon, so i'm adding them as well. are there
> any logs from keystone or horizon that show the error?
>
> ** Also affects: horizon
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1571150
>
> Title:
> login as admin to projects fails
>
> Status in OpenStack Dashboard (Horizon):
> New
> Status in keystoneauth:
> New
>
> Bug description:
> create project:
> 1)login as admin.
> 2)add project, add admin as member to that project.
> 3)logout
>
> recreate bug:
> 2.1)login as admin.
> 2.2)from "projects" on top left choose the project.
> 2.3)you are "unauthorized" and sent out ....
> 2.4)try login again (no change to url) - unsuccessful ...
> 2.5)change url back to root level, login again, and you are now
> authorized inside the project.
>
> repeat 2.1 to 2.5 many times ....same results
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/horizon/+bug/1571150/+subscriptions
>

[koren (korenlev)]

can be easily re-produced ....
effected versions ( the ones tested and verified) " juno,kilo,liberty
just follow steps above and get some logs from ur systems.

[Morgan Fainberg (mdrnstm)]

Seeing as we have not seen a large number of errors for this (meaning either it is isolated to your deployment or most deployers do not hit it). I would like to see what the logs for your deployment show when you're running into this. Having your logs will help a lot when we make an attempt to duplicate this.

Likely this is an invalidation of your token due to the change in grants for the admin user.

It would help us greatly to see your logs if possible and we can look into what can be done with this issue. I am marking this bug as incomplete pending your log files.

As a note, the Juno and Kilo releases will probably not get the backport (due to EOL and very-near-to-EOL), but we might be able to backport (if there is a clean fix) to liberty (depending on complexity).

Thanks for the bug report and when you attach the logs, please set the status back to "new".

[Morgan Fainberg (mdrnstm)]

As an additional note this would not affect keystoneauth but affect keystone from what I can tell. Your logs will help us significantly. I've retargeted the bug to keystone instead of keystoneauth, pending your log files.

[Rob Cresswell (robcresswell-deactivatedaccount)]

I can't reproduce this on Horizon master when testing those steps manually; we'll need more information to verify the issue.

[koren (korenlev)]

only effects mirantis (confirmed by mirantis)
not other distros

[Launchpad Janitor (janitor)]

[Expired for OpenStack Identity (keystone) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for OpenStack Dashboard (Horizon) because there has been no activity for 60 days.]