Configs tied to specific interface IPs
Bug #1090370 reported by
Ian Wells
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cisco Openstack |
Fix Committed
|
Critical
|
Ian Wells | ||
| Folsom |
Fix Released
|
Critical
|
Ian Wells | ||
Bug Description
$ fgrep ipaddress *
core.pp: ovs_local_ip => $ipaddress_eth0,
core.pp: internal_address => $ipaddress_eth0,
core.pp: ovs_local_ip => $ipaddress_eth0,
These are not in the configurable part of the config, so they shouldn't be bound to eth0. This installation fails on anything where eth0 is not the right interface (which is very common).
| Changed in openstack-cisco: | |
| status: | New → Confirmed |
| importance: | Undecided → Critical |
| assignee: | nobody → Ian Wells (ijw-ubuntu) |
Revision history for this message
| Ian Wells (ijw-ubuntu) wrote | #1 |
| Changed in openstack-cisco: | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| Robert Starmer (starmer) wrote | #2 |
| Changed in openstack-cisco: | |
| milestone: | none → 2012.2.2 |
| Changed in openstack-cisco: | |
| milestone: | 2012.2.2 → none |
To post a comment you must log in.
https:/
Not ideal, we seem to have too many IP addresses, but it's what this bug needs. With tidying we could make this a little simpler.