I'll add an ifupdown bug task for you.
> If "auto dummy0" and "ifup dummy0" are not maintained then why
bother to have a dummy device at all?
We haven't discussed that, since that wasn't the failing use case you
presented in your original report! I appreciate that you narrowed down
the root cause to your reported change in behaviour in ifconfig, but for
judging importance and priority, it is the use case that matters.
Please could you provide full steps to reproduce your ifupdown use case
that works in Xenial but fails in Bionic? Including a sample
/etc/network/interfaces, details of why you're using dummy0, what
documentation directed you to do that, etc. Then we can refer to the
same understanding of your situation as a starting point.
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ifupdown (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828749
Title:
ifconfig dummy0 : Device not found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1828749/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
