Restore failed: error fetching address
Bug #1499571 reported by
Curtis Hovey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Michael Foord | ||
1.24 |
Fix Released
|
Critical
|
Michael Foord | ||
1.25 |
Fix Released
|
Critical
|
Michael Foord |
Bug Description
Restore can fail when bootstrapping a new server and the provider is slow to provide public addresses, as seen in
http://
http://
This looks like a timing related issue. Retrying or waiting longer might fix this.
summary: |
- public no address + Restore failed: error fetching address |
description: | updated |
Changed in juju-core: | |
importance: | Medium → Critical |
importance: | Critical → Medium |
description: | updated |
tags: | added: blocker ci regression |
Changed in juju-core: | |
assignee: | nobody → Michael Foord (mfoord) |
Changed in juju-core: | |
status: | Triaged → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
description: | updated |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
These failures are definitely related (as in - at least hitting the code) to the recent changes around determining the public (and private) address of a machine. "no address" is a new error, for when no preferred address has been set.
However, the restore code does set machine / provider addresses using the standard machine. Set*Addresses methods - which ought to be setting the preferred addresses. (In state/backups/ restore. go:updateMachin eAddresses )
I'll dig in a bit further and see if I can find anything more.