All Posts

Hi, The cluster creation never completed and the cluster never ready. Then vapp and vm are removed and recreated later in loop. Result of a "cat /var/log/cloud-final.err" Note: I am not sure if we can login as root with ssh, so screenshot is from the console All pods seems ok. And from the journal i don't see relevant error But few errors earlier of type "412 Precondition Failed"   Seems the latest error in event then is associated to the event of deleting vapp and load balancer     Any suggestion of what should be the next step in troubleshooting?  

Hi, Would it be possible to add pre-requisite health check in the gui? (similar to Distributed Switch health check) It would avoid trying to fix a deployment not working. There could be multiple level of health check: Infrastructure: Confirm that all objects have been properly created in the API. (Maybe the logged in user would not have the right to see such settings so this test should run under a different account) User: Confirm the logged in user has all prerequisites permissions. Then the user select in which organization network to simulate a deployment: Confirm network has an ip pool configured with enough free IP address Confirm DNS are configured. Confirm the EDGE is properly configured with access to a load balancer, Confirm Enough external IP addresse available Confirm enough VIP available in the edge. Confirm enough capacity (CPU/Memory/Storage) Confirm sizing policies created. Then deploy a test VM in this network (similar to how the ephemeral VM would be created) Confirm that the test VM has access to DNS server That the VM has access to all URLS needed. (List should be provided in documentation, not all environment can provide full internet access) That the VM has access to Cloud Director (and eventually if certificates are trusted) List non-exhaustive If all test results passed/failed are visible in the gui, it would be easy to pinpoint wrong settings and fix them before even trying to deploy a cluster. Regards,

I finished all workloads described in the provider workflow docs. When trying to deploy the a tkg cluster via GUI, I found the error on the TKG ova template page. The template catalog is published and shared with the user tenant. I also tried reboot cse, but still not work    

Issue: The vapp is created, then the VM "EPHEMERAL_TEMP_VM". Later the VAPP and VM are removed and the cycle is then repeated. I would like to analyse all logs in the VM. But when it is deleted i may have missed the latest. Is there an equivalent to the setting "rollback:false" in the legacy CSE?

This is my first try to provision cse.next k8s cluster, and it fails while creating EPHEMERAL_TEMP_VM with ScriptInitError and later with EphemeralVMError, and It doesn't even start.   VMware Cloud Director version: 10.3.2.19473806   I have attached whole cse log from journalctl -lu cse  

Hi, So far I have not managed to create a cluster. Creating CAPVCD cluster task stuck at 1%. I am trying to troubleshoot but it is difficult to identify what is wrong from the task/logs without knowing how it is supposed to look like. Would it be possible to provide the following information from a working environment? First step, deploy new clusters (management and workload) from the the new beta plugin and when they are ready: Export all related cloud director tasks Export all related cloud director event. And provide a copy of logs: cse.log journalctl -axel -u cse Such information would be very helpful for troubleshooting. Would it be also possible to provide step by step chart of what is happening when creating a new cluster? Addition: Would it be possible to add the list of all URL that need to be allowed from the vm/nodes?