This message was deleted.

sparse-intern-71089

10/03/2018, 8:33 PM

This message was deleted.

white-balloon-205

10/03/2018, 9:34 PM

That is surprising. When you say you got a valid resource ID - do you mean you got back an ARN or equivalent? If you use

aws

CLI to query for that - does it not exist?

dazzling-scientist-80826

10/04/2018, 5:18 PM

sooo i just went to answer this question for you, but i’m not able to reproduce this problem… on my test domain… even tho it was reproducing reliably a few times yesterday on my main domain - really confusing. let me do a little more investigation

dazzling-scientist-80826

10/04/2018, 5:31 PM

ok - soooo this works totally fine on my test domain - same pulumi script, but here’s what happens on my main domain:

dazzling-scientist-80826

10/04/2018, 5:31 PM

the resource name is just HOSTEDZONEID_domainname_TXT

dazzling-scientist-80826

10/04/2018, 5:32 PM

so removing that resource from the pulumi script & then running update causes the resource to be created

dazzling-scientist-80826

10/04/2018, 5:32 PM

but if i try to recreate it

dazzling-scientist-80826

10/04/2018, 5:32 PM

on both test & real domains, it reports success

dazzling-scientist-80826

10/04/2018, 5:32 PM

it’s shown in

aws route53 list-resource-record-sets

for both

dazzling-scientist-80826

10/04/2018, 5:32 PM

BUT for the test domain, it also shows up in the aws console

dazzling-scientist-80826

10/04/2018, 5:32 PM

for the real domain, it doesn’t!

dazzling-scientist-80826

10/04/2018, 5:33 PM

meanwhile, for the test domain,

dig

on the nameserver produces the right record

dazzling-scientist-80826

10/04/2018, 5:33 PM

but on the real domain, it does not

dazzling-scientist-80826

10/04/2018, 5:33 PM

i can manually add the record in the aws console & then it shows up & dig reports the right result

dazzling-scientist-80826

10/04/2018, 5:33 PM

aws route53 list-resource-record-sets

does not show a duplicate record

dazzling-scientist-80826

10/04/2018, 5:33 PM

seems like something is funky on the aws side … just for my main domain ¯\_(ツ)_/¯

dazzling-scientist-80826

10/04/2018, 5:38 PM

…. and just tried it one more time and it worked correctly

dazzling-scientist-80826

10/04/2018, 5:38 PM

my least favorite kind of bug 😕

dazzling-scientist-80826

10/04/2018, 5:39 PM

anyway, this is not really blocking/hurting me in any way now - but it was surprising/confusing

dazzling-scientist-80826

10/04/2018, 5:39 PM

i’m paranoid about checking DNS records anyway - so maybe no action necessary other than remember i said this so that later when somebody else has a similar problem a pattern may start to emerge 🙂 sorry for the distraction

2 Views

Open in Slack

Previous Next

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.