Project

General

Profile

Actions

Refactor #11709

closed

Improve DNS conflict timeout handling

Added by Lukas Zapletal over 8 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
DNS
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

We hardcode timeout to three seconds and our message should contain nicer error (at least the resolver server we use).


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #11850: DNS error message assumes two nameserversClosedLukas Zapletal09/16/2015Actions
Is duplicate of Foreman - Feature #2533: Operation FAILED: NET::ERROR when dns lookups fail. Maybe a more descriptive error?Duplicate05/21/2013Actions
Actions #1

Updated by The Foreman Bot over 8 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/2680 added
  • Pull request deleted ()
Actions #2

Updated by Lukas Zapletal over 8 years ago

  • Is duplicate of Feature #2533: Operation FAILED: NET::ERROR when dns lookups fail. Maybe a more descriptive error? added
Actions #3

Updated by Dominic Cleal over 8 years ago

  • translation missing: en.field_release set to 63
Actions #4

Updated by Dominic Cleal over 8 years ago

  • Related to Bug #11850: DNS error message assumes two nameservers added
Actions #5

Updated by Lukas Zapletal over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF