Updating subnet fails with error: Ipv6CidrBlock cannot be empty #788
Comments
pjoe
added
kind/bug
|
Thanks for this detailed report ⭐ I see what you mean -- and the field is not marked as required in the docs, either (https://www.pulumi.com/registry/packages/aws-native/api-docs/ec2/subnet/#inputs). I think there's enough info here to try and reproduce the problem (thanks!), so we'll look into it. |
|
Is there a workaround for this? |
Not sure; you could try explicitly supplying an empty string, but I'm making a guess. |
That blows up with a validation error 🙂 |
I'm facing same issue with |
|
In case some additional clarity is helpful: it will happily create the resource without specifying |
|
I am also experiencing this issue 😄 |
|
I have same problem. |
|
Same issue for me. The subnet resource will create just fine, but fails with the same error when attempting to update. |
|
I believe this is, unfortunately, an upstream issue on AWS' side. Here's a minimal program that reproduces the issue using the latest Pulumi azs-native v0.96: import * as awsnative from "@pulumi/aws-native";
// Create a new VPC using AWS Native
const vpc = new awsnative.ec2.Vpc("my-vpc-native", {
cidrBlock: "10.0.0.0/16", // Example CIDR block for the VPC
});
// Create a subnet within the VPC using AWS Native
const subnet = new awsnative.ec2.Subnet("my-subnet-native", {
vpcId: vpc.id, // Associates the subnet with the VPC using the id property from the VPC
cidrBlock: "10.0.1.0/24", // Example CIDR block for the subnet
availabilityZone: "us-east-1c", // Specify the availability zone
tags: [ {key: "foo", value: "bar"} ], // Add a tag to the subnet
});
// Export the IDs of the VPC and subnet
export const vpcId = vpc.id;
export const subnetId = subnet.id;To isolate whether the issue is on Pulumi's side, I replicated the operation of editing or removing tags using the ❯ aws cloudcontrol update-resource --type-name "AWS::EC2::Subnet" --region us-east-1 \
--identifier subnet-011fcc8640b709368 \
--patch-document '[{"op":"remove","path":"/Tags"}]'I get the same error:
I double-checked in the Cloud Control specs that So this seems to be an issue on the Cloud Control side. I'll work with our Pulumi AWS contacts to get an issue filed in the right place. |
|
I filed #1927 EC2::Subnet cannot be updated if |
|
I just updated the referenced issue, but posting here as well for visibility. As a work-around, you can append the following string: |
|
AWS have now resolved the upstream issue. That means updates should now work without a workaround. Please give it a try. |
What happened?
Trying to update a
awsnative.ec2.Subnet(just adding a name tag).pulumi previewworks fine butpulumi uperrors complaining aboutipv6CidrBlockHere is the error from
pulumi up:Expected Behavior
Changes to subnet applies without errors.
Steps to reproduce
Here is source for the subnet:
Output of
pulumi aboutLooks like it isn't picking up deps from my monorepo setup, but here are some info:
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: