[Bug 1381703] [NEW] preseed with unqualified host:port fails - upstream bug fixed

dberger 1381703 at bugs.launchpad.net
Wed Oct 15 19:06:33 UTC 2014


Public bug reported:

This (fixed) Debian bug : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=695908 affects 12.04.5 (preseed-1.50ubuntu1)

If you're (for example) using multi-site puppet to deploy hosts, and
want the pxe clients to fetch their preseed from their "domain local"
puppet install, you might say they should preseed from http://puppet:80
- unfortunately, when the host boots it attempts to fetch
puppet:80.domain.dom

(In theory removing the port would "fix" this, unfortunately foreman
likes to make sure there's a port in the preseed url, so that's not
trivial either).

** Affects: preseed (Ubuntu)
     Importance: Undecided
         Status: New

** Package changed: netcfg (Ubuntu) => preseed (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netcfg in Ubuntu.
https://bugs.launchpad.net/bugs/1381703

Title:
  preseed with unqualified host:port fails - upstream bug fixed

Status in “preseed” package in Ubuntu:
  New

Bug description:
  This (fixed) Debian bug : https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=695908 affects 12.04.5 (preseed-1.50ubuntu1)

  If you're (for example) using multi-site puppet to deploy hosts, and
  want the pxe clients to fetch their preseed from their "domain local"
  puppet install, you might say they should preseed from
  http://puppet:80 - unfortunately, when the host boots it attempts to
  fetch puppet:80.domain.dom

  (In theory removing the port would "fix" this, unfortunately foreman
  likes to make sure there's a port in the preseed url, so that's not
  trivial either).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1381703/+subscriptions



More information about the foundations-bugs mailing list