Comment 9 for bug 1902945

Given the bundle doesn't specify which track/channel at all, the old
behavior of just grabbing the charms from wherever they are should continue
to work.

On Thu, Nov 5, 2020 at 2:45 PM Kenneth Koski <email address hidden>
wrote:

> Ah, I see. The stable bundle points at charms that are on the edge
> channel. The charms haven't been getting promoted to stable due to a
> recent change to the CD process, so I'll fix that.
>
> That being said, Juju should really be a lot more vocal about this
> situation. Seems like low-hanging fruit to automatically set the message
> to e.g. "Bundle specified stable track; argo-controller-10 is not marked
> stable".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1902945
>
> Title:
> 2.9rc2: kubeflow deploy fails on microk8s
>
> Status in juju:
> In Progress
>
> Bug description:
> I'm trying to deploy kubeflow on microk8s using juju 2.9rc2. It fails,
> with most applications getting stuck trying fetch resource: oci-image:
>
> http://paste.ubuntu.com/p/vqS3DsGwmy/
>
> steps to reproduce:
>
> bootstrap juju 2.9rc2 against mircok8s
> juju deploy cs:kubeflow
>
> This works fine with 2.8.6, but fails with 2.9rc2.
>
> I'm not sure what logs to grab or how to grab them - let me know what
> additional info you need.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1902945/+subscriptions
>