api-endpoints fails if run just after bootstrap
Bug #1338511 reported by
Free Ekanayaka
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Andrew Wilkins | ||
1.20 |
Fix Released
|
High
|
Andrew Wilkins |
Bug Description
To reproduce:
juju bootstrap -e maas --to my.node && juju api-endpoints; echo $?
and the output looks like:
Launching instance
<... rest of bootstrap log ...>
Starting Juju machine agent (jujud-machine-0)
ERROR EOF
1
This is a regression introduced in 1.20.0, it was working fine in 1.19.4. It seems to happen only when using the MAAS provider, not when using the Amazon one.
The diff between 1.19.4 and 1.20.0 is very small:
http://
so I'm not really sure what could be the cause.
The workaround is to put a little sleep before running "juju api-endpoints".
Changed in juju-core: | |
assignee: | nobody → Frank Mueller (themue) |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.21-alpha1 |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
assignee: | Frank Mueller (themue) → Andrew Wilkins (axwalk) |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Same error with local provider, but only once.So maybe a race condition due to loading of dependent software packages.