Hi David,This ticket is for the source-list, which is for dns resolver and the
config is as follows.
version: 1
config:
- type: physical
name: eth0
- type: nameserver
address: ['xx.xx.xx.xx'] sortlist: ['xx.xx.xx.xx', 'xx.xx.xx.xx'] I
believe the only thing that is needed for
** Also affects: openvswitch
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698181
Title:
Switch to netplan renderer in Artful
To manage notifications
Hi Scott,I know you're aware of and dealing with netplan issues, but not
if you're directly involved with it. But netplan has serious
deficiencies and nowhere near as inclusive or as capable as the current
system. Functions such as source-based routing, open vswitch support,
etc. One release
For 17.10 forward, due to netplan being incomplete and lacking too many
features, it is unsuitable for production use. What packages need to be
added/removed to drop netplan and restore full network functionality as
it existed in 16.04?
--
You received this bug notification because you are a
You mention that all the examples can already be done by netplan, yet
one, he mentioned was modifying iptables, something I use myself, and
have yet to find that anywhere in netplan.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hey Scott,
Been taking a deep dive into the netplan package, a la 17.10. Less than 20
minutes review, and can already see 1/2 dozen things that aren't implemented
and will completely break networking in just my environment. Given its current
state, I can't believe they even allowed it into
Damn, I just realized, netplan doesn't use ifup and ifdown now, does it?
That's going to completely break my source-based routing. The important
part is as follows:
IF_GATEWAY="$(echo "$IF_ADDRESS" | cut -d. -f1-3).254"
ip route flush table "$IFACE"
ip route add default via "$IF_GATEWAY" table
Hey Scott, was going back and forth a bit with Stephane. Something
goofy stil, as I was using ubuntu-daily:artful, which should have
actually failed, cause daily doesn't have artful, but has 17.10, and
images:, is the opposite. so even though I specified ubuntu-daily, it
seemed to still be using
Well, build with the ubuntu-daily, and there weren't even any files at
/var/lib/cloud. I put up a post in lxc/lxd to inquire whether the image
actually supports cloud-init under lxd with the new version. network-
config, user-data, vendor-data, etc were all missing and non-functioning
under lxd.
Appreciate that. I always forget about daily. So spun it up, and due to
netplan, everything networking broke, as in network-config was ignored, and
cloud-init couldn't use any of it. I'm guessing that netplan is supported
using Networking Config Version 2 — Cloud-Init 17.1 documentation? I
Hi Scott,Not sure if launchpad sends you notice of updates or not. Let me know
if it does. Was surprised that this message came from your actual address, so
you sent, or that's just how launchpad works, but added some comments on the
ticket for you to see. I might be able to use packer to
hmm...launchpad doesn't let me edit, so adding this from systemd-resolve
docs:
Alternatively, /etc/resolv.conf may be managed by other packages, in
which case systemd-resolved will read it for DNS configuration data. In
this mode of operation systemd-resolved is consumer rather than provider
of
While I joked about it on github, it looks like sortlist from resolv may
very well be superceded by RFC 3484 when falling under systemd-resolve.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704402
Trying to do some testing real quick and research on systemd-resolve.
Unfortunately it doesn't seem there is a cloud-init enabled version of
artful yet on ubuntu: to really test. I have looked at what systemd-
resolve is doing with it on 16.10 and earlier, and systemd-resolve seems
to be
3 months and not a single response?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704402
Title:
dns-sortlist not recognized in network-config
To manage notifications about this bug go to:
Is this site even monitored?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704402
Title:
dns-sortlist not recognized in network-config
To manage notifications about this bug go to:
Beuller?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1704402
Title:
dns-sortlist not recognized in network-config
To manage notifications about this bug go to:
Public bug reported:
I'm using LXD with Ubuntu images, and cloud-init to do initial setup of
container. I'm not sure, but I believe the issue is in cloud-init, but
would appreciate a pointer to the right location if not. Currently
using network-config meta data, cloud-init takes the following
18 matches
Mail list logo
