cannot bootstrap candidate snap release on kubernetes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned |
Bug Description
Hi,
Data team is waiting for Juju 3.1.6 bugfixes and tried to use it for Demo (from 3.1/candidate snap channel), but failed.
MicroK8s cannot fetch OCI Image: jujusolutions/
The issue:
Normal Pulling 32s kubelet Pulling image "jujusolutions/
Warning Failed 1s kubelet Failed to pull image "jujusolutions/
Warning Failed 1s kubelet Error: ErrImagePull
Normal BackOff 0s kubelet Back-off pulling image "jujusolutions/
Warning Failed 0s kubelet Error: ImagePullBackOff
The full K8s log: https:/
Reason: 3.1.6.1 is not available here
https:/
The bootstrap with --agent-version 3.1.6 doesn't help either.
HUGE thanks to Pedro Guimarães for noticing this!
P.S. juju bootstrap with debug: https:/
...
09:45:35 INFO juju.environs.
09:45:35 DEBUG juju.environs.tools tools.go:87 finding agent binaries in stream: "released"
09:45:35 DEBUG juju.environs.tools tools.go:89 reading agent binaries with major.minor version 3.1
09:45:35 DEBUG juju.environs.tools tools.go:98 filtering agent binaries by version: 3.1.6
...
09:45:36 DEBUG juju.environs.tools build.go:364 forcing version to 3.1.6.1
Changed in juju: | |
milestone: | 4.0-beta1 → 4.0-beta2 |
Changed in juju: | |
milestone: | 4.0-beta2 → 4.0-beta3 |
Changed in juju: | |
milestone: | 4.0-beta3 → 4.0-beta4 |
Changed in juju: | |
milestone: | 4.0-beta4 → 4.0-beta5 |
The workaround (from Pedro) is to choose stream 'proposed':
juju bootstrap image-stream= proposed \ proposed \
--config container-
--config agent-stream=
--agent-version 3.1.6 \
mycloud mycontroller
I would ask for the fix here, as candidate risk should work out of the box, IMHO. Tnx!