external-dns icon indicating copy to clipboard operation
external-dns copied to clipboard
verified publisher icon kubernetes-sigs

Google Cloud client does not handle missing a- TXT records

Open misha-ridge opened this issue 3 years ago • 1 comments

What happened:

external-dns tried to update some records. Their TXT records with prefix a- were missing, and external-dns failed to handle it:

googleapi: Error 404: The 'entity.change.deletions[18]' resource named 'a-AA.XX.com. (TXT)' does not exist.
More details:
Reason: notFound, Message: The 'entity.change.deletions[18]' resource named 'a-AA.XX.com. (TXT)' does not exist.
Reason: notFound, Message: The 'entity.change.deletions[19]' resource named 'a-BB.XX.com. (TXT)' does not exist.
Reason: notFound, Message: The 'entity.change.deletions[20]' resource named 'a-CC.XX.com. (TXT)' does not exist.
Reason: notFound, Message: The 'entity.change.deletions[21]' resource named 'a-DD.XX.com. (TXT)' does not exist.
Reason: notFound, Message: The 'entity.change.deletions[22]' resource named 'a-EE.XX.com. (TXT)' does not exist.
Reason: notFound, Message: The 'entity.change.deletions[23]' resource named 'a-FF.XX.com. (TXT)' does not exist.
Reason: notFound, Message: The 'entity.change.deletions[24]' resource named 'a-GG.XX.com. (TXT)' does not exist.
Reason: notFound, Message: The 'entity.change.deletions[25]' resource named 'a-HH.XX.com. (TXT)' does not exist.
Reason: notFound, Message: The 'entity.change.deletions[26]' resource named 'a-II.XX.com. (TXT)' does not exist.

What you expected to happen:

external-dns can handle missing a- TXT records and continue.

How to reproduce it (as minimally and precisely as possible):

  • Create a record in Google Cloud via external-dns
  • Stop external-dns
  • Remove a-... TXT record manually
  • Start external-dns
  • See it failing due to missing record

Anything else we need to know?:

Environment:

  • External-DNS version (use external-dns --version): 0.12.0
  • DNS provider: Google Cloud
  • Others: Kubernetes 1.22.8 (GKE)

misha-ridge avatar Jun 15 '22 10:06 misha-ridge

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Sep 18 '22 09:09 k8s-triage-robot

/remove-lifecycle stale

misha-ridge avatar Sep 26 '22 06:09 misha-ridge

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Dec 25 '22 08:12 k8s-triage-robot

/remove-lifecycle stale

misha-ridge avatar Dec 25 '22 08:12 misha-ridge

Looks like resolved in #2811

misha-ridge avatar Dec 25 '22 08:12 misha-ridge