Additionally, for the future, we could use this opportunity to further improve the sosreport SRU exception/test coverage [1,2] with release upgrade testing too (after understanding the details here; and it should be easy to automate).
Apparently this issue got in the SRU of sosreport 4.3 [3], but only got a bug report at the 4.4 timeframe.
(Ok, this means it isn't apparently widespread, which is good news, but we can always improve on catching issues early! :)
--- sosreport-4.1/sos/report/plugins/gcp.py 1970-01-01 00:00:00.000000000 +0000
+++ sosreport-4.3/sos/report/plugins/gcp.py 2022-02-15 04:20:20.000000000 +0000
...
+ f"Failed to communicate with Metadata Server "
+ f"(code: {response.code}): " + response.read().decode())
...
Additionally, for the future, we could use this opportunity to further improve the sosreport SRU exception/test coverage [1,2] with release upgrade testing too (after understanding the details here; and it should be easy to automate).
Apparently this issue got in the SRU of sosreport 4.3 [3], but only got a bug report at the 4.4 timeframe.
(Ok, this means it isn't apparently widespread, which is good news, but we can always improve on catching issues early! :)
--- sosreport- 4.1/sos/ report/ plugins/ gcp.py 1970-01-01 00:00:00.000000000 +0000 4.3/sos/ report/ plugins/ gcp.py 2022-02-15 04:20:20.000000000 +0000 read(). decode( ))
+++ sosreport-
...
+ f"Failed to communicate with Metadata Server "
+ f"(code: {response.code}): " + response.
...
...
Thanks again for all your work on this!
[1] https:/ /wiki.ubuntu. com/StableRelea seUpdates# sosreport /wiki.ubuntu. com/SosreportUp dates /launchpadlibra rian.net/ 588301517/ sosreport_ 4.1-1ubuntu0. 18.04.3_ 4.3-1ubuntu0. 18.04.1. diff.gz
[2] https:/
[3] https:/