Installing with Cloud Lifecycle Manager
- Installation Overview
- I Pre-Installation
- II Cloud Installation
- 7 Overview
- 8 Preparing for Stand-Alone Deployment
- 9 Installing with the Install UI
- 10 Using Git for Configuration Management
- 11 Installing a Stand-Alone Cloud Lifecycle Manager
- 12 Installing Mid-scale and Entry-scale KVM
- 13 DNS Service Installation Overview
- 14 Magnum Overview
- 15 Installing ESX Computes and OVSvAPP
- 16 Integrating NSX for vSphere
- 17 Installing Baremetal (Ironic)
- 18 Installation for HPE Helion OpenStack Entry-scale Cloud with Swift Only
- 19 Installing SLES Compute
- 20 Installing Manila and Creating Manila Shares
- 21 Installing SUSE CaaS Platform Heat Templates
- 22 Installing RHEL Compute
- 23 Integrations
- 24 Troubleshooting the Installation
- 25 Troubleshooting the ESX
- III Post-Installation
- 34 Support
25 Troubleshooting the ESX
This section contains troubleshooting tasks for your HPE Helion OpenStack® 8 for ESX.
25.1 Issue: ardana-service.service is not running #
If you perform any maintenance work or reboot the Cloud Lifecycle Manager/deployer node, make sure to restart the Cloud Lifecycle Manager API service for standalone deployer node and shared Cloud Lifecycle Manager/controller node based on your environment.
For standalone deployer node, execute ardana-start.yml
playbook to restart the Cloud Lifecycle Manager API service on the deployer node after a reboot.
For shared deployer/controller node, execute
ardana-start.yml playbook on all the controllers to
restart Cloud Lifecycle Manager API service.
For example:
cd ~/scratch/ansible/next/ardana/ansible ansible-playbook -i hosts/verb_hosts ardana-start.yml --limit HOST_NAME
Replace HOST_NAME with the host name of the Cloud Lifecycle Manager node or the Cloud Lifecycle Manager Node/Shared Controller.
25.2 Issue: ESX Cluster shows UNKNOWN in Operations Console #
In the Operations Console Alarms dashboard, if all the alarms for ESX cluster are
showing UNKNOWN then restart the openstack-monasca-agent running in
ESX compute proxy.
SSH to the respective compute proxy. You can find the hostname of the proxy from the dimensions list shown against the respective alarm.
Restart the
openstack-monasca-agentservice.sudo systemctl restart openstack-monasca-agent
25.3 Issue: Unable to view the VM console in Horizon UI #
By default the gdbserver firewall is disabled in ESXi host which results in a Handshake error when accessing the VM instance console in the Horizon UI.
Procedure to enable gdbserver
Login to vSphere Client.
Select the ESXi Host and click tab in the menu bar. You must perform the following actions on all the ESXi hosts in the compute clusters.
On the left hand side select Security Profile from the list of Software. Click Properties on the right hand side.
Firewall Properties box displays.
Select gdbserver checkbox and click OK.
