A: Verify RKE2 and Rancher is deployed successfully
Login to rancher UI and validate rancher cluster is listed in cluster table of rancher.
...
Open the browser enter rancher domain.
...
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
Verify if you are able to log in to the Rancher UI using the username and password you configured at the time of deployment
)We should get successfully login to rancher UI and cluster name local should be shown in cluster table at home page, as shown in below image.
In the Rancher UI, validate if the Rancher cluster is listed in Clusters table with the name local at the home page.
Verify if all the attached nodes to the cluster are up and readyrunning by following the steps given below.
From rancher In the Rancher UI click on more option button at , click the menu icon at the top left corner > Local > Nodes, and then click Local.
Click Nodes.
Verify if all the nodes are in ready Active state and assigned roles are the roles assigned to each of them is set to Control Plane, Etcd.
Verify Check the status of rancher pods
From rancher UI click on more option button at top left corner > Local > Workloads > pods
From the namespace dropdown (at top aligned to centre) In the Rancher UI, click the menu icon at the top left corner, and then click Local.
Go to Workload > Pods.
In the Namespaces dropdown menu, select cattle-system.
All the listed pod in This lists all the pods in the cattle-system namespace should be in running .Validate if all the listed pods are in Running state.
Verify all .
the Rancher pods by following the steps given below.
B: Verify Adeptia-connect is deployed successfully
Validate helm deployment status for adeptia-connect
- From rancher UI click on more option button at top left corner > Local > Apps > Installed Apps
Verifying the deployment of Adeptia Connect application
Validate if the Adeptia Connect helm is deployed by following the steps given below.
Log in to the Rancher UI.
Click the menu icon at the top left corner, and then click Local.
Go to Apps > Installed Apps.
In the Installed Apps, verify if the chart entry for adeptia-connect application should be shown with status deployed is in Deployed state.
Verify Check the status of the deployed pods for of adeptia-connect
From rancher UI click on more option button at top left corner > Local > Workloads > pods
From the namespace dropdown (at top aligned at entre) select adeptia-connect namespace (Select namespace in which adeptia-connect application is deployed).
All the listed pods should be in running status.
Verify the logs of each pods
From rancher UI click on more option button at top left corner > Local > Workloads > pods
From the namespace dropdown (at top aligned at entre) select adeptia-connect namespace (Select namespace in which adeptia-connect application is deployed).
Click on more options icon of a pod and select view logs.
Search for message “Microservice started successfully” in each pod logs except runtime deployment manager and rabbitmq pods.
Note: This screenshot is reference from runtime pod
Verify shared Runtime pod is launched and running
From rancher UI click on more option button at top left corner > Local > Workloads > pods
From the namespace dropdown (at top aligned at entre) select adeptia-connect namespace (Select namespace in which adeptia-connect application is deployed).
Pod
Log in to the Rancher UI.Anchor aThroughc aThroughc Click the menu icon at the top left corner, and then click Local.
Go to Workload > Pods.
In the Namespaces dropdown menu, select the namespace to which you have deployed the Adeptia Connect application.
Validate if all the listed pods are in Running state.
Check the logs to see the status of the pods by following the steps given below.
Follow the steps from a through d.
Click the more options icon against the pod whose status you want to view, and then click View Logs.
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.
Follow the steps given below to check the status of the shared Runtime pod.
VerifyFollow the steps from a through d.
Verify if the pod for ac-runtime microservice is present and is in running Running state.
Access the adeptia-connect application UI and login to the application.
Open the browser and enter adeptia-connect domain.
Enter the username & password
User should successfully navigate to home page after successful sign in operation.
Verify if you are able to log in to the Adeptia Connect application.
Verify if the shared NFS volumes are attached with required pods
From rancher UI click on more option button at top left corner > Local > Workloadsby following the steps given below.
Log in to the Rancher UI.
Click the menu icon at the top left corner, and then click Local.
Go to Workload > Deployments.
From In the namespace dropdown (at top aligned at centre) select adeptia-connect namespace (Select namespace in which adeptia-connect application is deployed).
Click on name link of required deployment(On which we need to verify the mounted volumes)
Click on config
Click on storage > It will list down all the mounted volumes to the pods
Verify Namespaces dropdown menu, select the namespace to which you have deployed the Adeptia Connect application.
Click the deployment (link in the name column) for which you want to check the mounted volumes.
Select Config at the top-right corner.
Click Storage.
A list of all the volumes that are mounted to the pods is displayed.Follow the steps given below to check if the shared NFS volumes are attached to below following pods:
Runtimeruntime
Eventevent
Archival archival and cleanup
Portalportal
Webrunnerwebrunner
Listener
by following the steps given below.
...
listener
Verifying the deployment of EFK
Check the status of pods running for EFK service
From rancher UI click on more option button at top left corner > Local > Workloads > pods
From the namespace dropdown (at top aligned at entre) select logging namespace.
All pods should be in running state in logging namespace
User is able to login to Kibana UI.
Open the browser and enter EFK access domain.
Login using elastic user(password is Log in to the Rancher UI.
Click the menu icon at the top left corner, and then click Local.
Go to Workload > pods.
In the Namespaces dropdown menu, select logging.
Verify if all the pods are in Running state.
Verify if you are able to log in to the Kibana UI using the username elastic and the password you configured at the time of deployment
)Index .
Verify if the index pattern for all microservices should be is listed in kibana UIKibana UI by following the steps given below.
Login Log in to kibana the Kibana UI.
Click on more option button the menu icon at top left corner > .
Click Discover.
Click on kibana the Kibana index pattern dropdown.
Dropdown should contain Verify if the list of all the microservices deployed in adeptia-connect namespace is displayed.
the EFK services pods' by following the steps given below.
...
Verifying the user Id (UID)
...
Check the allocation of UID “1000“ 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.
Login into Log in to the Jumpbox and access .
Access the cluster node (VM) using by running the below following command.
Code Block ssh <nodename/IP>
View the passwd file using by running the below following command and verify the user associated with UID “1000“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
Refer to the below screenshot
...
The screenshot given below is an example that shows user Id 1000 is assigned to the ec2-user.
Note |
---|
If the user Id 1000 is being used by another user, then refer to the guideline this documentto swap the UIDuser Id. |
Check if the user with assigned user Id 1000 is being used for running the Adeptia Connect Rancher processes running under user ID “1000“ on the cluster nodes by following the steps given below.
Login into Log in to the Jumpbox and access .
Access the cluster node (VM) using by running the below following command.
Code Block ssh <nodename/IP>
Check the Rancher processes running as Run the following command to check if the user ID “1000“ using the below commandis being used for running the Rancher processes.
Code Block sudo ps aux | grep <user>
Identify This displays all the processes displayed running as user ID “1000” in the above command result. Refer to the below screenshot.
...
Rancher processes.
Verify if 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.