starlingx/docs
Code Issues Proposed changes

Add known limitation to R3 release notes

Browse Source 
Add known limitatoins section to R3 release notes to address
the known issue with changing the Keystone admin pwd, and the
known workaround.

Change-Id: I2c048f5cbea82a9f251c50a8f43fa8a4349a7fc9
Signed-off-by: Kristal Dale <kristal.dale@intel.com>
This commit is contained in:
Kristal Dale 2020-01-10 17:07:12 -08:00
parent 70e0f89220
commit 797db421eb
1 changed files with 47 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

47
doc/source/releasenotes/r3_release.rst
View File

@ -96,3 +96,50 @@ StoryBoard entries for the features.
`2005860, <https://storyboard.openstack.org/#!/story/2005860>`_
`2006347 <https://storyboard.openstack.org/#!/story/2006347>`_
-------------------------
Known limitations in R3.0
-------------------------
The following are known limitations in the StarlingX R3.0 release. Workarounds
are suggested where applicable. Note that these limitations are considered
temporary and will likely be resolved in a future release.
********************************
Changing Keystone admin password
********************************
After the Keystone admin password is changed, kube-system namespace registry
secrets must be manually updated.
Tracking Launchpad: https://bugs.launchpad.net/starlingx/+bug/1853017
It is recommended that the Keystone admin password not be changed unless necessary.
**Workaround:** If you must update the WRCP's Keystone admin user password in R3.0,
you must also manually update the kube-system namespace's registry secrets that
hold the admin password for image pulls:
#. Update the WRCP Keystone admin user password:
::
openstack user set --password newP@ssw0rd admin
#. Update the kube-system namespace's `registry-local-secret` secret:
::
kubectl -n kube-system create secret docker-registry registry-local-secret --docker-server=registry.local:9001 --docker-username=admin --docker-password=newP@ssw0rd -o yaml --dry-run=true > registry-local-secret-update.yaml
kubectl -n kube-system replace secret registry-local-secret -f registry-local-secret-update.yaml
#. Update the kube-system namespace's `default-registry-key` secret:
::
kubectl -n kube-system create secret docker-registry default-registry-key --docker-server=registry.local:9001 --docker-username=admin --docker-password=newP@ssw0rd -o yaml --dry-run=true > default-registry-key-update.yaml
kubectl -n kube-system replace secret default-registry-key -f default-registry-key-update.yaml
In a distributed cloud deployment, the registry secrets must also be updated on
all subclouds in the system.