Python Client for VMware Cloud on AWS is an open-source Python-based tool. Written in Python, the tool enables VMware Cloud on AWS users to automate the consumption of their VMware Cloud on AWS SDDC.
I have also tried keeping sddc_id as null in config.ini but it it fails in validation:
mithilra@b0be83701edd python-client-for-vmware-cloud-on-aws-development % ./pyVMC.py sddc create -n mithilra-1node-sddc -r us-east-1 -num 1 -t i3.metal -sid subnet-04d122190192cd7fa -mgt 10.9.0.0/16 -s medium -aws 75135642-c21c-3312-93fa-d1d7db7b4f18 -v
strProdURL, strCSPProdURL, Refresh_Token, ORG_ID, and SDDC_ID must all be populated in config.ini
There are problems with your config.ini file.
Please be sure you have the latest version and ensure at least the following values are populated:
Refresh_Token - this should be a properly scoped refresh refresh token from the VMware Cloud Services Console.
oauth_clientId - this should be OAuth Client ID properly scoped from VMware Cloud Services Console.
oauth_clientSecret - this should be OAuth Client Secret.
ORG_ID - this should be the ID of your VMware Cloud Organization, found in the VMware Cloud Services Portal.
SDDC_ID - if applicable, this should be the ID of the VMware Cloud SDDC (Software Defined Datacenter) you wish to work with.
strVCDRProdURL - if applicable, this should be the URL of your VMware Cloud DR Orchestrator.
Is it expected to pass sddc_id with a value even if SDDC is created using the cli ./pyVMC.py sddc create. It anyway fails even if one of the existing SDDC ID is provided in the config.ini
Reproduction steps
Execute the cli ./pyVMC.py sddc create -n mithilra-1node-sddc -r us-east-1 -num 1 -t i3.metal -sid subnet-04d122190192cd7fa -mgt 10.9.0.0/16 -s medium -aws 75135642-c21c-3312-93fa-d1d7db7b4f18 -v. It fails with error :
./pyVMC.py sddc create -n mithilra-1node-sddc -r us-east-1 -num 1 -t i3.metal -sid subnet-04d122190192cd7fa -mgt 10.9.0.0/16 -s medium -aws 75135642-c21c-3312-93fa-d1d7db7b4f18 -v should be successfully executed with and without -v option
Describe the bug
I am trying to create the sddc with following syntax (tried with and without both -v) but it fails with an "Unknown Error"
mithilra@b0be83701edd python-client-for-vmware-cloud-on-aws-development % ./pyVMC.py sddc create -n mithilra-1node-sddc -r us-east-1 -num 1 -t i3.metal -sid subnet-04d122190192cd7fa -mgt 10.9.0.0/16 -s medium -aws 75135642-c21c-3312-93fa-d1d7db7b4f18 -v Status code: 500: Unknown error ['An internal error has occurred.']
I have provided the guid in the arg -aws.
I have also tried keeping sddc_id as null in config.ini but it it fails in validation: mithilra@b0be83701edd python-client-for-vmware-cloud-on-aws-development % ./pyVMC.py sddc create -n mithilra-1node-sddc -r us-east-1 -num 1 -t i3.metal -sid subnet-04d122190192cd7fa -mgt 10.9.0.0/16 -s medium -aws 75135642-c21c-3312-93fa-d1d7db7b4f18 -v
strProdURL, strCSPProdURL, Refresh_Token, ORG_ID, and SDDC_ID must all be populated in config.ini
There are problems with your config.ini file.
Please be sure you have the latest version and ensure at least the following values are populated:
Is it expected to pass sddc_id with a value even if SDDC is created using the cli ./pyVMC.py sddc create. It anyway fails even if one of the existing SDDC ID is provided in the config.ini
Reproduction steps
Execute the cli ./pyVMC.py sddc create -n mithilra-1node-sddc -r us-east-1 -num 1 -t i3.metal -sid subnet-04d122190192cd7fa -mgt 10.9.0.0/16 -s medium -aws 75135642-c21c-3312-93fa-d1d7db7b4f18 -v. It fails with error :
mithilra@b0be83701edd python-client-for-vmware-cloud-on-aws-development % ./pyVMC.py sddc create -n mithilra-1node-sddc -r us-east-1 -num 1 -t i3.metal -sid subnet-04d122190192cd7fa -mgt 10.9.0.0/16 -s medium -aws 75135642-c21c-3312-93fa-d1d7db7b4f18 -v Status code: 500: Unknown error ['An internal error has occurred.']
Expected behavior
./pyVMC.py sddc create -n mithilra-1node-sddc -r us-east-1 -num 1 -t i3.metal -sid subnet-04d122190192cd7fa -mgt 10.9.0.0/16 -s medium -aws 75135642-c21c-3312-93fa-d1d7db7b4f18 -v should be successfully executed with and without -v option
Additional context
No response