Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This document helps you ensure that all the components have been deployed successfully and they are up and running. The following sections discuss the checklist items that you need to verify after the deployment.

Verifying the RKE2 and Rancher deployment

  1. Verify if you are able to log in to the Rancher UI using the username and password you configured at the time of deployment.

  2. In the Rancher UI, validate if the Rancher cluster is listed in Clusters table with the name local at the home page.

  3. Verify if all the attached nodes to the cluster are up and running by following the steps given below.

    1. In the Rancher UI, click the menu icon at the top left corner, and then click Local.

    2. Click Nodes.

    3. Verify if all the nodes are in Active state and the roles assigned to each of them is set to Control Plane, Etcd.

  4. Check the status of the Rancher pods by following the steps given below.

    1. In the Rancher UI, click the menu icon at the top left corner, and then click Local.

    2. Go to Workload > Pods.

    3. In the Namespaces dropdown menu, select cattle-system.
      This lists all the pods in the cattle-system namespace.

    4. Validate if all the listed pods are in Running state.

...

  1. Validate if the Adeptia Connect helm is deployed by following the steps given below.

    1. Log in to the Rancher UI.

    2. Click the menu icon at the top left corner, and then click Local.

    3. Go to Apps > Installed Apps.

    4. In the Installed Apps, verify if the chart entry for adeptia-connect is in Deployed state.

  2. Check the status of the deployed pods of adeptia-connect by following the steps given below.

    1. Log in to the Rancher UI.

    2. Anchor
      aThroughc
      aThroughc
      Click the menu icon at the top left corner, and then click Local.

    3. Go to Workload > Pods.

    4. In the Namespaces dropdown menu, select the namespace to which you have deployed the Adeptia Connect application.

    5. Validate if all the listed pods are in Running state.

  3. Check the logs to see the status of the pods by following the steps given below.

    1. Follow the steps from a through d.

    2. Click the more options icon against the pod whose status you want to view, and then click View Logs.

    3. Search for “Microservice started successfully” to validate if the pod was started successfully.
      The screenshot given below is an example that shows the status of the Runtime pod.

      Note: The status of runtime deployment manager and rabbitmq pods could not be viewed in their respective logs.

  4. Follow the steps given below to check the status of the shared Runtime pod.

    1. Follow the steps from a through d.

    2. Verify if the pod for ac-runtime microservice is present and is in Running state.

  5. Verify if you are able to log in to the Adeptia Connect application.

  6. Verify if the shared NFS volumes are attached with required pods by following the steps given below.

    1. Log in to the Rancher UI.

    2. Click the menu icon at the top left corner, and then click Local.

    3. Go to Workload > Deployments.

    4. In the Namespaces dropdown menu, select the namespace to which you have deployed the Adeptia Connect application.

    5. Click the deployment (link in the name column) for which you want to check the mounted volumes.

    6. Select Config at the top-right corner.

    7. Click Storage.
      A list of all the volumes that are mounted to the pods is displayed.

    8. Follow the steps given below to check if the shared NFS volumes are attached to following pods:

      1. runtime

      2. event

      3. archival and cleanup

      4. portal

      5. webrunner

      6. listener

...

  1. Follow the steps given below to check if the user Id 1000 is assigned to the system user or the user who has installed the Adeptia Connect Rancher package on cluster nodes.

    1. Log in to the Jumpbox.

    2. Access the cluster node (VM) by running the following command.

      Code Block
      ssh <nodename/IP>
    3. View the passwd file by running the following command and verify if user Id 1000 is assigned to the user who has installed the Adeptia Connect Rancher package on cluster nodes.

      Code Block
      sudo cat /etc/passwd

      The screenshot given below is an example that shows user Id 1000 assigned to the logged in user.
      The screenshot given below is an example that shows user Id 1000 assigned to the ec2-user.

Note

If the user Id 1000 is being used by another user, refer to this document to swap the user Id.

...

  1. Check if the user with assigned user Id 1000 is being used for running the Adeptia Connect Rancher processes on the cluster nodes by following the steps given below.

    1. Log in to the Jumpbox.

    2. Access the cluster node (VM) by running the following command.

      Code Block
      ssh <nodename/IP>
    3. Run the following command to check if the user ID “1000“ is being used for running the Rancher processes.

      Code Block
      sudo ps aux | grep <user>

      This displays all the Rancher processes.

    4. Verify if all the Identify the processes displayed running as user ID “1000” in the above command result. Refer to the below screenshot.

      Image Removed

...

    1. the user with user Id 1000, for example ec2-user as shown in the following screenshot, is being used for running the Adeptia Connect Rancher processes.
      Note: Only a user with user Id 1000 or a root user must be used for running the rancher processes.

      Image Added