Since the v1 1 0 upgrade `pulumi up` always detects a change Pulumi Community #general

Since the v1.1.0 upgrade `pulumi up` always detect...

fierce-cpu-94517

09/16/2019, 1:14 PM

Since the v1.1.0 upgrade

pulumi up

always detects a change in an EBS volume attachment though nothing changed:

Copy code

$ pulumi up
Previewing update (acmecorp-demo):

     Type                                                 Name                           Plan        Info
     pulumi:pulumi:Stack                                  private-cloud-acmecorp-demo              
 +-  ├─ aws:ec2:Instance                                  services                       replace     [diff: ~ebsBlockDevices]
     ...

Resources:
    +-8 to replace
    156 unchanged

Do you want to perform this update? details
  pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:acmecorp-demo::private-cloud::pulumi:pulumi:Stack::private-cloud-acmecorp-demo]
    ++aws:ec2/instance:Instance: (create-replacement)
        [id=i-0eba90d7bd7c11af4]
        [urn=urn:pulumi:acmecorp-demo::private-cloud::aws:ec2/instance:Instance::services]
        [provider=urn:pulumi:acmecorp-demo::private-cloud::pulumi:providers:aws::default_0_18_27::4e650a8e-8d3d-4c3c-a9d1-b31c8638bd95]
      ~ ebsBlockDevices: [
          ~ [0]: {
                  ~ deleteOnTermination: true => true
                  ~ deviceName         : "/dev/sdf" => "/dev/sdf"
                  + encrypted          : true
                  + volumeSize         : 100
                  + volumeType         : "gp2"
                }
        ]
    +-aws:ec2/instance:Instance: (replace)
        [id=i-0eba90d7bd7c11af4]
        [urn=urn:pulumi:acmecorp-demo::private-cloud::aws:ec2/instance:Instance::services]
        [provider=urn:pulumi:acmecorp-demo::private-cloud::pulumi:providers:aws::default_0_18_27::4e650a8e-8d3d-4c3c-a9d1-b31c8638bd95]
      ~ ebsBlockDevices: [
          ~ [0]: {
                  ~ deleteOnTermination: true => true
                  ~ deviceName         : "/dev/sdf" => "/dev/sdf"
                  + encrypted          : true
                  + volumeSize         : 100
                  + volumeType         : "gp2"
                }
        ]

stocky-spoon-28903

09/16/2019, 1:19 PM

This looks like a regression in the upstream Terraform provider with regards to diffing (potentially normalization of the mount point). Does this occur on every instance/volume or only in certain situations?

fierce-cpu-94517

09/16/2019, 1:26 PM

I currently have only one volume attachment

stocky-spoon-28903

09/16/2019, 2:36 PM

In your code, do you explicitly set the mount point?

fierce-cpu-94517

09/16/2019, 2:57 PM

Copy code

export const servicesInstance = new aws.ec2.Instance("services", {
    ami: "xxxxxx",
    ebsOptimized: true,
    ebsBlockDevices: [{
        deviceName: "/dev/sdf",
        encrypted: true,
        volumeSize: 100,
        volumeType: "gp2",
    }],
    ...

stocky-spoon-28903

09/16/2019, 4:40 PM

OK thanks. I’m going to open an issue to track this

stocky-spoon-28903

09/16/2019, 4:41 PM

https://github.com/pulumi/pulumi-aws/issues/747

👍 1

2 Views

Open in Slack

Previous Next