Bug 908373 - Quantum: adding fixed ip to an instance on a network with two subnets using NOVA will results with two ip address
Summary: Quantum: adding fixed ip to an instance on a network with two subnets using N...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 2.0 (Folsom)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: snapshot4
: 2.1
Assignee: Gary Kotton
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-06 14:42 UTC by Ofer Blaut
Modified: 2022-07-09 06:10 UTC (History)
4 users (show)

Fixed In Version: openstack-nova-2012.2.3-2.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-21 18:16:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
two ips example (8.33 KB, text/plain)
2013-02-06 14:42 UTC, Ofer Blaut
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-16357 0 None None None 2022-07-09 06:10:24 UTC
Red Hat Product Errata RHSA-2013:0657 0 normal SHIPPED_LIVE Moderate: openstack-nova security, bug fix, and enhancement update 2013-03-21 22:12:14 UTC

Description Ofer Blaut 2013-02-06 14:42:03 UTC
Created attachment 693962 [details]
two ips example

Description of problem:

I have installed quantum.
creating network with two subnets and adding fixed ip from nova cli, will result with two ip address assgined to that VM ( see example attached )

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. create network with two subnets on quantum.
2. launch a VM 
3. removed it fixed ip using Nova remove-fixed-ip
4. add fixed ip ( nova add-fixed-ip) from the network that has two subnets
5. check nova-list
  
Actual results:


Expected results:


Additional info:

Comment 4 Ofer Blaut 2013-03-11 09:57:42 UTC
Tested
openstack-quantum-2012.2.3-5.el6ost.noarch

Only one ip is used

Comment 6 errata-xmlrpc 2013-03-21 18:16:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0657.html


Note You need to log in before you can comment on or make changes to this bug.