[Bug 1787603] [NEW] netplan device order does matter (has been fixed in past)
Marcus Wellnitz
1787603 at bugs.launchpad.net
Fri Aug 17 14:35:36 UTC 2018
Public bug reported:
defining a bridge device _before_ the ethernet devices triggers an
error:
`netplan apply`failes if you specify a virtual devices before their
member devices.
Was fixed in the past according to this bug report:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1670495
Problem: When deploying via ansible the order is mixed up. In my case
'bonds' are always before 'ethernets' and netplan fails
affects:
* 18.04 LTS (Bionic Beaver)
* netplan.io 0.36.3
* netplan.io 0.36.1
** Affects: nplan (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nplan in Ubuntu.
https://bugs.launchpad.net/bugs/1787603
Title:
netplan device order does matter (has been fixed in past)
Status in nplan package in Ubuntu:
New
Bug description:
defining a bridge device _before_ the ethernet devices triggers an
error:
`netplan apply`failes if you specify a virtual devices before their
member devices.
Was fixed in the past according to this bug report:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1670495
Problem: When deploying via ansible the order is mixed up. In my case
'bonds' are always before 'ethernets' and netplan fails
affects:
* 18.04 LTS (Bionic Beaver)
* netplan.io 0.36.3
* netplan.io 0.36.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1787603/+subscriptions
More information about the foundations-bugs
mailing list