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

boot_volume: size does not work on gen2 #2205

Closed
tehlers320 opened this issue Jan 26, 2021 · 6 comments · Fixed by #3629
Closed

boot_volume: size does not work on gen2 #2205

tehlers320 opened this issue Jan 26, 2021 · 6 comments · Fixed by #3629
Labels
service/VPC Infrastructure Issues related to the VPC Infrastructure

Comments

@tehlers320
Copy link

Terraform Version

0.12.29

Affected Resource(s)

  • ibm_is_instance_template

Terraform Configuration Files

In your ibm_is_instance_template add:

  boot_volume {
    name                             = "some-name"
    delete_volume_on_instance_delete = true
    profile                          = "general-purpose"
    size                             = 200
  }

Debug Output

            {
                "code": "validation_oneof",
                "message": "Expected only one oneOf fields to be set: got 0",
                "target": {
                    "name": "InstanceTemplatePrototype",
                    "type": "field"
                }
            },
            {
                "code": "validation_invalid_field",
                "message": "InstanceByImage is invalid: Key: 'InstanceByImage.BootVolumeAttachment.Volume.Capacity' Error:Field validation for 'Capacity' failed on the 'enum' tag",
                "target": {
                    "name": "InstanceByImage",
                    "type": "field"
                }
            },
            {
                "code": "validation_invalid_field",
                "message": "InstanceByVolume is invalid: Message: Expected only one oneOf fields to be set: got 0 Code: validation_oneof TargetName: VolumeAttachmentPrototypeInstanceByVolumeContextVo4b06 TargetType: field:: Message: VolumeIdentity is invalid: Message: Expected only one oneOf fields to be set: got 0 Code: validation_oneof TargetName: VolumeIdentity TargetType: field:: Message: VolumeIdentityByID is invalid: Key: 'VolumeIdentityByID.ID' Error:Field validation for 'ID' failed on the 'required' tag Code: validation_invalid_field TargetName: VolumeIdentityByID TargetType: field:: Message: VolumeIdentityByCrn is invalid: Key: 'VolumeIdentityByCrn.Crn' Error:Field validation for 'Crn' failed on the 'required' tag Code: validation_invalid_field TargetName: VolumeIdentityByCrn TargetType: field:: Message: VolumeIdentityByHref is invalid: Key: 'VolumeIdentityByHref.Href' Error:Field validation for 'Href' failed on the 'required' tag Code: validation_invalid_field TargetName: VolumeIdentityByHref TargetType: field::  Code: validation_invalid_field TargetName: VolumeIdentity TargetType: field:: Message: VolumePrototypeInstanceByVolumeContext is invalid: Key: 'VolumePrototypeInstanceByVolumeContext.SourceSnapshot' Error:Field validation for 'SourceSnapshot' failed on the 'required' tag\nKey: 'VolumePrototypeInstanceByVolumeContext.Capacity' Error:Field validation for 'Capacity' failed on the 'enum' tag Code: validation_invalid_field TargetName: VolumePrototypeInstanceByVolumeContext TargetType: field:: ",
                "target": {
                    "name": "InstanceByVolume",
                    "type": "field"
                }
            },

Panic Output

If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.

Expected Behavior

adjustment of boot volume size operates

Actual Behavior

error

Steps to Reproduce

see the boot volume snippit above.

@tehlers320
Copy link
Author

This is actually a gen2 problem i think. In a completely un-reasonable move the boot_volume size is immutable i think. Can anybody confirm this?

If true the documentation needs an update.

@kavya498 kavya498 added the service/VPC Infrastructure Issues related to the VPC Infrastructure label Mar 30, 2021
@anilkumarnagaraj
Copy link
Collaborator

@astha-jain
Could you please confirm this?

@ujjwal-ibm
Copy link
Collaborator

Accepted value for size of the boot volume is image's minimum_provisioned_size (this will change in future), so for now size is not configurable in boot_volume configuration and documentation.

@lgmaviles
Copy link

Good morning,
we are in a cloud migration process and it is a blocking point not being able to create VSI with a custom boot_volume size.
Do you have an estimate of when this functionality will be included?
Thx

@astha-jain
Copy link
Contributor

Hi @lgmaviles We are working on getting this feature included in upcoming release.

@lgmaviles
Copy link

Thank you for your response,
Do you have a date estimate for this release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/VPC Infrastructure Issues related to the VPC Infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants