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

data-source/aws_instance: Add missing volume_id fields #2936

Merged
merged 1 commit into from
Jan 11, 2018

Conversation

radeksimko
Copy link
Member

This is to address the following test failures related to #1489

=== RUN   TestAccAWSInstanceDataSource_PlacementGroup
--- FAIL: TestAccAWSInstanceDataSource_PlacementGroup (231.35s)
    testing.go:513: Step 0 error: Error applying: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
    testing.go:573: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.
        
        Error: Error refreshing: 1 error(s) occurred:
        
        * data.aws_instance.foo: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
        
        State: <nil>
=== RUN   TestAccAWSInstanceDataSource_VPCSecurityGroups
--- FAIL: TestAccAWSInstanceDataSource_VPCSecurityGroups (145.01s)
    testing.go:513: Step 0 error: Error applying: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
    testing.go:573: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.
        
        Error: Error refreshing: 1 error(s) occurred:
        
        * data.aws_instance.foo: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
        
        State: <nil>
=== RUN   TestAccAWSInstanceDataSource_blockDevices
--- FAIL: TestAccAWSInstanceDataSource_blockDevices (30.65s)
    testing.go:513: Step 0 error: Error applying: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"ebs_block_device", "0", "volume_id"}
    testing.go:573: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.
        
        Error: Error refreshing: 1 error(s) occurred:
        
        * data.aws_instance.foo: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"ebs_block_device", "0", "volume_id"}
        
        State: <nil>
=== RUN   TestAccAWSInstanceDataSource_gp2IopsDevice
--- FAIL: TestAccAWSInstanceDataSource_gp2IopsDevice (32.75s)
    testing.go:513: Step 0 error: Error applying: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
    testing.go:573: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.
        
        Error: Error refreshing: 1 error(s) occurred:
        
        * data.aws_instance.foo: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
        
        State: <nil>
=== RUN   TestAccAWSInstanceDataSource_keyPair
--- FAIL: TestAccAWSInstanceDataSource_keyPair (45.90s)
    testing.go:513: Step 0 error: Error applying: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
    testing.go:573: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.
        
        Error: Error refreshing: 1 error(s) occurred:
        
        * data.aws_instance.foo: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
        
        State: <nil>
=== RUN   TestAccAWSInstanceDataSource_privateIP
--- FAIL: TestAccAWSInstanceDataSource_privateIP (88.66s)
    testing.go:513: Step 0 error: Error applying: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
    testing.go:573: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.
        
        Error: Error refreshing: 1 error(s) occurred:
        
        * data.aws_instance.foo: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
        
        State: <nil>
=== RUN   TestAccAWSInstanceDataSource_SecurityGroups
--- FAIL: TestAccAWSInstanceDataSource_SecurityGroups (78.04s)
    testing.go:513: Step 0 error: Error applying: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
    testing.go:573: Error destroying resource! WARNING: Dangling resources
        may exist. The full state and error is shown below.
        
        Error: Error refreshing: 1 error(s) occurred:
        
        * data.aws_instance.foo: 1 error(s) occurred:
        
        * data.aws_instance.foo: data.aws_instance.foo: Invalid address to set: []string{"root_block_device", "0", "volume_id"}
        
        State: <nil>

Test results

=== RUN   TestAccAWSInstanceDataSource_basic
--- PASS: TestAccAWSInstanceDataSource_basic (653.96s)
=== RUN   TestAccAWSInstanceDataSource_tags
--- PASS: TestAccAWSInstanceDataSource_tags (247.97s)
=== RUN   TestAccAWSInstanceDataSource_AzUserData
--- PASS: TestAccAWSInstanceDataSource_AzUserData (507.52s)
=== RUN   TestAccAWSInstanceDataSource_gp2IopsDevice
--- PASS: TestAccAWSInstanceDataSource_gp2IopsDevice (258.03s)
=== RUN   TestAccAWSInstanceDataSource_blockDevices
--- PASS: TestAccAWSInstanceDataSource_blockDevices (247.48s)
=== RUN   TestAccAWSInstanceDataSource_rootInstanceStore
--- PASS: TestAccAWSInstanceDataSource_rootInstanceStore (156.10s)
=== RUN   TestAccAWSInstanceDataSource_privateIP
--- PASS: TestAccAWSInstanceDataSource_privateIP (359.39s)
=== RUN   TestAccAWSInstanceDataSource_keyPair
--- PASS: TestAccAWSInstanceDataSource_keyPair (132.83s)
=== RUN   TestAccAWSInstanceDataSource_VPC
--- PASS: TestAccAWSInstanceDataSource_VPC (194.66s)
=== RUN   TestAccAWSInstanceDataSource_PlacementGroup
--- PASS: TestAccAWSInstanceDataSource_PlacementGroup (181.95s)
=== RUN   TestAccAWSInstanceDataSource_SecurityGroups
--- FAIL: TestAccAWSInstanceDataSource_SecurityGroups (154.28s)
	testing.go:503: Step 0 error: Check failed: Check 3/5 error: data.aws_instance.foo: Attribute 'vpc_security_group_ids.#' expected "0", got "1"
=== RUN   TestAccAWSInstanceDataSource_VPCSecurityGroups
--- PASS: TestAccAWSInstanceDataSource_VPCSecurityGroups (221.65s)

That last failure is unrelated and will need to be addressed in a separate PR.

@radeksimko radeksimko added the bug Addresses a defect in current functionality. label Jan 11, 2018
@radeksimko radeksimko added this to the v1.7.0 milestone Jan 11, 2018
Copy link
Contributor

@Ninir Ninir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Sorry for the oversight!

@radeksimko radeksimko merged commit 67fc256 into master Jan 11, 2018
@radeksimko radeksimko deleted the b-ds-aws-instance-volume-id branch January 11, 2018 13:30
@ghost
Copy link

ghost commented Apr 8, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants