Removed lock/unlock the controllers and subclouds after the keystone admin password change.
Story: 2009194 Task: 43599 Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com> Change-Id: I458b7b3fc0555df851e38e3ab2fa16c25004ac6f
This commit is contained in:
parent
af7f3bdb78
commit
728b29af8e
@ -42,18 +42,12 @@ Ensure that all subclouds are managed and online.
|
||||
$ source /etc/platform/openrc
|
||||
~(keystone_admin)]$
|
||||
|
||||
|
||||
#. After five minutes, lock and then unlock each controller in the System
|
||||
Controller.
|
||||
|
||||
#. Lock and then unlock each controller in each subcloud.
|
||||
|
||||
.. note::
|
||||
In a subcloud, if the |CLI| command returns an authentication error after
|
||||
you source the script /etc/platform/openrc, you can verify the password
|
||||
on the subcloud by using the command :command:`env \| grep
|
||||
OS\_PASSWORD`. If it returns the old password, you will need to run the
|
||||
command :command:`keyring set CGCS admin` and provide the new admin
|
||||
In a subcloud, if the |CLI| command returns an authentication error
|
||||
after you source the script /etc/platform/openrc, you can verify
|
||||
the password on the subcloud by using the :command:`env \| grep OS\_PASSWORD`
|
||||
command . If it returns the old password, you will need to run the
|
||||
:command:`keyring set CGCS admin` command and provide the new admin
|
||||
password.
|
||||
|
||||
.. only:: partner
|
||||
|
@ -24,12 +24,6 @@ This section describes how to change or reset a Keystone user password.
|
||||
|
||||
~(keystone_admin)]$ openstack user password set
|
||||
|
||||
.. warning::
|
||||
Both controller nodes must be locked and unlocked after changing
|
||||
the Keystone admin password. You must wait five minutes before
|
||||
performing the lock/unlock operations.
|
||||
|
||||
|
||||
- Use the following command to reset a Keystone non-admin user \(tenant user\) account.
|
||||
|
||||
.. code-block:: none
|
||||
|
Loading…
Reference in New Issue
Block a user