Bridge port's hairpin mode not set after resuming a machine
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Yaguang Tang | ||
Essex |
Fix Released
|
Undecided
|
Unassigned | ||
nova (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi there,
after resuming a guest machine from suspend, the bridge port's hairpin mode is not set. This leads to the machine not being accessible from inside the cloud installation via it's assigned floating IP. As far as I understand, this was the reason why hairpin_mode has been introduced.
Looking at the code of nova/virt/
Being uncertain about the implications and correct fix for this bug, I thought I'd post it this way rather than providing a questionable fix.
My approach would be to alter resume_instance in nova/compute/
I'd be happy to give more information if required. I found this problem in the Essex release. However, it can be verified in the current master.
Best regards,
Björn
Changed in nova: | |
status: | New → Confirmed |
assignee: | nobody → Yaguang Tang (heut2008) |
Changed in nova: | |
milestone: | none → folsom-rc1 |
status: | Confirmed → Triaged |
importance: | Undecided → High |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | folsom-rc1 → 2012.2 |
Changed in nova (Ubuntu): | |
status: | New → Fix Released |
tags: |
added: verification-done removed: verification-needed |
Fix proposed to branch: master /review. openstack. org/11925
Review: https:/