curtin

Bug #1703689
Comment #5

Comment 5 for bug 1703689

Revision history for this message

Ryan Harper (raharper) wrote on 2017-07-17: Re: [Bug 1703689] Re: [2.2.1] When deploying servers with VLAN using IPv6 alias ifdown fails with cannot find device

On Mon, Jul 17, 2017 at 2:51 PM, Ben <email address hidden> wrote:

> The interfaces do function correctly after manual intervention even with
> the errors but my problem, from what I understand about MAAS is the
> following
>
> root@server01:/etc/network# ifdown enp2s0f0.11
> Removed VLAN -:enp2s0f0.11:-
> Cannot find device "enp2s0f0.11"
>

> is enough to stop the bridges from being constructed correctly. I hope
>

This sounds fatal; can you confirm the return code?

ifdown enp2s0f0.11; echo $?

> someone from the MAAS team can step in here with a little more detail on
> why it fails completely because of this error. This has not been an
> issue with previous versions of MAAS. I get the interfaces.new file
> with all the correct settings but it is never copied to interfaces and
> the network is not brought down and back up to load the new
> configuration. I have to manually do the interface.new to interfaces
> copy and reboot to get the interfaces to function correctly.
>

The reconfiguration of the network files is done by JUJU; let's see if they
can shed some light here on how they're doing their network configuration
modifications.

When the vlan ifdown script (/etc/network/if-down.d/vlan) is called a
second time (one for each iface stanza, there is a v4 and a v6 stanza in
/etc/network/interfaces
for the two IP configurations on the vlan in question) the vlan device is
already deleted. This is expected and in my testing, it shows to be
non-fatal but noisy.

# ifdown ens4.11; echo $?
Removed VLAN -:ens4.11:-
Cannot find device "ens4.11"
ERROR: trying to remove VLAN -:ens4.11:- error: No such device
run-parts: /etc/network/if-post-down.d/vlan exited with return code 4
0

The vlan hook exits non-zero, but ifdown returns 0. And functionally
the vlan interface is no long present.

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703689
>
> Title:
> [2.2.1] When deploying servers with VLAN using IPv6 alias ifdown fails
> with cannot find device
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1703689/+subscriptions
>

On Mon, Jul 17, 2017 at 2:51 PM, Ben <bjenkins@ally.technology> wrote:

> The interfaces do function correctly after manual intervention even with
> the errors but my problem, from what I understand about MAAS is the
> following
>
> root@server01:/etc/network# ifdown enp2s0f0.11
>   Removed VLAN -:enp2s0f0.11:-
>   Cannot find device "enp2s0f0.11"
>

> is enough to stop the bridges from being constructed correctly.  I hope
>

This sounds fatal; can you confirm the return code?

ifdown enp2s0f0.11; echo $?

> someone from the MAAS team can step in here with a little more detail on
> why it fails completely because of this error.  This has not been an
> issue with previous versions of MAAS.  I get the interfaces.new file
> with all the correct settings but it is never copied to interfaces and
> the network is not brought down and back up to load the new
> configuration.  I have to manually do the interface.new to interfaces
> copy and reboot to get the interfaces to function correctly.
>

The reconfiguration of the network files is done by JUJU; let's see if they
can shed some light here on how they're doing their network configuration
modifications.

When the vlan ifdown script (/etc/network/if-down.d/vlan) is called a
second time (one for each iface stanza, there is a v4 and a v6 stanza in
/etc/network/interfaces
for the two IP configurations on the vlan in question) the vlan device is
already deleted.   This is expected and in my testing, it shows to be
non-fatal but noisy.

The vlan hook exits non-zero, but ifdown returns 0.    And functionally
the vlan interface is no long present.

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703689
>
> Title:
>   [2.2.1] When deploying servers with VLAN using IPv6 alias ifdown fails
>   with cannot find device
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1703689/+subscriptions
>