Canonical Juju

  1. Bug #1834433
  2. Comment #5

Comment 5 for bug 1834433

Revision history for this message
Pedro Guimarães (pguimaraes) wrote :

Here is a trace from bootstrapping with application credentials:
https://pastebin.canonical.com/p/XyzJrBkW9g/

The most interesting part of that log is:
10:31:50 DEBUG cmd supercommand.go:519 error stack:
authentication failed
caused by: requesting token failed
caused by: Resource at https://<REDACTED>/v3/tokens not found
caused by: request (https://<REDACTED>/v3/tokens) returned unexpected status: 404; error info: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>404 Not Found</title>
<h1>Not Found</h1>
<p>The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.</p>

/build/juju/parts/juju/go/src/github.com/juju/juju/provider/openstack/provider.go:916: authentication failed.
/build/juju/parts/juju/go/src/github.com/juju/juju/environs/bootstrap/prepare.go:133:
/build/juju/parts/juju/go/src/github.com/juju/juju/cmd/juju/commands/bootstrap.go:735:

For some reason, Juju is searching on: https://<REDACTED>/v3/tokens instead of: https://<REDACTED>/v3/auth/tokens
Which is the rule for bionic-stein clouds.

Manually adding "auth/" does not resolve the issue.