Juju 2.8 models fail talking to Juju 2.9 controller with OAuth

Bug #1929910 reported by Thomas Miller
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Critical
Thomas Miller

Bug Description

With the fix to Kubernetes auth scopes in Juju 2.9, 2.8 models that have not been upgraded yet fail as the Kubernetes credential schemas they receive do no match what is understands.

The 2.9 controller should transform the credentials back to the old style for pre 2.9 models.

ERROR "caas-broker-tracker" manifold worker returned unexpected error: cannot
create caas broker: validating cloud spec: "oauth2" auth-type not supported

Thomas Miller (tlmiller)
Changed in juju:
assignee: nobody → Thomas Miller (tlmiller)
status: New → In Progress
importance: Undecided → Critical
Revision history for this message
Thomas Miller (tlmiller) wrote :
Changed in juju:
status: In Progress → Fix Committed
milestone: none → 2.9.9
Revision history for this message
Tom Haddon (mthaddon) wrote :

Thomas is going to test whether models will recover from this if they're upgraded shortly after a controller, or whether the recommendation is to only upgrade to 2.9.9 or later for any controller that contains k8s models.

tags: added: canonical-is-upgrades
Changed in juju:
status: Fix Committed → Fix Released
Revision history for this message
Thomas Miller (tlmiller) wrote :

FYI This has been tested from latest 2.8 -> 2.9.7. As long as the models are upgraded to 2.9 after the controller upgrade all the model agents become happy again.

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.