@rbalint @ddstreed any update on this issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking on Hirsute
Status in
Hi there,
Is there any update on this issue? I would like to understand who owns
the investigation/debugging process? Please tell us if you need any help
from the CPC team.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
@rbalint I was able to reproduce the issue with an image that was
running the following:
ii cloud-init20.4.1-79-g71564dce-0ubuntu1 all initialization
and customization tool for cloud instances
ii linux-image-azure 5.8.0.1017.19+21.04.14 amd64Linux kernel
image
It's been there for almost 3 months, I think it can wait a few more
days. It's affecting Azure's users who use Hirsute instances with
accelerated networking enabled, I don't know how many users that is.
--
You received this bug notification because you are a member of Kernel
Packages, which is
@rbalint, I just tested Impish and I cannot reproduce the issue. It
doesn't prove it's not there but it's a very good sign!
I can see that our automated testing failed because of this issue on the
2021-05-10 but not after. If I'm not wrong, systemd 248 was pushed on
the 14th, this would make a
I tried to reproduce the issue with the latest hirsute image pushed to
Azure and it appears that I cannot.
While I can still reproduce the issue with 20210511.1, I can't with
20210622.1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated
I isolated the issue between those two serial: 20210219 (doesn't have
the issue) and 20210220 (reproduces the issue).
The main difference I can see between those two serial is systemd
version:
20210219 -> 247.1-4ubuntu1
20210220 -> 247.3-1ubuntu2
Cloud-init version is the same
I attach here the full diff of packages between the two serials.
** Attachment added: "Package diff between 20210219 and 20210220 20.04 Azure
images"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1919177/+attachment/5491010/+files/package-diff.txt
--
You received this bug
I don't have any particular knowledge of how systemd waits for the
network to be ready but reading systemd-networkd-wait-online.service(8)
and networkctl(1) I wonder if cloud-init shouldn't wait for networkd-
wait-online to report that the link is "routable" instead of
"degradated" (default
Hi there,
For whether or not the issue affects Groovy. I've been creating Groovy
VMs on a loop to confirm if I could reproduce it there and (after ~50
tries) I still haven't seen it happen. I think we can safely assume that
this issue does not affect Groovy.
Also I was able to reproduce the
Hi,
Ok thanks. I am now trying to find at which time the issue was first
introduced. So far I tested an image from 20201222 and confirm that I
cannot reproduce the issue with this image.
Then by modifying the image (always before first boot) I was able to find that:
- upgrading cloud-init from
Hi,
Thanks for looking into that. Indeed, while trying to reproduce the
issue this morning, I found it more challenging than I originally
thought. I want to add a few points here on how I reproduced the issue:
1. Usually, I do not use the Azure CLI directly. I use a custom CLI of my own
that
** Description changed:
[General]
On Azure, when provisioning a Hirsute VM with Accelerated Networking
- enabled, sometimes the SSH key is not setup properly and the user cannot
- log into the VM.
+ enabled, sometimes part of the cloud-init configuration is not applied.
+
+ Especially, in
The issue probably* started between these two serials: 20210215 and
20210304.
*I say "probably" because while I'm sure I can reproduce the issue with
20210304, the fact I didn't manage to reproduce it with 20210215 (in ~15
tries) doesn't **absolutely prove** that the issue wasn't there.
--
You
Public bug reported:
To reproduce:
* start a bionic VM in azure:
az vm create --name bionic --resource-group test-bionic --image
"Canonical:UbuntuServer:18_04-lts-gen2:latest" --size Standard_M416s_v2
--admin-username ubuntu --ssh-key-value SSH_KEY_PATH
* "downgrade" the kernel to 4.15 and
** Changed in: linux-azure (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1951924
Title:
linux-azure 4.15 fails to boot on
Can it be related to this reddit post:
https://www.reddit.com/r/Ubuntu/comments/tkvjwu/this_is_why_i_love_linux_how_a_kernel_upgrade/
?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
Public bug reported:
If the daemon is started and the vmbus is not present it will just exit
with an error: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424
Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp"
in
** Patch added: "0001-UBUNTU-Packaging-disable-hv-kvp-daemon-if-needed.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024900/+attachment/5681661/+files/0001-UBUNTU-Packaging-disable-hv-kvp-daemon-if-needed.patch
--
You received this bug notification because you are a member of
20 matches
Mail list logo
