[Bug 820306] Re: debconf item apt-setup/security_path not fully honoured

[javierpb]

What I have done is to download initrd.gz and linux from wget http://archive.ubuntu.com/ubuntu/dists/lucid-proposed/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64
Installing with the new images partially solved the issue. The first access to the security mirror uses the right url
/mirror/ubuntu-security/dists/lucid-security/Release
But later, after configuring the installed base packages, and at the same time that the installer shows the text "Updating the list of available packages", the bad url is attempted again
/ubuntu/dists/lucid-security/Release.gpg

The installer syslog is attached, and the lines at the top of the
sources.list file on the resulting system are verbatim pasted below,
where commented lines show the rigt url for standard packages, and the
bad one for security

# deb http://192.168.40.138/repomirror/ubuntu lucid main restricted
# deb http://192.168.40.138/repomirror/ubuntu lucid-updates main restricted
# deb http://192.168.40.2/ubuntu lucid-security main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.


** Attachment added: "Syslog output for installer coming from luci-proposed"
   https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/820306/+attachment/2291408/+files/syslog.gz

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

Title:
  debconf item apt-setup/security_path not fully honoured

Status in “base-installer” package in Ubuntu:
  Fix Released
Status in “base-installer” source package in Lucid:
  Fix Committed
Status in “base-installer” source package in Maverick:
  Fix Committed
Status in “base-installer” source package in Natty:
  Fix Committed
Status in “base-installer” source package in Hardy:
  Fix Committed

Bug description:
  Stable release update justification:

  Impact: When the -security URL uses some path other than /ubuntu, security updates may not be installed as early during installation as they're supposed to be, and it's possible that there are corner cases where the -security entries are never set up correctly.
  Development branch: Fixed in base-installer 1.119ubuntu4.
  Patch: http://bazaar.launchpad.net/~ubuntu-core-dev/base-installer/ubuntu/revision/959
  TEST CASE: Find a -security mirror which is not rooted at /ubuntu.  Use preseeding similar to that used in the original report to select it during a server installation.  Look for 404 errors referring to Ubuntu in the logs during the base-installer phase of installation: there should be none.  You will need to use the 'apt-setup/proposed=true' boot parameter to test the proposed update for this bug.
  Regression potential: As long as installations complete successfully and the 'apt-get update' during base-installer is free of errors, we should be fine.

  Original report follows:

  I do a 10.04 netinstall with a preseed file, using local mirrors for the repositories. Security repository is defined with
  d-i apt-setup/security_host string 192.168.40.2
  d-i apt-setup/security_path string  /mirror/ubuntu-security
  And the logs from the apache serving the mirror shows some attempts for http://192.168.40.2/ubuntu.
  So it looks like that '/ubuntu' is somewhere hardcoded in the installer.

  When doing the same for lenny, I use
  apt-setup/security_host string 192.168.40.2/repomirror/debian-security
  and works without any issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/820306/+subscriptions