Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS: Update record from simple routing policy to weighted is not supported #1411

Closed
spohner opened this issue Feb 5, 2020 · 2 comments · Fixed by #1555
Closed

AWS: Update record from simple routing policy to weighted is not supported #1411

spohner opened this issue Feb 5, 2020 · 2 comments · Fixed by #1555

Comments

@spohner
Copy link
Contributor

spohner commented Feb 5, 2020

Updating an existing A record from a simple routing policy to weighted by adding annotations to a service fails. External-dns tries to create a new record using the same name and type and delete the old record with no weights. The aws cli fails with a describing error:

InvalidChangeBatch: [RRSet with DNS name example.org., type A, SetIdentifier foobar cannot be created as a non-weighted set exists with the same name and type., RRSet with DNS name example.org., type TXT, SetIdentifier foobar cannot be created as a non-weighted set exists with the same name and type.]\n\tstatus code: 400, request id: *"

May be fixed by correcting the logic to use UPSERT instead of CREATE/DELETE. Another idea is to do deletions before creating new records, but that may have some negative implications I have not foreseen.

@OmerKahani
Copy link
Contributor

Hi UPSERT is not possible, doing UPSERT will actually do a CREATE that will fail.

I was able to fix this locally by changing the order of the commands, so it will do DELETE before CREATE. AWS state the actions will happen in a single operation, so I think it's safe.

@nitrocode
Copy link
Contributor

@OmerKahani how did you change the order of the commands?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants