We try to use cloud bursting with an Azure virtual machine. The credentials step working well on the Azure side. On the side of the bright cluster, we did the steps as below:
1- Check the prerequisite (done).
2- Provide our azure credentials (done).
3- Select region(westeurop).
4- Select software image (cm/images/default-image).
5- Select 2 cloud nodes (Ds1-V2).
6- Review the summary and deploy (done).
7- Deploy (done).
8- Now in Devices-> cloud nodes we have two machines and a cloud director. The problem is when we try to power on the cloud director it does not respond and give down status.
On the Azure side, the director machine gets status on and we found resource group contains one cloud directory.
We monitored the log files. the errors we have as below :
Mar 27 18:02:29 bright90 cmd[5996]: [ HTTPD ] Info: SSL error: SSL handshake failed, from: 192.168.15.254
Mar 27 18:02:29 bright90 cmd[5996]: [ HTTPD ] Info: SSL error: SSL handshake failed, from: 192.168.15.254
Mar 27 18:02:33 bright90 cmd[5996]: [ CONF ] Info: ConfigWriter, unable to read: /var/named/37.42.10.in-addr.arpa.southafricanorth.zone
Mar 27 18:08:55 bright90 cmd[5996]: [ CONF ] Info: Could not read: /etc/sysconfig/serial-agetty.conf for inserting data
Mar 27 18:30:56 bright90 cmd[5996]: [ CONF ] Info: Could not read: /etc/sysconfig/serial-agetty.conf for inserting data
Mar 27 18:30:56 bright90 cmd[5996]: [ CONF ] Info: Could not read: /etc/sysconfig/serial-agetty.conf for inserting data
Mar 27 18:30:56 bright90 cmd[5996]: [ CONF ] Info: Update network config #nics: 4, bootif:
Mar 27 18:30:56 bright90 cmd[5996]: [ CONF ] Info: Did not update /etc/sysconfig/network-scripts/ifcfg-eno1
Mar 27 18:30:56 bright90 cmd[5996]: [ CONF ] Info: Did not update /etc/sysconfig/network-scripts/ifcfg-eno2
Mar 27 18:30:56 bright90 cmd[5996]: [ CONF ] Info: io::getHostname() returned 'bright90'; my hostname from DB is 'bright90'
Mar 27 18:30:56 bright90 cmd[5996]: [ CONF ] Info: Could not read: /etc/sysconfig/nfs for inserting data