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 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 notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1358586/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
