yahoo-eng-team team mailing list archive

[Armando Migliaccio <1690439@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Today if a tenant has more than a network visible to it and during boot
it does not specify any network, the famous NetworkAmbiguous is
returned. It would be nice if there was a way for Nova and Neutron to
fall back on the adoption of a tenant-level 'default' network.

[1] https://etherpad.openstack.org/p/pike-neutron-gman

** Affects: neutron
     Importance: Wishlist
         Status: Confirmed

** Affects: nova
     Importance: Wishlist
         Status: Confirmed


** Tags: auto-allocated-topology rfe

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

** Changed in: neutron
       Status: New => Confirmed

** Changed in: neutron
   Importance: Undecided => Wishlist

** Changed in: nova
       Status: New => Confirmed

** Changed in: nova
   Importance: Undecided => Wishlist

** Tags added: auto-allocated-topology rfe

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

Title:
  [RFE] Deal with NetworkAmbiguous error

Status in neutron:
  Confirmed
Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Today if a tenant has more than a network visible to it and during
  boot it does not specify any network, the famous NetworkAmbiguous is
  returned. It would be nice if there was a way for Nova and Neutron to
  fall back on the adoption of a tenant-level 'default' network.

  [1] https://etherpad.openstack.org/p/pike-neutron-gman

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