starlingx/docs
Code Issues Proposed changes

the rook-ceph uninstall procedure doesn't seem correct (dsr10)

Browse Source 
Change-Id: I6dc8e987101b402dea7502e3ef0221092efc76cf
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
Ngairangbam Mili 2025-01-17 04:25:46 +00:00
parent 2b8613d3b0
commit 49f242107e
1 changed files with 22 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

64
doc/source/storage/kubernetes/uninstall-rook-ceph-cbb046746782.rst
View File

@ -26,7 +26,7 @@ environment configurations to prevent an automatic reinstall.
rookstatus=$(system application-list | grep rook-ceph | awk '{print $10}')
echo $rookstatus
if [[ "$rookstatus" == "uploaded" ]]; then
system application-delete rook-ceph --force
system application-delete rook-ceph
break
fi
echo "Retry #" $retry_count
@ -55,61 +55,41 @@ environment configurations to prevent an automatic reinstall.
~(keystone_admin)$ system host-stor-delete <uuid>
#. Remove the storage backend ceph-rook.
.. code-block:: none
~(keystone_admin)$ system storage-backend-delete ceph-rook-store --force
#. Remove ``host-fs``.
#. Check ``host-fs`` status.
#. Unlock the host.
.. code-block:: none
~(keystone_admin)$ system host-fs-list <hostname>
~(keystone_admin)$ system host-unlock <hostname>
#. To remove a ``host-fs``, the filesystem needs to be in Ready state.
To release an In-Use host-fs, remove all functions from it and
reapply the application:
#. (|AIO-DX| Only) Remove ``controllerfs``.
.. code-block:: none
~(keystone_admin)$ system host-fs-modify <hostname> ceph --functions=
~(keystone_admin)$ system appliction-apply rook-ceph
#. When the ``host-fs`` is in Ready state, remove the ``host-fs``:
.. code-block:: none
~(keystone_admin)$ system host-fs-delete <hostname> ceph
#. (|AIO-DX| Only) Remove ``controller-fs``.
#. Check ``controller-fs`` status.
.. code-block:: none
~(keystone_admin)$ system controller-fs-list
#. To remove a ``controller-fs``, the standby controller must be
locked and the ``controller-fs`` needs to be in Ready state.
#. To remove a ``controllerfs``, the standby controller must be
locked and the ``controllerfs`` needs to be in Ready state.
.. code-block:: none
~(keystone_admin)$ system host-lock <hostname>
#. To release an In-Use ``controller-fs``, remove all functions from it
and reapply the application.
#. Remove the ``controllerfs``.
.. code-block:: none
~(keystone_admin)$ system controllerfs-modify ceph-float --functions=
~(keystone_admin)$ system appliction-apply rook-ceph
~(keystone_admin)$ system controllerfs-delete ceph-float
#. When the ``controller-fs`` is in Ready state, remove the
``host-fs``.
#. Unlock the standby controller.
.. code-block:: none
~(keystone_admin)$ system controller-fs-delete ceph-float
~(keystone_admin)$ system host-unlock <hostname>
#. Remove the ``host-fs``.
.. code-block:: none
~(keystone_admin)$ system host-fs-delete <hostname> ceph
#. Remove the storage backend ceph-rook.
.. code-block:: none
~(keystone_admin)$ system storage-backend-delete ceph-rook-store --force