← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1708316] [NEW] Nova send wrong information when there are several networks which have same name and VM uses more than one of them

 

Public bug reported:

Description
===========
Nova send wrong information when there are
several networks which have same name and
VM uses more than one of them

Steps to reproduce
==================
1. Create two networks which have same name
2. Create VM with the networks created in 1st step.
3. Check the VM using "nova show <VM>"

Expected result
===============
...
| tenant_id                            | 92f3ea23c5b84fd69b56583f322d213e                         |
| testnet1 network                     | 192.168.0.12                                             |
| testnet1 network                     | 192.168.1.4                                              |
| updated                              | 2017-07-31T14:33:49Z                                     |
...

Actual result
=============
...
| tenant_id                            | 92f3ea23c5b84fd69b56583f322d213e                         |
| testnet1 network                     | 192.168.0.12, 192.168.1.4                                |
| updated                              | 2017-07-31T14:33:49Z                                     |
...

Environment
===========
1. Openstack Version : I tested this using Mitaka & Ocata
2. Network : Neutron with LinuxBridge

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

  Description
  ===========
- Nova send wrong information when there are 
- several networks which have same name and 
+ Nova send wrong information when there are
+ several networks which have same name and
  VM uses more than one of them
- 
  
  Steps to reproduce
  ==================
  1. Create two networks which have same name
  2. Create VM with the networks created in 1st step.
  3. Check the VM using "nova show <VM>"
  
  Expected result
  ===============
  ...
  | tenant_id                            | 92f3ea23c5b84fd69b56583f322d213e                         |
- | testnet network                      | 192.168.0.12                                             |
- | testnet network                      | 192.168.1.4                                              |
+ | testnet1 network                     | 192.168.0.12                                             |
+ | testnet1 network                     | 192.168.1.4                                              |
  | updated                              | 2017-07-31T14:33:49Z                                     |
  ...
  
  Actual result
  =============
  ...
  | tenant_id                            | 92f3ea23c5b84fd69b56583f322d213e                         |
- | testnet network                      | 192.168.0.12, 192.168.1.4                                |
+ | testnet1 network                     | 192.168.0.12, 192.168.1.4                                |
  | updated                              | 2017-07-31T14:33:49Z                                     |
  ...
  
  Environment
  ===========
  1. Openstack Version : I tested this using Mitaka & Ocata
  2. Network : Neutron with LinuxBridge

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

Title:
  Nova send wrong information when there are several networks which have
  same name and VM uses more than one of them

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  Nova send wrong information when there are
  several networks which have same name and
  VM uses more than one of them

  Steps to reproduce
  ==================
  1. Create two networks which have same name
  2. Create VM with the networks created in 1st step.
  3. Check the VM using "nova show <VM>"

  Expected result
  ===============
  ...
  | tenant_id                            | 92f3ea23c5b84fd69b56583f322d213e                         |
  | testnet1 network                     | 192.168.0.12                                             |
  | testnet1 network                     | 192.168.1.4                                              |
  | updated                              | 2017-07-31T14:33:49Z                                     |
  ...

  Actual result
  =============
  ...
  | tenant_id                            | 92f3ea23c5b84fd69b56583f322d213e                         |
  | testnet1 network                     | 192.168.0.12, 192.168.1.4                                |
  | updated                              | 2017-07-31T14:33:49Z                                     |
  ...

  Environment
  ===========
  1. Openstack Version : I tested this using Mitaka & Ocata
  2. Network : Neutron with LinuxBridge

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


Follow ups