group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1592149@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package curtin - 0.1.0~bzr399-0ubuntu1~16.04.1

---------------
curtin (0.1.0~bzr399-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/new-upstream-snapshot: fix for specifying revision.
  * SRU current curtin
    - curtin/net: fix inet value for subnets, don't add interface attributes
      to alias (LP: #1588547)
    - improve net-meta network configuration (LP: #1592149)
    - reporting: set webhook handler level to DEBUG, no filtering
      (LP: #1590846)
    - tests/vmtests: add yakkety, remove vivid
    - curtin/net: use post-up for interface alias, resolve 120 second time out
      on Trusty when using interface aliases
    - vmtest: provide info on images used
    - fix multipath configuration and add multipath tests (LP: #1551937)
    - tools/launch and tools/xkvm: whitespace cleanup and bash -x
    - tools/launch: boot by root=LABEL=cloudimg-rootfs
    - Initial vmtest power8 support and TestSimple test.

 -- Ryan Harper <ryan.harper@xxxxxxxxxxxxx>  Tue, 12 Jul 2016 11:29:30
-0500

** Changed in: curtin (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1592149

Title:
  simple networking mode (net-meta) does not account for device names

Status in curtin:
  Fix Committed
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Trusty:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * Users which do not use a customized network configuration rely
     on curtin's fallback/automatic configuration.  On Xenial and newer
     systems the network configuration that is generated doesn't always
     work due to the persistent nic names which do not match between
     initial install environment and booting the system after
     installation.

     This affects all curtin releases which use auto configure
     networking and an Ubuntu release which uses persistent network
     device nameing.
     
   * This SRU resolves the bug by ensuring auto configured networking
     includes nic naming rules to ensure the network device names match
     what is generated in the config.

  
  [Test Case]

   * On a Xenial 16.04 system
      - % apt-get install curtin
      - % OUTPUT_NETWORK_CONFIG=rendered-eni curtin net-meta -t /tmp auto

  
    FAIL: Systems with the error will print an interfaces file to stdout

    PASS: Systems with the fix with emit host networking config to the file
          "rendered-eni" and produces no output to stdout.

  
  [Regression Potential]

   * Users that use auto configuration may find that the persistent nic
     names in the target system are no longer ethN, but named based on
     location.

  
  [Original Description]
  I ran
   nosetests3 -v tests/vmtests/test_basic.py:XenialTestBasic
  and was seeing failures.

  That does an install without network config, so it relies on 'net-
  meta' of 'auto'.

  The install worked, but boot failed as networking was not configured.

  The issue is that the net-meta was writing /etc/network/interfaces
  file, but no udev rules or other mechanism to ensure that the device
  got the same name in the new environment.  That, coupled with a change
  in the commands between 'launch' and 'xkvm' meant that the install
  environment named the device 'ens3' and the installed environment
  'ens4'.

  I'll attach logs just for completeness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1592149/+subscriptions