touch-packages team mailing list archive

[Ryan Harper <1524452@xxxxxxxxxxxxxxxxxx>]

If anyone wants to reproduce:

1.  uvt-simplestreams-libvirt sync release=trusty arch=amd64
2.  uvt-kvm create --memory 1024 --cpu 2 --disk 10 t1 release=trusty
3. uvt-kvm wait --insecure t1
4. uvt-kvm ssh --insecure t1
# inside t1 vm
5. edit /etc/network/interfaces to look like:
auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet static
    gateway 10.0.2.1
    address 10.0.2.100/24
    mtu 1492

auto eth1:1
iface eth1:1 inet static
    dns-nameservers 8.8.8.8
    address 10.0.2.200/24
    mtu 1492

6.  sudo init 0   # shutdown vm

# back on host
7. virsh edit t1

Add another interface by injecting into the <devices> section

 <interface type='network'>
      <source network='default'/>
      <model type='virtio'/>
    </interface>

8. virsh start --console t1

You'll watch and see the 120 second block upon boot.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1524452

Title:
  TrustyTestNetwork boots with cloud-init-nonet timeout

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  $ grep -ri "gave up waiting" --include "*-serial.log" output.success1/
  output.success1/TrustyTestNetwork/logs/boot-serial.log:cloud-init-nonet[133.62]: gave up waiting for a network device.

  This reproduces with:
  ./tools/jenkins-runner -vv tests/vmtests/test_network.py:TrustyTestNetwork

  basically something is causing networking to not automatically come up
  there.

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