This is an issue with Juju rather than MAAS. Juju does this networking
configuration. If eth0 doesn't exist, juju fails because juju makes the
assumption that eth0 always exists
** Changed in: maas
Status: New = Invalid
** Changed in: maas (Ubuntu)
Status: New = Invalid
--
You
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1358586
Title:
fails to deploy machines when eth0 does not exist
To
See also https://bugs.launchpad.net/juju-core/+bug/1335179
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1358586
Title:
fails to deploy machines when eth0 does not exist
To manage
FWIW, the machine in question has this:
cat /proc/net/dev
Inter-| Receive| Transmit
face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo: 0 0000
When you say deploying, do you mean a juju deploy ?
If so this is a juju bug I think as it tries to set up a container
bridge IIRC.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
