IP addresses of the subnet attached to the external network are hard-coded

Bug #1918276 reported by Tytus Kurek
This bug affects 16 people
Affects Status Importance Assigned to Milestone

Bug Description

IP addresses of the subnet attached to the external network are hard-coded, resulting in the lack of communication between instances running on MicroStack and the external world in the default installation. Check the following article for more details:


Revision history for this message
Corey Bryant (corey.bryant) wrote :

Tytus, thanks for reporting this issue. We now have a spec up to make microstack networking more flexible at. Please let us know if this spec doesn't address any issues related to this bug.


Changed in microstack:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Tytus Kurek (tkurek) wrote :

Hello Corey,

Thanks for linking the spec. It is challenging for me to read from it how an ultimate command would look like, but please make it as straightforward as possible. An ordinary MicroStack user will not understand things like a bridge to interface mappings. They will understand which interface to attach to the external network and which CIDR to use. I'm not saying those options shouldn't be there. Just the default options should be as straightforward as possible.

Revision history for this message
Lediard Spaqi (ladi123) wrote :


We are also experiencing with IP Public getting out issues since ex-br is hard coded with the IP and is not mapped to the Ethernet that provides external or internal access in microstack with Multi Node.

Please let us know if this would be fixed or any instructions on how to do It will be appreciated.

Thank you so much.

Revision history for this message
Ali Hasan Ahmed Khan (alihasanahmedkhan) wrote :

Hi Mr. Corey,

I was also looking in this issue. When I changed the IP of br-ex and tried to login it will eventually redirect to error page /auth/login error memcached. I saw the logs in which I saw there are two places where were hardcoded which is in snap directory openstack_dashboard/settings.py and one variable OPENSTACK_HOST. I don't have an access to make changes in snap files. So I would suggest we can try to write our custom bridge IP in these two places. May be this will solve the issue. I am attaching the Screenshots.

Revision history for this message
Keven Inman (inmanturbo) wrote :

Why is this not a higher priority? is it simply due to the amount of difficulty in finding a resolution?

This and this alone makes Microstack unusable for production.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.