All Posts

And here is the post &response for the RDE instance.  It got a 200 OK, but the urn of the item seems weird.. Instead of "urn:xxx:xxx" it shows like "urn%3Axxx%3Axxx"
I found that the cse process is running, but it seems waiting for the RDEs. And in the cse.log, only the following line is output "querying list of RDEs for processing"
thank you. you are right. I passed this step.
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 ... See more...
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    
Thanks for the reply. Unfortunately if I stop CSE service too early, maybe the task that trigger the issue will not be executed in the VM making the VM useless for troubleshooting. This future feat... See more...
Thanks for the reply. Unfortunately if I stop CSE service too early, maybe the task that trigger the issue will not be executed in the VM making the VM useless for troubleshooting. This future feature is really a must have for the GA,
Just a quick reminder. If you need to stop the CSE service vApp, please use Power On, force recustomization to restart the VM inside CSE service vApp. OtherWise, the vcd-ke server wouldn't restart. (... See more...
Just a quick reminder. If you need to stop the CSE service vApp, please use Power On, force recustomization to restart the VM inside CSE service vApp. OtherWise, the vcd-ke server wouldn't restart. (Please feel free to use systemctl status cse to check whether CSE server is alive).
>I am not sure why its trying to find a vApp with the name tkgcl01_ephemeral_vapp. We have a common function that is meant for user intitiated Delete Cluster operation as wells as for clean-up on ... See more...
>I am not sure why its trying to find a vApp with the name tkgcl01_ephemeral_vapp. We have a common function that is meant for user intitiated Delete Cluster operation as wells as for clean-up on error while creating the cluster. As you mentioned, there is no tkgcl01_ephemeral_vapp created in your use case. It is just a info level message that can be ignored.
At this point, you may want to stop the CSE service to get to the ephemeral vm before it is getting deleted and recreated as part of retry. If you are able to successfully login to ephemeral vm, p... See more...
At this point, you may want to stop the CSE service to get to the ephemeral vm before it is getting deleted and recreated as part of retry. If you are able to successfully login to ephemeral vm, please do the following. 1. export KUBECONFIG=/.kube/config 2. kubectl get pods -A for pods that are stuck or having issues 3. kubectl logs for individual log In addition if you can access: https://github.com/vmware/cloud-provider-for-cloud-director/blob/main/scripts/generate-k8s-log-bundle.sh Please run the above script after setting KUBECONFIG on ephemeral vm and upload the log bundle. We can take a look for further investigation.    
We have this feature in the upcoming GA release that prevents the deletion of EPHEMERAL_TEMP_VM But as a workaround, you may either want to stop the CSE service where the OVA is installed. Powering ... See more...
We have this feature in the upcoming GA release that prevents the deletion of EPHEMERAL_TEMP_VM But as a workaround, you may either want to stop the CSE service where the OVA is installed. Powering off the OVA vm also brings down the service. Either of them is required to stop EPHEMERAL_TEMP_VM getting deleted.  But, the above step should be done before the timeout happens. If you get to notice that it is looping on any existing phase. But timing this (stopping the service) requires little judgement on how fast the cluster creation happen.
Tried with 10.3.3.19780585, same thing happened, which lead me to check logs again and I found "Missing right to use ExtraConfig guestinfo.userdata.encoding." Then I figured out that I needed "Pre... See more...
Tried with 10.3.3.19780585, same thing happened, which lead me to check logs again and I found "Missing right to use ExtraConfig guestinfo.userdata.encoding." Then I figured out that I needed "Preserve All ExtraConfig Elements During OVF Import and Export" in my "Default rights bundle", not (only) in "Organization admin" role.   EPHEMERAL_TEMP_VM now boots (but cluster is in state Reconciling, so I'm checking it out).
Will try with VCD 10.3.3, didn't check requirements before trying
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... See more...
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 C... See more...
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 kno... See more...
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?
hello, Not sure i posted a message with logs which is not visible. Its getting marked as spam. I checked logs using command journalctl -u cse and could see [ENF] Entity not found message. I am not ... See more...
hello, Not sure i posted a message with logs which is not visible. Its getting marked as spam. I checked logs using command journalctl -u cse and could see [ENF] Entity not found message. I am not sure why its trying to find a vApp with the name tkgcl01_ephemeral_vapp. I dont see any vapp with this name. vApp name is tkgcl01 which is the name i used while creating tkg cluster 
hello, i checked log file cloud-final.err and last command i could see is provisioning pending. Log file attached for reference ++ kubectl get machines -n tkgcl01-ns -o 'jsonpath={.items[*].status.... See more...
hello, i checked log file cloud-final.err and last command i could see is provisioning pending. Log file attached for reference ++ kubectl get machines -n tkgcl01-ns -o 'jsonpath={.items[*].status.phase}' + [[ Provisioning Pending =~ ^(Running )*Running$ ]] + sleep 20
After logged into EPHEMERAL_TEMP_VM, you can see detailed log messages are recorded in: /var/log/cloud-final.err. This file records list of commands and statuses in the order of execution. Also, you... See more...
After logged into EPHEMERAL_TEMP_VM, you can see detailed log messages are recorded in: /var/log/cloud-final.err. This file records list of commands and statuses in the order of execution. Also, you can find out which command is in infinite loop or any error happened during the cluster creation. Currently, if cluster creation fails for any reason, the error handler in CSE removes the ephemeral vm and stamps the RDE in error state. After 10 minutes, it gets picked-up again to get a retry on cluster creation.   Your feedback on service command-line arguments with exposed password is appreciated. We will do the necessary updates in the upcoming release.
Hi, The VCD-KE config definedEntity does not automatically complete by itself actually. After successful POST request to /cloudapi/1.0.0/entityTypes/urn:vcloud:type:vmware:VCDKEConfig:0.5.0, the new... See more...
Hi, The VCD-KE config definedEntity does not automatically complete by itself actually. After successful POST request to /cloudapi/1.0.0/entityTypes/urn:vcloud:type:vmware:VCDKEConfig:0.5.0, the newly created definedEntity of VCD-KE config will remain at 1% until you resolve it manually. In order to bring it to completion, you must resolve it. To perform resolve operation: Similar to what vBahubali01 said and in their image, 1. You must grab the ID of your definedEntity, it is the long ID where vBahubali01 drew a red box around in the previous reply. From your screenshot, yours start with: urn:vcloud:entity:vmware:VCDKEConfig:0cf0ffc8-... 2. After you have the ID, you will need to make a POST request using administrator to: https://{{vcd-site}}/cloudapi/1.0.0/entities/<long id from step 1>/resolve   - Ensure urn:vcloud:entity:vmware:VCDKEConfig: is included as part of your ID.    - Example endpoint for POST using administrator credentials:       https://{{vcd-site}}/cloudapi/1.0.0/entities/urn:vcloud:entity:vmware:VCDKEConfig:0cf0ffc8-.../resolve   3. After successfully completing step 2, you should no longer see 1% but rather a success in VMware Cloud Director. Let us know if this works out for you. Thanks!
Login to CSE OVA machine where the service is running. Execute the following command to see the log statements journalctl -u cse  
Just to give feedback regarding cluster deployment. I am experiencing below behavior. EPHEMERAL_TEMP_VM is created and in the events i could see below events. Last event name is InfraVappAvailable. ... See more...
Just to give feedback regarding cluster deployment. I am experiencing below behavior. EPHEMERAL_TEMP_VM is created and in the events i could see below events. Last event name is InfraVappAvailable. After some time EPHEMERAL_TEMP_VM got deleted on its own  Again a new EPHEMERAL_TEMP_VM got deployed without any action from my side I could see Virtual Service got created on edge gateway but was down I could pool also got created without any member I logged into EPHEMERAL_TEMP_VM and could see all needed files were downloaded as per bootstrap.sh script which  confirm my connectivity with internet. I verified my cloud director portal endpoint is also getting resolved.  There are no logs under the path /var/log/vcd-ke/customization on EPHEMERAL_TEMP_VM to provide any clue regarding deployment not progressing. Cloud director version 10.3.3.