Same here with tigerlake on 22.04 freshly updated, with both `intel-
media-va-driver` and `intel-media-va-driver-non-free`. Rebuilding
`intel-media-va-driver` locally and installing that works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
From https://github.com/intel/media-driver/issues/1366 it looks like a
regression with intel-media-va-driver 22.x
** Also affects: intel-media-driver (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: github.com/intel/media-driver/issues #1366
Not sure if this is filed under the right package (is this a
driver/kernel issue ?), but I can reproduce with Intel TigerLake-LP GT2
hardware - it used to work from Ubuntu 20.04 to 21.10, and fails with
22.04 alpha, even from the Live 20220326 ISO.
vainfo shows the same thing as original post:
** Also affects: liferea (Ubuntu)
Importance: Undecided
Status: New
** Also affects: epiphany-browser (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
journalctl -e:
mars 15 11:25:09 mathieu-ThinkPad systemd[3226]: app-gnome-gufw-20889.scope:
Deactivated successfully.
mars 15 11:25:13 mathieu-ThinkPad systemd[1]: systemd-timedated.service:
Deactivated successfully.
mars 15 11:25:
status
+ 248.3-1ubuntu8 500
+ 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
journalctl -e:
mars 15 11:25:09 mathieu-ThinkPad systemd[3226]: app-gnome-gufw-20889.scope:
Deactivated successfully.
mars 15 11:25:13 mathieu-ThinkPad systemd[1]: systemd-timedated.s
://archive.ubuntu.com/ubuntu impish/main amd64 Packages
journalctl -e:
mars 15 11:25:09 mathieu-ThinkPad systemd[3226]: app-gnome-gufw-20889.scope:
Deactivated successfully.
mars 15 11:25:13 mathieu-ThinkPad systemd[1]: systemd-timedated.service:
Deactivated successfully.
mars 15 11:25:13 mathieu-ThinkPad dbus
Public bug reported:
Looks like rsync should be adapted to a new policy of the Linux kernel.
I found a report in the ZFS Github that looks a lot like my problem :
https://github.com/openzfs/zfs/issues/10742 But on that page, the
suggested solution using /proc/sys/fs/protected_regular doesn't seem
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1845529
Title:
bash completion shows `awk: line 18: function gensub never defined`
** Description changed:
+ [Impact]
+ Any user attempting to tab-complete from "umount /dev/" when running the bash
shell.
+
+ [Test cases]
Steps to reproduce:
1. Install Ubuntu MATE 19.10 using minimal desktop option
2. Open terminal and enter `umount /dev/s` and then hit
Expected
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845529
Title:
bash completion shows
** Changed in: software-properties (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852772
Title:
That's not /really/ helpful anyway. You'd have installed an extra
application, for a wholly unrelated issue, and still have to set the
profile to A2DP yourself.
Alistair, there are messages in your logs that seem to point to a firmware
issue:
Nov 26 16:56:25 albatross bluetoothd[1010]: Unable to
I see no objection at all; that fix looks obviously correct and does fix
the test.
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Corey Bryant (corey.bryant)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hi Sebastien,
I'm not unchecking any option, there is a default selected option for
the password field which is "remember this password for this user only".
And with this option, NetworkManager doesn't remember the password.
With "remember the password for all users" option, NetworkManager
I would like to add that if you choose to store the password for all
users, then it works, the password is stored by NetworkManager.
However, the bug is important because it affects the default option
selected for anyone willing to use a VPN connection: store password for
the current user.
Any
Hi Sebastien,
The only line that pops up when I click apply is the one I already
pasted before:
nov. 12 00:40:00 NetworkManager[1529]: [1573515600.3387]
audit: op="connection-update" uuid="45154b5c-
bed9-4904-a090-7d2e0303e27e" name="at-01.protonvpn.com.udp"
args="vpn.secrets" pid=23095
Public bug reported:
Hi,
Since recently, I can't import a VPN connection in NetworkManager and store my
credentials.
NetworkManager will systematically forget the password, despite a log entry
confirming that the operation was a success:
nov. 07 22:26:52 NetworkManager[1518]:
Hi Sebastien,
I'm using an the OpenVPN plugin.
I'm imported an .ovpn config file into NetworkManager and filled my credentials.
I found some interesting log messages in journalctl:
nov. 05 21:00:58 gnome-shell[2760]: Invalid connection type: vpn
nov. 05 21:00:58 gnome-shell[2760]:
Public bug reported:
Hi,
This is a duplicate of bug:
https://bugs.launchpad.net/network-manager/+bug/1718931
It is marked as fixed, but the feature is still broken for me.
I configured my Wifi connection to automatically connect to a VPN, but it only
works if I manually
connect to the Wifi
Thanks. Let's put both tasks as Triaged again then, since it's obviously
not fixed in disco and bionic.
I don't think this qualifies as a regression though, since the feature
was never available before. It's just not finished since the systemd
side of this isn't complete.
** Changed in: systemd
** Tags added: writable-etc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1849560
Title:
Please revise the files installed in /etc/
Status in openssh package in Ubuntu:
Public bug reported:
openssh-server and openssh-client install various files under /etc:
/etc/ssh/*
/etc/systemd/system/sshd.service
Please see if these files can be moved elsewhere, in accordance with
FHS: /etc should only contain files writable by the system
administrator, and in Ubuntu Core
** Tags added: writable-etc
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1849554
Title:
Please move cache files to a different location
Status in apparmor package in
Public bug reported:
The /etc/dbus-1/system.d/wpa_supplicant.conf is installed in the wrong
location. It is a system-wide default config for dbus, and as such
probably should be in /usr/share/dbus-1/system.d instead; like most
other DBus definitions installed on a typical system.
** Affects: wpa
Public bug reported:
/etc/apparmor.d/cache is currently used to keep cache files for
apparmor. Unfortunately, these files are in a location that is
inconsistent with FHS guidelines for cache.
Moreover, /etc is not a core path for Ubuntu Core 20, which means it is
planned to not be writable; and
I could reproduce this trivially; a simple netplan config:
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp: yes
Will show that my domain "cyphermox.net" here is not passed from DHCP in
networkd to resolved (and does not show in /run/systemd/resolve/stub-
resolv.conf
Verification-done on disco:
ubuntu@ip-172-30-0-243:~$ lsb_release -cs
disco
ubuntu@ip-172-30-0-243:~$ dpkg -l netplan.io systemd | grep ii
ii netplan.io 0.98-0ubuntu1~19.04.1 amd64YAML network
configuration abstraction for various backends
ii systemd240-6ubuntu5.7
Verification-done on bionic:
ubuntu@ip-172-30-0-140:/run/systemd/network$ lsb_release -cs
bionic
ubuntu@ip-172-30-0-140:/run/systemd/network$ dpkg -l netplan.io | grep ii
ii netplan.io 0.98-0ubuntu1~18.04.1 amd64YAML network
configuration abstraction for various backends
** Tags removed: rls-aa-incoming
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1723390
Title:
lxd containers have become degraded
Status
Is this still an issue on supported releases?
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
** Tags removed: rls-aa-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I can't find who promoted this package to main; but it is there right
now, and it seems it also was in previous releases. Closing as Fix
Released based on the ack from Seb128 thatit would be subscribed to by
desktop-bugs.
** Changed in: gssdp (Ubuntu)
Status: New => Fix Released
--
You
** Description changed:
+ = netplan.io =
+
+ [Impact]
+
+ * IPv6 traffic failing to send/receive due to incompatible/low MTU
+ setting. Specifically, IPv6 traffic may have higher MTU requirements
+ than IPv4 traffic and thus may need to be overridden and/or set to a
+ higher value than IPv6
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should allow configuring IPV6
Since netplan only does writing configuration to be consumed by the
backends like systemd, this would actually be a systemd bug;
reassigning.
I thought that worked though, in some setups, especially with use-
routes: false as it was being done in the config above.
Nevertheless, it needs
** Also affects: icu (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/1838322
Title:
Support Japanese new era "令和
icu split up into bug 1838322.
** Changed in: openjdk-8 (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: openjdk-8 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: openjdk-8 (Ubuntu Disco)
Status: New => Fix Released
** No longer affects: icu (Ubuntu)
There are mentions of Reiwa in icu in eoan. I'm not sure if this is a
complete fix, since the code appears to have changed somewhat from the
version of icu in Bionic and Disco.
Bionic certainly looks unfixed. Disco doesn't incldue the mentions of
"reiwa" that are present in the eoan code base.
Public bug reported:
[Background]
Many packages are affected by the requirement to support the new era "Reiwa"
(令和）
This is the meta bug to track packages that need fixes; which packages
have already been SRUd to previous releases, how to prioritize the work
needed, and general test cases for
gucharmap split up into bug 1838321
** No longer affects: gucharmap (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/1828884
Title:
[META] Handling Japanese new era
** Attachment added: "callstacks"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1837467/+attachment/5278556/+files/callstacks.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
Public bug reported:
Hello everyone,
Test setup: ubuntu 19.04, bluez 5.50, kernel bug id 204201
We are currently developing a device that contains two HID services.
That device, as it is right now, is properly functioning on Windows & Android.
However, when pairing the device on Linux running
Noted! Anyway we already had installed the latest bluez version - 5.50.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1836809
Title:
segfault when CCD are present in two
Ubuntu 18.10
bug id 204201
thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1836809
Title:
segfault when CCD are present in two different HOG services
Status in
Public bug reported:
Hello everyone,
We are currently developing a device that contains two HID services.
That device, as it is right now, is properly functioning on Windows & Android.
However, when pairing the device on Linux running bluez 5.50 we do get
segfaults (see attached files).
Our
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1791820
Title:
/usr/share/apport/apport-
** Changed in: vim (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1823651
Title:
vim ftbfs in cosmic (i386 only)
Status in vim package
** Tags removed: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1832882
Title:
libcurl-gnutls segfaults spotify client
Status in curl package in Ubuntu:
Looks like noto sources now have the right glyphs (since their April 9
release, actually). It will need an update both in Debian and Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: initramfs-tools (Ubuntu Bionic)
Status: New => Triaged
** Tags removed: rls-ee-incoming
** Tags
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1798369
Title:
Reinstall Ubuntu (with preserving existing data) shows error message
due to
** Tags removed: rls-dd-incoming
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1756595
Title:
disk space info inadvertently provides all
Closing as Invalid for netplan: the config generated is exactly as it
should for the netplan YAML that was provided. This isn't a bug in
netplan.
** Changed in: netplan
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
>From what I can tell, the routing is exactly how it should be:
[from the bug description]
root@search-3 /run/systemd/network # ip route
default via 95.216.96.129 dev enp0s31f6 proto static
10.0.0.0/24 dev tun0 proto kernel scope link src 10.0.0.13
10.0.2.0/24 dev vlan4000 proto kernel scope
After consideration, we're not going to prioritize fixing this for the
EE release (in other words, the Canonical Foundations time isn't going
to be actively working on fixing this). It doesn't mean the bug won't be
fixed, just that there is no company work assigned to the bug.
For now, there's a
** Tags removed: rls-ee-tracking
** Tags added: rls-ee-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1543799
Title:
isc-dhcp-server & isc-dhcp-server6 systemd
unicode-data in eoan does include Reiwa. Reverse-depends probably still
need to be rebuilt (I'm testing gucharmap which seemed easy enough to
patch to work).
** Changed in: unicode-data (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
mozc appears to be all done (LP: #1823444)
** Changed in: mozc (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: mozc (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: mozc (Ubuntu Cosmic)
Status: New => Fix Released
** Changed in: mozc (Ubuntu Disco)
Oops; picked the wrong openjdk...
FWIW; according to the email by Mitsuya Shibata, openjdk 8 and 11 at
least are affected (so, everything prior to disco if updates are not
applied. Openjdk-8 updates appear to already be at 8u212, which should
include Reiwa support. Marking as Fix Released so we
Kees,
I the fix in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766052 sufficient
to address the situation? Do we still need to do more to systemd (note,
the GH issue was closed upstream following Dimitri's input)?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
Assigning Dimitri who last updated this; is it still an issue?
** Changed in: console-setup (Ubuntu Xenial)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags removed: verification-done-artful verification-done-xenial
verification-done-zesty
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu Zesty)
Status: New =>
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1825448
Title:
gnupg2 autopkgtest 'simple-tests' should be included in x/b/c
Status in gnupg
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1825186
Title:
gpgv-win32 autopkgtest always fails
Status in gnupg package in Ubuntu:
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1828892
Title:
systemctl - alias service reports inactive while aliased is active
Status in
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1825856
Title:
gnupg package 'gpgv-udeb' conflicts with gnupg2 (xenial)
Status in gnupg
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1806012
Title:
set-cpufreq: 'powersave' governor configuration sanity on ubuntu
server
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828901
Title:
add PTY support for runuser
Status in util-linux package in Ubuntu:
Fix
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1668639
Title:
Add a trigger to reload rsyslog when a new configuration file is
dropped in
This appears to still be unresolved. What are the next steps? Do we
still want to add a Pre-Depends? How will d-i and image builds be
verified to not regress?
** Changed in: sysvinit (Ubuntu Xenial)
Status: In Progress => Triaged
** Changed in: sysvinit (Ubuntu Xenial)
Assignee:
This is a more complex issue; it's not just about LXD, but the general
story for installing "minimal" installs.
The fact that openssh-server was not installed as part of the ubuntu-
server is a separate bug we've covered in a different bug report.
Currently, desktops allow picking a "full"
I have a similar issue on Debian 9 (Stretch) on a Lenovo X1 Carbon 6th
Gen laptop.
DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET63W (1.38 ) 04/20/2019
The built-in speaker volume is limited to about 20% even if the volume
is set at 100%.
The sound card is a ALC285 handled by the snd_hda_intel
I don't think it's *-control-center.
At the time, that was filed there by pitti, who correctly pointed out
that something might need to depend on libnss-myhostname (from systemd)
for a fallback to resolving hostname via just /etc/hostname (since
/etc/hosts isn't changed). At this point though, it
** Tags removed: rls-x-incoming
** Tags added: rls-ee-incoming
** Also affects: gnome-control-center (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: unity-control-center (Ubuntu
I believe we've fixed this already, especially since it is a bug that
was reported prior to the release of 16.04. We do have developers who
routinely use dvorak for keymap and would otherwise not have been able
to login to their systems.
Reassigning to console-setup, since it is the most likely
Seems like this would still apply to Eoan, marking rls-ee-tracking
** Tags removed: rls-x-incoming
** Tags added: rls-ee-tracking
** Changed in: isc-dhcp (Ubuntu)
Status: Confirmed => Triaged
** Also affects: isc-dhcp (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also
Still verification-done on bionic and cosmic; this hasn't changed with
the new revision in -proposed.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug
** Description changed:
- * Impact
+ [Impact]
+ When using a VPN the DNS requests might still be sent to a DNS server outside
the VPN when they should not
- When using a VPN the DNS requests might still be sent to a DNS server
- outside the VPN when they should not
+ [Test case]
+ 1) Set up a
Started experiencing this in Ubuntu 18.04 on two different computers,
since a few days ago, presumably because of a package upgrade ; both
users are using the Unity shell (if it makes any difference; I didn't
try another one) ; disabling those shortcuts is important because
Alt+arrow are very
Okay, this bug has absolutely nothing to do with grub or netplan.
Changing the renderer couldn't possibly affect the behavior of X, and
the grub configuration looks, at a glace, to be run-of-the mill; pretty
much default if you disregard that there is any number of different
installs on the
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
No need to re-test these; it's already been included in bionic/cosmic
and bug comments are a side-effect of the changelogs for the upload with
this backport.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic
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
** 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
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
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 #
hanged in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821867
Title:
network
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
netplan is currently writing about as much as we can for the
networkd/udev configs; some values we don't know how to handle at all.
Looking at this, it feels to me like there will indeed be a need to find
a different data point to differentiate the interfaces, and MAC and
driver are not
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in:
That's odd. Let's dig in deeper, as it quite likely might be a systemd
bug, but I rather be certain it's not us doing something wrong.
Could you please attach the config files generated in
/run/systemd/network/ so we can confirm that the routes are created for
the right devices?
Thanks!
**
Reassigning to systemd -- netplan isn't limited, but if systemd-networkd
crashes that's a bug in systemd-networkd.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: netplan
--
You received this bug notification because you are a member of
** Summary changed:
- netplan removes keepalived configuration
+ Restarting systemd-networkd breaks keepalived clusters
** Summary changed:
- Restarting systemd-networkd breaks keepalived clusters
+ [master] Restarting systemd-networkd breaks keepalived clusters
--
You received this bug
*** This bug is a duplicate of bug 1815101 ***
https://bugs.launchpad.net/bugs/1815101
** This bug has been marked a duplicate of bug 1815101
Restarting systemd-networkd breaks keepalived clusters
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Summary changed:
- netplan, keepalived, netplan-apply
+ Restarting systemd-networkd breaks keepalived clusters
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: keepalived (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Kept a task for keepalived (Incomplete) in case it turns out there's
something we can do there.
Also added a task for systemd, since that would definitely require
development work.
Marked Invalid for netplan, as since netplan only translates config from
the YAML to what networkd or
This isn't netplan, it's systemd-networkd. Netplan only writes
configuration for the chosen renderer (in this case, systemd-networkd).
Either systemd needs to not wipe out foreign addresses (I believe there
is a PR in git for that) or keepalived should somehow interface with
systemd so they can
:Verification-done for cosmic:
ubuntu@superb-ram:~$ qemu-img convert vda1b.qcow2 vda1b.raw
ubuntu@superb-ram:~$ e2fsck -f vda1b.raw
e2fsck 1.44.4 (18-Aug-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking
Verification-done for bionic using e2fsprogs 1.44.1-1ubuntu1.1:
ubuntu@humble-cod:~$ qemu-img convert vda1b.qcow2 vda1b.raw
ubuntu@humble-cod:~$ e2fsck -f vda1b.raw
e2fsck 1.44.1 (24-Mar-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking
** Also affects: e2fsprogs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: e2fsprogs (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+ - Users resizing filesystems using resize2fs.
+ - Resizing an existing Linux
1 - 100 of 794 matches
Mail list logo
