Ask Your Question
0

You are not authorized to perform the requested action under admin user

asked 2019-09-05 22:53:31 -0600

corey gravatar image

I have two accounts on OpenStack (admin and corey), I would like to raise the permission of "corey" up to admin, and this is what I have done.

$ openstack role add --project service --user corey admin

$ source corey-openrc.sh

Nothing changed. So I tried this.

$ openstack role set --name corey admin

After doing this, both admin and corey lost all permissions, all commands can't work correctly.

$ openstack role list

You are not authorized to perform the requested action: identity:list_roles. (HTTP 403)

$ nova list

ERROR (ClientException): The server is currently unavailable. Please try again at a later time. (HTTP 503)

I can't see any info. on Horizon either, I logged in as admin, all I got is:

Error: Unable to retrieve instances

What should I do to fix this problem, I have completely no idea now.

edit retag flag offensive close merge delete
add a comment

1 answer

Sort by ยป oldest newest most voted
1

answered 2019-09-06 00:19:34 -0600

Bernd Bausch gravatar image

With openstack role set --name corey admin, you renamed the admin role corey. As a result, this role is not the admin role anymore.

Before that, you gave corey the admin role in project service. My guess is that corey-openrc.sh does not set the project to service. Thus, no admin privileges for corey.

How to fix this? Either by changing the name of the former admin role back to admin directly in the database. Or by using the ADMIN_TOKENto temporarily work around the lack of an admin role. To use the admin token, see https://docs.openstack.org/mitaka/ins....

edit flag offensive delete link more

Comments

I went into the database and changed the name of the former admin role back to admin, it works! Thanks!

corey gravatar imagecorey ( 2019-09-06 02:01:34 -0600 )edit
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2019-09-05 22:53:31 -0600

Seen: 1,284 times

Last updated: Sep 06 '19

Related questions

admin-openrc.sh

Missing auth plugin for endpoint url

die 413 'Unable to determine DISTRO, can not continue

instance stuck in build, AMQPLAIN login refused: user 'openstack' - invalid credentials

Credentials for keystone and other openstack services

why i am not able to list openstack users ("openstack user list") after installing "python-shade" package

How to check OpenStack Keystone LDAP working ?

How do I use python to call "neutron net-list"?

Cinder HTTP 503 : Keystone unavailable

How to change the openstack RC file to use tokens instead of passwd