Bug#1010555: marked as done (cloud-init - Fails to read generated Azure keys from metadata service)
Your message dated Wed, 14 Dec 2022 02:34:39 +0000
with message-id <E1p5HbT-005Mpz-Ct@fasolo.debian.org>
and subject line Bug#1010555: fixed in cloud-init 22.4.2-1
has caused the Debian Bug report #1010555,
regarding cloud-init - Fails to read generated Azure keys from metadata service
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1010555: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010555
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: cloud-init - Fails to read generated Azure keys from metadata service
- From: Bastian Blank <waldi@debian.org>
- Date: Wed, 04 May 2022 11:59:15 +0200
- Message-id: <165165835538.89841.12210462790477146353.reportbug@softhammer.credativ.lan>
Package: cloud-init
Version: 20.4.1-2+deb11u1
Severity: important
cloud-init fails to read keys provided by the new metadata service
sometimes. In those instances, stray \r\n are embedded and should be
stripped.
See https://bugs.launchpad.net/cloud-init/+bug/1910835
Bastian
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.17.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cloud-init depends on:
ii fdisk 2.38-4
ii gdisk 1.0.9-1
pn ifupdown <none>
ii isc-dhcp-client 4.4.2-P1-1+b1
ii locales 2.33-7
ii lsb-base 11.1.0
ii lsb-release 11.1.0
pn net-tools <none>
ii procps 2:3.3.17-7+b1
ii python3 3.10.4-1
pn python3-configobj <none>
ii python3-jinja2 3.0.3-1
pn python3-jsonpatch <none>
pn python3-jsonschema <none>
pn python3-netifaces <none>
ii python3-oauthlib 3.2.0-1
ii python3-requests 2.27.1+dfsg-1
ii python3-yaml 5.4.1-1+b1
ii util-linux 2.38-4
Versions of packages cloud-init recommends:
pn cloud-guest-utils <none>
pn eatmydata <none>
ii sudo 1.9.10-3
Versions of packages cloud-init suggests:
ii btrfs-progs 5.16.2-1+b1
ii e2fsprogs 1.46.5-2
pn xfsprogs <none>
--- End Message ---
--- Begin Message ---
Source: cloud-init
Source-Version: 22.4.2-1
Done: Noah Meyerhans <noahm@debian.org>
We believe that the bug you reported is fixed in the latest version of
cloud-init, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1010555@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Noah Meyerhans <noahm@debian.org> (supplier of updated cloud-init package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 13 Dec 2022 12:35:18 -0800
Source: cloud-init
Architecture: source
Version: 22.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cloud Team <debian-cloud@lists.debian.org>
Changed-By: Noah Meyerhans <noahm@debian.org>
Closes: 1010555
Changes:
cloud-init (22.4.2-1) unstable; urgency=medium
.
[ Bastian Blank ]
* Remove unused integration into rsyslog.
* Remove unneeded config overrides.
* Update main config from template
.
[ Noah Meyerhans ]
* d/watch: ignore ubuntu internal releases
* New upstream version 22.4.2 (Closes: #1010555)
* Refresh patches
Checksums-Sha1:
e309ec9cbb44ca32efb8be6d1cf91733aad84504 2438 cloud-init_22.4.2-1.dsc
1f82ec0077678909f0ad6ef2acffa7ca6727a77e 1511043 cloud-init_22.4.2.orig.tar.gz
a0ebef4ff6460a0dca0f8eb40956fbc0fa10c537 26480 cloud-init_22.4.2-1.debian.tar.xz
d67ed609993d8644d96838205b12e8175932c6ec 6973 cloud-init_22.4.2-1_source.buildinfo
Checksums-Sha256:
a128a577b3a23f9454100bf1e272bf1a8420af330326074060c1f849f4d9dea5 2438 cloud-init_22.4.2-1.dsc
9542bc57138f50bcbbb47283c8fc57762d0dfb4bdd0829a02c2104c26ca5e1ac 1511043 cloud-init_22.4.2.orig.tar.gz
7dd74667b75829aab2ba474d059f3f4f87f8e97cb4fa55739cf57c55a48d8794 26480 cloud-init_22.4.2-1.debian.tar.xz
948fa425cae964378a17ef8eefe5775c5b1dafcb45a82b273c0af80af2527043 6973 cloud-init_22.4.2-1_source.buildinfo
Files:
b924a8c7784475a0ef78780d22acc572 2438 admin optional cloud-init_22.4.2-1.dsc
71f79c0c855167f97b7ddae567ec59b5 1511043 admin optional cloud-init_22.4.2.orig.tar.gz
9aeb395c5341e0a0401708b31cbf6eea 26480 admin optional cloud-init_22.4.2-1.debian.tar.xz
0480d927451d011d1cd6b4c9ca85efbf 6973 admin optional cloud-init_22.4.2-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE5G+E0xEKhJuZ7RJ34+c1IpshdTUFAmOZLX0RHG5vYWhtQGRl
Ymlhbi5vcmcACgkQ4+c1IpshdTUX4xAAlj1dOvJDS8BMK3J3u5b1PkmggXkgKzN9
daHle4yfdRRaP0srx1vuf10IDc2bZ8APG7FxQXI7q0GnPsYq3zoLONrTnyx5gMPd
QQGiCTyac1fygS2pmbuOo248NFNJ54zAVLB9k+mIveGfIJ1hIRAvGoLbRseOJFaw
3g+N5pRtsIO8sJu/Nd/+KgSH0NWXJIO0oNVXQa4IubFTVnje2TNlzVxqSUHxTwmJ
wIht28Yn/DgXsDTpxYcFmIgGU+sEHEt5obmFlGXrOGiB/w6K6aMsn1Euc+V0la/g
bmyxhL/rxXNdy3ZeEm6KInkkjs6JESRewt56T8EZF8rsoqoei3SfKcp447ikJRLX
jHxVoLUZvIfvHN15tEnVUx2iTFEWV2Axv620eDEdQYuKp3NK3pLd2aydFDGApRSQ
Wnp+gx84LkW/ITXW9QGchxfTMMEFY31sV9LsqwxCnxU5lO6CS8H75ENBOKtwL1Ys
h1LvyalkDiidApjIobXCAhfPJFlxeyQCrw9SRsCzDiZ++GIk65WfAjOZF1mP5gVY
jEyCvuFdYnNXQVju0gCIwXfBaHWqTN2JhxDVcSOYAZFOh9yVZYKhCRvq97Raj2UR
8OXSGh32DMwvCCdMTukg+rj18rnXFOe7Lk1hlQ3YWsWZRSAYR+dpVTBO50V+R+aV
Bur83QOdNCw=
=Bq5D
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: