Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home for cloudfoundry.org
« Groups Home
BOSH Developers
+ new post
About this group
Join this group
Message from discussion Deleting a stemcell when the AWS AMI has already been removed
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Oleg Shaldybin  
View profile  
 More options Sep 21 2012, 8:30 am
From: Oleg Shaldybin <ol...@rbcon.com>
Date: Fri, 21 Sep 2012 05:30:52 -0700
Local: Fri, Sep 21 2012 8:30 am
Subject: Re: [bosh-dev] Deleting a stemcell when the AWS AMI has already been removed
Print | View thread | Show original | Find messages by this author

The flag has been added.

On Sep 21, 2012, at 4:14 AM, anees...@imaginea.com wrote:

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

> On Sunday, April 15, 2012 5:09:41 AM UTC+5:30, Oleg Shaldibin wrote:

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

>> On Sat, Apr 14, 2012 at 4:06 PM, Dr Nic Williams <drnicw...@gmail.com> wrote:
>>> 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?

>> --
>> Best,
>> Oleg


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google