Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

delete_on_termination=true attribute on new volume is not set on create #6

Closed
plribeiro3000 opened this issue Jan 15, 2015 · 3 comments

Comments

@plribeiro3000
Copy link
Member

original issue at : fog/fog#1737

I am using a config hash to create a new EBS volume and attach it to an existing server like so:

      new_ebs_config = {
                        'availability_zone'     => 'us-east-1d,
                        'size'                  => 20,
                        'device'                => "/dev/sdj",
                        'delete_on_termination' => true,
                        'type' => 'standard'
                        'server' => instance_id
      }
      new_volume = @ec2.volumes.create(new_ebs_config)

The delete_on_termination attribute is not being set on this new volume after it has been attached to the server. I have been using

          @ec2.modify_instance_attribute(
            @instance_id, {
              'BlockDeviceMapping.1.DeviceName'              => config['device'],
              'BlockDeviceMapping.1.Ebs.DeleteOnTermination' => config['delete_on_termination'].to_s
            }
          )

It would be nice to have it set after attach is called if server is part of the passed in config.

@plribeiro3000
Copy link
Member Author

cc/ @gregburek @karmi

@karmi
Copy link

karmi commented Jan 16, 2015

@plribeiro3000 Thanks for the report!, keeping the issue open for reference, I can't dive into it right now.

UPDATE: Gosh, sorry, I thought this is for cookbook-elasticsearch.

KevinLoiseau pushed a commit to KevinLoiseau/fog-aws that referenced this issue Aug 8, 2019
@github-actions
Copy link

This issue has been marked inactive and will be closed if no further activity occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants