** No longer affects: ubiquity (Ubuntu)

** Also affects: netcfg (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: netcfg (Ubuntu)
   Importance: Undecided => High

** Description changed:

  Hello.
  
  I've installed today from the Ubuntu Server Daily ISO.  During the
  installer process, we get the system identifying network interfaces with
  the traditional unpredictable naming algorithms of eth##.  After
  installation, the system uses systemd to identify network interface
  names, per
  
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
  
  In the Virtual Environment i'm using, on VMware Workstation x64 with two
  virtual NICs, I end up with ens33 and ens34 according to the installed
  system.
  
  However, the installer populated the /etc/network/interfaces
  configuration with eth0 and eth1.  As a result, networking fails to
  start up after a reboot, and either /etc/network/interfaces needs edited
  to match the correct identifiers and a reboot issued, or one has to do
  `sudo dhclient` to update the IP address.  For static addressing
  networks, of course, you still need to revise the interfaces file.
  
- 
- This is a serious issue, as upon installation via the ubuntu-server ISO, 
networking will fail to come up, leaving users to scratch their head expecting 
instant access.
+ This is a serious issue, as upon installation via the ubuntu-server ISO,
+ networking will fail to come up, leaving users to scratch their head
+ expecting instant access.
  
  Due to an uncertainty in the severity, I've set it to High given that
  last point.  Please feel free to change it.  Note that this is filed
- against both systemd and ubiquity as I am not sure which one needs to be
+ against both systemd and netcfg as I am not sure which one needs to be
  fixed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 222-1ubuntu1
  ProcVersionSignature: Ubuntu 4.0.0-4.6-generic 4.0.7
  Uname: Linux 4.0.0-4-generic x86_64
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  Date: Fri Jul 10 15:15:17 2015
  InstallationDate: Installed on 2015-07-10 (0 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Alpha amd64 
(20150709)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
-  TERM=linux
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=linux
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-4-generic 
root=UUID=34413d00-2883-4593-a395-7c6b16e3cc6e ro
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

Title:
  ubuntu-server daily iso - Upon installation, /etc/network/interfaces
  not populated with correct network interface names, so networking
  fails to start

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to