https://pulumi.com
Join Slack
This message was deleted.
# aws
s
This message was deleted.
a
Hey Damien, I'm sorry you encountered this and thanks for reporting it. We are working on that problem, it is being tracked here: https://github.com/pulumi/pulumi-aws/issues/2904 We are still not quite certain what caused it but in my testing it's been the result of a mismatch between pulumi state and cloud state. You could try running pulumi refresh and see if that fixes the issue. Has the rds cluster been modified/deleted in the aws console?
v
look like, pulumi refresh fixed the thing
🙌 1
so what i did previously
1/ create a RDS cluster with this values
Copy code
BackupRetentionPeriod:      <http://pulumi.Int|pulumi.Int>(7),
            PreferredBackupWindow:      pulumi.String("01:00-02:00"),
2/ call AWS backup NewPlan with
Copy code
Lifecycle: &backup.PlanRuleLifecycleArgs{
					DeleteAfter: <http://pulumi.Int|pulumi.Int>(30), // in days
				},
everything working well at this steps
3/ few weeks later, update cluster engine version 14.6 to 15.4
Copy code
AllowMajorVersionUpgrade:   pulumi.Bool(true),
			EngineVersion:              pulumi.String("15.4"),
I got AWS error
Copy code
InvalidParameterValue: RDS cluster rh-dev-postgres is associated with the following AwsBackupRecoveryPointArn: arn:aws:backup:eu-central-2:999999999:recovery-point:continuous:cluster-olploybnydw46flnzsh22ae5yq-58f01dc1. The BackupRetentionPeriod can be blank, or you can use the current value, 30. For more details, see the AWS Backup documentation.
    	status code: 400, request id: 67454eea-f51b-42bc-8b30-a1d69e715215
Copy code
pulumi preview --diff
reported this
Copy code
~ backupRetentionPeriod      : 30 => 7
      ~ engineVersion              : "14.6" => "15.4"
      ~ preferredBackupWindow      : "21:00-23:00" => "01:00-02:00"
      ~ availabilityZones          : [
          ~ [0]: "eu-central-2b" => "eu-central-2a"
          ~ [1]: "eu-central-2c" => "eu-central-2b"
          ~ [2]: "eu-central-2a" => "eu-central-2c"
        ]
then I guessed the backup plan conflicted with the cluster config for some reason
so I changed the my code to match the cluster state
Copy code
BackupRetentionPeriod:      <http://pulumi.Int|pulumi.Int>(30),
then i got the panic error using
Copy code
pulumi up
a
Thanks for the detailed steps - I'll give it a go! I'm glad you also managed to work around the issue
23 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by