Upload of netplan.io 0.35 that resolves this is in bionic unapproved
queue now. Once that lands, I'll reupload finish-install.
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: finish-install (Ubuntu)
Status: Fix Released => Triaged
--
You
Looks good. I did a full code review, and while there is DBus use, and
this is a daemon that runs as root, the DBus code is minimal and only
serves to trigger running non-DBus code when a particular signal is
received. Similarly, the sd_notify (socket code) implementation is
limited to telling
Public bug reported:
Any .yaml file in /run/netplan are wiped out when 'netplan generate' is
run. This is wrong, we might actually want to have .yaml files there for
netplan configuration.
What we don't want, however, is for generated wpa-*.conf files to be
left around: wpasupplicant
Indeed; but this is meant to be that way -- there is no usefulness in
having a network device listed in the file without any configuration, as
you can always just do "ip link set $device up" to bring it up.
If there is no configuration, the device is left alone, as it should be.
If you must have
Your original config in comment #1 is correct: you must specify the
underlying devices, because those names are matched later for
"interfaces:" in the bond config.
The issue with 802.3ad is likely a driver issue or a bug in systemd; the
right mode needs to be set by networkd (which may require
Moving this bug to the netplan project since the Ubuntu package got
renamed from 'nplan' to 'netplan.io'.
** Package changed: nplan (Ubuntu) => netplan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There's a WIP branch here:
https://github.com/CanonicalLtd/netplan/pull/18
** Changed in: nplan (Ubuntu)
Status: Confirmed => In Progress
** Changed in: nplan (Ubuntu)
Importance: Undecided => Medium
** Changed in: nplan (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel
In this case you may set:
accept-ra: no
In your netplan YAML; this will at least set IPv6AcceptRA=no, which
should be sufficient for the bridge to come up, and is already available
in netplan 0.34.1 (in Ubuntu 18.04)
Controlling LinkLocalAddressing= will remain as a TODO.
** Changed in: nplan
This got landed, but the rename means the bug wasn't closed
automatically. Closing:
netplan.io (0.34) bionic; urgency=medium
* New release 0.34 (LP: #1754019):
* Implement "optional: true" to correctly write systemd network definitions
with "RequiredForOnline=false", so that these
Package in Ubuntu was renamed from nplan to netplan.io; but regardless
this bug is relevant to the netplan project in general; just moving bugs
around here.
** Package changed: nplan (Ubuntu) => netplan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1738998 ***
https://bugs.launchpad.net/bugs/1738998
Marking this as a duplicate of bug 1738998 to set ClientIdentifer=mac.
SendHostname=true is already the default.
** This bug has been marked a duplicate of bug 1738998
netplan does not allow dhcp client
This would be a systemd-networkd bug, which I suspect might have already
been fixed too. Reassigning to systemd.
** Package changed: nplan (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1745597 ***
https://bugs.launchpad.net/bugs/1745597
This looks like a duplicate of bug 1745597; marking it as such.
** This bug has been marked a duplicate of bug 1745597
mii-monitor-interval unit is undocumented, and may be wrong
--
You received this
Public bug reported:
netplan 0.35 would include an additional command:
netplan try
This would be used to allow users to automatically attempt to apply any
config that can be safely programmatically revert in the case of
failure, and presenting the user with a prompt to acknowledge the
changes.
MIR approved.
The new version synced from debian in bionic (UNAPPROVED) looks good
now, and appears to have corrected test suite issues:
18057438 | X- | volume-key | 0.3.9-4 | 6 hours
| * volume-key/0.3.9-4 Component: universe Section: misc
** Changed in:
NetworkManager absolutely supports all kinds of network devices,
including Bluetooth, DSL/PPPoE, Infiniband, Bond, Bridge, IP tunnels,
Teamed devices, VLANS, etc. If GNOME software doesn't support it, that's
their decision / a bug. You can use 'nm-connection-editor', the real
connection editor
What's the point of having 'kernel'? You have a boolean here
specifically because you'll likely want to override the default,
whatever it might be. I'm fine with *not writing* accept-ra if that
helps, but for most cases, this is just the kind of option that people
should avoid touching.
FWIW, as
unbound attempts to add itself as a local resolver (pointing to
127.0.0.1). I think this will require specific integration work so that
unbound can properly update/ tell systemd-networkd that it wants to be
able to serve as a resolver.
** Changed in: squid3 (Ubuntu)
Status: New => Invalid
squid3: same story as sendmail, uses update-libc.d to get notified of
nameserver changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf with systemd needs
sendmail only uses an update-libc.d script to reload the daemon on
changes to resolv.conf, which should be sufficient for DNS resolution to
remain working as it did with resolvconf; seeing as the nameserver will
generally not change from 127.0.0.53
** Changed in: sendmail (Ubuntu)
Status:
Any news on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749228
Title:
Installing from sd card fails on some hardware
To manage notifications about this bug go to:
Have the tests been fixed? I really don't much like having things in
main that run tests but don't use the result; is there any way to just
ignore the test(s) that are really broken and otherwise keep the
remaining tests failing the build if they fail, such that we can catch a
possible regression?
Verified nplan 0.32~17.10.3 for artful:
Verified nplan 0.32~16.04.4 for xenial:
nplan behaves as expected when the keyword "optional: yes" is set;
device gets ignored by systemd-networkd-wait-online; which will report
the correct status based on whether other devices are providing a
connection.
The bug identified was not a regression from the SRU. We still need
testing on this stable update.
** Tags removed: verification-failed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437353
Thanks for letting us know!
This bug was identified automatically as a regression, so I'm adding
'bot-stop-nagging' tag here for the bot to also recognize it's not a
regression from the current in-flight stable update.
** Tags added: bot-stop-nagging
--
You received this bug notification
What about if you pass:
wifis:
wlp1s0:
dhcp4: yes
access-points:
"My Open Network": {}
This is non-obvious though, we should fix the doc to clarify.
** Package changed: nplan (Ubuntu) => netplan.io (Ubuntu)
** Changed in: netplan.io (Ubuntu)
Status: New =>
@Matt,
@Russell,
Is the package is xenial-proposed something you could help verifying? I
do not have access to hardware that would exhibit this issue; it would
help greatly in providing the fix to have someone with this hardware
follow the steps in
Go for it; the confusion from this message is greater than the benefit
to the very tiny set of users who might run into issues this is meant to
catch.
ie. automated partitioning will already DTRT; and people who write their
own partitions and don't add an ESP are presumed to already know what
pv is small and straightforward. Its own unit tests are run as part of
the build, and has a bug subscriber. However, it does appear to use IPC.
I've reviewed as much of it as I could and it looks like the code is
prudent, taking extra steps to check for errors, etc. Still, I think it
would be
At a glance, the tests should be runnable; please enable them if
possible.
Given the use of OpenSSL, and previous issues with DH length, let's have
this reviewed by the Security team.
** Changed in: socat (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
** Changed
Looks like the current behavior should be sufficient for postfix to
integrate as well as it did with resolvconf: marking this Invalid.
** Changed in: postfix (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
postfix takes a copy of resolv.conf for its own use, in its own queue
directory. This is already well integrated by way of either resolvconf
triggering the copy on changes (using update-libc.d) or by if-up / if-
down. This will need work to "improve" the integration story; however
postfix should
dhcpcd5 is redundant as a DHCP implementation in Ubuntu; but it does
"integrate" with resolvconf by way of its own shipped dhcpcd-
hooks/20-resolv.conf. It does check before calling 'resolvconf -a' and
'resolvconf -d' to add/remove its own interface file; and uses this hook
file in order to
libbluray is missing a bug subscriber.
** Changed in: libbluray (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/1746629
Title:
[MIR] libbluray
To manage
** Changed in: netplan
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756322
Title:
'netplan apply' fails when trying to activate another interface on
another
I reviewed the code, nothing jumps out as being terrible; there's a bug
subscriber, and tests being run as part of the build.
MIR approved.
** Changed in: pyxs (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is straightforward and obvious, same u2f rules as were previously
in udev itself.
MIR approved for the binary only: libu2f-udev
** Changed in: libu2f-host (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: libu2f-host (Ubuntu)
Assignee: Mathieu Trudel-Lapie
Wild guess is this is a test that expects user input, and the input
never shows up?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754422
Title:
[MIR] volume-key
To manage notifications about this
** Changed in: libu2f-host (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: libu2f-host (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed in netplan 0.34
** Package changed: nplan (Ubuntu) => netplan.io (Ubuntu)
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status: Incomplete => Fix Committed
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
** Description changed:
[Impact]
MAAS commissioning may fail when deploying Xenial images or using grubx64.efi
from Xenial due to hardware particularities of some Intel 82599-based network
cards. Other network manufacturers may be affected as well. The main failure
mode appears to be an
** Description changed:
[Impact]
MAAS commissioning may fail when deploying Xenial images or using grubx64.efi
from Xenial due to hardware particularities of some Intel 82599-based network
cards. Other network manufacturers may be affected as well. The main failure
mode appears to be an
Reviewed the whole thing, there is now a bug subscriber. There's some
crypto use but all through other libraries we've already MIRed (or in
progress), and none of it looks crazy. MIR approved.
(This is still going to be blocked on python-nacl though...)
** Changed in: pymacaroons (Ubuntu)
Unassinging myself. I'm not working on this.
** Changed in: libappindicator (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
So, what is the outcome of this?
** Changed in: ujson (Ubuntu)
Assignee: (unassigned) => James Page (james-page)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737989
Title:
[MIR] ujson?
To
pyparted tests are now run, I did a quick re-review of the package. MIR
approved.
** Changed in: pyparted (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
MIR approved.
** Changed in: rax-nova-agent (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753754
Title:
[MIR] rax-nova-agent
To manage notifications
bolt is still missing a team subscriber.
** Changed in: bolt (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/1752056
Title:
[MIR] bolt
To manage
Assigning to security as per the description...
** Changed in: thunderbolt-tools (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking incomplete so it still shows in my list, but is more clearly
already looked at and NAKed by Security.
** Changed in: chrome-gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verification-done for xenial (nplan 0.32~16.04.4):
I am unable to validate ath6kl_sdio behavior directly on hardware (I do
not have such hardware available), but the right stanza is present in
the netplan script to skip over ath6kl_sdio.
--
You received this bug notification because you are a
Verification done for xenial (nplan 0.32~16.04.4):
Verification done for artful (nplan 0.32~17.10.3):
Verified that the configuration supplied in the test case is accepted by
netplan and correctly results in a bridge being brought up with a port-
priority of "14" for eth0, and a bridge priority
This was already fixed in bionic; closing as Fix Released the top-level
task.
** Changed in: nplan (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751814
Verification-done for xenial (nplan 0.32~16.04.4):
Verification-done for artful (nplan 0.32~17.10.3):
Verified that the documentation correctly lists resend-igmp and
clarifications for globbing and macaddress:. The unsupported "channel"
keyword is not listed.
** Tags removed: verification-needed
Verification-done for xenial (nplan 0.32~16.04.4):
Verification-done for artful (nplan 0.32~17.10.3):
Verified that the configuration examples in netplan manpage/doc
correctly escape (in quotes) IPv6 addresses.
** Tags removed: verification-needed verification-needed-artful
Verification-done for artful (nplan 0.32~17.10.3):
The netplan manpage/doc contain the right routes: configuration, it is
no longer shown as a top-level construct.
** Tags removed: verification-needed verification-needed-artful
verification-needed-xenial
** Tags added: verification-done-artful
Verification-done for xenial (nplan 0.32~16.04.4):
The netplan manpage/doc contain the right routes: configuration, it is
no longer shown as a top-level construct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verification done for xenial (nplan 0.32~16.04.4):
I used a dummy service on a new 16.04 install to have snap.network-
manager.networkmanager.service available on the system.
dummy service:
[Unit]
Description=Test
DefaultDependencies=no
Conflicts=shutdown.target
Before=shutdown.target
[Service]
Confirmed; finish-install includes code that only checks for the
presence of /e/n/i.
** Changed in: netcfg (Ubuntu)
Status: Incomplete => Triaged
** Package changed: netcfg (Ubuntu) => finish-install (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
installs here to try to
reproduce.
** Also affects: netcfg (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netcfg (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: netplan
Status: New => Incomplete
** Changed in: netcfg (
Please fix:
- Missing bug subscriber
- Package contains a limited test suite, which gets run at build time, but
failures are ignored (and it does happen to fail)
- crypto/secrets handling should have a security review
** Changed in: volume-key (Ubuntu)
Status: New => Incomplete
**
** Changed in: rax-nova-agent (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/1753754
Title:
[MIR] rax-nova-agent
To manage notifications about this bug go
Wrong team subscriber for the package; it should be subscribed to by
foundations-bugs for the Foundations team.
I've already done review of this software before, and we have had
Security signoff by email. Please fix the subscriber so we can promote
this package.
--
You received this bug
Fix Released for bionic; this landed in netplan.io 0.34 (not shown
because of the package rename):
netplan.io (0.34) bionic; urgency=medium
* New release 0.34 (LP: #1754019):
* Implement "optional: true" to correctly write systemd network definitions
with "RequiredForOnline=false",
There's a bug subscriber, and this is already in main -- closing as Fix
Released so it's finally out of the MIR buglist.
** Changed in: vmdk-stream-converter (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
find in netplan here:
https://bugs.launchpad.net/netplan/+filebug
If you are unsure whether something is a bug, it might well be. If
you're unsure how to do something, you can also look up questions, or
add your own, here:
https://askubuntu.com/questions/tagged/netplan
Thanks,
Mathieu Trudel
Fix Released in netplan 0.34.
** Changed in: netplan
Status: Fix Committed => Fix Released
** Package changed: nplan (Ubuntu) => netplan.io (Ubuntu)
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member
** Changed in: libblockdev (Ubuntu)
Status: New => Fix Committed
** Changed in: udisks2 (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirming this is broken. Dropping the patch 0001-dns-use-DBus-to-make-
dnsmasq-nameserver-changes.patch in network-manager
(1.2.4-0ubuntu0.16.04.1) was done, but it looks like not all the code in
that patch was actually upstream.
** Changed in: network-manager (Ubuntu)
Status: New =>
Ack on libblockdev, provided only the listed binaries are promoted.
udisks2 also deals with crypto even though the libblockdev- packages are
not installed; I do believe it should be reviewed as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
o a source package.
I had another look, let's indeed have this reviewed by the Security
Team.
** Changed in: chrome-gnome-shell (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
** Changed in: chrome-gnome-shell (Ubuntu)
Status: In Pr
** Description changed:
netplan 0.34 introduces new features:
- - optional: true on an interface to allow it to be "ignored" by
networkd-wait-online at boot, and avoid 5 minute delays.
- - added 'help' subcommands everywhere.
- - added bash completion
- - 'netplan ip leases' now allows
build logs:
[amd64]
https://launchpadlibrarian.net/359874933/buildlog_ubuntu-bionic-amd64.netplan.io_0.34_BUILDING.txt.gz
[i386]
https://launchpadlibrarian.net/359874911/buildlog_ubuntu-bionic-i386.netplan.io_0.34_BUILDING.txt.gz
install log:
root@giving-ghost:~# apt install nplan
Reading
Landed in git.
** Changed in: netplan
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735193
Title:
Netplan does not support onlink gateway
To manage
Public bug reported:
netplan 0.34 introduces new features:
- optional: true on an interface to allow it to be "ignored" by
networkd-wait-online at boot, and avoid 5 minute delays.
- added 'help' subcommands everywhere.
- added bash completion
- 'netplan ip leases' now allows retrieving the
bolt does authentication of the devices it should interact with; this
code should be checked. It's straightforward, but I'm not sufficiently
knowledgeable about the protocol to assess it. Reassigning to the
Security Team.
** Changed in: bolt (Ubuntu)
Assignee: (unassigned) => Ubuntu Security
MIR approved
** Changed in: libdazzle (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748905
Title:
[MIR] libdazzle
To manage notifications about this
Go for libmp3lame0, on the condition that CVE-2017-15019 be looked into.
** Changed in: lame (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: lame (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
** Changed in: lame (Ubuntu)
Assignee:
libmpg123-0 's MIR is approved then.
** Changed in: mpg123 (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753450
Title:
[MIR] mpg123
To manage
libtwolame0 is approved.
** Changed in: twolame (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753458
Title:
[MIR] twolame
To manage
** Changed in: twolame (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753458
Title:
[MIR] twolame
To manage
** Changed in: mpg123 (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753450
Title:
[MIR] mpg123
To manage
** Changed in: lame (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753441
Title:
[MIR] lame
To manage notifications
MIR ack for libmpg123-0 if the Security Team acknowledges they are aware
of this requirement.
** Changed in: mpg123 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
MIR ack for libtwolame0 if the Security Team acknowledges they are aware
of this requirement.
** Changed in: twolame (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This package has a long security history, and a currently left-open CVE
because the upload of 3.100 did not include closing the active CVE.
If there's a go-ahead from the Security Team (I'm not looking for a code
review, just an acknowledgement that they are aware of the requirement
for this
nee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747460
Title:
[MIR] py-macaroon-bakery, protobuf, pyrfc3339
To
py-macaroons-bakery looks good to me; MIR approved.
** Changed in: py-macaroon-bakery (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747460
Title:
** Description changed:
+ [Impact]
+ netplan users on Ubuntu Core systems wishing to change netplan configuration
that affects NetworkManager
+
+ [Test cases]
+ 1) Run 'sudo netplan apply'
+ 2) Verify that NetworkManager has been restarted, and no errors were shown on
console.
+
+ [Regression
** Changed in: ubiquity (Ubuntu)
Status: Invalid => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724224
Title:
ubiquity crashed with FileNotFoundError in _execute_child():
** Changed in: nplan (Ubuntu)
Status: New => Triaged
** Changed in: nplan (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752162
Title:
netplan 0.33
This looks a lot like bug 1738998; there's a lot of non-compliant DHCP
servers that are unable to deal with using a unique identified for
Client Identifier, or pre-existing configuration that has yet to be
updated.
The relevant RFC is 4361 [1]; it is meant to address the issues of
replacing
If you copy the files generated by netplan from /run/systemd/network
into /etc/systemd/network and add "ClientIdentifier=mac" under the
"[DHCP]" section, do you then get the behavior you expect from DHCP?
** Changed in: nplan (Ubuntu)
Status: New => Incomplete
--
You received this bug
Whether or not /e/n/i supports something correctly or just happens to
work by sheer luck has no bearing on what is technically correct and
sensical -- let's abstract this, what we need to concern ourselves with
here is netplan, cloud-init and maas.
In the network world, it is absolutely true that
** Description changed:
+ [Impact]
+ Atheros users -- some of our users with wireless devices driven by the
ath6kl_sdio driver; when running 'netplan apply' may wedge the wireless driver
in an unrecoverable state.
+
+
+ [Test case]
+ -- requires ath6kl_sdio hardware --
+ 1) Run 'sudo netplan
That's not the point; the system is also warning you that proceeding
with the install is potentially breaking your setup if there is a pre-
existing partition.
In the past Steve McIntyre changed the code to avoid having this message
show up when dealing with a blank disk; plus further updates
** Description changed:
[Impact]
Netplan users referring to documentation to know how to write configurations.
[Test case]
1) check 'man netplan'
[Regression potential]
None, this change is limited to correcting incorrect documentation.
---
There are various errors
** Description changed:
+ [Impact]
+ Users of netplan configuring any bridge. Port priority is a very common
setting to change when setting up bridge devices that might have multiple
interfaces.
+
+ [Test case]
+ 1) Write a netplan configuration:
+ network:
+ version: 2
+ ethernets:
+
** Description changed:
+ [Impact]
+ Netplan users referring to documentation to know how to write configurations.
+
+ [Test case]
+ 1) check 'man netplan'
+
+ [Regression potential]
+ None, this change is limited to correcting incorrect documentation.
+
+ ---
+
The only reference to routes
1001 - 1100 of 8586 matches
Mail list logo
