You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PARS stacks seem to persist even when deleted multiple times. Eventually they go away, but it seems to require several requests to delete (doesn't seem to be a fixed number, but I haven't kept track of it very closely). This might be a bug in AWS, not on our end, but I am still recording this here, so we can keep an eye on it.
The text was updated successfully, but these errors were encountered:
I realize this is a very old issue so perhaps you don't remember. But are you talking about deleting the PARS stacks through the AWS web interface or using clobber. If through the web interface, then this could be because the dependent Knot stack hadn't yet been deleted. If through clobber then it's a real issue. If you don't remember that's fine too.
My memory of this is that this was happening even after the knot stack was long gone, but it's been a while since I've had a chance to look into this. I suggest to keep this open until we have a chance to take a closer look.
The PARS stacks seem to persist even when deleted multiple times. Eventually they go away, but it seems to require several requests to delete (doesn't seem to be a fixed number, but I haven't kept track of it very closely). This might be a bug in AWS, not on our end, but I am still recording this here, so we can keep an eye on it.
The text was updated successfully, but these errors were encountered: