the trove guestagent mechanism for determining ip may be non-deterministic
Bug #1365033 reported by
Amrith Kumar
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Triaged
|
Low
|
Unassigned | ||
Bug Description
In the case of multi-networked machines, the IP address returned in get_ip_address() is not necessarily guaranteed to be the address that the user wants to use for the service.
First, we default the interface to be eth0 in most places.
Then we could have multiple IP's bound to an interface and it is unclear which IP we will get.
All around, the guest agent wants the IP to know where it is running. We should come up with a different way of figuring this out.
| Changed in trove: | |
| importance: | Undecided → Low |
| assignee: | nobody → Amrith (amrith) |
| summary: |
- the trove mechanism for determining ip address has issues + the trove mechanism for determining ip may have issues |
| Changed in trove: | |
| status: | New → Confirmed |
| summary: |
- the trove mechanism for determining ip may have issues + the trove guestagent mechanism for determining ip may be non- + deterministic |
| Changed in trove: | |
| milestone: | none → juno-rc1 |
| status: | Confirmed → Triaged |
| Changed in trove: | |
| milestone: | juno-rc1 → kilo-1 |
| Changed in trove: | |
| milestone: | kilo-1 → kilo-2 |
| Changed in trove: | |
| milestone: | kilo-2 → next |
| Changed in trove: | |
| assignee: | Amrith Kumar (amrith) → nobody |
To post a comment you must log in.
