yahoo-eng-team team mailing list archive

[Brian O'Donnell <brian.odonnell@xxxxxxx>]

Public bug reported:

I am running RDO Liberty, with openstack-neutron v7.0.1

When an instance attempts to fetch metadata, the proxy logs on the
neutron server show this error:

2016-03-17 15:00:47.268 20766 ERROR
neutron.agent.metadata.namespace_proxy BadStatusLine: ''

However, I cannot find a corresponding error in the nova controller
node's logs, which is making this difficult to troubleshoot. I have
`Debug = True` set in nova.conf but there is no activity in the logs
when these requests to the proxy are failing.

I have attached a snippet showing the entire traceback, as well as a
sanitized version of my metadata_agent.ini from the neutron server.

I can curl https://nova:8775 from the neutron server, and I get a 200
response showing the following, so I have reason to believe nova is
configured correctly:

1.0
2007-01-19
2007-03-01
2007-08-29
2007-10-10
2007-12-15
2008-02-01
2008-09-01
2009-04-04

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: liberty metadata neutron nova proxy

** Attachment added: "details.txt"
   https://bugs.launchpad.net/bugs/1558756/+attachment/4602534/+files/details.txt

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

Title:
  metadata proxy returns 500 error

Status in neutron:
  New

Bug description:
  I am running RDO Liberty, with openstack-neutron v7.0.1

  When an instance attempts to fetch metadata, the proxy logs on the
  neutron server show this error:

  2016-03-17 15:00:47.268 20766 ERROR
  neutron.agent.metadata.namespace_proxy BadStatusLine: ''

  However, I cannot find a corresponding error in the nova controller
  node's logs, which is making this difficult to troubleshoot. I have
  `Debug = True` set in nova.conf but there is no activity in the logs
  when these requests to the proxy are failing.

  I have attached a snippet showing the entire traceback, as well as a
  sanitized version of my metadata_agent.ini from the neutron server.

  I can curl https://nova:8775 from the neutron server, and I get a 200
  response showing the following, so I have reason to believe nova is
  configured correctly:

  1.0
  2007-01-19
  2007-03-01
  2007-08-29
  2007-10-10
  2007-12-15
  2008-02-01
  2008-09-01
  2009-04-04

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