We've just had the same problem, on multiple VMs running in Azure.
In the dpkg log we can see that systemd was indeed updated (times in
UTC):
2022-08-30 06:31:18 status unpacked udev:amd64 237-3ubuntu10.54
2022-08-30 06:31:18 status half-configured udev:amd64 237-3ubuntu10.54
2022-08-30 06:31:19
*** This bug is a duplicate of bug 1988119 ***
https://bugs.launchpad.net/bugs/1988119
** This bug has been marked a duplicate of bug 1988119
Update to systemd 237-3ubuntu10.54 broke dns
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Summary changed:
- Availability of tzdata 2022c for Ubuntu 20.04
+ [FFe] tzdata 2022c update
** Description changed:
- tzdata 2022b and 2022c were just released that includes some timezone
- changes for Chile. According to the tzdata lib listed for Ubuntu 20.04,
- the latest package is
It is released now, but we are looking into fixing build with gcc 12.
And we are also looking into if we can port to ayatana this cycle.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
Microsoft has created an incident for this.
https://azure.status.microsoft/en-us/status reports:
Azure customers running Canonical Ubuntu 18.04 experiencing DNS errors
- Investigating
Starting at approximately 06:00 UTC on 30 Aug 2022, a number of
customers running Ubuntu 18.04 (bionic) VMs
Public bug reported:
Examining the .list file for the amd64 image it contains various kernel
5.13 .deb packages.
http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
amd64.list
e.g.
/pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb
Seems to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938791 - same
symptoms.
[Workaround]
Reboot the node, DNS should return back to normal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
After the discussion on the mailing list (ubuntu-devel@) has settled, and
@bluca provided an updated MP#427557 to ship systemd-repart as an additional
binary package in Jammy (universe, not installed by default), I've moved ahead
and staged the changes to provide an upgrade path (removal of
** Description changed:
Examining the .list file for the amd64 image it contains various kernel
5.13 .deb packages.
http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop-
amd64.list
e.g.
Public bug reported:
I tried to run
http://iso.qa.ubuntu.com/qatracker/milestones/438/builds/257552/testcases/1318/results
I downloaded http://cdimage.ubuntu.com/ubuntu-
base/focal/daily/20220829.1/focal-base-riscv64.tar.gz
mkdir base
sudo tar -C base -zxf focal-base-riscv64.tar.gz
sudo mount
Outside the chroot these are my mounts relevant for the test:
$ mount | grep /home
/dev/mapper/vgubuntu-home on /home type ext4 (rw,relatime)
proc on /home/user/temp/base/proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /home/user/temp/base/sys type sysfs
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
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/1988145
Title:
Couldn't create temporary file /tmp/apt.conf.fsIutr
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1988145
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Closing this as invalid. The analysis is flawed, the configuration file
is created by user _apt, not root, the call is literally just mkstemp()
with the path given in the error message, or rather a template, so there
is no bug in apt here.
It's more likely to be wrong permissions on /tmp
** Description changed:
[Impact]
systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
Ubuntu/Debian packages of systemd - probably because it has an extra
dependency?
The bug reporter would like to use it in their new raspberry pi images
where they don't have cloud-init
** Description changed:
[Impact]
systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
Ubuntu/Debian packages of systemd - probably because it has an extra
dependency?
The bug reporter would like to use it in their new raspberry pi images
where they don't have cloud-init
exact the same as described above happened today morning after an
unattended update on Ubuntu 18.04 and 20.04 machines.
`grep 'configure systemd:amd64 237-3ubuntu10.54' /var/log/dpkg.log`
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
[Impact]
systemd-repart is not (as of 246.6-1ubuntu1) packaged in the
Ubuntu/Debian packages of systemd - probably because it has an extra
dependency?
The bug reporter would like to use it in their new raspberry pi images
where they don't have cloud-init
This update has been prepared in the following PPA:
https://launchpad.net/~schopin/+archive/ubuntu/tzdata
The kinetic upload has been prepared as a full merge from Debian,
however I kept the other series' diff as small as possible by doing a
plain "upstream update". Notably, I didn't pick up the
It seems like https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1533631 is the same bug as this one.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
The fix for kinetic is included in 251.4-1ubuntu1, and the patch is
staged in git for the next jammy SRU.
** Changed in: systemd (Ubuntu Kinetic)
Status: In Progress => Fix Released
** Changed in: systemd (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug
Microsoft Support provided fix for AKS, which I also tested successfully
is:
kubectl get no -o json | jq -r '.items[].spec.providerID' | cut -c 9- | az vmss
run-command invoke --ids @- \
--command-id RunShellScript \
--scripts 'grep nameserver /etc/resolv.conf || { dhclient -x; dhclient -i
Hello Erich, or anyone else affected,
Accepted kdesu into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/kdesu/5.92.0-0ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I've added a few alternatives how to fix the problem, mainly using az
cli for vmss, ansible or running a daemonset in this gist :
https://gist.github.com/naioja/eb8bac307a711e704b7923400b10bc14
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
this worked for us: https://github.com/joaguas/aksdnsfallback#if-the-
above-method-fails-because-dhclient-might-stall-another-alternative-is-
to-configure-resolved-to-use-a-fallback-dns-server-which-we-can-
hardcode-in-its-configuration
--
You received this bug notification because you are a
Public bug reported:
I'm filing this bug in case we want to fix it before letting glib 2.73
in to kinetic.
** Affects: glib
Importance: Unknown
Status: Unknown
** Affects: glib2.0 (Ubuntu)
Importance: High
Status: Triaged
** Affects: modemmanager (Ubuntu)
You can find here some simple Python script to run a command to the VMSS
instances for all subscriptions [or filtered ones]:
https://github.com/foreachtoil/execute-command-on-all-vmss
I still lack threading, so this might take a little bit.
--
You received this bug notification because you are
This bug was fixed in the package linux-restricted-modules-hwe-5.15 -
5.15.0-46.49~20.04.1+1
---
linux-restricted-modules-hwe-5.15 (5.15.0-46.49~20.04.1+1) focal; urgency=medium
* Miscellaneous Ubuntu changes (LP: #1988143)
- [packaging] revert drop nvidia 390
-- Alberto
I have filed a separate ticket on this for ubuntu 16.04 and cherry-picked the
linked fix and tested.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901
I didn't see this ticket before I filed my ticket.
--
You received this bug notification because you are a member of
The verification of the Stable Release Update for linux-restricted-
modules-hwe-5.15 has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In
Hi Seth,
I am using the GUI built into the desktop - the one in the top right
where I can turn bluetooth on/off and change wifi networks.
Toggling the DNS Server section from automatic to off did not result in
the DNS server entered being used. Additionally using nslookup didn't
result in a
This bug was fixed in the package tzdata - 2022c-1ubuntu1
---
tzdata (2022c-1ubuntu1) kinetic; urgency=medium
* Merge with Debian unstable (LP: #1987642). Remaining changes:
- Ship ICU timezone data files which are utilized by php and update them to
2022b as 2022c isn't
This was covered in the 251.2-2ubuntu1 release in kinetic, but the
changelog did not reference the bug number to indicate this.
** Changed in: systemd (Ubuntu Kinetic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch
Hello Josh, which GUI are you using to change dns or dhcp settings?
Thanks
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Bionic)
Importance: Undecided
Cool, thanks Josh
--
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/1988010
Title:
systemd ignoring DHCP DNS servers and DNS servers set in Network
Manager GUI
Status in
Since there is known workaround for this I am setting the Importance to
Low.
** Changed in: rsync (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
This bug was fixed in the package initramfs-tools - 0.140ubuntu17
---
initramfs-tools (0.140ubuntu17) kinetic; urgency=medium
* Include update from Debian for depmod from kmod 30 (LP: #1987620)
+ Copy modules.builtin.modinfo into initramfs (Closes: #1014319)
-- Graham Inggs
This bug was fixed in the package presage - 0.9.1-2.2ubuntu3
---
presage (0.9.1-2.2ubuntu3) kinetic; urgency=medium
* d/p/c++17.patch: fix the build against GCC-11 by porting the code to C++17
(LP: #1988196)
* d/p/format-security.patch: fix insecure format strings in the demo
** Tags added: regression-update
--
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/1988119
Title:
Update to systemd 237-3ubuntu10.54 broke dns
Status in systemd package in
Have just upgraded initramfs-tools 0.140ubuntu17 with kinetic 5.19.0-15
kernel, and the previous issue has not been seen. (1987329)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
@atykhyy thank you that worked for VMSS!
I also had some VMs without scale sets, fixed those with:
az vm availability-set list -g --query
"[].virtualMachines[].id" --output tsv | az vm run-command invoke
--scripts "echo FallbackDNS=168.63.129.16 >> /etc/systemd/resolved.conf;
systemctl restart
** Description changed:
[Impact]
* This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
used.
* Network manager might kill dhclient(6) and fail to start it again
causing the IPv6 address to be lost on a network that uses mixed
IPv4/IPV6.
The network
manually scaling node pool/reboot nodes solves this issue.
--
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/1988119
Title:
Update to systemd 237-3ubuntu10.54 broke dns
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: bionic sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You
** Package changed: ubuntu => cups (Ubuntu)
--
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/1988151
Title:
Printer not working anymore after update
Status in cups package in
> I'll upload it using git-ubuntu style, too, so it will be easier to do
the next merge.
I must get Robie to remind me what I need to stuff in the .changes file
to make that automatic (I vaguely recall him mentioning there were some
extra tags that could/should be placed there).
> Using a
Thanks for pointing at user _apt.
My /tmp is chmod 777 and mounted as
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,inode64)
When I create the chroot directory in / which is chmod 755 I can execute
the test case.
So I guess it is one of the mount options that is incompatible with the
test
** Description changed:
+ [Impact]
+
+ * Linux-restricted-modules for the 390 drivers were disabled
+ temporarily back in January, however they were not re-enabled when
+ support for the new kernel was added.
+
+ * Including the 390 release in the ISO causes the 5.13 packages to be
+ pulled
Not sure if this is the best place to help people out understanding if nodes
are impacted.
We already saw 2 different types of impact on our Azure AKS clusters.
- Pod not able to Terminate
- New images being pulled from ACR (or any container registry
Sometimes it was very clear that we saw the
You have been subscribed to a public bug:
Multifunction printer (Brother MFC-J6510DW) not working anymore.
Since one of the last updates the printer is cancelling the print job it
receives.
Reinstallation of the driver/printer trying all available connections did not
bring success.
(dnssd, IPP,
...discussed this with the kernel team and it seems to be a bug in the
5.15 hwe lrm kernel packages. Apparently because of an error, the
nvidia-390 packages have not been prepared for this kernel. And since we
pull in 390 (and should), this causes the build infrastructure to pull
in the old 5.13
** Also affects: systemd
Importance: Undecided
Status: New
** No longer affects: systemd
--
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/1988119
Title:
Update
Updated bug description with:
Moreover, the dmesg output failed and it has showed that the 'k' flag is
required for the *.tdb files within /etc/apparmor.d/abstractions/samba.
It is required to close that bug in professional way, because the flag
is also affected by samba-bgqd.
** Description
** Changed in: glib-networking (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib-networking in Ubuntu.
https://bugs.launchpad.net/bugs/1988062
Title:
Tests are
I've removed the update from bionic-security and bionic-updates, and
restored the versions which were previously in there.
This won't help anyone that has already received the broken update - I
think the advice there is to restart, or there is a workaround in the OP
here - but it should prevent
You have been subscribed to a public bug:
Hello,
iam not sure if this is a bug, but iam noticed a different behaviour of
kinit/klist between Ubuntu 18.04 and 22.04
I already talked to sam hartman who is maintainer of krb5 packages at debian
and he told that basically there is no difference
** Package changed: ubuntu => krb5 (Ubuntu)
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1988144
Title:
klist not showing tgt after reboot
Status in
> This won't help anyone that has already received the broken update - I
think the advice there is to restart, or there is a workaround in the OP
here - but it should prevent any further occurrences.
Do note this is not a solution for those using non-Azure resolvers
provided via DHCP through
** Description changed:
See bug here:
https://bugzilla.opensuse.org/show_bug.cgi?id=1191532
Fix was backported, but the path to samba-bgqd is wrong on 22.04.
Currently apparmor profile has it like this:
/usr/lib*/samba/samba-bgqd
When in fact 22.04 has it on
The bug is from 2017 without activity until now, from a desktop
perspective it isn't a rls issue, tagging a notfixing
** Tags removed: rls-kk-incoming
** Tags added: rls-kk-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Please proceed! Approved.
** Changed in: tzdata (Ubuntu Kinetic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1986984
Title:
[FFe]
> Could this be a related issue, when deployment to aks fails, due to a
connection refused when pulling images from azure container
registry(ImagePullBackOff).
I you look closer at the message accompanying the ImagePullBackOff, you should
see something like:
dial tcp: lookup
Yes @richardprammer, it appears ImagePullBackOff is one of the symptoms
of this issue.
--
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/1988119
Title:
Update to systemd
For anyone hitting this issue with AKS clusters: I have embedded the
workaround above in a daemonset to avoid having to restart all nodes
(for now)
https://gist.github.com/skinny/96e7feb6b347299ebfacaa76295a82e7
- Please check the image+tag used in the daemonset to whatever is available in
** Merge proposal linked:
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/429150
--
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/1988078
Hey guys, nothing is working. My application has been out since this
early morning. We have already tried to restart the nodes, restart the
VM, but nothing has been working and we don't have any update from
Microsoft. 4 hours ago they said "More information will be provided
within 60 minutes, when
I just hit it, after system upgrades of the following packages:
Start-Date: 2022-08-30 06:13:35
Commandline: /usr/bin/unattended-upgrade
Upgrade: systemd-sysv:i386 (237-3ubuntu10.50, 237-3ubuntu10.54)
End-Date: 2022-08-30 06:13:36
Start-Date: 2022-08-30 06:13:42
Commandline:
** Changed in: kmod (Ubuntu)
Status: Confirmed => Invalid
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Graham Inggs (ginggs)
** Bug watch added: Debian Bug tracker #1014319
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014319
** Also affects:
For people having this is issue on AKS clusters with custom DNS...
We have done this on all affected nodepools:
$ VMSS=XXX-vmss
$ nodeResourceGroup=XXX-worker
$ az vmss list-instances -g $nodeResourceGroup -n $VMSS --query "[].id"
--output tsv | az vmss run-command invoke --scripts
We are testing this in our AKS clusters now, but we were able to
manually scale up a node pool which brought up new "working" nodes. Then
manually scaled the pool back down to remove the "non-working" nodes.
This left only new nodes up and the services are functioning properly
now.
--
You
It appears dbus is stuck in kinetic-proposed due to failures in
dependency resolution on i386; there are two new arch-indep packages in
the merged package which the dbus package depends on, but they lack
Multi-Arch tags in d/control.
I'm attaching (yet another :) debdiff which adds M-A: foreign
** Changed in: tzdata (Ubuntu Kinetic)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Focal)
Importance: Undecided => High
** Changed in: tzdata (Ubuntu Bionic)
Importance: Undecided => High
** Changed
Could this be a related issue, when deployment to aks fails, due to a
connection refused when pulling images from azure container
registry(ImagePullBackOff). This problem started this morning out of the blue.
Credentials for azure container service are ok and about every 20 image pulls I
get
Public bug reported:
Imported from Debian bug http://bugs.debian.org/984297:
Package: src:presage
Version: 0.9.1-2.2
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue
To temporary mitigate the ImagePullBackOff I scaled up a new functional node
(DNS wise) and used this command to reconcile the AKS cluster:
az resource update --resource-group --name
--namespace Microsoft.ContainerService --resource-type ManagedClusters
This recovered CoreDNS in the
On Fri, Aug 05, 2022 at 00:35:32 -, Don wrote:
> It appears the issue is resolved in libssl3 3.0.4-1ubuntu1 from kinetic
> (in addition to enabling the legacy providers)
Thanks for that hint.
Can you provide any additional details on your Tinc environment and what
exactly allowed the
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]
** Changed in: openssh (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
*** This bug is a duplicate of bug 1842320 ***
https://bugs.launchpad.net/bugs/1842320
I am getting this error on a workstation with 128GB of RAM. Compression
does nothing to fix, especially with how big the nvidia driver is.
--
You received this bug notification because you are a member of
This issue also exists for "Yeti Stereo Microphone" and "HD Pro Webcam
C920".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1002952
Title:
[meta-bug] Invalid extra
az cli from cmd.exe, something like this for AKS nodes experiencing the
issue: az vmss list-instances -g -n vmss --query "[].id"
--output tsv | az vmss run-command invoke --scripts "echo
FallbackDNS=168.63.129.16 >> /etc/systemd/resolved.conf; systemctl
restart systemd-resolved.service"
Is it safe to downgrade from systemd 237-3ubuntu10.54 to the previous
237-3ubuntu10.50?
--
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/1988119
Title:
Update to systemd
84 matches
Mail list logo
