Closed Koch closed 7 years ago
can you post the complete config yaml file you used.
Of course!
compute:
hypervisors:
host1:
hostname: host1
ipaddress: 10.243.89.11
dns: 10.1.1.1
credential:
username: root
password: ServerPw42!
lightwave:
domain: "pht.local"
credential:
username: "administrator"
password: "AdminPw42!!"
controllers:
phtlw-001:
site: u93b
appliance:
hostref: host1
datastore: "ds1"
credential:
username: root
password: ServerPw42!
network-config:
network: "NAT=VM Network"
type: "static"
hostname: phtlw-001.pht.local
ipaddress: 10.243.89.21
dns: 10.1.1.1
ntp: 10.1.6.1
netmask: 255.255.255.0
gateway: 10.243.89.1
photon:
imagestore:
img-store-1:
hostref: "host1"
datastore: "ds1"
enableimagestoreforvms: "true"
cloud:
hostref1: "host1"
administrator-group: "pht.local\\Administrators"
controllers:
"phtctl-001":
appliance:
hostref: "host1"
datastore: "ds1"
credential:
username: "root"
password: "ServerPw42!"
network-config:
network: "NAT=VM Network"
type: "static"
hostname: phtctl-001.pht.local
ipaddress: 10.243.89.22
netmask: 255.255.255.0
dns: 10.243.89.21
ntp: 10.1.1.1
gateway: 10.243.89.1
loadBalancer:
phtlb-001:
appliance:
hostref: host1
datastore: "ds1"
credential:
username: "root"
password: "ServerPw42!"
network-config:
network: "NAT=VM Network"
type: "static"
hostname: phtlb-001.pht.local
ipaddress: 10.243.89.23
netmask: 255.255.255.0
dns: 10.243.89.21
ntp: 10.1.1.1
gateway: 10.243.89.1
dns of your host is set to your ntp server IP. It should be the IP of the LW VM 10.243.89.21
It was actually set to that to sanitize, but looking at my non-sanitized file it was set to something else either way. I'll try that out now, thanks!
That did it, many thanks! :)
Deploying freshly with the latest OVA for the installer. Run with the following config for controllers:
However, when it gets to the provisioning host stage:
Installer logs say the following:
I logged onto the Photon Controller VM and ran ip addr, that was fine. I'm unable to open a connection on port 9000, so I gave that up. However, upon running "netstat -tulpn", Java is bound to ::9000 rather than IPv4 (however I don't believe that matters in Linux either way(?)). Once I ruled that out (I changed the config whilst the VIBS were being installed and rebooted the controller to make it bind to 0.0.0.0:9000), I checked the logs of the controller.
Controller is complaining about SSL Engine errors, I can't paste the logs out as the console is being screwy and SSH isn't working, but it's a "General SSLEngine" error from Java.
Anyone seen this before, or any tips? I've tried redeploying on a freshly installed ESX several times now - even reinstalled the ESX first thinking that was the error. Note: I can reach the VM from both the host and other VMs on the network, as well as my management server.
Thanks!