yahoo-eng-team team mailing list archive

[OpenStack Infra <1545101@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/279721
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f2c1cfae53e7d9efb36b1a1b3a8d6334d9ca688f
Submitter: Jenkins
Branch:    master

commit f2c1cfae53e7d9efb36b1a1b3a8d6334d9ca688f
Author: Matt Riedemann <mriedem@xxxxxxxxxx>
Date:   Fri Feb 12 10:46:13 2016 -0800

    Partial revert of ec2 removal patch
    
    In Id7936be290b6febd18deb4c2db8ea4d678d4d9b1 and
    I8bf7cbaa7015bb61656ab90ccc8f944aaeebb095 parts of the ec2
    infrastructure were removed that had been deprecated and warned about
    in Liberty.
    
    However, changes were made to the metadata server in these changes as
    well, none of which had been warned about, and arguably should not be
    removed ever. The metadata server is an AWS construct, and given the
    implementation order of APIs in Nova (ec2 was the first API) it shares
    code with the ec2 base classes. But it's the ec2 API we were
    deprecating out and deleting.
    
    Removing these breaks anyone upgrading using the metadata server, as
    was seen by the neutron multinode job.
    
    In addition, paste filters should *never* return a response code
    directly. Doing so means they block processing the rest of the
    pipeline. Which means that the deprecation approach that was used here
    actually forcably broke anyone with existing deploys.
    
    Change-Id: I22eb3a3fcd8e74a1d9085acde15c25a927ae12cb
    Closes-Bug: #1545101


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

Title:
  Nova Metadata server in Mitaka can not work with Liberty config

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  http://logs.openstack.org/59/265759/24/experimental/gate-grenade-dsvm-
  neutron-
  multinode/8f1deec/logs/new/screen-n-api.txt.gz?level=INFO#_2016-02-12_16_28_16_860

  2016-02-12 16:28:16.860 20168 INFO nova.metadata.wsgi.server [-] Traceback (most recent call last):
    File "/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py", line 470, in handle_one_response
      result = self.application(self.environ, start_response)
    File "/usr/local/lib/python2.7/dist-packages/paste/urlmap.py", line 216, in __call__
      return app(environ, start_response)
    File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__
      resp = self.call_func(req, *args, **self.kwargs)
    File "/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func
      return self.func(req, *args, **kwargs)
    File "/opt/stack/new/nova/nova/api/ec2/__init__.py", line 32, in __call__
      return webob.exc.HTTPException(message=_DEPRECATION_MESSAGE)
  TypeError: __init__() takes exactly 3 arguments (2 given)

  This only shows up in the gate-grenade-dsvm-neutron-multinode job
  which is not running the n-api-meta service but is running the neutron
  metadata service, which has a bunch of warnings because it's not
  getting valid responses back from the nova metadata API (b/c it's not
  running):

  http://logs.openstack.org/59/265759/24/experimental/gate-grenade-dsvm-
  neutron-multinode/8f1deec/logs/new/screen-q-meta.txt.gz?level=TRACE

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