Deployment of private charms is broken in 2.9 (was working in 2.8)

[Nikolay Vinogradov]

Hi,

I was trying to deploy a private charm with Juju 2.9.4 and I got this, while deploying a bundle with it:
....
15:35:51 DEBUG cmd supercommand.go:537 error stack:
cannot resolve charm URL "cs:<private_charm_path>": cannot get "/<private_charm_path>/meta/any?include=id&include=supported-series&include=published": cannot get discharge from "https://api.jujucharms.com/identity": cannot start interactive session: interaction required but not possible
/build/snapcraft-juju-35d6cf/parts/juju/src/cmd/juju/application/deployer/bundlehandler.go:343: cannot resolve charm or bundle "<private_charm>"
/build/snapcraft-juju-35d6cf/parts/juju/src/cmd/juju/application/deployer/bundlehandler.go:97:
/build/snapcraft-juju-35d6cf/parts/juju/src/cmd/juju/application/deployer/bundle.go:172: cannot deploy bundle

If I switch to Juju 2.8.11 on the same host the bundle is deployed just fine:
.....
Resolving charm: cs:~<private_charm_path>
Opening an authorization web page in your browser.
If it does not open, please open this URL:
https://api.jujucharms.com/identity/login?did=<token>

[Simon Richardson (simonrichardson)]

I can reproduce this one easily.
I'll work on a fix asap.

[Simon Richardson (simonrichardson)]

Note: the workaround for this is to use an older client against the new controller. I deployed a private charm easily by doing:

    snap install juju --channel=2.8/stable
    juju deploy cs:<private_charm_path>

[Simon Richardson (simonrichardson)]

Juju PR: https://github.com/juju/juju/pull/13151