4.4 Updating (Patching) CIS Configured Server

4.4.1 Applying OES 24.3 Update

After applying the OES 24.3 update, ensure to complete the following steps:

  1. (Conditional) If the CIS is configured on the NSS media volume, then copy the newly updated files from the cis_local location to the media path (/media/nss/CISVOL).

    sh /opt/novell/cis/bin/copy_upgraded_files.sh

  2. Restart the CIS services.

    systemctl restart oes-cis-server.target

4.4.2 Applying OES 24.2 Update

OpenText recommends moving to K3s as support for Docker Swarm will discontinue in OES 24.4.

After applying the OES 24.2 update, perform the following steps to move the infrastructure servers from Docker Swarm to the K3s cluster:

  1. Login to the server as a root user.

  2. Verify if the CIS service on the CIS core server is in a Healthy state.

  3. Verify if all the available CIS infrastructure servers (3/5/7) are Active.

    docker node ls

  4. Run the following command on the CIS core server to move the infrastructure servers from Docker Swarm to the K3s cluster:

    cis_ext_service.sh upgradeinfra

  5. Verify if all the available CIS infrastructure servers (3/5/7) are moved to K3s.

    kubectl get nodes

    kubectl get pods

    You must repeat Step 4 if the CIS infrastructure servers are not moved to K3s.

  6. (Conditional) If CIS infrastructure pods are not running then stop and start the services.

    1. Stop the infrastructure services on any one of the nodes.

      sh cis_ext_service.sh stop

    2. Verify the infrastructure service status should not list any pods.

      sh cis_ext_service.sh status

      NOTE:If there are any pods shown in the status, wait until they have all stopped running.

    3. Start the infrastructure service on any one of the node.

      sh cis_ext_service.sh start