← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1409795] [NEW] It is possible to assign External Network for VM and it will doesn't work

 

Public bug reported:

It is possible to assign external neutron network for instances, and
instances will get the floating IP, but in fact the routing will not
work. Looks like we need to deny to assign external networks for VMs
interfaces to avoid incorrect network configurations.

** Affects: mos
     Importance: Medium
     Assignee: MOS Neutron (mos-neutron)
         Status: New

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: neutron

** Description changed:

  It is possible to assign external neutron network for instances, and
  instances will get the floating IP, but in fact the routing will not
- work. Looks like we need to not allow to assign external networks for
- VMs interfaces to avid incorrect network configurations.
+ work. Looks like we need to deny to assign external networks for VMs
+ interfaces to avid incorrect network configurations.

** Description changed:

  It is possible to assign external neutron network for instances, and
  instances will get the floating IP, but in fact the routing will not
  work. Looks like we need to deny to assign external networks for VMs
- interfaces to avid incorrect network configurations.
+ interfaces to avoid incorrect network configurations.

** Also affects: mos
   Importance: Undecided
       Status: New

** Changed in: mos
   Importance: Undecided => Medium

** Changed in: mos
     Assignee: (unassigned) => MOS Neutron (mos-neutron)

** Tags added: neutron

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1409795

Title:
  It is possible to assign External Network for VM and it will doesn't
  work

Status in Mirantis OpenStack:
  New
Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  It is possible to assign external neutron network for instances, and
  instances will get the floating IP, but in fact the routing will not
  work. Looks like we need to deny to assign external networks for VMs
  interfaces to avoid incorrect network configurations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mos/+bug/1409795/+subscriptions


Follow ups

References