yahoo-eng-team team mailing list archive

[Jean-Philippe Evrard <1649298@xxxxxxxxxxxxxxxxxx>]

This is an upstream issue. Linking bug to nova.

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

** Changed in: openstack-ansible
       Status: New => Invalid

-- 
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/1649298

Title:
  multiple fixed ips assigned to newly spawned instance

Status in OpenStack Compute (nova):
  New
Status in openstack-ansible:
  Invalid

Bug description:
  Upon the creation of an instance where the network is attached, there
  is a possibility that the instance will be assigned 2 or more IPv4
  addresses from the address pool of the network.  Multiple ports are
  created along with the assignment of each address but only one of
  these ports is actually up.

  Versions of relevant services:
  neutron: 4.1.1
  OpenStack-ansible: ansible-playbook 1.9.4
  novaclient: 6.0.0
  os_client_config: 1.24.0

  What is expected:
  An instance that is configured with a network is spawned and built with a single IPv4 address assigned to it.

  What actually occurs:
  An instance is spawned and built with two or more IPv4 addresses assigned to it.  If an instance is spawned with 2 or more networks, 2 or more IPv4 addresses from each network are assigned to the instance.

  How to recreate it:
  Create an instance using the Horizon dashboard or create a server using the CLI.
  In both cases, the network device needs to be specified during in the creation command.
  It is not guaranteed that the issue will occur on every attempt to create the instance.
  It has been noted that the probability of the instance being assigned two or more IPv4 addresses from the same network is higher when the instance is created with two or more networks devices attached.

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