Rebooting Aria Orchestrator Standalone Appliances

Products

• VCF Automation

Issue/Introduction

Instructions for rebooting the Aria Orchestrator Standalone Appliances

Environment

Aria Orchestrator Standalone 8.x

Cause

 

 

Resolution

1. Connect to the console of one node in the cluster or SSH to one node
   
   
2. Stop the services (this will stop services on all nodes in the cluster) by running:
   /opt/scripts/svc-stop.sh
sleep 120
/opt/scripts/deploy.sh --onlyClean
   
   
3. After the Deploy script finishes, and the command prompt reappears, confirm that they have shut down by running:
   kubectl -n prelude get pods
   The output will show "No resources found in prelude namespace."
   
   
4. Reboot the Server via vCenter or by running reboot at the command prompt.
   
   
5. After the reboot, verify that the kube-system pods are running. In vCenter, when the blue splash screen shows the kube-system should be running.
   This can be validated via command line after reconnecting to SSH or by logging in via the console by running:
   kubectl get pods --all-namespaces
        Note: All pods should show as Running or Completed
   
   
6. Start the Services by running:
   /opt/scripts/deploy.sh
When it is finished it will report "Prelude has been deployed successfully"
   
   
7. Login into the UI at https://<Your_Orchestrator_FQDN>/orchestration-ui/

Additional Information

For restarting Aria Automation with Embedded Orchestrator, please follow the steps in Starting and stopping VMware Aria Automation