[Yahoo-eng-team] [Bug 1744032] Re: Hyper-V: log warning on PortBindingFailed exception

2018-03-07 Thread Matt Riedemann
** Also affects: nova/queens
   Importance: Undecided
   Status: New

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

Title:
  Hyper-V: log warning on PortBindingFailed exception

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) queens series:
  In Progress

Bug description:
  Description
  ===

  When spawning an Hyper-V instance with NICs having the vif_type
  "hyperv", neutron will fail to bind the port to the Hyper-V host if
  the neutron server doesn't have the "hyperv" mechanism driver
  installed and configured, resulting in a PortBindingFailed exception
  on the nova-compute side.

  When this exception is encountered, the logs will say to check the
  neutron-server logs, but the problem and its solution are not obvious
  or clear, resulting in plenty of questions / reports, all having the
  same solution: install networking-hyperv and configure neutron-server
  to use the "hyperv" mechanism_driver.

  
  Steps to reproduce
  ==

  1. Do not configure neutron-server with a "hyperv" mechanism_driver.
  2. Spawn an instance having NICs with the vif_type "hyperv".

  
  Expected result
  ===

  PortBindingFailed, and a clear explanation and / or solution for it.

  After the execution of the steps above, what should have
  happened if the issue wasn't present?

  Actual result
  =

  PortBindingFailed, telling users to check the neutron-server logs,
  which doesn't contain the obvious problem / solution.

  
  Environment
  ===

  Hyper-V compute nodes, with neutron-hyperv-agent agent.
  Any OpenStack version.

  Logs & Configs
  ==

  Logs: http://paste.openstack.org/show/646888/

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1744032] Re: Hyper-V: log warning on PortBindingFailed exception

2018-03-07 Thread OpenStack Infra
Reviewed:  https://review.openstack.org/539584
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=b80c245ba529ab603910b5c0e2fa466bf0b6a146
Submitter: Zuul
Branch:master

commit b80c245ba529ab603910b5c0e2fa466bf0b6a146
Author: Claudiu Belu 
Date:   Sat Jan 13 17:58:56 2018 -0800

hyper-v: Logs tips on PortBindingFailed

When spawning an Hyper-V instance with NICs having the vif_type "hyperv",
neutron will fail to bind the port to the Hyper-V host if the neutron
server doesn't have the "hyperv" mechanism driver installed and configured,
resulting in a PortBindingFailed exception on the nova-compute side.

When this exception is encountered, the logs will say to check the
neutron-server logs, but the problem and its solution are not obvious
or clear, resulting in plenty of questions / reports, all having the
same solution: is there an L2 agent on the host alive and reporting to
neutron, and if neutron Hyper-V agent is used, make sure to install
networking-hyperv and configure neutron-server to use the "hyperv"
mechanism_driver.

Change-Id: Idceeb08e1452413e3b10ecd0a65f71d4d82866e0
Closes-Bug: #1744032


** Changed in: nova
   Status: In Progress => Fix Released

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

Title:
  Hyper-V: log warning on PortBindingFailed exception

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description
  ===

  When spawning an Hyper-V instance with NICs having the vif_type
  "hyperv", neutron will fail to bind the port to the Hyper-V host if
  the neutron server doesn't have the "hyperv" mechanism driver
  installed and configured, resulting in a PortBindingFailed exception
  on the nova-compute side.

  When this exception is encountered, the logs will say to check the
  neutron-server logs, but the problem and its solution are not obvious
  or clear, resulting in plenty of questions / reports, all having the
  same solution: install networking-hyperv and configure neutron-server
  to use the "hyperv" mechanism_driver.

  
  Steps to reproduce
  ==

  1. Do not configure neutron-server with a "hyperv" mechanism_driver.
  2. Spawn an instance having NICs with the vif_type "hyperv".

  
  Expected result
  ===

  PortBindingFailed, and a clear explanation and / or solution for it.

  After the execution of the steps above, what should have
  happened if the issue wasn't present?

  Actual result
  =

  PortBindingFailed, telling users to check the neutron-server logs,
  which doesn't contain the obvious problem / solution.

  
  Environment
  ===

  Hyper-V compute nodes, with neutron-hyperv-agent agent.
  Any OpenStack version.

  Logs & Configs
  ==

  Logs: http://paste.openstack.org/show/646888/

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp