Contact Us

CSE 2.6.1 Error: Default template ubuntu-16.04_k8-1.15_weave-2.5.2_rev3 with revision 0 not found. Unable to start CSE server.

Cloud, VMware

While trying to run my Container Service Extension 2.6.1 after a successful installation. I kept getting the following error “Default template ubuntu-16.04_k8-1.15_weave-2.5.2_rev3 with revision 0 not found. Unable to start CSE server.”

To fix this you will need to:

  1. Edit your CSE config.yaml file to include the right name of the default template and revision number. (Much more on this below)
  2. Encrypt your CSE config file again
  3. Re-Run CSE with your encrypted config file

In this post I will explain this in a bit more details for those hitting the same issue, as the resolution is quite simple but might not be as obvious if you are doing this for the first time.

For a start, here is what the exact error look like:

[root@vtcse01 Python-3.7.3]# cse run --config encrypted-config.yaml
Required Python version: >= 3.7.3
Installed Python version: 3.7.3 (default, May 4 2020, 15:36:31)
[GCC 8.3.1 20190507 (Red Hat 8.3.1-4)]
Password for config file decryption:
Decrypting 'encrypted-config.yaml'
Validating config file 'encrypted-config.yaml'
Connected to AMQP server (VTAMQP01.vt.com:5672)
InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised.
Connected to vCloud Director (vcd.vt.com:443)
Connected to vCenter Server 'vtvc01' as 'administrator@vsphere.local' (vtvc01.vt.com:None)
Config file 'encrypted-config.yaml' is valid
Loading k8s template definition from catalog
Found K8 template 'ubuntu-16.04_k8-1.15_weave-2.5.2' at revision 3 in catalog 'cse'
Found K8 template 'ubuntu-16.04_k8-1.17_weave-2.6.0' at revision 1 in catalog 'cse'
Found K8 template 'ubuntu-16.04_k8-1.16_weave-2.6.0' at revision 1 in catalog 'cse'
Found K8 template 'photon-v2_k8-1.14_weave-2.5.2' at revision 2 in catalog 'cse'
Default template ubuntu-16.04_k8-1.15_weave-2.5.2_rev3 with revision 0 not found. Unable to start CSE server.

1- Edit your CSE config.yaml file to include the right name of the default template and revision number.

If you login to vCD organization that you are using for your Container Service Extension 2.6.1, and look in your vAPP templates tab you will see the templates created by CSE with their names and versions as below.

All you have to do is to fix it in your config.xml file in the following section. I am going to use the ubuntu-16.04_k8-1.17_weave-2.6.0_rev1 template as my default template, as you can see from the name it’s revision one. Note you must remove the _rev part of the name from it.

broker:
catalog: cse
default_template_name: ubuntu-16.04_k8-1.17_weave-2.6.0
default_template_revision: 1
ip_allocation_mode: pool
network: NVDSInternet
org: cse
remote_template_cookbook_url: https://raw.githubusercontent.com/vmware/container-service-extension-templates/master/template.yaml
storage_profile: ‘*’
vdc: csepvdc1

2- Encrypt your CSE config file again

Now you will need to encrypt your config file again using the below command
cse encrypt config.yaml –output encrypted-config.yaml

Change the encrypted-config.yaml files permissions using the below command:
[root@vtcse01 Python-3.7.3]# chmod 600 encrypted-config.yaml

3- Re-Run CSE with your encrypted config file

Try to run CSE again using the following run command, and things should work unless if you have another misconfiguration issue:

[root@vtcse01 Python-3.7.3]# cse run –config encrypted-config.yaml
Required Python version: >= 3.7.3
Installed Python version: 3.7.3 (default, May 4 2020, 15:36:31)
[GCC 8.3.1 20190507 (Red Hat 8.3.1-4)]
Password for config file decryption:
Decrypting ‘encrypted-config.yaml’
Validating config file ‘encrypted-config.yaml’
Connected to AMQP server (VTAMQP01.vt.com:5672)
InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised.
Connected to vCloud Director (vcd.doomdns.org:443)
Connected to vCenter Server ‘vtvc01’ as ‘administrator@vsphere.local’ (vtvc01.vt.com:None)
Config file ‘encrypted-config.yaml’ is valid
Loading k8s template definition from catalog
Found K8 template ‘ubuntu-16.04_k8-1.15_weave-2.5.2’ at revision 3 in catalog ‘cse’
Found K8 template ‘ubuntu-16.04_k8-1.17_weave-2.6.0’ at revision 1 in catalog ‘cse’
Found K8 template ‘ubuntu-16.04_k8-1.16_weave-2.6.0’ at revision 1 in catalog ‘cse’
Found K8 template ‘photon-v2_k8-1.14_weave-2.5.2’ at revision 2 in catalog ‘cse’
Processing compute policy for k8s templates.
Removing compute policy from template ‘ubuntu-16.04_k8-1.15_weave-2.5.2_rev3’.
Removing compute policy from template ‘ubuntu-16.04_k8-1.17_weave-2.6.0_rev1’.
Removing compute policy from template ‘ubuntu-16.04_k8-1.16_weave-2.6.0_rev1’.
Removing compute policy from template ‘photon-v2_k8-1.14_weave-2.5.2_rev2’.
Validating CSE installation according to config file
AMQP exchange ‘cse-ext’ exists
CSE on vCD is currently enabled
Found catalog ‘cse’
CSE installation is valid
Started thread ‘MessageConsumer-0 (140436199237376)’
Started thread ‘MessageConsumer-1 (140436190844672)’
Started thread ‘MessageConsumer-2 (140436182451968)’
Started thread ‘MessageConsumer-3 (140435968227072)’
Started thread ‘MessageConsumer-4 (140435959834368)’
Started thread ‘MessageConsumer-5 (140435951441664)’
Started thread ‘MessageConsumer-6 (140435943048960)’
Started thread ‘MessageConsumer-7 (140435934656256)’
Started thread ‘MessageConsumer-8 (140435926263552)’
Started thread ‘MessageConsumer-9 (140435917870848)’
Container Service Extension for vCloud Director
Server running using config file: encrypted-config.yaml
Log files: cse-logs/cse-server-info.log, cse-logs/cse-server-debug.log
waiting for requests (ctrl+c to close)

As you can see it is up and running now, and ready for you to enjoy! Hope you found it helpful!

<!–
–>

Privacy Settings
We use cookies to enhance your experience while using our website. If you are using our Services via a browser you can restrict, block or remove cookies through your web browser settings. We also use content and scripts from third parties that may use tracking technologies. You can selectively provide your consent below to allow such third party embeds. For complete information about the cookies we use, data we collect and how we process them, please check our Privacy Policy
Youtube
Consent to display content from Youtube
Vimeo
Consent to display content from Vimeo
Google Maps
Consent to display content from Google
Spotify
Consent to display content from Spotify
Sound Cloud
Consent to display content from Sound