Comment 10 for bug 1848248

Sorry for this. This was due to me testing the new juju release process last week for the new up and coming juju release. The changes originally should have been temporary, but ended up sticking in AWS and Azure.

I've cleaned up all remaining remnants of the "2.7beta1" test release from the stream json files and any lingering agent binaries built.

I'm currently detailing the process to correctly rollback a streams release for future reference.

Let me know if you're still having issues.