yahoo-eng-team team mailing list archive

[OpenStack Infra <1555384@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/313282
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=8a9538421c2f1642b5a7458fe3121b3ce4564769
Submitter: Jenkins
Branch:    master

commit 8a9538421c2f1642b5a7458fe3121b3ce4564769
Author: YAMAMOTO Takashi <yamamoto@xxxxxxxxxxxx>
Date:   Fri May 6 14:15:46 2016 +0900

    l3: Reject requests to connect to non-midonet networks gracefully
    
    This can easily happen with ML2.
    
    While MidoNet (backend) would reject those requests anyway,
    it's more user-friendly to reject them here.
    
    Closes-Bug: #1555384
    Change-Id: Ia27c12f2f7f5edd2004671b996cce882ac8a6f79


** Changed in: networking-midonet
       Status: In Progress => Fix Released

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

Title:
  ML2: routers and multiple mechanism drivers

Status in networking-midonet:
  Fix Released
Status in neutron:
  Confirmed

Bug description:
  We have an ML2 environment with linuxbridge and midonet networks. For
  L3 we use the midonet driver.

  If a user tries to bind a linuxbridge port to a midonet router it
  returns the following error:

  {"message":"There is no NeutronPort with ID eddb3d08-97f6-480d-
  a1a4-9dfe3d22e62c.","code":404}

  However the port is created (user can't see it)  and doing a router
  show shows the router as having that interface.

  Ideally this should not be allowed and should error out gracefully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-midonet/+bug/1555384/+subscriptions