setup-endpoints doesn't work with internal + public networks
Bug #1270012 reported by
Robert Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Fix Released
|
High
|
Unassigned | ||
Bug Description
when there are multiple networks - e.g.
private=10/8
public=1.2.3/24
compute hosts may have only private connectivity, but setup-endpoints won't setup internal urls on the private network today, because we use the public neutron IP parameter to override OVERCLOUD_IP
| tags: | added: cd |
| Changed in tripleo: | |
| assignee: | nobody → Nha Pham (phqnha) |
| Changed in tripleo: | |
| assignee: | Nha Pham (phqnha) → nobody |
Revision history for this message
| Ben Nemec (bnemec) wrote | #1 |
| Changed in tripleo: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
We're no longer using the setup-endpoints script, and I believe the new methods do handle this correctly.