[Bug 879605] Re: Specifying static network configuration in kickseed no longer works

[Stéphane Graber]

Hello Max, or anyone else affected,

Accepted kickseed into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/kickseed/0.57ubuntu1.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: kickseed (Ubuntu Precise)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: kickseed (Ubuntu Quantal)
       Status: In Progress => Fix Committed

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

Title:
  Specifying static network configuration in kickseed no longer works

Status in “kickseed” package in Ubuntu:
  Fix Released
Status in “kickseed” source package in Precise:
  Fix Committed
Status in “kickseed” source package in Quantal:
  Fix Committed
Status in “kickseed” source package in Raring:
  Fix Committed
Status in “kickseed” source package in Saucy:
  Fix Committed

Bug description:
  [Impact] The supported "network --bootproto=static" Kickstart option is broken during installation, so it's hard for users to tell how to preseed a static network configuration using Kickstart.
  [Test Case] Put a file somewhere web-server-accessible on your local network with "network --bootproto=static --hostname=statictest.pelham.vpn.ucam.org --ip=10.0.2.16 --netmask=255.255.255.0 --gateway=10.0.2.2 --nameserver=10.0.2.3" (this is suitable for my local network with KVM; adjust to match your local environment).  Boot the installer with ks=http://url/to/that/file.  Once installation finishes, you should have a static network configuration, not a dynamic one using DHCP.  Note that this test needs to be carried out using an installer image rebuilt against the new kickseed; we'll make one available in -proposed at some point shortly after this kickseed change is accepted into -proposed.
  [Regression Potential] Confined to Kickstart, since kickseed is used for nothing else.  I considered backporting the compatibility fix to netcfg instead, but that would have had a larger regression potential.

  Original report follows:

  In previous Ubuntu versions you used to be able to start the network
  installation using DHCP,  and then switch over to  a static network
  configuration in your kickstart file, with a line like:

  ==
  network --bootproto=static --ip=1.2.3.4 --netmask=255.255.255.0 --gateway=1.2.3.1 --nameserver=8.8.8.8 --hostname=dhcpunit
  ==

  However in Ubuntu 11.10 that does not seem to work, and it is still
  using DHCP after installation.

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