On Tue, Apr 17, 2018 at 2:50 PM, Andres Rodriguez
<email address hidden> wrote:
> @Jason,
>
> Instead of restarting regiond have you forced the import of images either
> via the API or via the UI?
> MAAS uses simple streams to download all streams and simple streams scans
> for signatures. The error you see is a simplestreams error.
>
> The way how the process work is that MAAS only parses data after simple
> streams downloads all descriptions and verifies signatures.
>
> So this is either simplestreams failing due to a proxy issue (as you still
> use the internal proxy, there is no direct internet access) or the
No, like I said, I tested with the proxy disabled and it still
occurred. We don't have to use the proxy to get to maas.io.
> signatures are not yet updated by the time you access the repository which
> causes the issues.
Nope, 3 hours later - the signatures were definitely updated and it
was working fine on other maas servers.
On Tue, Apr 17, 2018 at 2:50 PM, Andres Rodriguez
<email address hidden> wrote:
> @Jason,
>
> Instead of restarting regiond have you forced the import of images either
> via the API or via the UI?
Yes, as indicated in comment 6:
https:/ /bugs.launchpad .net/maas/ +bug/1761813/ comments/ 6
> MAAS uses simple streams to download all streams and simple streams scans
> for signatures. The error you see is a simplestreams error.
>
> The way how the process work is that MAAS only parses data after simple
> streams downloads all descriptions and verifies signatures.
>
> So this is either simplestreams failing due to a proxy issue (as you still
> use the internal proxy, there is no direct internet access) or the
No, like I said, I tested with the proxy disabled and it still
occurred. We don't have to use the proxy to get to maas.io.
> signatures are not yet updated by the time you access the repository which
> causes the issues.
Nope, 3 hours later - the signatures were definitely updated and it
was working fine on other maas servers.
Jason