Activity log for bug #1993836

Date Who What changed Old value New value Message
2022-10-21 15:56:39 Nobuto Murata bug added bug
2022-10-21 15:57:05 Nobuto Murata bug task added maas-images
2022-10-21 15:57:41 Nobuto Murata bug added subscriber Canonical Field Critical
2022-10-21 16:10:41 Nobuto Murata description I believe this is a regression in a MAAS image and/or package updates between image revision 20221010 and 20221018. And this is happening for both bionic and focal deployment. Focal image has the following updates between 20221010 and 20221018: cloud-init 22.3.4-0ubuntu1~20.04.1 git 1:2.25.1-1ubuntu3.6 git-man 1:2.25.1-1ubuntu3.6 libasn1-8-heimdal:amd64 7.7.0 libgmp10:amd64 2:6.2.0 libgssapi3-heimdal:amd64 7.7.0 libhcrypto4-heimdal:amd64 7.7.0 libheimbase1-heimdal:amd64 7.7.0 libheimntlm0-heimdal:amd64 7.7.0 libhx509-5-heimdal:amd64 7.7.0 libkrb5-26-heimdal:amd64 7.7.0 libroken18-heimdal:amd64 7.7.0 libwind0-heimdal:amd64 7.7.0 zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1.5 How to reproduce: 1. install maas: 1:3.2.6-12016-g.19812b4da-0ubuntu1~20.04.1 2. enlist one node 3. deploy the node with `install_kvm` parameter or select "Libvirt" in WebUI Expected: the machine becomes "Deployed" Actual: the machine becomes "Failed deployment" due to timeout There is no major error in the cloud-init log from the target host nor MAAS side, but the image revision makes a difference. How to confirm the behavior with the previous image revision: 1. Mirror content with a specific date $ sstream-mirror --progress --max=1 \ --keyring=/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg \ http://images.maas.io/ephemeral-v3/stable/ \ images_maas/ arch=amd64 \ 'release~(focal|bionic)' \ version_name=20221010 $ python3 -m http.server --directory ./images_maas 8080 2. Set the image source as "http://<mirror_host>:8080/" 3. import bionic image and use bionic for a VM host. (It seems MAAS doesn't allow downgrading an image and focal is already imported out of the box) 4. switch back the image source to the upstream one and update the bionic image to the latest. 5. use bionic again for a VM host to see the difference I believe this is a regression in a MAAS image and/or package updates between image revision 20221010 and 20221018. And this is happening for both bionic and focal deployment. Focal image has the following updates between 20221010 and 20221018: cloud-init 22.3.4-0ubuntu1~20.04.1 git 1:2.25.1-1ubuntu3.6 git-man 1:2.25.1-1ubuntu3.6 libasn1-8-heimdal:amd64 7.7.0 libgmp10:amd64 2:6.2.0 libgssapi3-heimdal:amd64 7.7.0 libhcrypto4-heimdal:amd64 7.7.0 libheimbase1-heimdal:amd64 7.7.0 libheimntlm0-heimdal:amd64 7.7.0 libhx509-5-heimdal:amd64 7.7.0 libkrb5-26-heimdal:amd64 7.7.0 libroken18-heimdal:amd64 7.7.0 libwind0-heimdal:amd64 7.7.0 zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1.5 How to reproduce: 1. install maas: 1:3.2.6-12016-g.19812b4da-0ubuntu1~20.04.1 2. enlist one node 3. deploy the node with `install_kvm` parameter or select "Libvirt" in WebUI Expected: the machine becomes "Deployed" Actual: the machine becomes "Failed deployment" due to timeout There is no major error in the cloud-init log from the target host nor MAAS side, but the image revision makes a difference.
2022-10-21 16:25:50 Adam Collard maas: status New Incomplete
2022-10-21 16:30:08 Christian Grabowski maas: assignee Christian Grabowski (cgrabowski)
2022-10-21 16:43:00 Nobuto Murata attachment added cloud-init-output.log https://bugs.launchpad.net/maas/+bug/1993836/+attachment/5625796/+files/cloud-init-output.log
2022-10-21 16:45:17 Chris Johnston bug added subscriber Chris Johnston
2022-10-21 16:46:13 Nobuto Murata attachment added sosreport-on-spider-2022-10-21-itvaqxo.tar.xz https://bugs.launchpad.net/maas/+bug/1993836/+attachment/5625797/+files/sosreport-on-spider-2022-10-21-itvaqxo.tar.xz
2022-10-21 16:46:29 Nobuto Murata maas: status Incomplete New
2022-10-21 16:50:42 Nobuto Murata attachment added sosreport-quick-maas-2022-10-21-xlgxcgw.tar.xz https://bugs.launchpad.net/maas/+bug/1993836/+attachment/5625798/+files/sosreport-quick-maas-2022-10-21-xlgxcgw.tar.xz
2022-10-21 17:05:08 Nobuto Murata attachment added cloud-init-output_with_20221010.log https://bugs.launchpad.net/maas/+bug/1993836/+attachment/5625800/+files/cloud-init-output_with_20221010.log
2022-10-21 17:07:20 Nobuto Murata attachment added sosreport-grown-swift-2022-10-21-xyzukmq.tar.xz https://bugs.launchpad.net/maas/+bug/1993836/+attachment/5625801/+files/sosreport-grown-swift-2022-10-21-xyzukmq.tar.xz
2022-10-21 17:09:27 Nobuto Murata bug task added cloud-init (Ubuntu)
2022-10-21 17:11:42 Nobuto Murata attachment added sosreport-quick-maas-2022-10-21-ccmudhv.tar.xz https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1993836/+attachment/5625802/+files/sosreport-quick-maas-2022-10-21-ccmudhv.tar.xz
2022-10-21 17:14:07 Nobuto Murata tags apport-collected focal uec-images
2022-10-21 17:14:09 Nobuto Murata description I believe this is a regression in a MAAS image and/or package updates between image revision 20221010 and 20221018. And this is happening for both bionic and focal deployment. Focal image has the following updates between 20221010 and 20221018: cloud-init 22.3.4-0ubuntu1~20.04.1 git 1:2.25.1-1ubuntu3.6 git-man 1:2.25.1-1ubuntu3.6 libasn1-8-heimdal:amd64 7.7.0 libgmp10:amd64 2:6.2.0 libgssapi3-heimdal:amd64 7.7.0 libhcrypto4-heimdal:amd64 7.7.0 libheimbase1-heimdal:amd64 7.7.0 libheimntlm0-heimdal:amd64 7.7.0 libhx509-5-heimdal:amd64 7.7.0 libkrb5-26-heimdal:amd64 7.7.0 libroken18-heimdal:amd64 7.7.0 libwind0-heimdal:amd64 7.7.0 zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1.5 How to reproduce: 1. install maas: 1:3.2.6-12016-g.19812b4da-0ubuntu1~20.04.1 2. enlist one node 3. deploy the node with `install_kvm` parameter or select "Libvirt" in WebUI Expected: the machine becomes "Deployed" Actual: the machine becomes "Failed deployment" due to timeout There is no major error in the cloud-init log from the target host nor MAAS side, but the image revision makes a difference. I believe this is a regression in a MAAS image and/or package updates between image revision 20221010 and 20221018. And this is happening for both bionic and focal deployment. Focal image has the following updates between 20221010 and 20221018: cloud-init 22.3.4-0ubuntu1~20.04.1 git 1:2.25.1-1ubuntu3.6 git-man 1:2.25.1-1ubuntu3.6 libasn1-8-heimdal:amd64 7.7.0 libgmp10:amd64 2:6.2.0 libgssapi3-heimdal:amd64 7.7.0 libhcrypto4-heimdal:amd64 7.7.0 libheimbase1-heimdal:amd64 7.7.0 libheimntlm0-heimdal:amd64 7.7.0 libhx509-5-heimdal:amd64 7.7.0 libkrb5-26-heimdal:amd64 7.7.0 libroken18-heimdal:amd64 7.7.0 libwind0-heimdal:amd64 7.7.0 zlib1g:amd64 1:1.2.11.dfsg-2ubuntu1.5 How to reproduce: 1. install maas: 1:3.2.6-12016-g.19812b4da-0ubuntu1~20.04.1 2. enlist one node 3. deploy the node with `install_kvm` parameter or select "Libvirt" in WebUI Expected: the machine becomes "Deployed" Actual: the machine becomes "Failed deployment" due to timeout There is no major error in the cloud-init log from the target host nor MAAS side, but the image revision makes a difference. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CloudName: MAAS DistroRelease: Ubuntu 20.04 Package: cloud-init 22.3.4-0ubuntu1~20.04.1 PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210 Tags: focal uec-images Uname: Linux 5.4.0-131-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True user_data.txt: Error: path contained symlinks.
2022-10-21 17:14:10 Nobuto Murata attachment added Dependencies.txt https://bugs.launchpad.net/bugs/1993836/+attachment/5625803/+files/Dependencies.txt
2022-10-21 17:14:12 Nobuto Murata attachment added ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1993836/+attachment/5625804/+files/ProcCpuinfoMinimal.txt
2022-10-21 17:14:14 Nobuto Murata attachment added cloud-init-log-warnings.txt https://bugs.launchpad.net/bugs/1993836/+attachment/5625805/+files/cloud-init-log-warnings.txt
2022-10-21 17:14:16 Nobuto Murata attachment added cloud-init-output.log.txt.txt https://bugs.launchpad.net/bugs/1993836/+attachment/5625806/+files/cloud-init-output.log.txt.txt
2022-10-21 17:14:19 Nobuto Murata attachment added logs.tgz.gz https://bugs.launchpad.net/bugs/1993836/+attachment/5625807/+files/logs.tgz.gz
2022-10-21 17:14:21 Nobuto Murata attachment added lshw.txt.txt https://bugs.launchpad.net/bugs/1993836/+attachment/5625808/+files/lshw.txt.txt
2022-10-21 18:25:43 Bill Wear maas: status New Triaged
2022-10-21 18:25:47 Bill Wear maas-images: status New Triaged
2022-10-21 18:25:51 Bill Wear maas: importance Undecided Critical
2022-10-21 18:25:54 Bill Wear maas-images: importance Undecided Critical
2022-10-21 22:08:30 Christian Grabowski maas: status Triaged Incomplete
2022-10-22 02:43:43 Nobuto Murata tags apport-collected focal uec-images apport-collected focal regression-update uec-images
2022-10-23 23:30:04 Yoshi Kadokawa bug added subscriber Yoshi Kadokawa
2022-10-24 04:32:05 James Falcon cloud-init (Ubuntu): status New Incomplete
2022-10-24 06:29:16 Christian Grabowski cloud-init (Ubuntu): status Incomplete New
2022-10-25 02:16:02 Nobuto Murata bug added subscriber Canonical Field High
2022-10-25 02:16:07 Nobuto Murata removed subscriber Canonical Field Critical
2022-10-26 13:55:56 James Falcon cloud-init (Ubuntu): status New Triaged
2022-10-26 13:56:01 James Falcon cloud-init (Ubuntu): importance Undecided Critical
2022-11-04 15:15:28 Chad Smith cloud-init (Ubuntu): status Triaged In Progress
2022-11-04 15:18:42 Chad Smith cloud-init (Ubuntu): assignee James Falcon (falcojr)
2022-11-09 22:50:31 Christian Grabowski maas: status Incomplete Triaged
2022-11-09 22:50:43 Christian Grabowski maas: status Triaged Invalid
2022-11-15 15:21:08 Chad Smith cloud-init (Ubuntu): status In Progress Fix Committed
2022-11-30 12:12:55 Diego Mascialino bug added subscriber Diego Mascialino
2022-12-07 17:02:18 James Falcon cloud-init (Ubuntu): status Fix Committed Fix Released
2023-01-13 02:04:28 Nobuto Murata maas-images: status Triaged Fix Released