starlingx/docs
Code Issues Proposed changes

Upgrade documentation comments/suggestions

Browse Source 
Fixed the comment from r8 cherry-picked one
No further cherry-picking needed (need to fix the same in r8 and ds8 after approval)

Original master review: https://review.opendev.org/c/starlingx/docs/+/892565
r8 cherrypicked one: https://review.opendev.org/c/starlingx/docs/+/897179

Change-Id: I03162b70b9ae66d1f64cf45920d3111e627858f4
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
Ngairangbam Mili 2023-10-06 04:28:12 +00:00
parent b5d5129244
commit 3b97974411
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/source/dist_cloud/kubernetes/upgrading-the-systemcontroller-using-the-cli.rst
View File

@ -204,9 +204,10 @@ Follow the steps below to manually upgrade the system controller:
Wait for controller-1 to reinstall with the load N+1 and enter the Wait for controller-1 to reinstall with the load N+1 and enter the
``locked-disabled-online`` state. ``locked-disabled-online`` state.
Controller-1 must boot using |PXE| from the internal management network, that controller-1 must pxe-boot over the management network and its load
is, controller-1 must boot from the interface that is connected to must be served from controller-0, and not from any external
controller-0's management network interface. pxe-boot server attached to the |OAM| network. To ensure this,
check that the network boot list/order of BIOS |NIC| is correct.
The following data migration states apply when this command is executed. The following data migration states apply when this command is executed.
@ -322,8 +323,11 @@ Follow the steps below to manually upgrade the system controller:
~(keystone_admin)]$ system host-upgrade controller-0 ~(keystone_admin)]$ system host-upgrade controller-0
.. note:: .. note::
Controller-0 must pxe-boot from the management network and not from
any pxe-boot server. Also, ensure that the |NIC| sequence is correct. controller-0 must pxe-boot over the management network and its load
must be served from controller-1, and not from any external
pxe-boot server attached to the |OAM| network. To ensure this,
check that the network boot list/order of BIOS |NIC| is correct.
#. Unlock controller-0. #. Unlock controller-0.