All Posts

vBahubali01 · ‎08-01-2022

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....

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

sakthi2019 · ‎08-01-2022

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...

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.

lzichong · ‎08-01-2022

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...

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!

sakthi2019 · ‎08-01-2022

Login to CSE OVA machine where the service is running. Execute the following command to see the log statements journalctl -u cse

vBahubali01 · ‎07-29-2022

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. ...

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.

tolgaanit1979 · ‎07-29-2022

Hi, It's not creating in Step 2. you can see status in screenshot. It has been waiting for 1 day to be completed

vBahubali01 · ‎07-29-2022

hello, Sorry if i was not clear. Step 1: When below API call is triggered a task starts in cloud director with 1% progress like you have currently POST https://{{vcd}}/cloudapi/1.0.0/entityTypes/...

hello, Sorry if i was not clear. Step 1: When below API call is triggered a task starts in cloud director with 1% progress like you have currently POST https://{{vcd}}/cloudapi/1.0.0/entityTypes/urn:vcloud:type:vmware:VCDKEConfig:0.5.0 Step 2: In my setup i noted urn id from task in cloud director as shown below in the screenshot After noting this id i executed below API call as provided in Provider Workflow section: POST https://{{vcd}}/cloudapi/1.0.0/entities/<id>/resolve I replaced id with urn id noted from cloud director task in above API call and executed POST. After this my task in cloud director which was at 1% got completed. POST https://cloud.lab.infra/cloudapi/1.0.0/entities/urn:vcloud:entity:vmware:VCDKEConfig:e4ac2d9f-767b-4e0f-a350-4bd06bf19b2d/resolve Hope this helps

vBahubali01 · ‎07-29-2022

hello, I made some progress with CSE OVA deployment on my management VLAN. Verified CSE Service status and its active. The first thing i noticed is that system admin service account password showing...

hello, I made some progress with CSE OVA deployment on my management VLAN. Verified CSE Service status and its active. The first thing i noticed is that system admin service account password showing up in service status which is not good ● cse.service - Cloud Director Container Service Extension Loaded: loaded (/etc/systemd/system/cse.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2022-07-29 09:00:51 UTC; 44min ago Main PID: 1491 (bash) Tasks: 7 (limit: 4693) Memory: 26.4M CGroup: /system.slice/cse.service ├─1491 /bin/bash /root/cse.sh └─1498 /root/vkp -u svc-cse-vcd -p XXXXXXXX -o system -s https://cloud.lab.infra Second i tried creating a new cluster. As part of deployment process a Virtual machine with name EPHEMERAL_TEMP_VM got created and after this i could not see any progress. In CSE Extension, cluster shows in reconciling state. Is it possible to check something in logs at what stage cluster deployment is ?

tolgaanit1979 · ‎07-29-2022

hi POST https://{{vcd}}/cloudapi/1.0.0/entityTypes/urn:vcloud:type:vmware:VCDKEConfig:0.5.0c API Call is sucessful. but task is not complete in cloud director. stuck at %1

vBahubali01 · ‎07-29-2022

hello Retrieve the identifier from cloud director task urn:vcloud:entity:vmware:VCDKEConfig:<Long UID>. Use this ID in below API call. If API call is sucessful task will also complete in cloud direc...

hello Retrieve the identifier from cloud director task urn:vcloud:entity:vmware:VCDKEConfig:<Long UID>. Use this ID in below API call. If API call is sucessful task will also complete in cloud director POST https://<HostName>/cloudapi/1.0.0/entities/urn:vcloud:entity:vmware:VCDKEConfig:<Long UID>/resolve

tolgaanit1979 · ‎07-28-2022

I'm creating API Call forVCDKE Config. But Cloud Director task is stuck .you can see the screenshot. Is there any idea for this issue?

vBahubali01 · ‎07-26-2022

Thank you we already have CSE 3.x in our setup and CSE Server is considered as backend component (no customer/no direct internet). CSE Server is deployed and configured in management area in a manage...

Thank you we already have CSE 3.x in our setup and CSE Server is considered as backend component (no customer/no direct internet). CSE Server is deployed and configured in management area in a management VLAN. Cloud director is only for hosting tenants and is considered Front end component i.e. (internet/customer facing) Considering 4.0 is still in beta but VMware should consider scenarios as explained above and provide recommendation/instructions because for many service provider platform you will find distinction between management/customer area

niandrew · ‎07-26-2022

Hello, It's not mandatory to deploy CSE Server in cloud director organization. We provide the OVA file that runs CSE Server, and the only requirement is that the resulting VM must be able to connect ...

Hello, It's not mandatory to deploy CSE Server in cloud director organization. We provide the OVA file that runs CSE Server, and the only requirement is that the resulting VM must be able to connect to the VCD host (input as OVA parameter when deploying the OVA, screenshot attached) Our recommendation is to deploy CSE OVA in a provider-managed org using standard vApp deployment workflow. Network specification and root password setup is available there. It's possible to deploy CSE OVA in other environments, but we do not have any recommendations or instructions there.

niandrew · ‎07-26-2022

Hello, to login as root to the CSE VM that is deployed by OVA: 1. Create a vApp from the CSE OVA 2. The vApp will be in "powered off" state 3. go to the VM's details -> Guest OS Customization pa...

Hello, to login as root to the CSE VM that is deployed by OVA: 1. Create a vApp from the CSE OVA 2. The vApp will be in "powered off" state 3. go to the VM's details -> Guest OS Customization page (screenshot attached) 4. check these 2 checkboxes: "Allow local administrator password", "Auto generate password" (screenshot attached) 5. Wait for the vApp to update, and then "power on" the vApp 6. Once the vApp is powered on, go to the VM's details -> Guest OS Customization page, and now you should see an auto-generated password (screenshot attached) 7. You can now access the VM via SSH / remote console / web console, and login as root using the auto-generated password For your issue regarding the defined entity PUT request, from the error it looks like your request body is incorrect. If you'd like you can post the request body you're using and we can take a look

tolgaanit1979 · ‎07-26-2022

hi root/vmware

vBahubali01 · ‎07-25-2022

hello, I went through provider workflow and under networking pre-req for CSE OVA deployment states: "Provider/system admin can create an Edge gateway, a routed network to connect the container serv...

hello, I went through provider workflow and under networking pre-req for CSE OVA deployment states: "Provider/system admin can create an Edge gateway, a routed network to connect the container service extension server" It seems that it is expected that CSE Server must be deployed with in an organization in cloud director. However i would like to deploy CSE server in our management area vCenter in a particular VLAN where CSE server can easily connect to VCD load balanced API endpoint. However when i try to deploy CSE Server in vCenter i dont see any option to specify IP address for CSE Server nor option to specify root password. Is it mandatory to deploy CSE Server in cloud director organization?

MichaelKri · ‎07-25-2022

Hey Team, can you tell me the login to toubleshoot some staff, root pw? provider workflow i only find "Login to the VM to check if CSE server has started." GET https://{{vcd}}/cloudapi/1.0.0/enti...

Hey Team, can you tell me the login to toubleshoot some staff, root pw? provider workflow i only find "Login to the VM to check if CSE server has started." GET https://{{vcd}}/cloudapi/1.0.0/entityTypes/urn:vcloud:type:vmware:VCDK EConfig:0.5.0 works fine, i try to edit the parameter to my key values but i fail with PUT. if i try the POST he sad allready exists. { "minorErrorCode": "VCD_50006", "message": "[ b849c5a4-0b2b-42cb-8e8d-cad1ffb53bed ] Json processing error.\n - Unexpected character (':' (code 58)): was expecting comma to separate Array entries\n at [Source: (org.apache.cxf.metrics.interceptors.CountingInputStream); line: 116, column: 37] (through reference chain: com.vmware.vcloud.rest.openapi.model.DefinedEntityType[\"schema\"])\n - Unexpected character (':' (code 58)): was expecting comma to separate Array entries\n at [Source: (org.apache.cxf.metrics.interceptors.CountingInputStream); line: 116, column: 37]", "stackTrace": "com.fasterxml.jackson.databind.JsonMappingException: Unexpected character (':' (code 58)): was expecting comma to separate Array entries\n at [Source: (org.apache.cxf.metrics.interceptors.CountingInputStream); line: 116, column: 37] (through reference chain: com.vmware.vcloud.rest.openapi.model.DefinedEntityType[\"schema\"])\n\tat com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:397)\n\tat com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:356)\n\tat com.fasterxml.jackson.databind.deser.BeanDeserializerBase.wrapAndThrow(BeanDeserializerBase.java:1726)\n\tat com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:295)\n\tat com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:156)\n\tat com.fasterxml.jackson.databind.ObjectReader._bind(ObjectReader.java:2042)\n\tat com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:1201)\n\tat com.fasterxml.jackson.jaxrs.base.ProviderBase.readFrom(ProviderBase.java:816)\n\tat org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBodyReader(JAXRSUtils.java:1500)\n\tat org.apache.cxf.jaxrs.utils.JAXRSUtils.readFromMessageBody(JAXRSUtils.java:1452)\n\tat org.apache.cxf.jaxrs.utils.JAXRSUtils.processRequestBodyParameter(JAXRSUtils.java:950)\n\tat org.apache.cxf.jaxrs.utils.JAXRSUtils.processParameters(JAXRSUtils.java:881)\n\tat org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:215)\n\tat org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:79)\n\tat line 113-116 "serviceAccount": { "type": "object", "required": [ "userOrgName":"system", best regards

agoel · ‎07-21-2022

Hi Marian CSE 3.1.3 and CSE 4.0 work independently on same VCD. You can give it a try. UI Plugin Beta build will work just fine with CSE 3.1.3. I do ask you to look at known issues page in the Beta ...

Hi Marian CSE 3.1.3 and CSE 4.0 work independently on same VCD. You can give it a try. UI Plugin Beta build will work just fine with CSE 3.1.3. I do ask you to look at known issues page in the Beta documents and the bullet that talks about 3.1.3 based clusters and what to expect in GA. Please report back issues if you see them. Thanks. Aashima

jaskaranv · ‎07-20-2022

Please Note: This document has been updated (7/20).

cm3c · ‎07-20-2022

Hi, is there anything special to take care of, when trying to run CSE 3.1.3 and CSE 4.0 beta in parallel on the same Cloud Director Cell? Do we have to consider something special? If it is indep...

Hi, is there anything special to take care of, when trying to run CSE 3.1.3 and CSE 4.0 beta in parallel on the same Cloud Director Cell? Do we have to consider something special? If it is independent from each other, there should be no problem i guess ...? Anyone tried that? Any hint would be helpful. After using cluster-api/CAPVCD in production with Cloud Director, we would like to thoroughly test the new CSE beta in co-existence with CSE 3.1.3. Thank you! //Marian

All

All Posts

Re: CSE Service Observation and TKG cluster deployement stuck on reconciling state

Re: CSE Service Observation and TKG cluster deployement stuck on reconciling state

Re: API call for VCDKE Config -stuck task

Re: CSE Service Observation and TKG cluster deployement stuck on reconciling state

Re: CSE Service Observation and TKG cluster deployement stuck on reconciling state

Re: API call for VCDKE Config -stuck task

Re: API call for VCDKE Config -stuck task

CSE Service Observation and TKG cluster deployement stuck on reconciling state

Re: API call for VCDKE Config -stuck task

Re: API call for VCDKE Config -stuck task

API call for VCDKE Config -stuck task

Re: cse ova deployment

Re: cse ova deployment

Re: CSE 4.0 appliance password ?

Re: CSE 4.0 appliance password ?

cse ova deployment

CSE 4.0 appliance password ?

Re: CSE 3.1.3 and CSE 4 beta co-existence

Re: Known Issues

CSE 3.1.3 and CSE 4 beta co-existence