Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 908373

Summary: Quantum: adding fixed ip to an instance on a network with two subnets using NOVA will results with two ip address
Product: Red Hat OpenStack Reporter: Ofer Blaut <oblaut>
Component: openstack-novaAssignee: Gary Kotton <gkotton>
Status: CLOSED ERRATA QA Contact: Ofer Blaut <oblaut>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0 (Folsom)CC: chrisw, gkotton, ndipanov, ykaul
Target Milestone: snapshot4Keywords: Triaged
Target Release: 2.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-nova-2012.2.3-2.el6ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-21 18:16:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
two ips example none

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