← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1651390] [NEW] Instance is getting 2 ports attached during launching with one of which is in down status

 

Public bug reported:

[Test process]
1. launch an instance in horizon or via API
2. select image, network, security rule...etc 
[Test result]:
1.2 IP addresses are shown to be attached to the created instance(eg:10.156.95.47 and 10.156.95.48)
2.go to network tab and check ports: port 10.156.95.47 is in status down while port 10.156.95.48 is in status up(both are up in admin status)
3.10.156.95.48 is actually assigned to the instance

I am using openstack mitaka. This happens only with internal networks
and not with external-provider ones. Frequency is about 2/3 launches. I
am not using any OVS tool to configure the network. FYI. This issue
won't occur if you launch instances with CLI. It happens only when using
horizon or API.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1651390

Title:
  Instance is getting 2 ports attached during launching with one of
  which is in down status

Status in neutron:
  New

Bug description:
  [Test process]
  1. launch an instance in horizon or via API
  2. select image, network, security rule...etc 
  [Test result]:
  1.2 IP addresses are shown to be attached to the created instance(eg:10.156.95.47 and 10.156.95.48)
  2.go to network tab and check ports: port 10.156.95.47 is in status down while port 10.156.95.48 is in status up(both are up in admin status)
  3.10.156.95.48 is actually assigned to the instance

  I am using openstack mitaka. This happens only with internal networks
  and not with external-provider ones. Frequency is about 2/3 launches.
  I am not using any OVS tool to configure the network. FYI. This issue
  won't occur if you launch instances with CLI. It happens only when
  using horizon or API.

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