Instance in isolated network could not get metadata
Bug #1476612 reported by
Ilya Shakhat
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
Medium
|
MOS Neutron | ||
Mirantis OpenStack |
Invalid
|
Medium
|
MOS Neutron |
Bug Description
In MOS 7.0 metadata proxy is enabled for isolated networks. However instance fails to retrieve metadata, curl reports "couldn't connect to host" error.
Steps to reproduce:
1. Create network
2. Launch instance and plug into the network
3. Via Horizon login to instance console and run "curl http://
It's expected that curl shows the root of metadata tree (list of versions) however it shows error.
Changed in mos: | |
assignee: | nobody → MOS Neutron (mos-neutron) |
importance: | Undecided → Medium |
tags: | added: neutron |
Changed in mos: | |
milestone: | none → 7.0 |
Changed in mos: | |
status: | New → Confirmed |
Changed in mos: | |
status: | Confirmed → Incomplete |
Changed in fuel: | |
assignee: | Fuel for Openstack (fuel) → MOS Neutron (mos-neutron) |
To post a comment you must log in.
I can't confirm the bug with this description.
I've tested the particular case with isolated networks, everything seems to be in place: metadata-proxy listening inside a namespace, 169.254 url is responding.
VMs are provided with 169.254.169.254/32 route to DHCP ip (each agent Provides IP of its port)