We are impacted by this as well, and all our new VMs that were spun up in Azure were failing due to mount issues. We were able to mitigate by adding the following to our cloud-init:
bootcmd:
- apt update
- apt-mark hold linux-image-6.2.0-1016-azure
- apt-mark hold linux-cloud-tools-6.2.0-1016-azure
- apt-mark hold linux-headers-6.2.0-1016-azure
- apt-mark hold linux-tools-6.2.0-1016-azure
This is obviously a temporary fix and if this is not addressed in the next release we'll regress again and it also prevents us from getting any bug fixes or security fixes in this most recent version. This feels like a huge regression in this kernel version and I hope it gets fixed and we prevent this from happening in future releases.
We are impacted by this as well, and all our new VMs that were spun up in Azure were failing due to mount issues. We were able to mitigate by adding the following to our cloud-init:
bootcmd: 6.2.0-1016- azure tools-6. 2.0-1016- azure 6.2.0-1016- azure 6.2.0-1016- azure
- apt update
- apt-mark hold linux-image-
- apt-mark hold linux-cloud-
- apt-mark hold linux-headers-
- apt-mark hold linux-tools-
This is obviously a temporary fix and if this is not addressed in the next release we'll regress again and it also prevents us from getting any bug fixes or security fixes in this most recent version. This feels like a huge regression in this kernel version and I hope it gets fixed and we prevent this from happening in future releases.