Yes, that's because it doesn't appear like the issues you have are a
regression caused by the updates, and we don't know what's wrong. You
have a bug open for your issue, and we still need to figure out what
doesn't work there.
--
You received this bug notification because you are a member of Ubu
@Marcos:
Please file a new bug for your own issue; include the output of
'networkctl', and report the bug number here so we can find it.
>From a quick look, I think there's no carrier detected. This could be a
driver bug.
--
You received this bug notification because you are a member of Ubuntu
Please use bug 1768827 to track such "no IP at boot" issues; there's
nothing that currently indicates that this is a regression, it needs
further investigation, but not here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
For context:
It looks like the issue is really with the call to
"set_handler_for_input_source()" on a plugin. renderer->plugin_interface
is null, so dereferencing that fails:
https://paste.ubuntu.com/p/tmcVcvgGXw/
All in all, much easier to comprehend when I think of looking at the
disassembly,
Actually, according to the backtraces the issue isn't with
renderer->backend; we're not even reaching that point. It's still a
potential issue though.
Same ppa as before: ppa:cyphermox/ppa
I have uploaded a new plymouth there, which should mitigate the crash
exactly as reported in the description
But does it fix the crash for you? You shouldn't worry about the dates
on the files, those are in part caused by the changelog entry when
building the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathi
s time, at the very least until the
package's lintian warnings are fixed and the package modernized to use /
provide python3 bindings instead of python2; and a clear list of the
binary packages to be promoted.
--
Mathieu Trudel-Lapierre
Freenode: cyphermox, Jabber: mathieu...@gmail.com
4096R/65B
** Changed in: gpsd (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
** Changed in: gpsd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
So, the patch would apply, but you're not seeing the error messages that
I expect you should be seeing if that was the problem. We can certainly
try to apply the patch (I will make it available in a PPA), but I'm not
sure that will help.
For one thing, you are using the same grub in both cases, an
The package versions we need are for grub-efi-amd64 and grub-efi-
amd64-signed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage no
We rolled back shim; this would now be regression-proposed.
** Changed in: shim-signed (Ubuntu)
Status: New => Triaged
** Changed in: shim-signed (Ubuntu)
Importance: Undecided => Critical
** Changed in: shim-signed (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel
* Changed in: shim (Ubuntu Bionic)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711203
Title:
Deployments fail when Secure Bo
** Also affects: grub2 (Ubuntu)
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/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage notifi
** Also affects: grub2-signed (Ubuntu)
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/1792575
Title:
Boot failure with efi shims from 20180913.0
To manage
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Triaged
** Changed in: netplan.io (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/1785493
Title:
This is identified as a proper "typo" bug in grub, fixing.
** Description changed:
+ [Impact]
+ Dual-boot installs of Ubuntu and Windows 10, and other instances of
chainloading another bootloader from grub2.
+
+ [Test cases]
+ 1) Install Windows 10
+ 2) Install Ubuntu in a dual-boot setup with
Not a regression in shim -- shim is doing what it should, but exposes an
actual latent bug in the grub2 EFI patchset. This is still in progress.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790724
T
@Alan, could you please confirm which version of plymouth you have
installed for the tests you did?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Login password from GDM is s
That's not what I mean though. For SRU verification we should aim to
have a positive identification of the exact version of the plymouth
package that was used for the tests.
For example, this can be achieved by looking at 'dpkg -l plymouth |
cat':
要望=(U)不明/(I)インストール/(R)削除/(P)完全削除/(H)保持
| 状態=(N)無/
Public bug reported:
[Impact]
All users of Ubuntu with network configurations using netplan.yaml.
[Test case]
[Regression potential]
---
Let's backport netplan.io 0.40 to bionic; as per policy for netplan.io
releases.
Given that it's a core component of the networking story, and new
features
** Description changed:
[Impact]
All users of Ubuntu with network configurations using netplan.yaml.
[Test case]
[Regression potential]
-
---
Let's backport netplan.io 0.40 to bionic; as per policy for netplan.io
releases.
Given that it's a core component of the net
Sponsored the package.
Woodrow, for next SRU uploads like this (which is effectively a
backport), or for other SRUs, please update the version number to be
above the one already in the archive, but below the version number for
the next release. For example:
in bionic right now: 0.79-2build1
the S
@Alan,
Can you confirm which version of plymouth you had installed?
You can use the following command to do so:
dpkg -l plymouth | cat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767918
Title:
Desktop team NAKed maintaining it, and it looks like reverse-
dependencies would need changes (and for one, having written the nm-
applet patch, I rather this be removed to use standard status icon code
than appindicators). Setting to Incomplete.
If this needs to be in main to support software, pl
What is the status of this MIR? Is it still required to provide some
feature?
Changes were requested, they don't appear to be all done, but I wouldn't
necessarily block on needing to use something other than JAM if the
maintainability of the pacakge is good.
** Changed in: argyll (Ubuntu)
Bug was confirmed fix, although we don't have a formal version number
for the pacakge that was tested, let's mark this verification-done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are
** Description changed:
+ [Impact]
+ Chainloading grub via grub in a netboot context using MAAS's Boot to local
disk feature.
+
+ [Test cases]
+ 1) Deploy UEFI system using MAAS
+ 2) After deployment, have the system reboot to local disk (via netboot).
+
+ [Regression potential]
+ It is possibl
** Description changed:
+ [Impact]
+ Ubuntu users configuring a custom umask on their system
+
+ [Test case]
+ 1) set UMASK in /etc/login.defs to 077
+ 2) Configure netplan to use the networkd renderer, run 'sudo netplan apply'.
+ 3) Verify that systemd-network applies the correct network configu
** Description changed:
+ [Impact]
+ All netplan users.
+
+ [Test case]
+ 1) Run 'sudo netplan try' to "try" a new netplan config.
+ 2) Hit Control-C during the timer, to escape to the terminal without applying
the configuration.
+
+ Validate that text typed on the terminal after hitting Contro
** Description changed:
+ [Impact]
+ Ubuntu users who make use of IPv4 link-local addresses.
+
+ [Test case]
+ 1) Add 'link-local: [ ipv4 ]' to the netplan configuration.
+ 2) Run 'sudo netplan apply'
+
+ [Regression Potential]
+ Enabling link local means additional addresses are available on th
** Description changed:
+ [Impact]
+ netplan.io users who define custom routes
+
+ [Test case]
+ 1) Configure netplan.
+ 2) Add a route:
+ [...]
+ routes:
+ - to: 10.10.10.0/24
+ scope: link
+
+ 3) Validate that the route is correctly added to the routing table
+ (using 'sudo ip ro
** Changed in: netplan
Status: In Progress => 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/1736975
Title:
netplan does not bring up anonymous bridge on boot
To manage notificat
** Description changed:
+ [Impact]
+ Netplan users setting up bridges.
+
+ [Test cases]
+ 1) Add a new bridge configuration in netplan yaml, without an IP address set:
+
+ [...]
+ bridges:
+ br0:
+ interfaces: [ interface ]
+ dhcp4: false
+ parameters:
+ stp:
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Released
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bug
** Description changed:
[Impact]
All users of Ubuntu with network configurations using netplan.yaml.
[Test case]
+ 1) Configure network via netplan.yaml for the feature one wants to verify.
+
+ Individual bugs have been opened for separate bugs fixed / features
+ added.
+
+ 1) Run autop
netplan.io 0.40 in cosmic contains this fix.
** Description changed:
+ [Impact]
+ Users configuring IPv6 static address with NetworkManager as a backend.
+
+ [Test cases]
+ 1) Configure netplan for static addresses for IPv6, dns settings, but no IPv4
configuration:
+
+ [...]
+ ens8:
+
netplan.io 0.40 landed in cosmic.
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => 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/1793309
Title:
Backport netplan.io 0.40 t
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Released
** Description changed:
+ [Impact]
+ All Ubuntu users.
+
+ [Test case]
+ 1) Look at the netplan manpage:
+
+ man netplan
+
+ 2) Verify that th
** Changed in: netplan
Status: Fix Committed => 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/1771440
Title:
"//" at beginning of YAML file path when error in network config foun
** Changed in: netplan
Status: In Progress => 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/1771704
Title:
support for ipv4 link-local addressing
To manage notifications about t
** Changed in: netplan.io (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/bugs/1768798
Title:
netplan try: terminal does
** Description changed:
- ## DRAFT ##
-
[Impact]
-
- "netplan ip leases " command is failing with a Traceback[1]
- when specifying an interface non-existing on the system. non-dhcp
- configured or non configured with netplan.
+ "netplan ip leases " command is failing with a Traceback[1] when
** Description changed:
+ [Impact]
+ Netplan documentation
+
+ [Test case]
+ 1) Run 'man netplan'
+ 2) Validate that the documentation contains a correctly spelled parameter
"gratuitous-arp".
+
+ [Regression potential]
+ This is a documentation-only fix. Watch out for documentation that fails t
plan.io (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/bugs/1768783
Title:
mtu is missing in doc reference (only mentioned in
*** This bug is a duplicate of bug 1766872 ***
https://bugs.launchpad.net/bugs/1766872
It's not quite a duplicate, because this message appears before the
network option is even attempted -- it's a bug in the menu code; but
we'll mark it as a duplicate anyway as it's only really apparent when
Could you please run:
sudo debconf-show grub-pc
sudo debconf-show grub-efi-amd64
I've attempted to reproduce this; by first downgrading to a previous version,
changing settings in /etc/default/grub, and proceeding with the upgrade, but no
matter what I do, the changes do remain in /etc/default
Julian verified this as not reproducing on disco now, with the livecd-
rootfs change. Closing the ubiquity task as invalid.
** Changed in: ubiquity (Ubuntu Disco)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Given the options shown in firmware and switching to AHCI fixes things
as per xnox's comments; this is squarely a "kernel" issue -- one we
can't really fix in ubiquity in any case.
The kernel side, to support this new RAID or "Intel RST" mode comes with
its own set of problems, but I'll let the ke
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821867
Title:
network interface is down after post-install reboot of a default disco
installation
To manage notifications about this bug go
Sounds like what you want is b). If all we need is the font, then also
why is a font bundled with an OAUTH server?
For all intents and purposes, it should be more or less easy to split
out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Setting mailman to Triaged; let's get this off the "New MIRs" list --
it's not new, just not completed yet. mailman3's status nicely captures
this.
** Changed in: mailman (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Thanks. MIR approved.
** Changed in: heat-dashboard (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/1750576
Title:
[MIR] heat-dashboard
To manage
Public bug reported:
>From Seth's security review:
TL;dr: please see if we could replace the use of chown -R with something
else.
"""
I reviewed heat-dashboard version 1.4.0-0ubuntu1 as checked into cosmic.
This shouldn't be considered a full audit but rather a quick gauge of
maintainability.
h
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822007
Title:
Grub fails to request the /grub/grub.cfg over HTTP when booting with
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823259
Title:
Update from grub-common AMD64 2.02-2ubuntu8.12 to 2.02-2ubuntu8.13
r
Okay, I wonder if this could be because GRUB_CMDLINE_LINUX_DEFAULT was
commented out earlier, and there's another entry with the value and
we're maybe not catching this appropriately?
I will try to reproduce this setup here, with the file attachments we
have I should be able to have a closer repro
Public bug reported:
We've moved to using GRUB_TIMEOUT_STYLE=hidden in /etc/default/grub, but
debian/postinst.in still references GRUB_HIDDEN_TIMEOUT variable and
attempts to set that in conffile handling:
case @PACKAGE@ in
grub-pc)
apply_conf_tweaks "$conf_files" merge_debconf_
r-bootstrap3 (Ubuntu)
Status: New => In Progress
** Changed in: twitter-bootstrap3 (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Server
(ubuntu-server)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: grub2-signed (Ubuntu Disco)
Status: Incomplete => Triaged
** Tags removed: rls-cc-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805490
Title:
Grub2 Failed to install
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed
--
You received this bug notification beca
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This does not need re-testing, already in bionic/cosmic, just closed
again due to changelog for this big backport.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs
This is still verification-done for bionic; re-upload was to skip some
failing tunnel tests due to a difference in kernel behavior.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a memb
This hasn't changed in bionic; previously released SRU which is again
included in the changelog for this backport.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs
Verification-done for xenial:
ubuntu@noted-fish:~$ sudo apt install shim-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
sbsigntool
The following packages will be upgraded:
sbsigntool sh
Verification-done trusty:
ubuntu@profound-donkey:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.6 LTS
Release:14.04
Codename: trusty
ubuntu@profound-donkey:~$ sudo apt install shim-signed
Reading package lists... Done
Building depe
There is no dependency on v239 for netplan backports. Bionic ships with
v237 (and some patches); the dependency on systemd is for >=
235-3ubuntu3 in netplan.io. I do not believe a newer version than that
is required.
Alexey, I really appreciate the work done to make such a backport
available, but
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811868
Title:
networkd/NetworkManager are not re-started on netplan apply when
config files are removed
To manage notifications about this b
That is up to the Ubuntu Core team to do; but before they can do it it
needs to be landed in the archive for classic :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739578
Title:
Missing support f
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776228
Title:
Duplicate default routes on VMs with multiple NICs
To manage notifications about this bug go to:
https://bugs.launchpad.net/netp
This means we'll need to identify what patches need to be applied on top
of v237 to make this work.
Is this crippling? Are we able to verify that dhcp customization work
despite anything missing in systemd? I think it's the case; but I'd like
a second opinion. To be clear: I think we can verify th
Verification done on bionic with netplan.io:
mtrudel@daikoku:~$ dpkg -l netplan.io | more
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Verification-done for both bionic and cosmic:
ubuntu@humble-cod:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.96-0ubuntu0.18.04.1 amd64 YAML network configuration
abstraction for various backends
ubuntu@superb-ram:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.96-0ubuntu0.18.10.1 amd64 YAML n
Verification-done for both bionic and cosmic:
ubuntu@humble-cod:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.96-0ubuntu0.18.04.1 amd64YAML network
configuration abstraction for various backends
ubuntu@superb-ram:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.96-0ubuntu0.18.
Verification-done for both bionic and cosmic:
ubuntu@humble-cod:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.96-0ubuntu0.18.04.1 amd64 YAML network configuration
abstraction for various backends
ubuntu@superb-ram:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.96-0ubuntu0.18.10.1 amd64 YAML n
** Changed in: cryptsetup
Assignee: TJ (tj) => (unassigned)
** Changed in: cryptsetup (Ubuntu)
Assignee: TJ (tj) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767527
Title:
There currently are no plans to that effect.
For now; shipping in the devel series, and the installer does not set up
any partitioning automatically that would make use of this. It's "only"
a convenience for people who do their own partitioning, which requires
some prior knowledge to set this up c
I see no obvious issues with the package, but it's huge and would
benefit the Security Team reviewing it as well.
** Changed in: containerd (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs
itical
** Changed in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821867
Title:
network interface is down a
All of these values should be coming directly from the netplan YAML. Are
all of these options required?
I see:
match:
macaddress: # Do you need to match the interface in this case? Is it
sufficient to match by name if only ens3 is being configured?
Also:
dhcp-identifier: mac # Th
I also forgot to mention another entry I see in some of the configs:
set-name: ens3
If you do not need to explicitly rename the interfaces yourself to a
different name, I would avoid setting this at all. It *may* be being set
automatically by cloud-init (if that's in use, but the configs provided
** Description changed:
+ [Impact]
+ Minimal installs using netplan to configure the network.
+
+ [Test case]
+ 1) Install Ubuntu minimal server / cloud image
+ 2) Edit /etc/netplan/01-netcfg.yaml to configure the network as necessary.
+ 3) Run 'sudo netplan apply'. Verify that the network comes
Yes, that does explain it.
/run/netplan/.yaml is written automatically by initramfs-
tools when booting with a remote root (ie. iscsi); so this does check
out: for example, 'critical' is required in that case, otherwise as soon
as someone runs 'netplan apply' the network will go down and you might
Verification done for both bionic and cosmic:
ubuntu@test-netplan-bionic:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.96-0ubuntu0.18.04.2 amd64YAML network
configuration abstraction for various backends
ubuntu@test-netplan-bionic:~$ sudo sysctl -a | grep tempaddr
sysctl: reading
Verification done with bionic and cosmic; using the following config:
network:
version: 2
ethernets:
ens4:
match:
macaddress: 52:54:00:ea:e6:7a
mtu: 9000
ens7:
match:
macaddress: 52:54:00:d7:62:4c
Verification-done on bionic with netplan.io 0.96-0ubuntu0.18.04.2:
I set up a new AWS instance (t2.micro in this case); and applied a
similar setup (attempting to just set mtu: 1500, that doesn't work, then
using the new dhcp4-overrides feature). Forcing UseMTU=false makes the
MTU apply to the int
Verification-done for cosmic, using netplan.io 0.96-0ubuntu0.18.10.2:
As for the above test, I set up a new AWS instance (t2.micro); and
applied the configuration (first trying to just set mtu: 1500; then
using dhcp4-overrides: { use-mtu: false }).
ubuntu@ip-172-30-0-81:~$ dpkg -l netplan.io | g
As a first step I'd look into whether grub is able to correctly get an
IP from DHCP. I wonder if the client class string confuses it.
Could you please take packet captures of the boot attempt? We could then
have a look at the whole thing and compare with grub code to see what
happens?
** Changed
Verification-done on trusty:
ii grub-common 2.02~beta2-9ubuntu1.17 amd64 GRand Unified Bootloader (common
files)
ii grub-efi-amd64 2.02~beta2-9ubuntu1.17 amd64 GRand Unified Bootloader,
version 2 (EFI-AMD64 version)
ii grub-efi-amd64-bin 2.02~beta2-9ubuntu1.17 amd64 GRand Unified Bootloader,
ve
901 - 1000 of 8571 matches
Mail list logo
