Canonical Juju

deploy k8s charms to juju 3.0 beta is broken

Bug #1947105 reported by Ian Booth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Ian Booth
Canonical Juju 3.0.0

Bug Description

bootstrap a microk8s controller
deploy snappass-test

the agent stays "allocating"

Looking at the logs

ERROR juju.worker.dependency "charm-downloader" manifold worker returned unexpected error: facade "CharmDownloader" not supported on container models (not supported)

Updating restrict_caasmodel.go fixed this error but deploys still fail.

Tags: k8s
Juan M. Tirado (tiradojm)
tags: added: ju-14
Juan M. Tirado (tiradojm)
tags: removed: ju-14
Revision history for this message
Ian Booth (wallyworld) wrote :

The controller log contains many lines like this, which are not present in 2.9

controller-0: 15:05:19 WARNING juju.worker.httpserver http: TLS handshake error from 10.1.78.92:52966: remote error: tls: bad certificate

The address is the vxlan.calico device

Revision history for this message
Ian Booth (wallyworld) wrote :

https://github.com/juju/juju/pull/13428

Changed in juju:
assignee: nobody → Ian Booth (wallyworld)
status: Triaged → In Progress
Ian Booth (wallyworld)
Changed in juju:
milestone: none → 3.0.0
Ian Booth (wallyworld)
Changed in juju:
status: In Progress → Fix Committed
John A Meinel (jameinel)
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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