yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


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

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1080278

Title:
  addFloatingIp multi-network  specifying  interface/fixed_ip

Status in OpenStack Compute (nova):
  Expired

Bug description:
  When I had multiple fixed network and started an instance It got two interface, the nova client listed two fixed ip.
  When I specified  explicitly the --nic I could get  just only one.

  This behavior implied the question, how to associate floating ip in this scenario.
  The nova-client does not had option for this. 
  I tried to lookup the rest call in the documentations, without success. So I traced the client.

  I found the server side code of this:
  nova/api/openstack/compute/contrib/floating_ips.py

  The source contains this comment:
  "this will associate the floating IP with the first fixed_ip an instance has. This should be changed to support specifying a particular fixed_ip if  multiple exist."

  It does not sounds  deterministic to me.

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