neutron-gateway fails if it can't resolve its own hostname
Bug #1489598 reported by
JuanJo Ciarlante
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron-gateway (Juju Charms Collection) |
Opinion
|
Wishlist
|
Unassigned | ||
Bug Description
* deploy: openstack HA using 1507 charms release
* neutron-gateway running inside LXCs (on a modified host for multinic juju LXCs
and apparmor profile allowing netns)
Booted VMs don't reliably get networking setup correctly, also trying e.g.
to move neutron routers around (to a different neutron-gateway) shows
the following failure at neutron-
http://
FYI I'm positive the issue is its own hostname resolution, as its solved
by adding their hostnames to respective /etc/hosts with:
http://
Related branches
lp:~jjo/charms/trusty/neutron-gateway/add-hostname-resolution-to-etc_hosts-lp1489598
- Liam Young (community): Disapprove
-
Diff: 129 lines (+55/-0)3 files modifiedhooks/neutron_hooks.py (+2/-0)
hooks/neutron_utils.py (+50/-0)
unit_tests/test_neutron_hooks.py (+3/-0)
Revision history for this message
| JuanJo Ciarlante (jjo) wrote | #1 |
| tags: | added: backport-potential |
Revision history for this message
| James Page (james-page) wrote | #2 |
| Changed in neutron-gateway (Juju Charms Collection): | |
| importance: | Undecided → Medium |
| importance: | Medium → Wishlist |
| status: | New → Opinion |
Revision history for this message
| Stuart Bishop (stub) wrote | #3 |
To post a comment you must log in.
BTW the confirmation that's solved is done by moving VMs'
router around L3 agents, then pinging/ssh-ing to the VMs.