Known issues

Upgrade to 1.16.1

If you upgrade Cloudbreak to 1.16.1 and you don't have the UAA_DEFAULT_SECRET specified in the Profile, Cloudbreak deployer will generate one automatically. Furthermore, if you have existing clusters, Cloudbreak will use this new secret to decrypt the database records; however, those were encrypted with the old secret so the old secret needs to be provided in the Profile.

Workaround: If you have an existing cluster without the UAA_DEFAULT_SECRET in your Profile, you must extend the Profile before starting Cloudbreak 1.16.1.

export UAA_DEFAULT_SECRET=cbsecret2015

This issue will be fixed in an upcoming release.

Decommission

Cloudbreak Shell

Example:

credential select --name my-aws-credential
...
template create --AWS --name my-aws-template --description aws-template --instanceType m3.large --volumeType ephemeral --volumeCount 1 --volumeSize 32 --topologyId 1 --encrypted false
...
stack create --AWS --name my-aws-cluster --region eu-west-1

Workaround: template creation commands should be executed before the credential selection command

template create --AWS --name my-aws-template --description aws-template --instanceType m3.large --volumeType ephemeral --volumeCount 1 --volumeSize 32 --topologyId 1 --encrypted false
...
credential select --name my-aws-credential
...
stack create --AWS --name my-aws-cluster --region eu-west-1
Edit on GitHub