[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#896463: autopkgtest-build-lxc times out waiting for network-online.target



Hi Ferenc,

Thanks for reporting your issues and sorry for not responding earlier.

On Sat, 21 Apr 2018 12:15:28 +0200 =?utf-8?q?Ferenc_W=C3=A1gner?=
<wferi@debian.org> wrote:
> --- /usr/bin/autopkgtest-build-lxc	2018-04-18 10:44:36.000000000 +0200
> +++ /home/wferi/autopkgtest-build-lxc	2018-04-19 18:36:05.937432180 +0200
> @@ -123,7 +123,7 @@
>      }
>  
>      # wait until a systemd based container has networking
> -    if ! echo '[ ! -d /run/systemd/system ] || systemctl start network-online.target' | timeout 60 lxc-attach --name=$1 -- sh -e; then
> +    if ! echo '[ ! -d /run/systemd/system ] || systemctl start network-online.target' | lxc-attach --name=$1 -- sh -e; then
>          echo "Timed out waiting for container to start network-online.target" >&2
>          exit 1
>      fi
> 
> That is, simply removing "timeout 60".

I fear that this may work for you, but isn't robust. I think we want
some form of timeout there to prevent infinite hang-ups.

> Maybe an alternate solution could be designed by installing a systemd
> service in the guest to run the setup-testbed and customize scripts
> without requiring these lxc-attach commands.  Just an idea, I'll be
> happy with any fix you prefer.

I think this isn't a great solution either, as that means we depend on
systemd in the guest. I don't think we should (yet?).

Maybe pitti can confirm both my statements.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: