Walrus IP is not correctly updated in DNS records
Bug #496761 reported by
Neil Soman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Eucalyptus |
Fix Released
|
High
|
Unassigned | ||
| eucalyptus (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
DNS entries for new buckets that are created do not correctly refer to the Walrus external IP address (they use 127.0.0.1, which is not externally routable).
Revision history for this message
| Neil Soman (neilsoman) wrote | #1 |
Revision history for this message
| Neil Soman (neilsoman) wrote | #2 |
| Changed in eucalyptus: | |
| status: | New → Fix Committed |
| importance: | Undecided → High |
Revision history for this message
| Thierry Carrez (ttx) wrote | #3 |
| Changed in eucalyptus (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Fix Released |
| Changed in eucalyptus: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Another issue is that DNS domain name and nameserver changes are lost after Eucalyptus is restarted.