I only marked it as affecting subiquity, in practice yes fixes need to happen in snapd.
I don't think that' uncommon to only our infrastructure. We have seen in the wild people enable the endspoints that are seen and only api.snapcraft.com is attempted (or so it would seem) without it being visible that fastly is needed too. It would be nice if snapd would try to hit both in parallel. Or whatever the brandstore / store-proxy endpoints are. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829510 Title: snapd connectivity check did not change fastly cdn To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1829510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
