The traceback indicates that the json document that was loaded did not include a PGP header.
No changes to simplestreams/util.py since 2015; so I expect there was some issue w.r.t the content loaded.
Simplestreams itself does not cache URL data; it fetches remotely first, and then mirrors content that's present in the streams data from URL and writes it locally.
If there is a proxy between simplestreams and the endpoint, I would suspect some issue there.
There are only 4 sjson files that it could be looking at:
I suggest firing up curl/wget on the endpoint where it's failing to see if you get the same contents as you do from some other place outside of the failure.
The traceback indicates that the json document that was loaded did not include a PGP header.
No changes to simplestreams/ util.py since 2015; so I expect there was some issue w.r.t the content loaded.
Simplestreams itself does not cache URL data; it fetches remotely first, and then mirrors content that's present in the streams data from URL and writes it locally.
If there is a proxy between simplestreams and the endpoint, I would suspect some issue there.
There are only 4 sjson files that it could be looking at:
http:// images. maas.io/ ephemeral- v3/daily/ streams/ v1/index. sjson images. maas.io/ ephemeral- v3/daily/ streams/ v1/com. ubuntu. maas:daily: v3:download. sjson images. maas.io/ ephemeral- v3/daily/ streams/ v1/com. ubuntu. maas:daily: centos- bases-download. sjson images. maas.io/ ephemeral- v3/daily/ streams/ v1/com. ubuntu. maas:daily: 1:bootloader- download. sjson
http://
http://
http://
I suggest firing up curl/wget on the endpoint where it's failing to see if you get the same contents as you do from some other place outside of the failure.