Project

General

Profile

Actions

Support #3531

closed

Error during creation of a new host

Added by Olivier Cruilles over 10 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
DNS
Target version:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Net::Error
execution expired
lib/net/dns.rb:36:in `rescue in lookup'
lib/net/dns.rb:15:in `lookup'
lib/net/dns.rb:61:in `dns_lookup'
lib/net/dns/ptr_record.rb:27:in `conflicts'
lib/net.rb:27:in `conflicting?'
app/models/concerns/orchestration/dns.rb:122:in `dns_conflict_detected?'
app/models/concerns/orchestration.rb:47:in `valid?'
app/models/concerns/foreman/sti.rb:29:in `save_with_type'
app/controllers/hosts_controller.rb:85:in `create'
app/models/concerns/foreman/thread_session.rb:33:in `clear_thread'

Actions #1

Updated by Dominic Cleal over 10 years ago

  • Tracker changed from Bug to Support
  • Category set to DNS
  • Status changed from New to Feedback

This suggests one of your authoritative DNS servers is unavailable. Double check NS addresses in your zones, as well as the server specified in the zone SOA and ensure they're answering queries from Foreman.

Actions #2

Updated by Olivier Cruilles over 10 years ago

Hi,

Thank you for your answer. I thought it was something like that.

So can you confirm me if it's possible in Foreman to not use DNS and DHCP features because I would manage by myself the DNS and the DHCP outside Foreman ?

I think it's not possible and logic too, but I not sure.

In case if it's not possible then it is possible to use Foreman to install an Host in a special isolated VLAN where a DHCP could deliver a dynamic IP address in a range but after installation of this host by Kickstart and Puppet, this host take static IP address and could be known and managed by continuation by Foreman through the static IP address.
Of course between the first installation and the first boot of the new host freshly installed, the machine will be changed from the Vlan install to the Vlan Production.

Could you say to me if it's possible currently with the Foreman v1.3 or not at all ?

Thank you in advance
Olivier

Actions #3

Updated by Dominic Cleal over 10 years ago

Olivier Cruilles wrote:

Hi,

Thank you for your answer. I thought it was something like that.

So can you confirm me if it's possible in Foreman to not use DNS and DHCP features because I would manage by myself the DNS and the DHCP outside Foreman ?

I think it's not possible and logic too, but I not sure.

Entirely possible, it's an optional component. Just don't associate any DNS or DHCP proxy with the subnet+domain, then it won't try and manage these. Since Foreman uses IPs for identification of incoming kickstart requests, you may wish to enable tokens in More>Settings (token_duration > 0) if you're not adding DHCP reservations.

In case if it's not possible then it is possible to use Foreman to install an Host in a special isolated VLAN where a DHCP could deliver a dynamic IP address in a range but after installation of this host by Kickstart and Puppet, this host take static IP address and could be known and managed by continuation by Foreman through the static IP address.

Yep, that's fine. Change the PXELinux template's kernel arguments to have:

ks=<%= foreman_url("provision")%>?static=yes

And the template that comes back will be set up for static IP addresses too.

Actions #4

Updated by Olivier Cruilles over 10 years ago

Thank you.

I'll try it as soon.

You can close the ticket.

Olivier

Actions #5

Updated by Dominic Cleal over 10 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF