Open vChrisR opened 7 years ago
@vChrisR I went through it quickly. That is good work.
Would love one covering a redundant setup using 5 servers.
Then one on kubernetes, I am having huge headaches trying to boostrap the cluster.
I found a way to hack the installer with the fixes:
vmware-vdiskmanager
and guestmount
vmware-vdiskmanager
to type 0guestmount
lib64
symlink on lightwave and edit /etc/esxcloud/run.sh
on the controller and change the KEYSTORE_PASSWORD=photon-controller
vmware-vdiskmanager
So is 1.1.1 just broken or what? I'm unable to deploy against my 6.0u3 cluster but can deploy 1.2 against a 6.5 cluster with no issues.
I just get endless logs like this on my hosts
[2017-05-18 06:12:44,964] [40773:40770:Thread-1] [TNonblockingServer.py:handle:318] thrift.server.TNonblockingServer: error while accepting ERROR [2017-05-18 06:12:44,964] [40773:40770:Thread-1] [TNonblockingServer.py:handle:318] thrift.server.TNonblockingServer: Traceback (most recent call last): ERROR [2017-05-18 06:12:44,964] [40773:40770:Thread-1] [TNonblockingServer.py:handle:318] thrift.server.TNonblockingServer: File "/var/lib/jenkins/workspace/photon-controller-python/agent/create_vib.yFQcg/vib/payloads/agent/opt/vmwar e/photon/controller/2.7/site-packages/thrift/server/TNonblockingServer.py", line 314, in handle ERROR [2017-05-18 06:12:44,965] [40773:40770:Thread-1] [TNonblockingServer.py:handle:318] thrift.server.TNonblockingServer: AttributeError: 'NoneType' object has no attribute 'handle' ERROR [2017-05-18 06:14:16,863] [40773:40770:Thread-1] [TNonblockingServer.py:handle:318] thrift.server.TNonblockingServer: error while accepting ERROR [2017-05-18 06:14:16,863] [40773:40770:Thread-1] [TNonblockingServer.py:handle:318] thrift.server.TNonblockingServer: Traceback (most recent call last): ERROR [2017-05-18 06:14:16,864] [40773:40770:Thread-1] [TNonblockingServer.py:handle:318] thrift.server.TNonblockingServer: File "/var/lib/jenkins/workspace/photon-controller-python/agent/create_vib.yFQcg/vib/payloads/agent/opt/vmwar e/photon/controller/2.7/site-packages/thrift/server/TNonblockingServer.py", line 314, in handle
Yep, Downgrading to 4600944 fixed it for me...
@LIV2 1.1.1 works perfectly. But you need ESXi 6.5.
@pompomJuice Well the release notes for 1.1.1 state the following:
VMware Photon Platform 1.1.1 Release Notes Supported Platforms • VMware ESXi 6.0.0 Patch 201611001 (ESXi600-201611001), which you can find by searching for patches for ESXi 6.0.0 on My VMware Product Patches at https://my.vmware.com/group/vmware/patch. • Lightwave version 1.0.3. • NSX-T version 1.1. • vSAN for Photon Platform version 1.1. • ESXi 6.5 is unsupported at this time.
Indeed it does work only on 6.0 Patch 201611001 from my testing, it does not work at all on newer versions it just hangs joining the ESXI host to the cluster.
It's pretty disappointing as I'm evaluating this for a production system, the Documentation claims that this software is production ready but if you can't even run up-to-date ESXI with all the latest security patches I fail to see how this is the case.
@LIV2 My bad, 1.2.0 needs ESXi 6.5 not 1.1.1.
Photon platform seems to install fine. vib installation on the ESXi host works OK, but when the agent starts just logs errors. This is the log:
The last three log entries are repeated a lot of time.
What stands out in the log are the two CRITICALs. Somehow the agent is trying to use 'datastore1' as the image store. But 'local02' was configured in the photon yaml.
Below is my photon yaml:
and here is the photon-installer.log:
2017-04-01 12:53:27 DEBUG headers:124 - http-outgoing-17 << HTTP/1.1 200 OK 2017-04-01 12:53:27 DEBUG headers:127 - http-outgoing-17 << Server: Apache-Coyote/1.1 2017-04-01 12:53:27 DEBUG headers:127 - http-outgoing-17 << Cache-Control: no-store 2017-04-01 12:53:27 DEBUG headers:127 - http-outgoing-17 << Pragma: no-cache 2017-04-01 12:53:27 DEBUG headers:127 - http-outgoing-17 << Content-Type: application/json;charset=UTF-8 2017-04-01 12:53:27 DEBUG headers:127 - http-outgoing-17 << Content-Length: 3800 2017-04-01 12:53:27 DEBUG headers:127 - http-outgoing-17 << Date: Sat, 01 Apr 2017 12:53:27 GMT 2017-04-01 12:53:27 DEBUG MainClientExec:284 - Connection can be kept alive indefinitely 2017-04-01 12:53:27 DEBUG PoolingHttpClientConnectionManager:314 - Connection [id: 17][route: {s}->https://192.168.192.78:443] can be kept alive indefinitely 2017-04-01 12:53:27 DEBUG PoolingHttpClientConnectionManager:320 - Connection released: [id: 17][route: {s}->https://192.168.192.78:443][total kept alive: 1; route allocated: 1 of 2; total allocated: 1 of 20] 2017-04-01 12:53:27 DEBUG PoolingHttpClientConnectionManager:388 - Connection manager is shutting down 2017-04-01 12:53:27 DEBUG DefaultManagedHttpClientConnection:81 - http-outgoing-17: Close connection 2017-04-01 12:53:27 DEBUG PoolingHttpClientConnectionManager:394 - Connection manager shut down 2017-04-01 12:53:27 DEBUG ControllerInstaller:736 - https://192.168.192.77:9000/tasks/434a3171-178c-4e3c-a72a-b40b72394557 2017-04-01 12:53:28 DEBUG ControllerInstaller:736 - https://192.168.192.77:9000/tasks/434a3171-178c-4e3c-a72a-b40b72394557 2017-04-01 12:53:30 DEBUG ControllerInstaller:736 - https://192.168.192.77:9000/tasks/434a3171-178c-4e3c-a72a-b40b72394557 2017-04-01 12:53:31 DEBUG ControllerInstaller:736 - https://192.168.192.77:9000/tasks/434a3171-178c-4e3c-a72a-b40b72394557 2017-04-01 12:53:32 DEBUG PoolingHttpClientConnectionManager:388 - Connection manager is shutting down 2017-04-01 12:53:32 DEBUG PoolingHttpClientConnectionManager:394 - Connection manager shut down 2017-04-01 12:53:32 DEBUG ControllerInstaller:736 - https://192.168.192.77:9000/tasks/434a3171-178c-4e3c-a72a-b40b72394557 2017-04-01 12:53:33 DEBUG ControllerInstaller:736 - https://192.168.192.77:9000/tasks/434a3171-178c-4e3c-a72a-b40b72394557 2017-04-01 12:53:34 DEBUG ControllerInstaller:736 - https://192.168.192.77:9000/tasks/434a3171-178c-4e3c-a72a-b40b72394557 2017-04-01 12:53:35 DEBUG ControllerInstaller:736 - https://192.168.192.77:9000/tasks/434a3171-178c-4e3c-a72a-b40b72394557
The last lines are repeated a lot of times and then:2017-04-01 12:54:32 DEBUG ControllerInstaller:736 - https://192.168.192.77:9000/tasks/434a3171-178c-4e3c-a72a-b40b72394557 2017-04-01 12:54:33 ERROR ControllerInstaller:540 - Failed in provisioning host: vesxi60c01