Deleting a stemcell when the AWS AMI has already been removed

Dr Nic Williams

unread,

Apr 14, 2012, 7:06:50 PM4/14/12

to bosh-dev

BOSH has a unidirectional relationship with IaaS data. BOSH assumes it
knows and controls everything. Someone couldn't possibly go behind
BOSH's back and delete an AMI when BOSH wasn't looking, surely?!

The consequence of this is that bosh_cli cannot subsequently delete
nor re-upload the stemcell.

# bosh delete stemcell bosh-stemcell 0.5.1
You are going to delete stemcell `bosh-stemcell (0.5.1)'
Are you sure? (type 'yes' to continue): yes
Tracking task output for task#2...

Deleting stemcell from cloud
delete stemcell: <?xml version="1.0" encoding="UTF-8"?
>
<Response><Errors><Error><Code>InvalidAMIID.Unavailable</
Code><Message>The image ID 'ami-163ae27f' is no longer available</
Message></Error></Errors><RequestID>85deae07-
f0fd-49eb-83c1-3ecbbbc5a017</RequestID></Response> (00:00:00)

My preference is to recognize that the underlying AMI has been deleted
(in the aws_cpi, it would look for the InvalidAMIID.Unavailable
error), and allow the CLI user to continue with deleting the BOSH data
entry.

That ok?

Oleg Shaldibin

unread,

Apr 14, 2012, 7:39:41 PM4/14/12

to bosh...@cloudfoundry.org

Sounds good, we will add --force flag to 'bosh delete stemcell', it will ignore cloud errors (similar to 'delete release' and 'delete deployment' behavior).

--
Best,

Oleg

anee...@imaginea.com

unread,

Sep 21, 2012, 7:14:01 AM9/21/12

to bosh...@cloudfoundry.org

Any Update on this?.. is the --force flag available now?

Oleg Shaldybin

unread,

Sep 21, 2012, 8:30:52 AM9/21/12

to bosh...@cloudfoundry.org, bosh...@cloudfoundry.org

The flag has been added.

anee...@imaginea.com

unread,

Sep 21, 2012, 9:18:52 AM9/21/12

to bosh...@cloudfoundry.org

Can you please tell me the latest version?..

Reply all

Reply to author

Forward