external-dns: OpenStack Designate provider: failure to update existing recordset
When trying to update the IP address of an existing record, external-dns fails to do so and displays the log entries:
time="2018-06-15T15:04:19Z" level=info msg="Creating records: training.k8s-playground.c.eu-de-2.cloud.sap./A: 10.236.96.161"
time="2018-06-15T15:04:19Z" level=error msg="Expected HTTP response code [201 202] when accessing [POST https://dns-3.eu-de-2.cloud.sap/v2/zones/ed3d348c-bc97-46ad-a28e-03205587c1b9/recordsets], but got 409 instead\n{\"message\": \"Duplicate RecordSet\", \"code\": 409, \"type\": \"duplicate_recordset\", \"request_id\": \"req-b1bbe4d1-a2c5-4cff-ba39-bbfd9f213a8a\"}"
Both A and TXT records are correctly created in the first place, and the configured user can list the domain’s recordsets using the openstack CLI.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 4
- Comments: 24 (10 by maintainers)
Commits related to this issue
- Remove receipts migration (#603) * Remove receipts migration * Remove receiptsmigration check from ci * Rename test * Remove oldenvironment * Code review changes — committed to lou-lan/external-dns by chriskim06 4 years ago
- Allow multiple records per A record Fetch labels from existing TXT records to fix https://github.com/kubernetes-sigs/external-dns/issues/603 — committed to hikhvar/external-dns by deleted user 2 years ago
- Allow multiple records per A record Fetch labels from existing TXT records to fix https://github.com/kubernetes-sigs/external-dns/issues/603 — committed to hikhvar/external-dns by deleted user 2 years ago
https://github.com/kubernetes-incubator/external-dns/pull/1136 fixes TXTRegistry to retain the endpoint labels between Records() and ApplyChanges() calls on the provider, which fixes this for us for the most part (there’s still one 409 per change happening for the TXT record, but the A record is updated correctly and all subsequent reconciliations go though without errors).
I’m sure this is not the right/best patch for this. This “remember stuff in labels” approach of the designate provider seems unusual; no other provider does this.