This message was deleted.
# awss
sparse-intern-71089
06/03/2021, 11:04 PMThis message was deleted.
s
square-dress-80180
06/03/2021, 11:13 PMIt gets weirder … if I
pulumi state deleteno such resource exists in current statel
little-cartoon-10569
06/03/2021, 11:31 PMLooks like the error is coming only form AWS and not Pulumi? Pulumi is all clean but the SubnetGroup and RDS instance are still in AWS?
s
square-dress-80180
06/07/2021, 4:29 PMthose resources were deleted manually in the aws console though. Are you saying @little-cartoon-10569 that Pulumi is getting the error from an api call to aws to confirm that the subnet group can be deleted? I am not clear whether it is pulumi
statestateInvalidDBSubnetGroupStateFaultsquare-dress-80180
06/07/2021, 4:46 PMnm - It seems like I had only “stopped” the rds instance and not actually “deleted” it. Once deleted the
pulumi destroysquare-dress-80180
06/07/2021, 6:04 PMIt still is confusing to me why pulumi would think it had deleted the rds instance if it wasn’t actually deleted and then try to move on to the related subnets.
l
little-cartoon-10569
06/07/2021, 8:56 PMThis is the downside of fully async systems. RDS databases can take a long time to delete, and in many cases, simply will not delete (e.g. if multiAZ is on) but won't tell you immediately. How long does Pulumi wait to find out?
little-cartoon-10569
06/07/2021, 8:57 PMI think most of the time, Pulumi works off the response to the initial request. If Pulumi sends a "delete" request to RDS, and RDS responds with "right-o, I'll get right on that", then Pulumi may have to assume that the DB will eventually be deleted...
s
square-dress-80180
06/22/2021, 3:39 PM(A very belated) Thanks @little-cartoon-10569 for the info!
👍 1
3 Views