Hi Robie,
Let me answer your questions:
Why is br0 being set up to bridge eth0? Is something doing this automatically
or is this configuration necessary for something (if so, what?)?
This configuration (br0 on a single physical interface) is automatically
generated by deploying openstack
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
- netbooting the bionic live CD[1] over NFS goes straight to maintenance
- mode :
+ [Impact]
+
+ Mounting manually a network share (NFS) and masking it breaks the state of
other units (and their dependencies).
+ Casper is masking a mounted NFS share, blocking the normal
** No longer affects: casper (Ubuntu)
--
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/1755863
Title:
netbooting the bionic live CD over NFS goes straight to maintenance
** Patch added: "disco-stop-mount-error-propagation.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1755863/+attachment/5222912/+files/disco-stop-mount-error-propagation.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hi,
I'm working on the patches for Disco, Cosmic, Bionic and Xenial. It's
not in Disco yet, but the fix process will be tracked in this bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Patch added: "xenial-stop-mount-error-propagation.debdiff"
https://bugs.launchpad.net/ubuntu/cosmic/+source/systemd/+bug/1755863/+attachment/5223751/+files/xenial-stop-mount-error-propagation.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Patch added: "bionic-stop-mount-error-propagation.debdiff"
https://bugs.launchpad.net/ubuntu/cosmic/+source/systemd/+bug/1755863/+attachment/5223753/+files/bionic-stop-mount-error-propagation.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Patch added: "cosmic-stop-mount-error-propagation.debdiff"
https://bugs.launchpad.net/ubuntu/cosmic/+source/systemd/+bug/1755863/+attachment/5223752/+files/cosmic-stop-mount-error-propagation.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
## VERIFICATION DISCO
- Before the fix:
ubuntu@disco:~$ dpkg -l | grep "ii systemd "
ii systemd 239-7ubuntu10 amd64
system and service manager
#EDNS query
ubuntu@disco:~$ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc
-l
** Patch added: "systemd-TCP-size-disco.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804487/+attachment/5217391/+files/systemd-TCP-size-disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Patch added: "systemd-TCP-size-cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804487/+attachment/5217390/+files/systemd-TCP-size-cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Description changed:
+ [Impact]
+
+ TCP stub is cutting down the payload to 512 bytes when EDNS is disabled.
+ This makes non-EDNS clients (nslookup) receive a "shortened" answer even
+ when UDP returns a truncated reply for a new TCP query. For instance,
+
+ - If the client supports EDNS:
+
** Patch added: "systemd-TCP-size-bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804487/+attachment/5217389/+files/systemd-TCP-size-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
Querying a domain name that has >512 bytes in records (e.g. 30+ A
records), the number of results depends on the DNS client used:
- If the client supports EDNS:
$ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l
30
- If the client does not support EDNS:
The fix works as expected in B/C:
#COSMIC
ubuntu@c-ufw:~$ dpkg -l | grep ufw
ii ufw 0.36-0ubuntu0.18.10.1 all
program for managing a Netfilter firewall
ubuntu@c-ufw:~$ sudo ufw status numbered
Status: active
To
Public bug reported:
When cups has set the "SystemGroup" directive to an external group
provided through sss and cups starts before sssd has finished booting,
cups will crash because the group does not exist. For instance, with a
group named lpadmins@tests.local served from Active Directory
# VERIFICATION: XENIAL
- Using the reproducer defined in the test case and the version in -updates:
ubuntu@xenial-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.1.3-4ubuntu0.7
amd64Common UNIX Printing
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1822062
# VERIFICATION: BIONIC
- Using the reproducer defined in the test case and the version in -updates:
ubuntu@bionic-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.2.7-1ubuntu2.4
amd64Common UNIX Printing
# VERIFICATION: COSMIC
- Using the reproducer defined in the test case and the version in -updates:
ubuntu@cosmic-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.2.8-5ubuntu1.2amd64
Common UNIX Printing System(tm) -
# VERIFICATION: DISCO
- Using the reproducer defined in the test case and the version in -updates:
ubuntu@disco-sssd-ad:~$ dpkg -l | grep -E "cups-daemon| cups |cups-common"
ii cups 2.2.10-4amd64
Common UNIX Printing System(tm) -
** Description changed:
+ [Impact]
+
+ * When cups has set the "SystemGroup" directive to an external group
+ provided through sss and cups starts before sssd has finished booting,
+ cups will crash because the group does not exist.
+
+ * The patch adds an "After=sssd.service" clause to the
** Patch added: "disco-cups.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258667/+files/disco-cups.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
** Patch added: "disco-cups.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258668/+files/disco-cups.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
** Patch added: "cosmic-cups.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258669/+files/cosmic-cups.debdiff
** Patch removed: "disco-cups.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258668/+files/disco-cups.debdiff
** Patch added: "bionic-cups.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258670/+files/bionic-cups.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
** Patch added: "xenial-cups.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258671/+files/xenial-cups.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
** Patch removed: "eoan debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+attachment/5288416/+files/systemd_241-7ubuntu2.debdiff
** Patch added: "eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+attachment/5294401/+files/eoan.debdiff
--
** Patch removed: "eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+attachment/5294401/+files/eoan.debdiff
** Patch added: "eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+attachment/5294438/+files/eoan.debdiff
--
You received
In the original report, the issue happened randomly on boot when a
service[1] was triggering a reload while systemd-logind was starting,
resulting in a list of queued jobs that were never executed.
The issue can happen too under high load conditions, as reported upstream:
Public bug reported:
In certain scenarios, such as high load environments or when "systemctl
daemon-reload" runs at the same time a dbus service is starting (e.g.
systemd-logind), systemd is not able to track properly when the service
has started, keeping the job 'running' forever.
The issue
# VERIFICATION
Note: As a reminder, the issue here is that there's a race condition
between any DBUS service and systemctl daemon-reload, where systemd adds
the DBUS filter (AddMatch) that looks for a name change when that has
already happened. I'll be using systemd-logind as the DBUS service in
Public bug reported:
[Description]
Fully numeric names support in Ubuntu is inconsistent in Focal onwards
because systemd does not like them[1] but are still allowed by default
by useradd, leaving the session behavior in hands of the running
applications. Two examples:
1. After creating a user
I don't have a strong opinion either, but given that scripts would
ignore the warnings and the resulting numeric users are going to face
random, seemingly unrelated issues thanks to the interaction with
systemd, I think I prefer the failure.
FWIW, I've prepared a test version in a PPA[1] which
35 matches
Mail list logo
