question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

When adding new entry to ManagedPrefixList get Version Error

See original GitHub issue

Hello!

  • 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)

Issue details

Hello! I am trying to add a new entry to a ManagedPrefixList. In preview, the diff correctly shows the new entry however, when running up, it crashes with following error:

  aws:ec2:ManagedPrefixList (resource_name):
    error: 1 error occurred:
    	* updating urn:urn_of_resource: 1 error occurred:
    	* error updating EC2 Managed Prefix List (id): InvalidParameterValue: The specified value for version is not valid. The value must be greater than (1).
    	status code: 400, request id: id

Code showing deploy below:

        aws.ec2.ManagedPrefixList(
            "name",
            address_family="IPv4",
            entries=[
                aws.ec2.ManagedPrefixListEntryArgs(description="entry_{}".format(cidr), cidr=cidr) for cidr in cidrs
            ],
            max_entries=20,
        )

Steps to reproduce

  1. Created a prefix list in a separate deploy
  2. Made a new deploy appending a new entry to the end
  3. Preview showed correct diff
  4. Deploy failed with error

The only other thing I did recently was change the stack name. But I had also applied that change and run a refresh before this error occurred

Issue Analytics

  • State:open
  • Created 2 years ago
  • Comments:6 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
peterhrisercommented, Jan 31, 2022

As a follow up to this @jordan52 and @pierskarsenbarg. I found if you create individual ManagedPrefixListEntry resources and associate them with empty ManagedPrefixList, it is a functional work around

0reactions
jordan52commented, Jan 31, 2022

update: You can avoid the “modify-in-progress” error above if you run pulumi up --paralllel=1

Read more comments on GitHub >

github_iconTop Results From Across the Web

Work with customer-managed prefix lists - AWS Documentation
For Prefix list entries, choose Add new entry, and enter the CIDR block and a description for the entry. Repeat this step for...
Read more >
modify-managed-prefix-list — AWS CLI 2.9.6 Command ...
Modifies the specified managed prefix list. Adding or removing entries in a prefix list creates a new version of the prefix list.
Read more >
aws ec2 create-managed-prefix-list - Fig.io
You can specify one or more entries for the prefix list. ... If you have the required permissions, the error response is DryRunOperation....
Read more >
aws_ec2_managed_prefix_list | Resources | hashicorp/aws
Terraform currently provides both a standalone Managed Prefix List Entry resource (a ... configuration block. version - Latest version of this prefix list....
Read more >
aws.ec2.ManagedPrefixList - Pulumi
At this time you cannot use a Managed Prefix List with in-line rules in conjunction with any Managed Prefix List Entry resources. Doing...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found