← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1715780] [NEW] Pecan controller not found for add tag API

 

Public bug reported:

I am trying to add a tag to a network resource using python
neutronclient's "add_tag" API, but its failing.

My neutron server is running in a VM (say A_VM).
I am making python neutronclient API calls from another VM (say B_VM).

Step by step reproduction steps:
i) In a python script (named neutron_add_tag.py), I created a neutron network via python neutronclient which got a resource_id = cab6f21c-a299-4c45-82a5-39d27938f005
ii) Then in the same script, using the same neutronclient session, I do -
result = neutron_client.add_tag(resource_type="network", resource_id="cab6f21c-a299-4c45-82a5-39d27938f005", tag="blue")

I see the following output on B_VM's terminal -

:~$ python neutron_add_tag.py
Created network - cc1016aa-4e31-4d8f-a7bd-e498f31a7b2e
Traceback (most recent call last):
  File "neutron_add_tag.py", line 32, in <module>
    result = neutron_client.add_tag(resource_type="network", resource_id=network['network']['id'], tag="blue")
  File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 2046, in add_tag
  File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 370, in put
  File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 338, in retry_request
  File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 301, in do_request
  File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 276, in _handle_fault_response
  File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 92, in exception_handler_v20
neutronclient.common.exceptions.NotFound: The resource could not be found.
Neutron server returns request_ids: ['req-10b7b440-aafe-41a2-ab74-addb8bbaa7f7']


In neutron's server.log, I see these logs corresponding to the add_tag call -

2017-09-08 01:22:55.322 166 DEBUG neutron.wsgi [-] (166) accepted ('10.15.17.63', 57838) server /usr/lib/python2.7/site-packages/eventlet/wsgi.py:883
2017-09-08 01:22:55.427 166 WARNING neutron.pecan_wsgi.controllers.root [req-9bb2a882-f075-40ea-bdcd-335bac6d285e 5d469c9c8d024a77a3b0ecd461c408ce 58c63ce668974b338fea81d33674865f - default default] No controller found for: network - returning response code 404: PecanNotFound
2017-09-08 01:22:55.427 166 INFO neutron.pecan_wsgi.hooks.translation [req-9bb2a882-f075-40ea-bdcd-335bac6d285e 5d469c9c8d024a77a3b0ecd461c408ce 58c63ce668974b338fea81d33674865f - default default] PUT failed (client error): The resource could not be found.
2017-09-08 01:22:55.428 166 DEBUG neutron.pecan_wsgi.hooks.notifier [req-9bb2a882-f075-40ea-bdcd-335bac6d285e 5d469c9c8d024a77a3b0ecd461c408ce 58c63ce668974b338fea81d33674865f - default default] Skipping NotifierHook processing as there was no resource associated with the request after /usr/lib/python2.7/site-packages/neutron/pecan_wsgi/hooks/notifier.py:64
2017-09-08 01:22:55.428 166 INFO neutron.wsgi [req-9bb2a882-f075-40ea-bdcd-335bac6d285e 5d469c9c8d024a77a3b0ecd461c408ce 58c63ce668974b338fea81d33674865f - default default] 10.15.17.63 "PUT /v2.0/network/fe70fad8-6255-40a1-bbe2-c97dd53a3a17/tags/blue.json HTTP/1.1" status: 404  len: 309 time: 0.1057429


I am using neutron version 11.0.0, and python neutronclient version
6.1.1

So looks like a Pecan REST API Controller could not be found. However,
my network create request was successful (using python neutronclient),
which I think would have gone through the same Pecan WSGI framework.

So is it the case that there is no REST API controller in neutron for add_tag API today ?
Would really appreciate some feedback.

** 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/1715780

Title:
  Pecan controller not found for add tag API

Status in neutron:
  New

Bug description:
  I am trying to add a tag to a network resource using python
  neutronclient's "add_tag" API, but its failing.

  My neutron server is running in a VM (say A_VM).
  I am making python neutronclient API calls from another VM (say B_VM).

  Step by step reproduction steps:
  i) In a python script (named neutron_add_tag.py), I created a neutron network via python neutronclient which got a resource_id = cab6f21c-a299-4c45-82a5-39d27938f005
  ii) Then in the same script, using the same neutronclient session, I do -
  result = neutron_client.add_tag(resource_type="network", resource_id="cab6f21c-a299-4c45-82a5-39d27938f005", tag="blue")

  I see the following output on B_VM's terminal -

  :~$ python neutron_add_tag.py
  Created network - cc1016aa-4e31-4d8f-a7bd-e498f31a7b2e
  Traceback (most recent call last):
    File "neutron_add_tag.py", line 32, in <module>
      result = neutron_client.add_tag(resource_type="network", resource_id=network['network']['id'], tag="blue")
    File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 2046, in add_tag
    File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 370, in put
    File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 338, in retry_request
    File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 301, in do_request
    File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 276, in _handle_fault_response
    File "/usr/local/nutanix/lib/py/python_neutronclient-0.0.1.dev978-py2.7.egg/neutronclient/v2_0/client.py", line 92, in exception_handler_v20
  neutronclient.common.exceptions.NotFound: The resource could not be found.
  Neutron server returns request_ids: ['req-10b7b440-aafe-41a2-ab74-addb8bbaa7f7']

  
  In neutron's server.log, I see these logs corresponding to the add_tag call -

  2017-09-08 01:22:55.322 166 DEBUG neutron.wsgi [-] (166) accepted ('10.15.17.63', 57838) server /usr/lib/python2.7/site-packages/eventlet/wsgi.py:883
  2017-09-08 01:22:55.427 166 WARNING neutron.pecan_wsgi.controllers.root [req-9bb2a882-f075-40ea-bdcd-335bac6d285e 5d469c9c8d024a77a3b0ecd461c408ce 58c63ce668974b338fea81d33674865f - default default] No controller found for: network - returning response code 404: PecanNotFound
  2017-09-08 01:22:55.427 166 INFO neutron.pecan_wsgi.hooks.translation [req-9bb2a882-f075-40ea-bdcd-335bac6d285e 5d469c9c8d024a77a3b0ecd461c408ce 58c63ce668974b338fea81d33674865f - default default] PUT failed (client error): The resource could not be found.
  2017-09-08 01:22:55.428 166 DEBUG neutron.pecan_wsgi.hooks.notifier [req-9bb2a882-f075-40ea-bdcd-335bac6d285e 5d469c9c8d024a77a3b0ecd461c408ce 58c63ce668974b338fea81d33674865f - default default] Skipping NotifierHook processing as there was no resource associated with the request after /usr/lib/python2.7/site-packages/neutron/pecan_wsgi/hooks/notifier.py:64
  2017-09-08 01:22:55.428 166 INFO neutron.wsgi [req-9bb2a882-f075-40ea-bdcd-335bac6d285e 5d469c9c8d024a77a3b0ecd461c408ce 58c63ce668974b338fea81d33674865f - default default] 10.15.17.63 "PUT /v2.0/network/fe70fad8-6255-40a1-bbe2-c97dd53a3a17/tags/blue.json HTTP/1.1" status: 404  len: 309 time: 0.1057429


  I am using neutron version 11.0.0, and python neutronclient version
  6.1.1

  So looks like a Pecan REST API Controller could not be found. However,
  my network create request was successful (using python neutronclient),
  which I think would have gone through the same Pecan WSGI framework.

  So is it the case that there is no REST API controller in neutron for add_tag API today ?
  Would really appreciate some feedback.

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


Follow ups