Unable to deploy charmed-kubernetes on Big Sur macos

Bug #1910284 reported by Jeff Pihach
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

When using Juju from macos I'm not able to deploy the charmed-kubernetes bundle. However switching to Ubuntu and the same version of Juju, it deploys as expected.

➜ ~ juju --version
2.8.7-bigsur-amd64

➜ ~ juju status
Model Controller Cloud/Region Version SLA Timestamp
charmed-kubernetes jaas aws/us-west-1 2.8.7 unsupported 13:30:54-06:00

➜ ~ juju deploy charmed-kubernetes
Located bundle "cs:bundle/charmed-kubernetes-559"
Resolving charm: cs:~containers/containerd-100
Resolving charm: cs:~containers/easyrsa-342
Resolving charm: cs:~containers/etcd-546
Resolving charm: cs:~containers/flannel-514
Resolving charm: cs:~containers/kubeapi-load-balancer-754
Resolving charm: cs:~containers/kubernetes-master-926
Resolving charm: cs:~containers/kubernetes-worker-718
Executing changes:
- upload charm cs:~containers/containerd-100 for series focal
- deploy application containerd on focal using cs:~containers/containerd-100
ERROR cannot deploy bundle: containerd is not available on the following series: focal not supported

Revision history for this message
Pen Gale (pengale) wrote :

I can confirm that I get the same error on an older version of OSX. It looks like the 2.8.7 client is missing a piece :-/

Changed in juju:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.9-rc4
Revision history for this message
Heather Lanigan (hmlanigan) wrote :

Reproducible with:

$ juju deploy cs:~containers/kubernetes-master-926
ERROR kubernetes-master is not available on the following series: focal not supported

However, kubernetes-master does support focal in the metadata.yaml.

Revision history for this message
Pen Gale (pengale) wrote :

The problem really does appear to be client side. I did the following:

1) Bootstrapped a controller on aws with juju 2.8.7 on macOS High Sierra:

    juju bootstrap aws aws-osx-test

2) Attempted to deploy the ubuntu charm with series focal:

    juju deploy ubuntu --series focal

This failed with the error documented above.

3) Grant an "ubuntu" user privileges to access the default model on my new controller:

    juju add-user ubuntu
    juju grant ubuntu admin default

4) Deploy from an ubuntu machine running the 2.8.7 client:

    juju register ... # output from add-user above
    juju switch admin/default
    juju deploy ubuntu --series focal

That last step worked! I'm also able to add units via juju add-unit from the Mac. Not sure where the check is in the client, but it does look like a client side check that is failing.

Changed in juju:
milestone: 2.9-rc4 → 2.8.8
Revision history for this message
Pen Gale (pengale) wrote :

After some discussion ...

At present, this is actually working as designed. Juju 2.8.x doesn't officially support focal. Juju 2.9.x is the series that was intended to release alongside, and support, Ubuntu focal.

Unfortunately, several things have happened:

1) We've delayed 2.9.x.
2) The 2.8.7 client takes a look at the supported distros file on Ubuntu systems, and works with focal, despite not officially supporting it.

I think that we need a better long term solution for how this works. For now, you can deploy to focal from a MacOS box with the --force flag. For example:

```
juju deploy ubuntu --series focal --force
```

(I'm going to triage this bug to the backlog for now, as it will be fixed for the next year and a half by the release of 2.9.x, and we can revisit when the next LTS comes around.)

Changed in juju:
milestone: 2.8.8 → none
importance: High → Medium
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.