Bug 747605

Summary:	floating IPs not available outside of a VM
Product:	[Fedora] Fedora	Reporter:	Pádraig Brady <p>
Component:	openstack-nova	Assignee:	Pádraig Brady <pbrady>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16	CC:	alexander.sakhnov, apevec, asalkeld, d.busby, markmc, matt_domsch, mlvov, p, rkukura
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-13 20:54:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pádraig Brady 2011-10-20 13:23:20 UTC

While following:

  https://fedoraproject.org/wiki/QA:Testcase_OpenStack_floating_IPs

and running openstack within a F16 VM,
the floating IP was available within the VM,
but not from outside.

I'm guessing this is because the packets from outside
traverse the ebtables rules in the VM, thus bypassing
the iptables NAT rules.  The openstack network component
may need to be updated to handle this situation.

Comment 1 Alan Pevec 2011-11-16 22:59:58 UTC

Default libvirt network is not open for the outside connections:

-A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state RELATED,ESTABLISHED -j ACCEPT

Comment 2 Mark McLoughlin 2012-03-08 08:48:27 UTC

Any update on this?

Comment 3 David Busby 2012-06-12 11:56:19 UTC

Noted:
---
-A FORWARD -d 192.168.122.0/24 -o virbr0 -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s 192.168.122.0/24 -i virbr0 -j ACCEPT

---

Present on F17

Comment 4 Fedora End Of Life 2013-01-16 16:51:25 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 20:54:42 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.