Date
1 - 3 of 3
Not able to do bosh delete Release <release-name> <version> --force
|
Lingesh Mouleeshwaran <lingeshmouleeshwaran@...>
Hi Team ,
we are in process of upgrading cf from 210 to 215 but our current cf deployment upgrade 215 got stuck with package compilation issue , so current bosh release is showing both cf-210 (existing) and cf-215(new deployment) are active. so we are trying to delete the cf-215 release from bosh using bosh delete release <releasename> version --force. but bosh is not allow since it's saying release locked by cf. Please have any one faced this issue during cf upgrade. Regards Lingesh M |
|
|
|
Amit Kumar Gupta
Yes, while it is in this intermediate state, you cannot delete the
releases, as both are in use. You either need to complete the upgrade to 215 or roll back the deployment to 210, before you can delete either version of the release. Best, Amit On Mon, Nov 9, 2015 at 12:57 AM, Lingesh Mouleeshwaran < lingeshmouleeshwaran(a)gmail.com> wrote: Hi Team , |
|
|
|
Aristoteles Neto
FYI, If the deployment failed during the compilation phase, it should be perfectly safe to rollback (essentially re-run the deployment for v210), as no changes have yet made it through to the servers.
toggle quoted message
Show quoted text
Aristoteles Neto dds.neto(a)gmail.com On 10/11/2015, at 10:18, Amit Gupta <agupta(a)pivotal.io> wrote:
Yes, while it is in this intermediate state, you cannot delete the releases, as both are in use. You either need to complete the upgrade to 215 or roll back the deployment to 210, before you can delete either version of the release. |
|
|