kubernetes: [sig-network] DNS configMap nameserver [IPv4] tests failing

Which jobs are failing:

Which test(s) are failing:

Job Test
gce-new-master-upgrade-master DNS configMap nameserver [IPv4] Change stubDomain should be able to change stubDomain configuration [Slow][Serial]
gce-new-master-upgrade-master DNS configMap nameserver [IPv4] Forward PTR lookup should forward PTR records lookup to upstream nameserver [Slow][Serial]
gce-new-master-upgrade-master DNS configMap nameserver [IPv4] Forward external name lookup should forward externalname lookup to upstream nameserver [Slow][Serial]
gce-new-master-upgrade-cluster DNS configMap nameserver [IPv4] Change stubDomain should be able to change stubDomain configuration [Slow][Serial]
gce-new-master-upgrade-cluster DNS configMap nameserver [IPv4] Forward PTR lookup should forward PTR records lookup to upstream nameserver [Slow][Serial]
gce-new-master-upgrade-cluster DNS configMap nameserver [IPv4] Forward external name lookup should forward externalname lookup to upstream nameserver [Slow][Serial]

Reason for failure:

dig result did not match: []string{";; connection timed out; no servers could be reached"}

Since when has it been failing:

  • gce-new-master-upgrade-master: since 2019-02-21
  • gce-new-master-upgrade-cluster: since 2019-02-23

Anything else we need to know:

  • gce-new-master-upgrade-master: Coincides with k/k commit 96043d91a.
  • gce-new-master-upgrade-cluster: Coincides with k/k commit 96043d91a

cc @mortent @kacole2 @alejandrox1 @mariantalla

/kind failing-test /priority important-soon /sig network /milestone 1.14

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 41 (30 by maintainers)

Most upvoted comments

The tests have started passing[1], will wait for ~5 successful runs and then come back to close this issue.

[1]

@alejandrox1 , @smourapina : i see the label “urgent”. The fix is to have the PR #74687 merged. Can you have v1.13 release people go ahead with its merge process ?