No agent binaries available
Bug #1900861 reported by
David
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
Hello,
I have seen the "No agent binaries available" error in machines deployed to an LXD Cloud added to a K8s Juju controller bootstrapped in Microk8s.
This error is only happening when the version of the juju controller is not officially released. So this happens for instance when I'm testing juju from 2.8/candidate.
For more information, see https:/
Changed in juju: | |
milestone: | 3.0.0 → 3.0.1 |
Changed in juju: | |
milestone: | 3.0.1 → 3.0.2 |
Changed in juju: | |
milestone: | 3.0.2 → 3.0.3 |
To post a comment you must log in.
So this is that if you bootstrap with a pre-release juju (to k8s) and then
try to add a non-k8s model, Juju doesn't find the pre-release Juju agent
binaries.
I'm guessing this is a case of needing to set "agent- stream= develop" or stream= proposed" for the model/controller so it will allow
"agent-
pre-release agent binaries to be used.
On Wed, Oct 21, 2020 at 10:00 AM David <email address hidden> wrote:
> Public bug reported: /discourse. juju.is/ t/no-agent- binaries- /discourse. juju.is/ t/no-agent- binaries- available/ 3329> /bugs.launchpad .net/bugs/ 1900861 /bugs.launchpad .net/juju/ +bug/1900861/ +subscriptions
>
> Hello,
>
> I have seen the "No agent binaries available" error in machines deployed
> to an LXD Cloud added to a K8s Juju controller bootstrapped in Microk8s.
>
> This error is only happening when the version of the juju controller is
> not officially released. So this happens for instance when I'm testing
> juju from 2.8/candidate.
>
> For more information, see https:/
> available/3329
> <https:/
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> No agent binaries available
>
> To manage notifications about this bug go to:
> https:/
>