HOST_IP not set correctly on multiple runs of stack.sh
Bug #887293 reported by
Anthony Young
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| devstack |
Fix Released
|
Low
|
Anthony Young | ||
Bug Description
If you run stack.sh, and then launch an instance, nova will move your eth0 ipaddress to br100, which means that the HOST_IP auto-detection will fail the second time around.
Steps to reproduce:
eth0 ip address: 192.168.1.50
1) run stack.sh
2) launch an instance
3) killall screen
4) run stack.sh
Expected: HOST_IP set to 192.168.1.50
Actual: HOST_IP set to 10.0.0.1 (the main address on br100)
| Changed in devstack: | |
| assignee: | nobody → Anthony Young (sleepsonthefloor) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to devstack (master) | #1 |
| Changed in devstack: | |
| status: | New → In Progress |
| Changed in devstack: | |
| importance: | Undecided → Low |
Revision history for this message
| Dean Troyer (dtroyer) wrote | #2 |
| Changed in devstack: | |
| status: | In Progress → Fix Committed |
| Changed in devstack: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/