Debian Bug report logs - #783202
[adt-buildvm-ubuntu-cloud] timeout nearly after display "Net device info"

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Jörg Frings-Fürst <debian@jff-webhosting.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: [adt-buildvm-ubuntu-cloud] timeout nearly after display "Net device info"

Date: Thu, 23 Apr 2015 21:07:10 +0200

Package: autopkgtest
Version: 3.6jessie1
Severity: grave

Hi,

at $ adt-buildvm-ubuntu-cloud -r vivid -v

I get a timeout always after:

[   24.805304] cloud-init[730]: Cloud-init v. 0.7.7 running 'init' at Thu, 23
Apr 2015 19:45:53 +0000. Up 19.94 seconds.
[   24.805553] cloud-init[730]: ci-info:
+++++++++++++++++++++++++++++++++++++Net device
info++++++++++++++++++++++++++++++++++++++
[   24.805739] cloud-init[730]: ci-info:
+--------+------+----------------------------+---------------+-------+-------------------+
[   24.805920] cloud-init[730]: ci-info: | Device |  Up  |          Address
|      Mask     | Scope |     Hw-Address    |
[   24.806099] cloud-init[730]: ci-info:
+--------+------+----------------------------+---------------+-------+-------------------+
[   24.806279] cloud-init[730]: ci-info: |  eth0  | True |         10.0.2.15
| 255.255.255.0 |   .   | 52:54:00:12:34:56 |
[   24.806457] cloud-init[730]: ci-info: |  eth0  | True |
fe80::5054:ff:fe12:3456/64 |       .       |  link | 52:54:00:12:34:56 |
[   24.806632] cloud-init[730]: ci-info: |   lo   | True |         127.0.0.1
|   255.0.0.0   |   .   |         .         |
[   24.806809] cloud-init[730]: ci-info: |   lo   | True |          ::1/128
|       .       |  host |         .         |
[   24.806983] cloud-init[730]: ci-info: +--------+--

timed out on cloud-init
qemu: terminating on signal 15 from pid 9400




-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-updates'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages autopkgtest depends on:
ii  apt-utils       1.0.9.8
ii  libdpkg-perl    1.17.25
ii  procps          2:3.3.9-9
ii  python3         3.4.2-2
ii  python3-debian  0.1.27

Versions of packages autopkgtest recommends:
ii  autodep8  0.1

Versions of packages autopkgtest suggests:
pn  lxc          <none>
ii  qemu-system  1:2.1+dfsg-11
ii  qemu-utils   1:2.1+dfsg-11
ii  schroot      1.6.10-1+b1

-- no debconf information

Message #12 received at 783202@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: Jörg Frings-Fürst <debian@jff-webhosting.net>, 783202@bugs.debian.org

Subject: Re: Bug#783202: [adt-buildvm-ubuntu-cloud] timeout nearly after display "Net device info"

Date: Fri, 4 Mar 2016 12:14:55 +0100

Control: tag -1 moreinfo unreproducible

Hello Jörg,

Jörg Frings-Fürst [2015-04-23 21:07 +0200]:
> I get a timeout always after:
> [   24.805304] cloud-init[730]: Cloud-init v. 0.7.7 running 'init' at Thu, 23

Sorry for the very late response, just spotted that on bug review. I
haven't seen this myself so far, does that still happen with current
autopkgtest from unstable/current cloud images?

Thanks,

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Message #19 received at 783202@bugs.debian.org (full text, mbox, reply):

From: Barry Warsaw <barry@debian.org>

To: 783202@bugs.debian.org

Date: Tue, 10 Jan 2017 14:11:57 -0500

I've run into this --or something similar-- too.

$ autopkgtest-buildvm-ubuntu-cloud -v

When you run this on an Ubuntu 17.04 (zesty) host, it finishes quickly and
leaves you with a nice autopkgtest-zesty-amd64.img.  When you run the same
command on an Ubuntu 16.10 (yakkety) host, it hangs and eventually times out.

I've seen it hang in different spots, so I'm not sure what's going on, but
usually when it times out, it does indicate a timeout in cloud-init.  E.g.

[   60.843487] cloud-init[1416]: Found kernel: /boot/vmlinuz-4.9.0-11-generic

--> hangs here for a long time, but eventually returns

         Starting Cleanup of Temporary Directories...
[  OK  ] Started Cleanup of Temporary Directories.

--> hangs here for a long time

timed out on cloud-init
qemu-system-x86_64: terminating on signal 15 from pid 6948

Send a report that this bug log contains spam.