[Yahoo-eng-team] [Bug 1276142] [NEW] Physical image can not be deleted again if deletion is failed with OSError for some reason

[Abhishek Kekane]

Public bug reported:

If the deletion of physical image failed with OSError for some reason,
it is not possible to delete the image using image-delete api call.

Please refer steps-to-reproduce.txt to reproduce the issue.

Possible solution:

Image status should not get updated in database to deleted if response
is HTTPForbidden (HTTP 403) or other than HTTP 200

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New


** Tags: ntt

** Attachment added: steps-to-reproduce.txt
   
https://bugs.launchpad.net/bugs/1276142/+attachment/3968664/+files/steps-to-reproduce.txt

** Changed in: glance
 Assignee: (unassigned) = Abhishek Kekane (abhishek-kekane)

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

Title:
  Physical image can not be deleted again if deletion is failed with
  OSError for some reason

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  If the deletion of physical image failed with OSError for some reason,
  it is not possible to delete the image using image-delete api call.

  Please refer steps-to-reproduce.txt to reproduce the issue.

  Possible solution:

  Image status should not get updated in database to deleted if
  response is HTTPForbidden (HTTP 403) or other than HTTP 200

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1276142/+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 1363103] [NEW] The server has either erred or is incapable of performing the requested operation. (HTTP 500)

[Abhishek Kekane]

Public bug reported:

Gate jobs failed on 'gate-tempest-dsvm-neutron-full' with following
error.

ClientException: The server has either erred or is incapable of
performing the requested operation. (HTTP 500) (Request-ID: req-
7d7ab999-1351-43be-bd51-96a100a7cdeb)

Detailed stack trace is:

RESP BODY: {itemNotFound: {message: Instance could not be found, code: 
404}}
}}}

Traceback (most recent call last):
File tempest/scenario/test_network_advanced_server_ops.py, line 73, in setUp
create_kwargs=create_kwargs)
File tempest/scenario/manager.py, line 778, in create_server
self.status_timeout(client.servers, server.id, 'ACTIVE')
File tempest/scenario/manager.py, line 572, in status_timeout
not_found_exception=not_found_exception)
File tempest/scenario/manager.py, line 635, in _status_timeout
CONF.compute.build_interval):
File tempest/test.py, line 614, in call_until_true
if func():
File tempest/scenario/manager.py, line 606, in check_status
thing = things.get(thing_id)
File /opt/stack/new/python-novaclient/novaclient/v1_1/servers.py, line 555, 
in get
return self._get(/servers/%s % base.getid(server), server)
File /opt/stack/new/python-novaclient/novaclient/base.py, line 93, in _get
_resp, body = self.api.client.get(url)
File /opt/stack/new/python-novaclient/novaclient/client.py, line 487, in get
return self._cs_request(url, 'GET', **kwargs)
File /opt/stack/new/python-novaclient/novaclient/client.py, line 465, in 
_cs_request
resp, body = self._time_request(url, method, **kwargs)
File /opt/stack/new/python-novaclient/novaclient/client.py, line 439, in 
_time_request
resp, body = self.request(url, method, **kwargs)
File /opt/stack/new/python-novaclient/novaclient/client.py, line 433, in 
request
raise exceptions.from_response(resp, body, url, method)
 ClientException: The server has either erred or is incapable of performing the 
requested operation. (HTTP 500) (Request-ID: 
req-7d7ab999-1351-43be-bd51-96a100a7cdeb)

Traceback (most recent call last):
StringException: Empty attachments:
stderr
stdout

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: ntt

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

Title:
  The server has either erred or is incapable of performing the
  requested operation. (HTTP 500)

Status in OpenStack Compute (Nova):
  New

Bug description:
  Gate jobs failed on 'gate-tempest-dsvm-neutron-full' with following
  error.

  ClientException: The server has either erred or is incapable of
  performing the requested operation. (HTTP 500) (Request-ID: req-
  7d7ab999-1351-43be-bd51-96a100a7cdeb)

  Detailed stack trace is:

  RESP BODY: {itemNotFound: {message: Instance could not be found, 
code: 404}}
  }}}

  Traceback (most recent call last):
  File tempest/scenario/test_network_advanced_server_ops.py, line 73, in setUp
  create_kwargs=create_kwargs)
  File tempest/scenario/manager.py, line 778, in create_server
  self.status_timeout(client.servers, server.id, 'ACTIVE')
  File tempest/scenario/manager.py, line 572, in status_timeout
  not_found_exception=not_found_exception)
  File tempest/scenario/manager.py, line 635, in _status_timeout
  CONF.compute.build_interval):
  File tempest/test.py, line 614, in call_until_true
  if func():
  File tempest/scenario/manager.py, line 606, in check_status
  thing = things.get(thing_id)
  File /opt/stack/new/python-novaclient/novaclient/v1_1/servers.py, line 555, 
in get
  return self._get(/servers/%s % base.getid(server), server)
  File /opt/stack/new/python-novaclient/novaclient/base.py, line 93, in _get
  _resp, body = self.api.client.get(url)
  File /opt/stack/new/python-novaclient/novaclient/client.py, line 487, in get
  return self._cs_request(url, 'GET', **kwargs)
  File /opt/stack/new/python-novaclient/novaclient/client.py, line 465, in 
_cs_request
  resp, body = self._time_request(url, method, **kwargs)
  File /opt/stack/new/python-novaclient/novaclient/client.py, line 439, in 
_time_request
  resp, body = self.request(url, method, **kwargs)
  File /opt/stack/new/python-novaclient/novaclient/client.py, line 433, in 
request
  raise exceptions.from_response(resp, body, url, method)
   ClientException: The server has either erred or is incapable of performing 
the requested operation. (HTTP 500) (Request-ID: 
req-7d7ab999-1351-43be-bd51-96a100a7cdeb)

  Traceback (most recent call last):
  StringException: Empty attachments:
  stderr
  stdout

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1363103/+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 1372888] [NEW] g-api raise 500 error if filesystem_store_datadirs and filesystem_store_datadir both specified

[Abhishek Kekane]

Public bug reported:

g-api raise 500 error if filesystem_store_datadirs and
filesystem_store_datadir both specified

If both filesystem_store_datadirs and filesystem_store_datadir
parameters specified in glance-api.conf file then while creating new
image 500 internal server error will be raised. Ideally it should raise
'BadStoreConfiguration' exception and glance-api service should not be
started.

Stack trace on the console:

2014-09-23 03:15:24.407 7594 ERROR glance.api.v1.upload_utils 
[f351b844-8b1e-429c-8943-a79b331311be 41d56c1d7e134fdb8a1dcfe4ea3c82de 
73078aaf41fb47b5bb0cfd4e9fdc79fb - - -] Failed to upload image 
288f7386-bddf-4b2b-a97f-49d2814f7b99
2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils Traceback (most 
recent call last):
2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils   File 
/opt/stack/glance/glance/api/v1/upload_utils.py, line 106, in 
upload_data_to_store
2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils store)
2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils   File 
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py, line 342, in 
store_add_to_backend
2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils (location, 
size, checksum, metadata) = store.add(image_id, data, size)
2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils   File 
/usr/local/lib/python2.7/dist-packages/glance_store/driver.py, line 149, in 
add_disabled
2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils raise 
exceptions.StoreAddDisabled
2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils StoreAddDisabled: 
None

Steps to reproduce:
1. edit glance-api.conf file and specify values for both 
filesystem_store_datadirs and filesystem_store_datadir options
2. Restart the glance-api service
3. Hit create-image api/upload image using horizon

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New


** Tags: ntt

** Changed in: glance
 Assignee: (unassigned) = Abhishek Kekane (abhishek-kekane)

** Description changed:

  g-api raise 500 error if filesystem_store_datadirs and
  filesystem_store_datadir both specified
  
  If both filesystem_store_datadirs and filesystem_store_datadir
  parameters specified in glance-api.conf file then while creating new
  image 500 internal server error will be raised. Ideally it should raise
  'BadStoreConfiguration' exception and glance-api service should not be
  started.
  
  Stack trace on the console:
  
  2014-09-23 03:15:24.407 7594 ERROR glance.api.v1.upload_utils 
[f351b844-8b1e-429c-8943-a79b331311be 41d56c1d7e134fdb8a1dcfe4ea3c82de 
73078aaf41fb47b5bb0cfd4e9fdc79fb - - -] Failed to upload image 
288f7386-bddf-4b2b-a97f-49d2814f7b99
  2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils Traceback (most 
recent call last):
  2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils   File 
/opt/stack/glance/glance/api/v1/upload_utils.py, line 106, in 
upload_data_to_store
  2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils store)
  2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils   File 
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py, line 342, in 
store_add_to_backend
  2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils (location, 
size, checksum, metadata) = store.add(image_id, data, size)
  2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils   File 
/usr/local/lib/python2.7/dist-packages/glance_store/driver.py, line 149, in 
add_disabled
  2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils raise 
exceptions.StoreAddDisabled
  2014-09-23 03:15:24.407 7594 TRACE glance.api.v1.upload_utils 
StoreAddDisabled: None
  
  Steps to reproduce:
  1. edit glance-api.conf file and specify values for both 
filesystem_store_datadirs and filesystem_store_datadir options
  2. Restart the glance-api service
- 3. Hit create-image api
+ 3. Hit create-image api/upload image using horizon

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

Title:
  g-api raise 500 error if filesystem_store_datadirs and
  filesystem_store_datadir both specified

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  g-api raise 500 error if filesystem_store_datadirs and
  filesystem_store_datadir both specified

  If both filesystem_store_datadirs and filesystem_store_datadir
  parameters specified in glance-api.conf file then while creating new
  image 500 internal server error will be raised. Ideally it should
  raise 'BadStoreConfiguration' exception and glance-api service should
  not be started.

  Stack trace on the console:

  2014-09-23 03:15:24.407 7594 ERROR glance.api.v1.upload_utils 
[f351b844-8b1e-429c-8943-a79b331311be 41d56c1d7e134fdb8a1dcfe4ea3c82de

[Yahoo-eng-team] [Bug 1373454] [NEW] glance-api raises 500 error for invalid scheme while creating image

[Abhishek Kekane]

Public bug reported:

glance-api raises 500 error for invalid scheme while creating image using v1 
api in get_store_or_400() method.
The reason, in this method exception.UnknownScheme() exception is caught and 
this UnknownScheme exception class is not present in glance/common/excepion.py 
module as it is moved under glance_store project.

Ideally it should caught UnknownScheme exception from glance_store's
exception  module.

Stacktrace on glance-api screen:
2014-09-24 07:06:38.868 31867 INFO glance.wsgi.server 
[e03c9dff-5213-4b05-9958-9b53d404c419 8264cb3f7ed04408ad6df9f6741f5be2 
be4a5d48cbb748be923182b30ec
ed78c - - -] Traceback (most recent call last):
  File /usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py, line 434, in 
handle_one_response
result = self.application(self.environ, start_response)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 130, in __call__
resp = self.call_func(req, *args, **self.kwargs)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 195, in call_func
return self.func(req, *args, **kwargs)
  File /opt/stack/glance/glance/common/wsgi.py, line 394, in __call__
response = req.get_response(self.application)
  File /usr/lib/python2.7/dist-packages/webob/request.py, line 1320, in send
application, catch_exc_info=False)
  File /usr/lib/python2.7/dist-packages/webob/request.py, line 1284, in 
call_application
app_iter = application(self.environ, start_response)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 130, in __call__
resp = self.call_func(req, *args, **self.kwargs)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 195, in call_func
return self.func(req, *args, **kwargs)
  File /usr/local/lib/python2.7/dist-packages/osprofiler/web.py, line 106, in 
__call__
return request.get_response(self.application)
  File /usr/lib/python2.7/dist-packages/webob/request.py, line 1320, in send
application, catch_exc_info=False)
  File /usr/lib/python2.7/dist-packages/webob/request.py, line 1284, in 
call_application
app_iter = application(self.environ, start_response)
  File 
/usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token.py, line 
559, in __call__
return self._app(env, start_response)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 130, in __call__
resp = self.call_func(req, *args, **self.kwargs)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 195, in call_func
return self.func(req, *args, **kwargs)
  File /opt/stack/glance/glance/common/wsgi.py, line 394, in __call__
response = req.get_response(self.application)
  File /usr/lib/python2.7/dist-packages/webob/request.py, line 1320, in send
application, catch_exc_info=False)
  File /usr/lib/python2.7/dist-packages/webob/request.py, line 1284, in 
call_application
app_iter = application(self.environ, start_response)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 130, in __call__
resp = self.call_func(req, *args, **self.kwargs)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 195, in call_func
return self.func(req, *args, **kwargs)
  File /opt/stack/glance/glance/common/wsgi.py, line 394, in __call__
response = req.get_response(self.application)
  File /usr/lib/python2.7/dist-packages/webob/request.py, line 1320, in send
application, catch_exc_info=False)
  File /usr/lib/python2.7/dist-packages/webob/request.py, line 1284, in 
call_application
app_iter = application(self.environ, start_response)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 130, in __call__
resp = self.call_func(req, *args, **self.kwargs)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 195, in call_func
return self.func(req, *args, **kwargs)
  File /opt/stack/glance/glance/common/wsgi.py, line 394, in __call__
response = req.get_response(self.application)
  File /usr/lib/python2.7/dist-packages/webob/request.py, line 1320, in send
application, catch_exc_info=False)
  File /usr/lib/python2.7/dist-packages/webob/request.py, line 1284, in 
call_application
app_iter = application(self.environ, start_response)
  File /usr/lib/python2.7/dist-packages/paste/urlmap.py, line 206, in __call__
return app(environ, start_response)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 144, in __call__
return resp(environ, start_response)
  File /usr/local/lib/python2.7/dist-packages/routes/middleware.py, line 131, 
in __call__
response = self.app(environ, start_response)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 144, in __call__
return resp(environ, start_response)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 130, in __call__
resp = self.call_func(req, *args, **self.kwargs)
  File /usr/lib/python2.7/dist-packages/webob/dec.py, line 195, in call_func
return self.func(req, *args, **kwargs)
  File /opt/stack/glance/glance/common/wsgi.py, line 683, in __call__
request, **action_args)
  File 

[Yahoo-eng-team] [Bug 1380547] [NEW] Image is not added when filesystem_store_datadirs specified in glance configuration

[Abhishek Kekane]

Public bug reported:

If user specifies 'filesystem_store_datadirs' option in the glance api
configuration, he is not able to add the image to the specified location
as following response is returned to the user.

html
 head
  title410 Gone/title
 /head
 body
  h1410 Gone/h1
  Error in store configuration. Adding images to store is disabled.br /br /

 /body
/html (HTTP N/A)

Steps to reproduce:

1. Edit glance-api.conf file to add 'filesystem_store_datadirs' parameter.
   filesystem_store_datadirs = /opt/stack/data/glance/images/:1
   
   Note: Disable 'filesystem_store_datadir' option

2. restart glance-api service

3. create image
   glance image-create --file /etc/passwd --name passwd --container-format bare 
--disk-format raw

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New


** Tags: ntt

** Changed in: glance
 Assignee: (unassigned) = Abhishek Kekane (abhishek-kekane)

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

Title:
  Image is not added when filesystem_store_datadirs specified in glance
  configuration

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  If user specifies 'filesystem_store_datadirs' option in the glance api
  configuration, he is not able to add the image to the specified
  location as following response is returned to the user.

  html
   head
title410 Gone/title
   /head
   body
h1410 Gone/h1
Error in store configuration. Adding images to store is disabled.br /br 
/

   /body
  /html (HTTP N/A)

  Steps to reproduce:

  1. Edit glance-api.conf file to add 'filesystem_store_datadirs' parameter.
 filesystem_store_datadirs = /opt/stack/data/glance/images/:1
 
 Note: Disable 'filesystem_store_datadir' option

  2. restart glance-api service

  3. create image
 glance image-create --file /etc/passwd --name passwd --container-format 
bare --disk-format raw

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1380547/+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 1380617] [NEW] In-consistence behaviour for unshelve if snapshot and image is deleted from glance

[Abhishek Kekane]

Public bug reported:

In-consistence behaviour for unshelve if snapshot and image is deleted
from glance

When the instance is shelved it creates the instance snapshot in the glance.
If the instance snapshot and the image from which instance is created is 
deleted then unshelving the instance in the first try gives the error 
'ImageNotFound', and in second try the unshelve completes successfully and 
instance goes in the active state.

Steps to reproduce:
1. create instance, wait until it becomes active.
2. shelve the instance 
$ nova shelve instance_id or instance_name

3. A snapshot is created and uploaded to glance.
4. Delete the snapshot and the image from which instance is created in the 1st 
step. (using admin credentials)
5. unshelve the instance
$ nova unshelve instance_id or instance_name

6. Stack trace is printed on screen logs:

nova-copute log:
   ImageNotFound: Image 442ea9bb-b664-41b4-b38b-8f5a690998d6 could not be found.

glance-api log:
   2014-10-10 04:02:49.007 4546 DEBUG glance.api.v1.controller [-] Image 
476b81bc-d1b1-40db-bad8-4f37ae3c66ac is not active 
get_active_image_meta_or_404 /opt/stack/glance/glance/api/v1/controller.py:61
   2014-10-10 04:02:49.008 4546 INFO glance.wsgi.server [-] 10.69.4.130 - - 
[10/Oct/2014 04:02:49]
GET /v1/images/476b81bc-d1b1-40db-bad8-4f37ae3c66ac HTTP/1.1 404 400 0.121644

7. Once again unshelve the same instance.
$ nova unshelve instance_id or instance_name

8. This time you can not see the stack trace and instance goes in the active 
state successfully.
9. When I use nova show command, it shows that instance is booted from the same 
image which is used in step #1.

I have tested this scenario in the single node deployment.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: ntt

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

Title:
  In-consistence behaviour for unshelve if snapshot and image is deleted
  from glance

Status in OpenStack Compute (Nova):
  New

Bug description:
  In-consistence behaviour for unshelve if snapshot and image is deleted
  from glance

  When the instance is shelved it creates the instance snapshot in the glance.
  If the instance snapshot and the image from which instance is created is 
deleted then unshelving the instance in the first try gives the error 
'ImageNotFound', and in second try the unshelve completes successfully and 
instance goes in the active state.

  Steps to reproduce:
  1. create instance, wait until it becomes active.
  2. shelve the instance 
  $ nova shelve instance_id or instance_name

  3. A snapshot is created and uploaded to glance.
  4. Delete the snapshot and the image from which instance is created in the 
1st step. (using admin credentials)
  5. unshelve the instance
  $ nova unshelve instance_id or instance_name

  6. Stack trace is printed on screen logs:

  nova-copute log:
 ImageNotFound: Image 442ea9bb-b664-41b4-b38b-8f5a690998d6 could not be 
found.

  glance-api log:
 2014-10-10 04:02:49.007 4546 DEBUG glance.api.v1.controller [-] Image 
476b81bc-d1b1-40db-bad8-4f37ae3c66ac is not active 
  get_active_image_meta_or_404 /opt/stack/glance/glance/api/v1/controller.py:61
 2014-10-10 04:02:49.008 4546 INFO glance.wsgi.server [-] 10.69.4.130 - - 
[10/Oct/2014 04:02:49]
  GET /v1/images/476b81bc-d1b1-40db-bad8-4f37ae3c66ac HTTP/1.1 404 400 
0.121644

  7. Once again unshelve the same instance.
  $ nova unshelve instance_id or instance_name

  8. This time you can not see the stack trace and instance goes in the active 
state successfully.
  9. When I use nova show command, it shows that instance is booted from the 
same image which is used in step #1.

  I have tested this scenario in the single node deployment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1380617/+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 1380547] Re: Image is not added when filesystem_store_datadirs specified in glance configuration

[Abhishek Kekane]

The issue of moving deprecated filesystem options from DEFAULT sections
to glance_store section in glance-api.conf, is addressed by this bug
https://bugs.launchpad.net/bugs/1380689

Marking this bug as invalid.

** Changed in: glance
   Status: New = Invalid

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

Title:
  Image is not added when filesystem_store_datadirs specified in glance
  configuration

Status in OpenStack Image Registry and Delivery Service (Glance):
  Invalid

Bug description:
  If user specifies 'filesystem_store_datadirs' option in the glance api
  configuration, he is not able to add the image to the specified
  location as following response is returned to the user.

  html
   head
title410 Gone/title
   /head
   body
h1410 Gone/h1
Error in store configuration. Adding images to store is disabled.br /br 
/

   /body
  /html (HTTP N/A)

  Steps to reproduce:

  1. Edit glance-api.conf file to add 'filesystem_store_datadirs' parameter.
 filesystem_store_datadirs = /opt/stack/data/glance/images/:1
 
 Note: Disable 'filesystem_store_datadir' option

  2. restart glance-api service

  3. create image
 glance image-create --file /etc/passwd --name passwd --container-format 
bare --disk-format raw

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1380547/+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 1326781] [NEW] v2 api returns 200 with blank response (no image data) for download_image policy

[Abhishek Kekane]

Public bug reported:

v2 api returns 200 with blank response (no image data) for
download_image policy

If you have enabled download_image policy in policy.json to role:admin then 
it should return 403 error if user other admin role is calling image-download 
api.
Presently it is returning 200 with blank response (no image data). If you 
enable cache filter, then it returns 403 error correctly.

Steps to reproduce:

1. Ensure following flavor is set in glance-api.conf
   [paste-deploy]
   flavor = keystone+cachemanagement

2. Disable cache
   a. Open /etc/glance/glance-api-paste.ini file.
   b. Remove cahce from following sections.
 [pipeline:glance-api-caching]
 [pipeline:glance-api-cachemanagement]
 [pipeline:glance-api-keystone+caching]
 [pipeline:glance-api-keystone+cachemanagement]
 [pipeline:glance-api-trusted-auth+cachemanagement]
   c. Save and exit from file.
   d. Restart the g-api (glance-api) service.

3. Ensure that 'download_image' policy is set in policy.json
   download_image: role:admin

4. Download image using v2 api for role other than admin
   a. source openrc normal_user normal_user
   b. glance --os-image-api-version 2 image-download image-id
   
   Output:
   ---
   ''
   
   glance-api screen log:
   --
2014-06-05 12:45:00.711 24883 INFO glance.wsgi.server [-] Traceback 
(most recent call last):
  File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 395, 
in handle_one_response
for data in result:
  File /mnt/stack/glance/glance/notifier.py, line 228, in get_data
for chunk in self.image.get_data():
  File /mnt/stack/glance/glance/api/policy.py, line 233, in get_data
self.policy.enforce(self.context, 'download_image', {})
  File /mnt/stack/glance/glance/api/policy.py, line 143, in enforce
exception.Forbidden, action=action)
  File /mnt/stack/glance/glance/api/policy.py, line 131, in _check
return policy.check(rule, target, credentials, *args, **kwargs)
  File /mnt/stack/glance/glance/openstack/common/policy.py, line 183, 
in check
raise exc(*args, **kwargs)
Forbidden: You are not authorized to complete this action.
2014-06-05 12:45:00.711 24883 INFO glance.wsgi.server [-] 10.146.146.4 
- - [05/Jun/2014 12:45:00] GET 
/v2/images/63826dea-e281-4ffe-821b-f598c747ba54/file HTTP/1.1 200 0 0.062499

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: ntt

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

Title:
  v2 api returns 200 with blank response (no image data) for
  download_image policy

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  v2 api returns 200 with blank response (no image data) for
  download_image policy

  If you have enabled download_image policy in policy.json to role:admin then 
it should return 403 error if user other admin role is calling image-download 
api.
  Presently it is returning 200 with blank response (no image data). If you 
enable cache filter, then it returns 403 error correctly.

  Steps to reproduce:

  1. Ensure following flavor is set in glance-api.conf
 [paste-deploy]
 flavor = keystone+cachemanagement

  2. Disable cache
 a. Open /etc/glance/glance-api-paste.ini file.
 b. Remove cahce from following sections.
   [pipeline:glance-api-caching]
   [pipeline:glance-api-cachemanagement]
   [pipeline:glance-api-keystone+caching]
   [pipeline:glance-api-keystone+cachemanagement]
   [pipeline:glance-api-trusted-auth+cachemanagement]
 c. Save and exit from file.
 d. Restart the g-api (glance-api) service.

  3. Ensure that 'download_image' policy is set in policy.json
 download_image: role:admin

  4. Download image using v2 api for role other than admin
 a. source openrc normal_user normal_user
 b. glance --os-image-api-version 2 image-download image-id
 
 Output:
 ---
 ''
 
 glance-api screen log:
 --
2014-06-05 12:45:00.711 24883 INFO glance.wsgi.server [-] Traceback 
(most recent call last):
  File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 395, 
in handle_one_response
for data in result:
  File /mnt/stack/glance/glance/notifier.py, line 228, in get_data
for chunk in self.image.get_data():
  File /mnt/stack/glance/glance/api/policy.py, line 233, in get_data
self.policy.enforce(self.context, 'download_image', {})
  File /mnt/stack/glance/glance/api/policy.py, line 143, in enforce
exception.Forbidden, action=action)
  File /mnt/stack/glance/glance/api/policy.py, line 131, in _check
return policy.check(rule, 

[Yahoo-eng-team] [Bug 1328900] [NEW] Boot From Image, Instance Source should list only images in dropdown while launching an instance

[Abhishek Kekane]

Public bug reported:

While creating n new instance, after selecting Boot from image from
the Instance Boot Source, images and image snapshots both gets
displayed in the dropdown on horizon.

Only image list should be displayed in Image Name: dropdown.

Steps to reproduce:

1. Login to horizon using admin credentials.
2. Click on Project tab and select admin project.
3. Click on Instances menu.
4. On Instances page click on Launch Instance button to create instances.
5. After launching an instance click on Create Snapshot button in the row 
   of newly created instance to create it's snapshot.
6. After successful execution of create snapshot click on Launch Instance 
button.
7. Click on Instance Boot Source: dropdown and select source as Boot from 
image.
8. Click on Image Name: dropdown.
9. Both Images and Snapshots will be displayed in the dropdown.

** Affects: horizon
 Importance: Undecided
 Status: New


** Tags: ntt

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1328900

Title:
  Boot From Image, Instance Source should list only images in dropdown
  while launching an instance

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  While creating n new instance, after selecting Boot from image from
  the Instance Boot Source, images and image snapshots both gets
  displayed in the dropdown on horizon.

  Only image list should be displayed in Image Name: dropdown.

  Steps to reproduce:

  1. Login to horizon using admin credentials.
  2. Click on Project tab and select admin project.
  3. Click on Instances menu.
  4. On Instances page click on Launch Instance button to create instances.
  5. After launching an instance click on Create Snapshot button in the row 
 of newly created instance to create it's snapshot.
  6. After successful execution of create snapshot click on Launch Instance 
button.
  7. Click on Instance Boot Source: dropdown and select source as Boot from 
image.
  8. Click on Image Name: dropdown.
  9. Both Images and Snapshots will be displayed in the dropdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1328900/+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 1337850] [NEW] Keystone service outputs error messages when SIGHUP signal is sent

[Abhishek Kekane]

Public bug reported:

When SIGHUP signal is send to keystone service, it stops the process and
while restarting the keystone process, it throws AttributeError:
'Server' object has no attribute 'reset'

Steps to reproduce:
1. Run keystone service as daemon.
2. Send SIGHUP signal to keystone service
   kill -1 parent_process_id_of_keystone

** Affects: keystone
 Importance: Undecided
 Status: New


** Tags: ntt

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

Title:
  Keystone service outputs error messages when SIGHUP signal is sent

Status in OpenStack Identity (Keystone):
  New

Bug description:
  When SIGHUP signal is send to keystone service, it stops the process
  and while restarting the keystone process, it throws AttributeError:
  'Server' object has no attribute 'reset'

  Steps to reproduce:
  1. Run keystone service as daemon.
  2. Send SIGHUP signal to keystone service
 kill -1 parent_process_id_of_keystone

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1337850/+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 1351026] Re: IdentityError in TokensV3TestJSON.test_rescope_token

[Abhishek Kekane]

** Also affects: glance
   Importance: Undecided
   Status: New

** No longer affects: glance

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

Title:
  IdentityError in TokensV3TestJSON.test_rescope_token

Status in OpenStack Identity (Keystone):
  In Progress
Status in Tempest:
  In Progress

Bug description:
  2014-07-31 19:07:29.894 | 
tempest.api.identity.admin.v3.test_tokens.TokensV3TestJSON.test_rescope_token[gate]
  2014-07-31 19:07:29.894 | 
---
  2014-07-31 19:07:29.895 | 
  2014-07-31 19:07:29.895 | Captured traceback:
  2014-07-31 19:07:29.895 | ~~~
  2014-07-31 19:07:29.895 | Traceback (most recent call last):
  2014-07-31 19:07:29.895 |   File 
tempest/api/identity/admin/v3/test_tokens.py, line 145, in test_rescope_token
  2014-07-31 19:07:29.895 | domain='Default')
  2014-07-31 19:07:29.895 |   File 
tempest/services/identity/v3/json/identity_client.py, line 587, in auth
  2014-07-31 19:07:29.895 | resp, body = self.post(self.auth_url, 
body=body)
  2014-07-31 19:07:29.895 |   File tempest/common/rest_client.py, line 
218, in post
  2014-07-31 19:07:29.895 | return self.request('POST', url, 
extra_headers, headers, body)
  2014-07-31 19:07:29.895 |   File 
tempest/services/identity/v3/json/identity_client.py, line 613, in request
  2014-07-31 19:07:29.895 | 'Unexpected status code 
{0}'.format(resp.status))
  2014-07-31 19:07:29.896 | IdentityError: Got identity error
  2014-07-31 19:07:29.896 | Details: Unexpected status code 404

  The following logstash query has 24 hits in last 48 hours:
  IdentityError: Got identity error AND 
build_name:check-tempest-dsvm-postgres-full

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1351026/+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 1284996] [NEW] reduce VM network down time during live (block) migration

[Abhishek Kekane]

Public bug reported:

It appears that during live migration, for certain duration network is
unavailable and there is a scope to reduce the network downtime.

Please refer http://paste.openstack.org/show/69718/ to check the packet
loss during live migration.

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New


** Tags: ntt

** Changed in: nova
 Assignee: (unassigned) = Abhishek Kekane (abhishek-kekane)

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

Title:
  reduce VM network down time during live (block) migration

Status in OpenStack Compute (Nova):
  New

Bug description:
  It appears that during live migration, for certain duration network is
  unavailable and there is a scope to reduce the network downtime.

  Please refer http://paste.openstack.org/show/69718/ to check the
  packet loss during live migration.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1284996/+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 1285000] [NEW] Delete a VM when live-migration is in progress

[Abhishek Kekane]

Public bug reported:

During live migration, the vm undergoes various
task_state/power_state/VM_state changes and uers are able to terminate
virtual machine while live migration is running.

IMO, one of the possible solution is to restrict deletion of VM if live-
migration is in progress.

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: ntt

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

Title:
  Delete a VM when live-migration is in progress

Status in OpenStack Compute (Nova):
  New

Bug description:
  During live migration, the vm undergoes various
  task_state/power_state/VM_state changes and uers are able to terminate
  virtual machine while live migration is running.

  IMO, one of the possible solution is to restrict deletion of VM if
  live-migration is in progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1285000/+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 1287093] [NEW] Selected Instances are not deleted with pagination

[Abhishek Kekane]

Public bug reported:

Instance is not getting deleted from other than first page of pagination
when pagination is enabled.

Steps to reproduce:

1. Login to horizon using admin credentials.
2. Click on settings menu.
3. In User Settings menu set Items Per Page count as 5 and click on Save 
button to save the settings.
4. Click on Project tab and select admin project.
5. Click on Instances menu.
6. On Instances page click on Launch Instance button to add instances.
7. Add 6 to 7 instances.
8. On the Instances page 5 instances will be displayed. Click on More » link 
at the bottom of Instances table.
9. On the second page select instance and delete it.
10. You will be redirected to 1st page and the selected instances from 2nd page 
will not get deleted.

Note:
If you delete the instances from 1st page then it will get deleted.

** Affects: horizon
 Importance: Undecided
 Assignee: Ankit Agrawal (ankitagrawal)
 Status: New


** Tags: ntt

** Changed in: horizon
 Assignee: (unassigned) = Abhishek Kekane (abhishek-kekane)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1287093

Title:
  Selected Instances are not deleted with pagination

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Instance is not getting deleted from other than first page of
  pagination when pagination is enabled.

  Steps to reproduce:

  1. Login to horizon using admin credentials.
  2. Click on settings menu.
  3. In User Settings menu set Items Per Page count as 5 and click on 
Save button to save the settings.
  4. Click on Project tab and select admin project.
  5. Click on Instances menu.
  6. On Instances page click on Launch Instance button to add instances.
  7. Add 6 to 7 instances.
  8. On the Instances page 5 instances will be displayed. Click on More » 
link at the bottom of Instances table.
  9. On the second page select instance and delete it.
  10. You will be redirected to 1st page and the selected instances from 2nd 
page will not get deleted.

  Note:
  If you delete the instances from 1st page then it will get deleted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1287093/+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 1287101] [NEW] restrict live migration when users are connected to the VNC console

[Abhishek Kekane]

Public bug reported:

Users should not be affected due to live migration especially when they
are using vnc consoles.

Possible Solution:
A new parameter force will be added to the existing live migration api, if 
it's set to False and user is connected to the VNC console, it won't live 
migrate that vm.
If force parameter is set to True then even if user is connected to VNC 
console, live migration will be performed.
To detect whether users are connected to the vnc console or not, we can check 
if the vnc port is opened on the compute node where the vm is running.

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New


** Tags: ntt

** Description changed:

  Users should not be affected due to live migration especially when they
- are using vnc consoles.\
+ are using vnc consoles.
  
  Possible Solution:
  A new parameter force will be added to the existing live migration api, if 
it's set to False and user is connected to the VNC console, it won't live 
migrate that vm.
  If force parameter is set to True then even if user is connected to VNC 
console, live migration will be performed.
  To detect whether users are connected to the vnc console or not, we can check 
if the vnc port is opened on the compute node where the vm is running.

** Changed in: nova
 Assignee: (unassigned) = Abhishek Kekane (abhishek-kekane)

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

Title:
  restrict live migration when users are connected to the VNC console

Status in OpenStack Compute (Nova):
  New

Bug description:
  Users should not be affected due to live migration especially when
  they are using vnc consoles.

  Possible Solution:
  A new parameter force will be added to the existing live migration api, if 
it's set to False and user is connected to the VNC console, it won't live 
migrate that vm.
  If force parameter is set to True then even if user is connected to VNC 
console, live migration will be performed.
  To detect whether users are connected to the vnc console or not, we can check 
if the vnc port is opened on the compute node where the vm is running.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1287101/+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 1288583] [NEW] Space is not allowed while creating Key Pairs

[Abhishek Kekane]

Public bug reported:

Space is not allowed while creating Key Pairs


If you enter the space in the Key Pair Name while creating new key pairs 
following error is displayed in a popup message.
Key pair names may only contain letters, numbers, underscores and hyphens.

Steps to reproduce:
---
1. Login to Horizon dashboard
2. On Project tab click on Access  Security Group
3. Click on Key Pairs tab and click on Create Key Pair button
4. Enter space in Key Pair Name e.g. Sample Key Pair
5. Click on Create Key Pair button
6. Key pair names may only contain letters, numbers, underscores and hyphens. 
error message will be displayed.

Note:
-
If you create the key pair using nova-client then it will create the key pair 
with space in name.

nova keypair-add Sample Key Pair

nova keypair-show Sample Key Pair
+-+-+
| Property| Value   |
+-+-+
| created_at  | 2014-03-06T06:56:41.00  |
| deleted | False   |
| deleted_at  | -   |
| fingerprint | 03:e7:67:f4:f0:20:87:31:20:ad:31:0d:05:73:04:c2 |
| id  | 1   |
| name| Sample Key Pair |
| updated_at  | -   |
| user_id | 98bbc9ecd6eb4c6cab2d08d7f560d0f1|
+-+-+

** Affects: horizon
 Importance: Undecided
 Assignee: Rajesh Tailor (rajesh-tailor)
 Status: New


** Tags: ntt

** Changed in: horizon
 Assignee: (unassigned) = Abhishek Kekane (abhishek-kekane)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1288583

Title:
  Space is not allowed while creating Key Pairs

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Space is not allowed while creating Key Pairs

  
  If you enter the space in the Key Pair Name while creating new key pairs 
following error is displayed in a popup message.
  Key pair names may only contain letters, numbers, underscores and hyphens.

  Steps to reproduce:
  ---
  1. Login to Horizon dashboard
  2. On Project tab click on Access  Security Group
  3. Click on Key Pairs tab and click on Create Key Pair button
  4. Enter space in Key Pair Name e.g. Sample Key Pair
  5. Click on Create Key Pair button
  6. Key pair names may only contain letters, numbers, underscores and 
hyphens. error message will be displayed.

  Note:
  -
  If you create the key pair using nova-client then it will create the key pair 
with space in name.

  nova keypair-add Sample Key Pair

  nova keypair-show Sample Key Pair
  +-+-+
  | Property| Value   |
  +-+-+
  | created_at  | 2014-03-06T06:56:41.00  |
  | deleted | False   |
  | deleted_at  | -   |
  | fingerprint | 03:e7:67:f4:f0:20:87:31:20:ad:31:0d:05:73:04:c2 |
  | id  | 1   |
  | name| Sample Key Pair |
  | updated_at  | -   |
  | user_id | 98bbc9ecd6eb4c6cab2d08d7f560d0f1|
  +-+-+

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1288583/+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 1291367] [NEW] Leading, trailing spaces are truncated for security group names on dashboard

[Abhishek Kekane]

Public bug reported:

When you create the security group with leading and trailing white spaces in 
security group name, you can see it using
nova secgroup-list command, where as in Horizon dashboard under Security 
Group, the same security group name is displayed without leading and trailing 
white spaces.

If you click on Edit security group, then security group name will be
displayed with leading and trailing white spaces.

Steps to reproduce:

1. Create security group with leading and trailing white spaces in name.
 nova secgroup-create ' Security Group Name ' 'Security Group 
Description'

2. Run secgroup-list from command line you can see Security Group Name with 
leading and trailing spaces.
 nova secgroup-list

++-++
| Id | Name| Description|
++-++
| 2  |  Security Group Name  | Security Group Description |
| 1  | default | default|
++-++

3. Login to the horizon dashboard.
4. Click on Access  Security link from the tab.
5. It will show you the list of available security groups.
6. Check for the security group name you have created.
7. Here it will display the name as Security Group Name instead of  
Security Group Name .
8. Click on More button and select Edit Security Group
9. In Popup box security group will be displayed with leading and trailing 
white spaces.

IMO, We should display the security group names on the dashboard as it
is stored in the database i.e. with leading and trailing white spaces.

If to remove the leading and trailing spaces from the name while creating
security groups, we need to write migration script to update the existing
security groups to remove the leading and trailing spaces in existing names.

** Affects: horizon
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New


** Tags: ntt

** Changed in: horizon
 Assignee: (unassigned) = Abhishek Kekane (abhishek-kekane)

** Description changed:

  When you create the security group with leading and trailing white spaces in 
security group name, you can see it using
  nova secgroup-list command, where as in Horizon dashboard under Security 
Group, the same security group name is displayed without leading and trailing 
white spaces.
  
  If you click on Edit security group, then security group name will be
  displayed with leading and trailing white spaces.
  
- 
  Steps to reproduce:
  
  1. Create security group with leading and trailing white spaces in name.
-  nova secgroup-create ' Security Group Name ' 'Security Group 
Description'
+  nova secgroup-create ' Security Group Name ' 'Security Group 
Description'
  
  2. Run secgroup-list from command line you can see Security Group Name with 
leading and trailing spaces.
-  nova secgroup-list
+  nova secgroup-list
  
- ++-++
- | Id | Name| Description|
- ++-++
- | 2  |  Security Group Name  | Security Group Description |
- | 1  | default | default|
- ++-++
+ ++-++
+ | Id | Name| Description|
+ ++-++
+ | 2  |  Security Group Name  | Security Group Description |
+ | 1  | default | default|
+ ++-++
  
  3. Login to the horizon dashboard.
  4. Click on Access  Security link from the tab.
  5. It will show you the list of available security groups.
  6. Check for the security group name you have created.
  7. Here it will display the name as Security Group Name instead of  
Security Group Name .
  8. Click on More button and select Edit Security Group
  9. In Popup box security group will be displayed with leading and trailing 
white spaces.
  
- 
- IMO, We should display the security group names on the dashboard as it is 
stored in
- the database.
+ IMO, We should display the security group names on the dashboard as it
+ is stored in the database i.e. with leading and trailing white spaces.
  
  If to remove the leading and trailing spaces from the name while creating
  security groups, we need to write migration script to update the existing
  security groups to remove the leading and trailing spaces in existing names.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon

[Yahoo-eng-team] [Bug 1317392] [NEW] Glance image-list returns different results for MySQL and PostgreSQL

[Abhishek Kekane]

Public bug reported:

Glance image-list is returning different results for MySQL and
PostgreSQL with sort_key=name

Steps to reproduce:

1. Assume images with following names are present in database
   
   'image--1439541877',
   'Fedora-x86_64-20-20131211.1-sda', 
   'cirros-0.3.1-x86_64-uec-ramdisk',
   'cirros-0.3.1-x86_64-uec-kernel',
   'cirros-0.3.1-x86_64-uec'

2.   
a. For MySQL :

List Images with sort_key = name
   $ glance image-list --sort-key=name --sort-dir=desc

Output:
+--+-+-+--+--+---+
| ID   | Name| Disk 
Format | Container Format | Size | Status |
+--+-+-+--+--++
| 662998c2-4e19-4ddf-9eb4-91ad1ffae8c9 | image--1439541877   | 
qcow2   | bare | 12185586 | active 
| d067e2bd-7679-4e36-a1d0-0715e1d11a84 | cirros-0.3.1-x86_64-uec | ami  
   | ami  | 25165824 | active |
| 61ebb7f7-56ff-423b-8816-838a31ada1bf | cirros-0.3.1-x86_64-uec-kernel  | aki  
   | aki  | 4955792  | active |
| 87f3642c-a1b7-4925-948c-05684b5fcb93 | cirros-0.3.1-x86_64-uec-ramdisk | ari  
   | ari  | 3714968  | active |
| e6aeba3c-07d9-4b40-96c9-8013c52e8816 | Fedora-x86_64-20-20131211.1-sda | 
qcow2   | bare | 2341 | queued |
---
Here ,'Fedora-x86_64-20-20131211.1-sda' is at last position . 

b. For PostgreSQL :

List Images with sort_key = name
   $ glance image-list --sort-key=name --sort-dir=desc

Output:
+--+-+-+--+--+---+
| ID   | Name| Disk 
Format | Container Format | Size | Status |
+--+-+-+--+--++
| 662998c2-4e19-4ddf-9eb4-91ad1ffae8c9 | image--1439541877   | 
qcow2   | bare | 12185586 | active 
| e6aeba3c-07d9-4b40-96c9-8013c52e8816 | Fedora-x86_64-20-20131211.1-sda | 
qcow2   | bare | 2341 | queued |
| d067e2bd-7679-4e36-a1d0-0715e1d11a84 | cirros-0.3.1-x86_64-uec | ami  
   | ami  | 25165824 | active |
| 61ebb7f7-56ff-423b-8816-838a31ada1bf | cirros-0.3.1-x86_64-uec-kernel  | aki  
   | aki  | 4955792  | active |
| 87f3642c-a1b7-4925-948c-05684b5fcb93 | cirros-0.3.1-x86_64-uec-ramdisk | ari  
   | ari  | 3714968  | active |
---
 
Here 'Fedora-x86_64-20-20131211.1-sda' is at 2nd position.
  
Note :
I am adding a new test case in glance tempest to 'list image with sort_key'
Blueprint: testcases-expansion-icehouse

But after submitting the patch to the community, Jenkins is continuously 
failing with mismatch error for Test: check-tempest-dsvm-postgres-full
Please refer:
http://logs.openstack.org/69/81769/12/check/check-tempest-dsvm-postgres-full/411e98c/console.html

Locally this test case is getting passed where i am using MySQL
Database.

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: ntt

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

Title:
  Glance image-list returns different results for MySQL and PostgreSQL

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  Glance image-list is returning different results for MySQL and
  PostgreSQL with sort_key=name

  Steps to reproduce:

  1. Assume images with following names are present in database
 
 'image--1439541877',
 'Fedora-x86_64-20-20131211.1-sda', 
 'cirros-0.3.1-x86_64-uec-ramdisk',
 'cirros-0.3.1-x86_64-uec-kernel',
 'cirros-0.3.1-x86_64-uec'

  2.   
  a. For MySQL :

  List Images with sort_key = name
 $ glance image-list --sort-key=name --sort-dir=desc

  Output:
  
+--+-+-+--+--+---+
  | ID   | Name| 
Disk Format | Container Format | Size | Status |
  
+--+-+-+--+--++
  | 662998c2-4e19-4ddf-9eb4-91ad1ffae8c9 | image--1439541877   | 
qcow2   | bare | 12185586 | active 
  | d067e2bd-7679-4e36-a1d0-0715e1d11a84 | 

[Yahoo-eng-team] [Bug 1387973] [NEW] Normal user not able to download image if protected property is not associated with the image with restrict-download policy

[Abhishek Kekane]

Public bug reported:

If restrict download rule is configured in policy.json, and image is
added without protected property mentioned in restricted rule, then
normal users (other than admin) not able to download the image.

Steps to reproduce:

1. Create normal_user with _member_ role using horizon

2. Configure download rule in policy.json

   download_image: role:admin or rule:restricted,
   restricted: not ('test_1234':%(test_key)s and role:_member_),

3. Restart glance-api service

4. create image without property 'test_key' with admin user

   i. source devstack/openrc admin admin
   ii. glance image-create
   iii. glance image-update image_id --name non_protected --disk-format qcow2 
--container-format bare --is-public True --file /home/openstack/api.log

5. Try to download the newly created image with normal_user.

   i. source devstack/openrc normal_user admin
   ii. glance image-download image_id

It returns 403 Forbidden response to the user, where as admin user can
download the image successfully.

Expected behavior is all users can download the images if restricted
property is not added.

Note:
With the current oslo-incubator policy module, this issue is not reproducible.

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: ntt

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

Title:
  Normal user not able to download image if protected property is not
  associated with the image with restrict-download policy

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  If restrict download rule is configured in policy.json, and image is
  added without protected property mentioned in restricted rule, then
  normal users (other than admin) not able to download the image.

  Steps to reproduce:

  1. Create normal_user with _member_ role using horizon

  2. Configure download rule in policy.json

 download_image: role:admin or rule:restricted,
 restricted: not ('test_1234':%(test_key)s and role:_member_),

  3. Restart glance-api service

  4. create image without property 'test_key' with admin user

 i. source devstack/openrc admin admin
 ii. glance image-create
 iii. glance image-update image_id --name non_protected --disk-format 
qcow2 --container-format bare --is-public True --file /home/openstack/api.log

  5. Try to download the newly created image with normal_user.

 i. source devstack/openrc normal_user admin
 ii. glance image-download image_id

  It returns 403 Forbidden response to the user, where as admin user can
  download the image successfully.

  Expected behavior is all users can download the images if restricted
  property is not added.

  Note:
  With the current oslo-incubator policy module, this issue is not reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1387973/+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 1316137] Re: glance --location images handling is hiding HTTP errors and uses incorrect HTTP codes...

[Abhishek Kekane]

** Also affects: glance-store
   Importance: Undecided
   Status: New

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

Title:
  glance --location images handling is hiding HTTP errors and uses
  incorrect HTTP codes...

Status in OpenStack Image Registry and Delivery Service (Glance):
  New
Status in OpenStack Glance backend store-drivers library (glance_store):
  New

Bug description:
  1) Glance is hiding error messages when used with --location. If the
  URL returns HTTP 404, glance is just ignoring it.

  2) Reply to GET request to http://CENSORED:9292/v1/images/2e34a168
  -62ca-412d-84bb-852fcaf2a391 contains header:

     location: http://CENSORED:9292/v1/images/2e34a168-62ca-412d-84bb-
  852fcaf2a391

  which is referring the same URL. This feels weird.

  3) It also replies with HTTP 200 in the case above, so why does the reply 
contain the location header?
  How can it reply 200 when it couldn't have succeed to download the image?

  [root@cloudimg ~(keystone_admin)]# glance image-create --location 
http://www.google.com/glance_handles_404_and_other_errors_incorrectly.html 
--is-public False --container-format bare --disk-format qcow2 --name 404.html; 
echo exit code: $?
  /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: 
PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp 
= 5 to avoid timing attack vulnerability.
    _warn(Not using mpz_powm_sec.  You should rebuild using libgmp = 5 to 
avoid timing attack vulnerability., PowmInsecureWarning)
  +--+--+
  | Property | Value|
  +--+--+
  | checksum | None |
  | container_format | bare |
  | created_at   | 2014-05-05T12:42:17  |
  | deleted  | False|
  | deleted_at   | None |
  | disk_format  | qcow2|
  | id   | 2e34a168-62ca-412d-84bb-852fcaf2a391 |
  | is_public| False|
  | min_disk | 0|
  | min_ram  | 0|
  | name | 404.html |
  | owner| 56be9abf0ca24193908472465157112f |
  | protected| False|
  | size | 0|
  | status   | active   |
  | updated_at   | 2014-05-05T12:42:17  |
  +--+--+
  exit code: 0

  [root@cloudimg ~(keystone_admin)]# glance --debug image-download --file 
404.html 404.html; echo exit code: $?
  /usr/lib64/python2.6/site-packages/Crypto/Util/number.py:57: 
PowmInsecureWarning: Not using mpz_powm_sec.  You should rebuild using libgmp 
= 5 to avoid timing attack vulnerability.
    _warn(Not using mpz_powm_sec.  You should rebuild using libgmp = 5 to 
avoid timing attack vulnerability., PowmInsecureWarning)
  curl -i -X GET -H 'X-Auth-Token: 
MIIO3wYJKoZIhvcNAQcCoIIO0DC...EcKIsfbUbm5A74Gg==' -H 'Content-Type: 
application/json' -H 'User-Agent: python-glanceclient' 
http://CENSORED:9292/v1/images/detail?limit=20name=404.html

  HTTP/1.1 200 OK
  date: Mon, 05 May 2014 12:44:06 GMT
  content-length: 425
  content-type: application/json; charset=UTF-8
  x-openstack-request-id: req-d1bb2f3a-31ea-4da8-b1a5-e8a021f6e122

  {images: [{status: active, name: 404.html, deleted: false,
  container_format: bare, created_at: 2014-05-05T12:42:17,
  disk_format: qcow2, updated_at: 2014-05-05T12:42:17,
  min_disk: 0, protected: false, id: 2e34a168-62ca-412d-84bb-
  852fcaf2a391, min_ram: 0, checksum: null, owner:
  56be9abf0ca24193908472465157112f, is_public: false, deleted_at:
  null, properties: {}, size: 0}]}

  curl -i -X GET -H 'X-Auth-Token:
  MIIO3wYJKoZIhvcNAQcCo...EcKIsfbUbm5A74Gg==' -H 'Content-Type:
  application/octet-stream' -H 'User-Agent: python-glanceclient'
  http://CENSORED:9292/v1/images/2e34a168-62ca-412d-84bb-852fcaf2a391

  HTTP/1.1 200 OK
  content-length: 0
  x-image-meta-id: 2e34a168-62ca-412d-84bb-852fcaf2a391
  date: Mon, 05 May 2014 12:44:07 GMT
  x-image-meta-deleted: False
  x-image-meta-container_format: bare
  x-image-meta-protected: False
  x-image-meta-min_disk: 0
  x-image-meta-created_at: 2014-05-05T12:42:17
  x-image-meta-size: 0
  x-image-meta-status: active
  location: http://CENSORED:9292/v1/images/2e34a168-62ca-412d-84bb-852fcaf2a391
  x-image-meta-is_public: False
  x-image-meta-min_ram: 0
  x-image-meta-owner: 56be9abf0ca24193908472465157112f
  x-image-meta-updated_at: 2014-05-05T12:42:17
  content-type: 

[Yahoo-eng-team] [Bug 1404801] [NEW] Unshelve instance not working if instance is boot from volume

[Abhishek Kekane]

Public bug reported:

If instance is booted from volume, then shelving the instance sets the
status as SHELVED_OFFLOADED, instance files are getting deleted properly
from the base path. When you call the unshelve instance, it fails on the
conductor with error Unshelve attempted but the image_id is not
provided, and instance goes in to error state.

Steps to reproduce:
---

1. Log in to Horizon, create a new volume.
2. Create an Instance using newly created volume.
3. Verify instance is in active state.
$ source devstack/openrc demo demo
$ nova list
+--+--+++-+--+
| ID   | Name | Status | Task State | Power 
State | Networks |
+--+--+++-+--+
| dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | ACTIVE | -  | Running   
  | private=10.0.0.3 |
+--+--+++-+--+

4. Shelve the instance
$ nova shelve instance-uuid

5. Verify the status is SHELVED_OFFLOADED.
$ nova list
+--+--+---++-+--+
| ID   | Name | Status| Task State 
| Power State | Networks |
+--+--+---++-+--+
| dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | SHELVED_OFFLOADED | -  
| Shutdown| private=10.0.0.3 |
+--+--+---++-+--+

6. Unshelve the instance.
$ nova unshelve instance-uuid

Following stack-trace logged in nova-conductor

2014-12-19 02:55:59.634 ERROR nova.conductor.manager 
[req-a071fbc9-1c23-4e7a-8adf-7b3d0951aadf demo demo] [instance: 
dae3a13b-6aa8-4794-93cd-5ab7bf90f604] Unshelve attempted but the image_id is 
not provided
2014-12-19 02:55:59.647 ERROR oslo.messaging.rpc.dispatcher 
[req-a071fbc9-1c23-4e7a-8adf-7b3d0951aadf demo demo] Exception during message 
handling: Error during unshelve instance dae3a13b-6aa8-4794-93cd-5ab7bf90f604: 
Unshelve attempted but the image_id is not provided
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher Traceback (most 
recent call last):
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 
137, in _dispatch_and_reply
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher 
incoming.message))
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 
180, in _dispatch
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher return 
self._do_dispatch(endpoint, method, ctxt, args)
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher   File 
/usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 
126, in _do_dispatch
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher result = 
getattr(endpoint, method)(ctxt, **new_args)
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/nova/nova/conductor/manager.py, line 727, in unshelve_instance
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher 
instance_id=instance.uuid, reason=reason)
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher UnshelveException: 
Error during unshelve instance dae3a13b-6aa8-4794-93cd-5ab7bf90f604: Unshelve 
attempted but the image_id is not provided
2014-12-19 02:55:59.647 TRACE oslo.messaging.rpc.dispatcher

7. Instance goes into error state.
$ nova list
+--+--+++-+--+
| ID   | Name | Status | Task State | Power 
State | Networks |
+--+--+++-+--+
| dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | ERROR  | unshelving | Shutdown  
  | private=10.0.0.3 |
+--+--+++-+--+

Note:
1. This issue is reproducible with admin as well as demo tenant.
2. In all cases of shelved_offload_time values (-1, 0,  0) this issue is 
reproducible.

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New


** Tags: ntt

** Changed in: nova
 Assignee: (unassigned) = Abhishek Kekane (abhishek-kekane)

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

Title:
  Unshelve instance not working if instance is boot from volume

Status

[Yahoo-eng-team] [Bug 1404867] [NEW] Volume remains in-use status, if instance booted from volume deleted when it is in the error state

[Abhishek Kekane]

Public bug reported:

If the instance is booted from volume and goes in to error state due to some 
reason.
Volume from which instance is booted, remains in-use state even the instance is 
deleted.
IMO, volume should be detached so that it can be used to boot other instance.

Steps to reproduce:

1. Log in to Horizon, create a new volume.
2. Create an Instance using newly created volume.
3. Verify instance is in active state.
$ source devstack/openrc demo demo
$ nova list
+--+--+++-+--+
| ID   | Name | Status | Task State | Power 
State | Networks |
+--+--+++-+--+
| dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | ACTIVE | -  | Running   
  | private=10.0.0.3 |
+--+--+++-+--+

Note:
Use shelve-unshelve api to see the instance goes into error state.
unshelving volumed back instance does not work and sets instance state to error 
state (ref: https://bugs.launchpad.net/nova/+bug/1404801)

4. Shelve the instance
$ nova shelve instance-uuid

5. Verify the status is SHELVED_OFFLOADED.
$ nova list
+--+--+---++-+--+
| ID   | Name | Status| Task State 
| Power State | Networks |
+--+--+---++-+--+
| dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | SHELVED_OFFLOADED | -  
| Shutdown| private=10.0.0.3 |
+--+--+---++-+--+

6. Unshelve the instance.
$ nova unshelve instance-uuid

5. Verify the instance is in Error state.
$ nova list
+--+--+---++-+--+
| ID   | Name | Status| Task State 
| Power State | Networks |
+--+--+---++-+--+
| dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | Error | unshelving 
| Spawning| private=10.0.0.3 |
+--+--+---++-+--+

6. Delete the instance using Horizon.

7. Verify that volume still in in-use state
$ cinder list
+--++--+--+-+--+--+
|  ID  | Status | Name | Size | Volume Type | 
Bootable | Attached to  |
+--++--+--+-+--+--+
| 4aeefd25-10aa-42c2-9a2d-1c89a95b4d4f | in-use | test |  1   | lvmdriver-1 |   
true   | 8f7bdc24-1891-4bbb-8f0c-732b9cbecae7 |
+--++--+--+-+--+--+

8. In Horizon, volume Attached To information is displayed as
Attached to None on /dev/vda.

9. User is not able to delete this volume, or attached it to another
instance as it is still in use.

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New


** Tags: ntt

** Description changed:

  If the instance is booted from volume and goes in to error state due to some 
reason.
  Volume from which instance is booted, remains in-use state even the instance 
is deleted.
- IMO, volume should be detached so that it can be used to boot other instance. 
+ IMO, volume should be detached so that it can be used to boot other instance.
  
  Steps to reproduce:
  
  1. Log in to Horizon, create a new volume.
  2. Create an Instance using newly created volume.
  3. Verify instance is in active state.
  $ source devstack/openrc demo demo
  $ nova list
  
+--+--+++-+--+
  | ID   | Name | Status | Task State | Power 
State | Networks |
  
+--+--+++-+--+
  | dae3a13b-6aa8-4794-93cd-5ab7bf90f604 | nova | ACTIVE | -  | Running 
| private=10.0.0.3 |
  
+--+--+++-+--+
  
  Note:
  Use shelve-unshelve api to see the instance goes into error state.
- unshelving volume back instance does not work and sets instance state to 
error (ref: https://bugs.launchpad.net/nova/+bug/1404801)
+ unshelving volumed back instance

[Yahoo-eng-team] [Bug 1423861] [NEW] Jenkins pythnon26 and python27 failure for stable/juno

[Abhishek Kekane]

Public bug reported:

Following tests are failing on Jenkins for python26 and python27

glance.tests.functional.v1.test_copy_to_file.TestCopyToFile.test_copy_from_http_nonexistent
glance.tests.unit.test_store_image.TestStoreImage.test_image_change_delete_locations
glance.tests.unit.test_store_image.TestStoreImage.test_image_delete
glance.tests.unit.test_store_image.TestStoreImage.test_image_set_data_location_metadata
glance.tests.unit.test_store_image.TestStoreImage.test_image_set_data_unknown_size
glance.tests.unit.v1.test_api.TestGlanceAPI.test_add_copy_from_image_authorized_upload_image_authorized
glance.tests.unit.v2.test_image_data_resource.TestImageDataSerializer.test_download_not_found
glance.tests.unit.v2.test_images_resource.TestImagesController.test_update_add_locations_list

These tests are failing because stable/juno is using new glance_store
0.1.11

Refrences:
stable/juno patch: https://review.openstack.org/#/c/157067/
https://jenkins06.openstack.org/job/gate-glance-python26/774/console
https://jenkins02.openstack.org/job/gate-glance-python27/4681/console

** Affects: glance
 Importance: Undecided
 Status: New

** Description changed:

  Following tests are failing on Jenkins for python26 and python27
  
  
glance.tests.functional.v1.test_copy_to_file.TestCopyToFile.test_copy_from_http_nonexistent
  
glance.tests.unit.test_store_image.TestStoreImage.test_image_change_delete_locations
  glance.tests.unit.test_store_image.TestStoreImage.test_image_delete
  
glance.tests.unit.test_store_image.TestStoreImage.test_image_set_data_location_metadata
  
glance.tests.unit.test_store_image.TestStoreImage.test_image_set_data_unknown_size
  
glance.tests.unit.v1.test_api.TestGlanceAPI.test_add_copy_from_image_authorized_upload_image_authorized
  
glance.tests.unit.v2.test_image_data_resource.TestImageDataSerializer.test_download_not_found
  
glance.tests.unit.v2.test_images_resource.TestImagesController.test_update_add_locations_list
  
  These tests are failing because stable/juno is using new glance_store
  0.1.11
  
- 
  Refrences:
  stable/juno patch: https://review.openstack.org/#/c/157067/
  https://jenkins06.openstack.org/job/gate-glance-python26/774/console
  https://jenkins02.openstack.org/job/gate-glance-python27/4681/console

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

Title:
  Jenkins pythnon26 and python27 failure for stable/juno

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  Following tests are failing on Jenkins for python26 and python27

  
glance.tests.functional.v1.test_copy_to_file.TestCopyToFile.test_copy_from_http_nonexistent
  
glance.tests.unit.test_store_image.TestStoreImage.test_image_change_delete_locations
  glance.tests.unit.test_store_image.TestStoreImage.test_image_delete
  
glance.tests.unit.test_store_image.TestStoreImage.test_image_set_data_location_metadata
  
glance.tests.unit.test_store_image.TestStoreImage.test_image_set_data_unknown_size
  
glance.tests.unit.v1.test_api.TestGlanceAPI.test_add_copy_from_image_authorized_upload_image_authorized
  
glance.tests.unit.v2.test_image_data_resource.TestImageDataSerializer.test_download_not_found
  
glance.tests.unit.v2.test_images_resource.TestImagesController.test_update_add_locations_list

  These tests are failing because stable/juno is using new glance_store
  0.1.11

  Refrences:
  stable/juno patch: https://review.openstack.org/#/c/157067/
  https://jenkins06.openstack.org/job/gate-glance-python26/774/console
  https://jenkins02.openstack.org/job/gate-glance-python27/4681/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1423861/+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 1431784] Re: Traceback in glanceapi and glance registry in devstack

[Abhishek Kekane]

Hi Anand,

Earlier I was getting same error when I have pulled latest glance code.
Then  I have done fresh installation using devstack and this error is
not reproducible.


** Changed in: glance
   Status: New = Invalid

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

Title:
  Traceback in glanceapi and glance registry in devstack

Status in OpenStack Image Registry and Delivery Service (Glance):
  Invalid

Bug description:
  when running devstack  got the followng traceback whenever  do a
  listing of glance images from cli or horizon.The traceback occurs both
  in glance-ap and glance-registry.

  == glance image-list

  Trace in g-api
  +
  Logged from file policy.py, line 296
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'
  Logged from file client.py, line 401
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'
  Logged from file client.py, line 124
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'

  Traceback from g-registry
  
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'
  Logged from file session.py, line 509
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'
  Logged from file images.py, line 186
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'

  

[Yahoo-eng-team] [Bug 1431784] Re: Traceback in glanceapi and glance registry in devstack

[Abhishek Kekane]

** Changed in: glance
   Status: Invalid = New

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

Title:
  Traceback in glanceapi and glance registry in devstack

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  when running devstack  got the followng traceback whenever  do a
  listing of glance images from cli or horizon.The traceback occurs both
  in glance-ap and glance-registry.

  == glance image-list

  Trace in g-api
  +
  Logged from file policy.py, line 296
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'
  Logged from file client.py, line 401
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'
  Logged from file client.py, line 124
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'

  Traceback from g-registry
  
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'
  Logged from file session.py, line 509
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'
  Logged from file images.py, line 186
  Traceback (most recent call last):
    File /usr/lib/python2.7/logging/__init__.py, line 851, in emit
  msg = self.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/handlers.py, line 
69, in format
  return logging.StreamHandler.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 724, in format
  return fmt.format(record)
    File /usr/local/lib/python2.7/dist-packages/oslo_log/formatters.py, line 
235, in format
  return logging.Formatter.format(self, record)
    File /usr/lib/python2.7/logging/__init__.py, line 467, in format
  s = self._fmt % record.__dict__
  KeyError: 'user_id'

  This can be bug in glance or devstack

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

-- 
Mailing list: 

[Yahoo-eng-team] [Bug 1431860] [NEW] Cannot delete vm instance if send duplicate delete requests

[Abhishek Kekane]

Public bug reported:

I deployed openstack with icehouse rc1 and booted 100 vms on my nodes. After my 
testing, i tried to delete my vms at the same time. Then i fount all of my vms` 
status change to deleting but cannot be deleted. I checked my openstack, the 
rabbitmq-server crashed . Then i restart rabbitmq-server and my openstack nova 
services, sended the delete requests again and again, the vms still cannot be 
deleted. While , in havana, the vms can be deleted if received duplicate delete 
requests .
I think icehouse should handle duplicate delete requests like havana .


Note:
This bug is already reported in launchpad [1] but the fix [2] proposed to 
resolve it was reverted back as it was breaking the cells.

[1] https://bugs.launchpad.net/nova/+bug/1308342
[2] https://review.openstack.org/121800

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: In Progress


** Tags: ntt

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

Title:
  Cannot delete vm instance if send duplicate delete requests

Status in OpenStack Compute (Nova):
  In Progress

Bug description:
  I deployed openstack with icehouse rc1 and booted 100 vms on my nodes. After 
my testing, i tried to delete my vms at the same time. Then i fount all of my 
vms` status change to deleting but cannot be deleted. I checked my openstack, 
the rabbitmq-server crashed . Then i restart rabbitmq-server and my openstack 
nova services, sended the delete requests again and again, the vms still cannot 
be deleted. While , in havana, the vms can be deleted if received duplicate 
delete requests .
  I think icehouse should handle duplicate delete requests like havana .

  
  Note:
  This bug is already reported in launchpad [1] but the fix [2] proposed to 
resolve it was reverted back as it was breaking the cells.

  [1] https://bugs.launchpad.net/nova/+bug/1308342
  [2] https://review.openstack.org/121800

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1431860/+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 1423861] Re: Jenkins pythnon26 and python27 failure for stable/juno

[Abhishek Kekane]

** Changed in: glance
   Status: New = Invalid

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

Title:
  Jenkins pythnon26 and python27 failure for stable/juno

Status in OpenStack Image Registry and Delivery Service (Glance):
  Invalid

Bug description:
  Following tests are failing on Jenkins for python26 and python27

  
glance.tests.functional.v1.test_copy_to_file.TestCopyToFile.test_copy_from_http_nonexistent
  
glance.tests.unit.test_store_image.TestStoreImage.test_image_change_delete_locations
  glance.tests.unit.test_store_image.TestStoreImage.test_image_delete
  
glance.tests.unit.test_store_image.TestStoreImage.test_image_set_data_location_metadata
  
glance.tests.unit.test_store_image.TestStoreImage.test_image_set_data_unknown_size
  
glance.tests.unit.v1.test_api.TestGlanceAPI.test_add_copy_from_image_authorized_upload_image_authorized
  
glance.tests.unit.v2.test_image_data_resource.TestImageDataSerializer.test_download_not_found
  
glance.tests.unit.v2.test_images_resource.TestImagesController.test_update_add_locations_list

  These tests are failing because stable/juno is using new glance_store
  0.1.11

  Refrences:
  stable/juno patch: https://review.openstack.org/#/c/157067/
  https://jenkins06.openstack.org/job/gate-glance-python26/774/console
  https://jenkins02.openstack.org/job/gate-glance-python27/4681/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1423861/+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 1433435] [NEW] Change http_keepalive default value from Ture to False

[Abhishek Kekane]

Public bug reported:

In order to close the client socket connection explicitly after the
response is sent and read successfully by the client, you simply have to
set keepalive to False when you create a wsgi server.

Right now it is set to True for backward compatibility.

** Affects: glance
 Importance: Medium
 Status: Confirmed


** Tags: ntt

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

Title:
  Change http_keepalive default value from Ture to False

Status in OpenStack Image Registry and Delivery Service (Glance):
  Confirmed

Bug description:
  In order to close the client socket connection explicitly after the
  response is sent and read successfully by the client, you simply have
  to set keepalive to False when you create a wsgi server.

  Right now it is set to True for backward compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1433435/+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 1442006] [NEW] failed to reach SHELVED_OFFLOADED status within the required time

[Abhishek Kekane]

Public bug reported:

check-grenade-dsvm-partial-ncpu is failing for
'tempest.scenario.test_shelve_instance.TestShelveInstance.test_shelve_instance'
with following error,

Captured traceback:
2015-04-08 16:08:42.672 | ~~~
2015-04-08 16:08:42.672 | Traceback (most recent call last):
2015-04-08 16:08:42.673 |   File tempest/test.py, line 129, in wrapper
2015-04-08 16:08:42.673 | return f(self, *func_args, **func_kwargs)
2015-04-08 16:08:42.673 |   File 
tempest/scenario/test_shelve_instance.py, line 94, in test_shelve_instance
2015-04-08 16:08:42.674 | self._shelve_then_unshelve_server(server)
2015-04-08 16:08:42.674 |   File 
tempest/scenario/test_shelve_instance.py, line 54, in 
_shelve_then_unshelve_server
2015-04-08 16:08:42.674 | server['id'], 'SHELVED_OFFLOADED', 
extra_timeout=offload_time)
2015-04-08 16:08:42.675 |   File 
tempest/services/compute/json/servers_client.py, line 183, in 
wait_for_server_status
2015-04-08 16:08:42.675 | ready_wait=ready_wait)
2015-04-08 16:08:42.675 |   File tempest/common/waiters.py, line 94, in 
wait_for_server_status
2015-04-08 16:08:42.676 | raise exceptions.TimeoutException(message)
2015-04-08 16:08:42.676 | tempest.exceptions.TimeoutException: Request 
timed out
2015-04-08 16:08:42.676 | Details: 
(TestShelveInstance:test_shelve_instance) Server 
5623198f-fc72-4888-8fde-084a5222b147 failed to reach SHELVED_OFFLOADED status 
and task state None within the required time (196 s). Current status: ACTIVE. 
Current task state: None.

** Affects: nova
 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/1442006

Title:
  failed to reach SHELVED_OFFLOADED status within the required time

Status in OpenStack Compute (Nova):
  New

Bug description:
  check-grenade-dsvm-partial-ncpu is failing for
  
'tempest.scenario.test_shelve_instance.TestShelveInstance.test_shelve_instance'
  with following error,

  Captured traceback:
  2015-04-08 16:08:42.672 | ~~~
  2015-04-08 16:08:42.672 | Traceback (most recent call last):
  2015-04-08 16:08:42.673 |   File tempest/test.py, line 129, in wrapper
  2015-04-08 16:08:42.673 | return f(self, *func_args, **func_kwargs)
  2015-04-08 16:08:42.673 |   File 
tempest/scenario/test_shelve_instance.py, line 94, in test_shelve_instance
  2015-04-08 16:08:42.674 | self._shelve_then_unshelve_server(server)
  2015-04-08 16:08:42.674 |   File 
tempest/scenario/test_shelve_instance.py, line 54, in 
_shelve_then_unshelve_server
  2015-04-08 16:08:42.674 | server['id'], 'SHELVED_OFFLOADED', 
extra_timeout=offload_time)
  2015-04-08 16:08:42.675 |   File 
tempest/services/compute/json/servers_client.py, line 183, in 
wait_for_server_status
  2015-04-08 16:08:42.675 | ready_wait=ready_wait)
  2015-04-08 16:08:42.675 |   File tempest/common/waiters.py, line 94, in 
wait_for_server_status
  2015-04-08 16:08:42.676 | raise exceptions.TimeoutException(message)
  2015-04-08 16:08:42.676 | tempest.exceptions.TimeoutException: Request 
timed out
  2015-04-08 16:08:42.676 | Details: 
(TestShelveInstance:test_shelve_instance) Server 
5623198f-fc72-4888-8fde-084a5222b147 failed to reach SHELVED_OFFLOADED status 
and task state None within the required time (196 s). Current status: ACTIVE. 
Current task state: None.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1442006/+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 1505134] [NEW] error message not clear when image-show is called on deactivated image

[Abhishek Kekane]

Public bug reported:

Error message is not clear when user tries to use image-show on
deactivated image.

Steps to reproduce:
1. Create image
2. Deactivate image
3. Call image-show on deactivated image

Actual message:
glance image-show 5f0f914b-9f04-42c4-9769-07dc09e09056
u'deactivated' is not one of [u'queued', u'saving', u'active', u'killed', 
u'deleted', u'pending_delete']

Failed validating u'enum' in schema[u'properties'][u'status']:
{u'description': u'Status of the image (READ-ONLY)',
 u'enum': [u'queued',
   u'saving',
   u'active',
   u'killed',
   u'deleted',
   u'pending_delete'],
 u'type': u'string'}

On instance[u'status']:
u'deactivated'

Expected image:
something like Image  is deactivated

** Affects: glance
 Importance: Undecided
 Status: New

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

Title:
  error message not clear when image-show is called on deactivated image

Status in Glance:
  New

Bug description:
  Error message is not clear when user tries to use image-show on
  deactivated image.

  Steps to reproduce:
  1. Create image
  2. Deactivate image
  3. Call image-show on deactivated image

  Actual message:
  glance image-show 5f0f914b-9f04-42c4-9769-07dc09e09056
  u'deactivated' is not one of [u'queued', u'saving', u'active', u'killed', 
u'deleted', u'pending_delete']

  Failed validating u'enum' in schema[u'properties'][u'status']:
  {u'description': u'Status of the image (READ-ONLY)',
   u'enum': [u'queued',
 u'saving',
 u'active',
 u'killed',
 u'deleted',
 u'pending_delete'],
   u'type': u'string'}

  On instance[u'status']:
  u'deactivated'

  Expected image:
  something like Image  is deactivated

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1505134/+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 1472946] [NEW] _poll_shelved_instances periodic task is offloading instances even if shelved_offload_time is -1

[Abhishek Kekane]

Public bug reported:

shelved_offload_time -1 means instance will remain in the SHELVED state until 
user unshelves it.
Current behavior of _poll_shelved_instances periodic task is not considering 
shelved_offload_time is configured as -1 and offloading all the instances which 
are in 'SHELVED' state.


Stpes to reproduce:
1. set shelved_offload_time to -1 and restart nova-compute service.
2. create instance and shelve it using command, nova shelve instance_id
3. verify instance is in SHELVED state and instance files are present in 
instance path.
4. wait until  _poll_shelved_instances periodic task executes (default is 3600 
seconds, you can change it to 120 seconds)
5. Once _poll_shelved_instances periodic task is executed, instance state 
changes to SHELVED_OFFLOADED and instance files are deleted from instance path.

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: nova
 Assignee: (unassigned) = Abhishek Kekane (abhishek-kekane)

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

Title:
  _poll_shelved_instances periodic task is offloading instances even if
  shelved_offload_time is -1

Status in OpenStack Compute (Nova):
  New

Bug description:
  shelved_offload_time -1 means instance will remain in the SHELVED state until 
user unshelves it.
  Current behavior of _poll_shelved_instances periodic task is not considering 
shelved_offload_time is configured as -1 and offloading all the instances which 
are in 'SHELVED' state.

  
  Stpes to reproduce:
  1. set shelved_offload_time to -1 and restart nova-compute service.
  2. create instance and shelve it using command, nova shelve instance_id
  3. verify instance is in SHELVED state and instance files are present in 
instance path.
  4. wait until  _poll_shelved_instances periodic task executes (default is 
3600 seconds, you can change it to 120 seconds)
  5. Once _poll_shelved_instances periodic task is executed, instance state 
changes to SHELVED_OFFLOADED and instance files are deleted from instance path.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1472946/+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 1525259] [NEW] Add request_ids attribute to v2 schemas

[Abhishek Kekane]

Public bug reported:

We are adding support for returning ‘x-openstack-request-id’  to the caller as 
per the design proposed in cross-project specs:
http://specs.openstack.org/openstack/openstack-specs/specs/return-request-id.html

Problem Description:
Cannot add a new property of list type to the warlock.model object.

The requirement we are trying to meet is to make the request id
available to the user of the client library [3].  The user typically
doesn't have access to the headers, so the request id needs to be part
of the payload returned from each method. In other clients that work
with simple data types, we've subclassed dict, list, etc. to add the
extra property. This adds the request id to the return value without
making a breaking change to the API of the client library.

How is a model object created:
Let’s take an example of glanceclient.api.v2.images.get() call [1]:

Here after getting the response we call model() method. This model()
does the job of creating a warlock.model object(essentially a dict)
based on the schema given as argument (image schema retrieved from
glance in this case). Inside model() the raw() method simply return the
image schema as JSON object. The advantage of this warlock.model object
over a simple dict is that it validates any changes to object based on
the rules specified in the reference schema.  The keys of this  model
object are available as object properties to the caller.

Underlying reason:
The schema for different sub APIs is returned a bit differently. For images, 
metadef APIs glance.schema.Schema.raw() is used which returns a schema 
containing “additionalProperties”: {“type”: “string”}. Whereas for members and 
tasks APIs glance.schema.Schema.minimal() is used to return schema object which 
does not contain “additionalProperties”.

So we can add extra properties of any type to the model object returned
from members or tasks API but for images and metadef APIs we can only
add properties which can be of type string. Also for the latter case we
depend on the glance configuration to allow additional properties.

As per our analysis we have come up with two approaches for resolving
this issue:

Approach #1:  Inject request_ids property in the warlock model object in glance 
client
Here we do the following:
1. Inject the ‘request_ids’ as additional property into the model 
object(returned from model())
2. Return the model object which now contains request_ids property

Limitations:
1. Because the glance schemas for images and metadef only allows additional 
properties of type string, so even though natural type of request_ids should be 
list we have to make it as a comma separated ‘string’ of request ids as a 
compromise.
2. Lot of extra code is needed to wrap objects returned from the client API so 
that the caller can get request ids. For example we need to write wrapper 
classes for dict, list, str, tuple, generator.
3. Not a good design as we are adding a property which should actually be a 
base property but added as additional property as a compromise.
4. There is a dependency on glance whether to allow custom/additional 
properties or not. [2]

Approach #2:  Add ‘request_ids’ property to all schema definitions in
glance

Here we add  ‘request_ids’ property as follows to the various APIs
(schema):

“request_ids”: {
  "type": "array",
  "items": {
"type": "string"
  }
}

Doing this will make changes in glance client very simple as compared to 
approach#1.
This also looks a better design as it will be consistent.
We simply need to modify the request_ids property in  various API calls for 
example glanceclient.v2.images.get().

[1] 
https://github.com/openstack/python-glanceclient/blob/master/glanceclient/v2/images.py#L179
[2] https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L944
[3] 
http://specs.openstack.org/openstack/openstack-specs/specs/return-request-id.html

** Affects: glance
 Importance: Wishlist
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New


** Tags: lite-spec

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

Title:
  Add request_ids attribute to v2 schemas

Status in Glance:
  New

Bug description:
  We are adding support for returning ‘x-openstack-request-id’  to the caller 
as per the design proposed in cross-project specs:
  
http://specs.openstack.org/openstack/openstack-specs/specs/return-request-id.html

  Problem Description:
  Cannot add a new property of list type to the warlock.model object.

  The requirement we are trying to meet is to make the request id
  available to the user of the client library [3].  The user typically
  doesn't have access to the headers, so the request id needs to be part
  of the payload returned from each method. In other clients that work
  with simple data types, we've subclassed dict,

[Yahoo-eng-team] [Bug 1526150] [NEW] Use imageutils from oslo_utils

[Abhishek Kekane]

Public bug reported:

imageutils module is sync to oslo.utis with unittest in version 3.1. So
instead of using imageutils from openstack.common package, use from
oslo_utils.

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Use imageutils from oslo_utils

Status in OpenStack Compute (nova):
  New

Bug description:
  imageutils module is sync to oslo.utis with unittest in version 3.1.
  So instead of using imageutils from openstack.common package, use from
  oslo_utils.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1526150/+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 1526641] [NEW] Invalid metadata value to location-add causing 500 Internal Server Error

[Abhishek Kekane]

Public bug reported:

Passing invalid metadata value to location-add or location-update
command raises 500 Internal Server Error.

1.  glance location-add  --url 
http://10.69.4.136:8111/run_tests.sh --metadata '{"a":1234}'
or
2.  glance location-update  --url 
http://10.69.4.136:8111/run_tests.sh --metadata '{"a":1234}'

Stacktrace on g-api:
 
2015-12-15 03:47:49.876 ERROR glance.common.wsgi 
[req-3a349a22-8b69-40bf-93f1-6388eb5cb4ee 6c9c7376e75b4e37ab3c052a911731dd 
d1ee7fd5dcc341c3973f19f790238e63] Caught error: The image metadata key a has an 
invalid type of . Only dict, list, and unicode are supported.
2015-12-15 03:47:49.876 TRACE glance.common.wsgi Traceback (most recent call 
last):2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/common/wsgi.py", line 882, in __call__
2015-12-15 03:47:49.876 TRACE glance.common.wsgi request, **action_args)
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/common/wsgi.py", line 911, in dispatch
2015-12-15 03:47:49.876 TRACE glance.common.wsgi return method(*args, 
**kwargs)
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/common/utils.py", line 423, in wrapped
2015-12-15 03:47:49.876 TRACE glance.common.wsgi return func(self, req, 
*args,**kwargs)
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/api/v2/images.py", line 147, in update
2015-12-15 03:47:49.876 TRACE glance.common.wsgi change_method(req, image, 
change)
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/api/v2/images.py", line 197, in _do_add
2015-12-15 03:47:49.876 TRACE glance.common.wsgi 
self._do_add_locations(image, path[1], value)
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/api/v2/images.py", line 292, in _do_add_locations
2015-12-15 03:47:49.876 TRACE glance.common.wsgi 
image.locations.insert(pos, value)
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/api/policy.py", line 275, in _checker
2015-12-15 03:47:49.876 TRACE glance.common.wsgi return method(*args, 
**kwargs)
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/quota/__init__.py", line 273, in insert
2015-12-15 03:47:49.876 TRACE glance.common.wsgi return 
self.locations.insert(index, object)
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/location.py", line 179, in insert
2015-12-15 03:47:49.876 TRACE glance.common.wsgi location)
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/location.py", line 91, in _check_image_location
2015-12-15 03:47:49.876 TRACE glance.common.wsgi 
store_api.check_location_metadata(location['metadata'])
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/glance_store/backend.py", line 309, in 
check_location_metadata
2015-12-15 03:47:49.876 TRACE glance.common.wsgi 
check_location_metadata(val[key], key=key)
2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/glance_store/backend.py", line 320, in 
check_location_metadata
2015-12-15 03:47:49.876 TRACE glance.common.wsgi % dict(key=key, 
type=type(val)))
2015-12-15 03:47:49.876 TRACE glance.common.wsgi BackendException: The image 
metadata key a has an invalid type of . Only dict, list, and 
unicode are supported.
2015-12-15 03:47:49.876 TRACE glance.common.wsgi

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Invalid metadata value to location-add causing 500 Internal Server
  Error

Status in Glance:
  New

Bug description:
  Passing invalid metadata value to location-add or location-update
  command raises 500 Internal Server Error.

  1.glance location-add  --url 
http://10.69.4.136:8111/run_tests.sh --metadata '{"a":1234}'
  or
  2.glance location-update  --url 
http://10.69.4.136:8111/run_tests.sh --metadata '{"a":1234}'

  Stacktrace on g-api:
   
  2015-12-15 03:47:49.876 ERROR glance.common.wsgi 
[req-3a349a22-8b69-40bf-93f1-6388eb5cb4ee 6c9c7376e75b4e37ab3c052a911731dd 
d1ee7fd5dcc341c3973f19f790238e63] Caught error: The image metadata key a has an 
invalid type of . Only dict, list, and unicode are supported.
  2015-12-15 03:47:49.876 TRACE glance.common.wsgi Traceback (most recent call 
last):2015-12-15 03:47:49.876 TRACE glance.common.wsgi   File 
"/opt/stack/glance/glance/

[Yahoo-eng-team] [Bug 1290234] Re: do not use __builtin__ in Python3

[Abhishek Kekane]

** Also affects: nova
   Importance: Undecided
   Status: New

** Changed in: nova
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

** Also affects: keystone
   Importance: Undecided
   Status: New

** Changed in: keystone
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  do not use __builtin__ in Python3

Status in Bandit:
  In Progress
Status in Glance:
  Fix Released
Status in heat:
  Triaged
Status in Ironic:
  Fix Released
Status in OpenStack Identity (keystone):
  New
Status in Magnum:
  In Progress
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  New
Status in octavia:
  In Progress
Status in Trove:
  In Progress
Status in tuskar:
  Fix Released

Bug description:
  __builtin__ does not exist in Python 3, use six.moves.builtins
  instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bandit/+bug/1290234/+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 1529836] Re: Fix deprecated library function (os.popen()).

[Abhishek Kekane]

** Also affects: manila
   Importance: Undecided
   Status: New

** Changed in: manila
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

** Also affects: cinder
   Importance: Undecided
   Status: New

** Changed in: cinder
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

** Also affects: keystone
   Importance: Undecided
   Status: New

** Changed in: keystone
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Fix deprecated library function (os.popen()).

Status in Cinder:
  New
Status in devstack:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in OpenStack Identity (keystone):
  New
Status in Manila:
  New
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  In Progress
Status in oslo-incubator:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress

Bug description:
  Deprecated library function os.popen is still in use at some places.
  Need to replace it using subprocess module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1529836/+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 1457757] Re: Glance- Failed validating deactivated in schema

[Abhishek Kekane]

*** This bug is a duplicate of bug 1505218 ***
https://bugs.launchpad.net/bugs/1505218

Already fixed in master against commit
135a946a2d1a74dda67fcc35ab31c9d83d4d0c40

by Mike committed on 12 Oct


** This bug has been marked a duplicate of bug 1505218
   Image schema doesn't contain 'deactivated' status

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

Title:
  Glance- Failed validating deactivated in schema

Status in Glance:
  New

Bug description:
  Hi
  I am working on a new test for glance image deactivated, on kilo release .
  During the tests , while running self.admin_client.image_list() got 
validation error , 

  In tempest they query glance for get_scheme , so i guess the new state of 
image "deactivated" should be added to image status.
  How can we update the schem ? Please help


  
  Error
  _StringException: Empty attachments:
pythonlogging:''

  Traceback (most recent call last):
File 
"/home/bkopilov/Automation/tempest/tempest/api/image/admin/v2/test_images.py", 
line 51, in test_deactivate_image
  images = self.admin_client.image_list()
File 
"/home/bkopilov/Automation/tempest/tempest/services/image/v2/json/image_client.py",
 line 126, in image_list
  self._validate_schema(body, type='images')
File 
"/home/bkopilov/Automation/tempest/tempest/services/image/v2/json/image_client.py",
 line 59, in _validate_schema
  jsonschema.validate(body, schema)
File 
"/home/bkopilov/.local/lib/python2.7/site-packages/jsonschema/validators.py", 
line 432, in validate
  cls(schema, *args, **kwargs).validate(instance)
File 
"/home/bkopilov/.local/lib/python2.7/site-packages/jsonschema/validators.py", 
line 117, in validate
  raise error
  ValidationError: u'deactivated' is not one of [u'queued', u'saving', 
u'active', u'killed', u'deleted', u'pending_delete']

  Failed validating u'enum' in 
schema[u'properties'][u'images'][u'items'][u'properties'][u'status']:
  {u'description': u'Status of the image (READ-ONLY)',
   u'enum': [u'queued',
 u'saving',
 u'active',
 u'killed',
 u'deleted',
 u'pending_delete'],
   u'type': u'string'}

  On instance[u'images'][0][u'status']:
  u'deactivated'


  Process finished with exit code 0

  Thans, 
  Benny

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1457757/+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 1447322] Re: Attempting to reactivate a queued image returns a 403

[Abhishek Kekane]

As per discussion in glance meeting [1] this bug should be marked as
Invalid.

[1]
http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-11-19-14.01.log.html

** Changed in: glance
   Status: New => Invalid

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

Title:
  Attempting to reactivate a queued image returns a 403

Status in Glance:
  Invalid

Bug description:
  Overview:
  When attempting to reactivate a queued image (one without an image file) 
returns a "'403 Forbidden - Not allowed to reactivate image in status 'queued'".

  Steps to reproduce:
  1) Register a new image as user
  2) Without uploading an image file, reactivate the image as admin via:
  POST /images//actions/reactivate
  3) Notice that a "'403 Forbidden - Not allowed to reactivate image in status 
'queued'" is returned

  Expected:
  Currently a 400 response should be returned with the same message per spec, 
but this is expected to be changed to a 409

  Actual:
  A 403 response is returned

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1447322/+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 1445487] Re: Attempting to deactivate a queued image returns a 403

[Abhishek Kekane]

similar to https://bugs.launchpad.net/glance/+bug/1447322
please refer glance meeting [1] for reason behind marking this as invalid

[1]
http://eavesdrop.openstack.org/meetings/glance/2015/glance.2015-11-19-14.01.log.html

** Changed in: glance
   Status: In Progress => Invalid

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

Title:
  Attempting to deactivate a queued image returns a 403

Status in Glance:
  Invalid

Bug description:
  Overview:
  When attempting to deactivate a queued image (one without an image file) 
returns a "'403 Forbidden - Not allowed to deactivate image in status 'queued'".

  Steps to reproduce:
  1) Register a new image as user
  2) Without uploading an image file, deactivate the image as admin via:
  POST /images//actions/deactivate
  3) Notice that a "'403 Forbidden - Not allowed to deactivate image in status 
'queued'" is returned

  Expected:
  A 400 response should be returned with the same message

  Actual:
  A 403 response is returned

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1445487/+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 1321545] Re: creating image with only "--file" parameter will raise error but will create a queued image

[Abhishek Kekane]

Now its not creating queued image as --file without --container-format,
--disk-format is not allowed

** Changed in: glance
   Status: In Progress => Invalid

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

Title:
  creating image with only "--file" parameter will raise error but will
  create a queued image

Status in Glance:
  Invalid

Bug description:
  When I use following command to create an image:

  glance image-create --file
  /devstack/files/cirros-0.3.0-x86_64-disk.img

  it returns:

  400 Bad Request
  Invalid disk format 'None' for image.
  (HTTP 400)

  and I use "glance image-list", a queued image has been created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1321545/+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 1585917] [NEW] member-create will raise 500 Internal Server error if member-id is greater that 255 characters

[Abhishek Kekane]

ommon.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/cursors.py", line 161, in 
execute
2016-05-26 12:23:43.234 TRACE glance.common.wsgi result = self._query(query)
2016-05-26 12:23:43.234 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/cursors.py", line 317, in _query
2016-05-26 12:23:43.234 TRACE glance.common.wsgi conn.query(q)
2016-05-26 12:23:43.234 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 835, in 
query
2016-05-26 12:23:43.234 TRACE glance.common.wsgi self._affected_rows = 
self._read_query_result(unbuffered=unbuffered)
2016-05-26 12:23:43.234 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 1019, in 
_read_query_result
2016-05-26 12:23:43.234 TRACE glance.common.wsgi result.read()
2016-05-26 12:23:43.234 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 1302, in 
read
2016-05-26 12:23:43.234 TRACE glance.common.wsgi first_packet = 
self.connection._read_packet()
2016-05-26 12:23:43.234 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 981, in 
_read_packet
2016-05-26 12:23:43.234 TRACE glance.common.wsgi packet.check_error()
2016-05-26 12:23:43.234 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 393, in 
check_error
2016-05-26 12:23:43.234 TRACE glance.common.wsgi 
err.raise_mysql_exception(self._data)
2016-05-26 12:23:43.234 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/err.py", line 120, in 
raise_mysql_exception
2016-05-26 12:23:43.234 TRACE glance.common.wsgi 
_check_mysql_exception(errinfo)
2016-05-26 12:23:43.234 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/err.py", line 112, in 
_check_mysql_exception
2016-05-26 12:23:43.234 TRACE glance.common.wsgi raise errorclass(errno, 
errorvalue)
2016-05-26 12:23:43.234 TRACE glance.common.wsgi DBError: 
(pymysql.err.DataError) (1406, u"Data too long for column 'member' at row 1") 
[SQL: u'INSERT INTO image_members (created_at, updated_at, deleted_at, deleted, 
image_id, member, can_share, status) VALUES (%(created_at)s, %(updated_at)s, 
%(deleted_at)s, %(deleted)s, %(image_id)s, %(member)s, %(can_share)s, 
%(status)s)'] [parameters: {'status': 'pending', 'deleted': 0, 'created_at': 
datetime.datetime(2016, 5, 26, 6, 53, 43, 201107), 'updated_at': 
datetime.datetime(2016, 5, 26, 6, 53, 43, 201144), 'member': 
u'3424244gdegddfgdffffffffffdddddddd
 
',
 'image_id': u'3174767b-7ccc-4691-a3ca-6884d04c0330', 'can_share': 0, 
'deleted_at': None}]

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  member-create will raise 500 Internal Server error if member-id is
  greater that 255 characters

Status in Glance:
  New

Bug description:
  While adding members to image (image sharing) if member-id is
  specified above 255 characters then it will raise 500 Internal server
  error.

  Steps to reproduce:

  :~$ glance member-create 3174767b-7ccc-4691-a3ca-6884d04c0330 
3424244gdegddfgdff
  500 Internal Server Error
  The server has either erred or is incapable of performing the requested 
operation.
  (HT

[Yahoo-eng-team] [Bug 1543092] [NEW] glance-manage db purge failure

[Abhishek Kekane]

2-05 01:46:02.468 TRACE glance raise errorclass(errno, errorvalue)
2016-02-05 01:46:02.468 TRACE glance DBError: (pymysql.err.NotSupportedError) 
(1235, u"This version of MySQL doesn't yet support 'LIMIT & IN/ALL/ANY/SOME 
subquery'") [SQL: u'DELETE FROM image_tags WHERE image_tags.id IN (SELECT 
image_tags.id \nFROM image_tags \nWHERE image_tags.deleted_at < 
%(deleted_at_1)s \n LIMIT %(param_1)s)'] [parameters: {u'deleted_at_1': 
datetime.datetime(2016, 2, 4, 9, 46, 1, 906022), u'param_1': 100}]
2016-02-05 01:46:02.468 TRACE glance

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  glance-manage db purge failure

Status in Glance:
  New

Bug description:
  While running glance-manage db purge command, it fail with error "his
  version of MySQL doesn't yet support 'LIMIT & IN/ALL/ANY/SOME
  subquery'"

  $ glance-manage db purge 1

  2016-02-05 01:46:01.902 DEBUG oslo_db.sqlalchemy.engines 
[req-1cfabb0d-e775-44ea-b253-d134b0abb303 None None] MySQL server mode set to 
STRICT_TRANS_TABLES,STRICT_ALL_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,TRADITIONAL,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
 from (pid=26959) _check_effective_sql_mode 
/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/engines.py:256
  2016-02-05 01:46:02.340 INFO glance.db.sqlalchemy.api 
[req-1cfabb0d-e775-44ea-b253-d134b0abb303 None None] Purging deleted rows older 
than %(age_in_days)d day(s) from table %(tbl)s
  2016-02-05 01:46:02.417 ERROR oslo_db.sqlalchemy.exc_filters 
[req-1cfabb0d-e775-44ea-b253-d134b0abb303 None None] DBAPIError exception 
wrapped from (pymysql.err.NotSupportedError) (1235, u"This version of MySQL 
doesn't yet support 'LIMIT & IN/ALL/ANY/SOME subquery'") [SQL: u'DELETE FROM 
image_tags WHERE image_tags.id IN (SELECT image_tags.id \nFROM image_tags 
\nWHERE image_tags.deleted_at < %(deleted_at_1)s \n LIMIT %(param_1)s)'] 
[parameters: {u'deleted_at_1': datetime.datetime(2016, 2, 4, 9, 46, 1, 906022), 
u'param_1': 100}]
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters Traceback (most 
recent call last):
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1139, 
in _execute_context
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters context)
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 
450, in do_execute
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters 
cursor.execute(statement, parameters)
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/cursors.py", line 146, in 
execute
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters result = 
self._query(query)
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/cursors.py", line 296, in _query
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters conn.query(q)
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 819, in 
query
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters 
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 1001, in 
_read_query_result
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters result.read()
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 1285, in 
read
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters first_packet 
= self.connection._read_packet()
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 965, in 
_read_packet
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters 
packet.check_error()
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 394, in 
check_error
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters 
err.raise_mysql_exception(self._data)
  2016-02-05 01:46:02.417 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packag

[Yahoo-eng-team] [Bug 1544437] [NEW] messages in glance-manage purge are not formatted properly

[Abhishek Kekane]

Public bug reported:

Info messages in glance-manage purge method are not formatting properly
as it shows variable names in the message and not the corresponding
values.

For example:

$ glance-manage db purge 1

2016-02-08 04:22:20.373 INFO glance.db.sqlalchemy.api [req-1bcebb2f-
bc3a-468d-b4c5-5701ea2cfa19 None None] Deleted %(rows)d row(s) from
table %(tbl)s

2016-02-08 04:22:20.374 INFO glance.db.sqlalchemy.api [req-1bcebb2f-
bc3a-468d-b4c5-5701ea2cfa19 None None] Purging deleted rows older than
%(age_in_days)d day(s) from table %(tbl)s

** Affects: glance
 Importance: Undecided
 Status: New

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

Title:
  messages in glance-manage purge are not formatted properly

Status in Glance:
  New

Bug description:
  Info messages in glance-manage purge method are not formatting
  properly as it shows variable names in the message and not the
  corresponding values.

  For example:

  $ glance-manage db purge 1

  2016-02-08 04:22:20.373 INFO glance.db.sqlalchemy.api [req-1bcebb2f-
  bc3a-468d-b4c5-5701ea2cfa19 None None] Deleted %(rows)d row(s) from
  table %(tbl)s

  2016-02-08 04:22:20.374 INFO glance.db.sqlalchemy.api [req-1bcebb2f-
  bc3a-468d-b4c5-5701ea2cfa19 None None] Purging deleted rows older than
  %(age_in_days)d day(s) from table %(tbl)s

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1544437/+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 1543937] Re: 'nova-manage db archive_deleted_rows' fails for very large number

[Abhishek Kekane]

Similarly glance-manage db purge 1
111 fails
and give long stack trace.


** Also affects: glance
   Importance: Undecided
   Status: New

** Changed in: glance
 Assignee: (unassigned) => Dinesh Bhor (dinesh-bhor)

** Summary changed:

- 'nova-manage db archive_deleted_rows' fails for very large number
+ db purge records fails for very large number

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

Title:
  db purge records fails for very large number

Status in Glance:
  New
Status in OpenStack Compute (nova):
  In Progress

Bug description:
  The command:
  $ nova-manage db archive_deleted_rows  --verbose
  fails for very large NUMBER value on nova master

  Nova version:
  openstack@openstack-136:/opt/stack/nova$ git log -1
  commit 29641bd9778b51ac5794dfed9d4b881c5d47dc50
  Merge: 21e79d5 9fbe683
  Author: Jenkins 
  Date:   Wed Feb 10 06:03:00 2016 +

  Merge "Top 100 slow tests: api.openstack.compute.test_api"

  Example:

  openstack@openstack-136:~$ nova-manage db archive_deleted_rows 
214748354764774747774747477536654545649 --verbose
  2016-02-09 22:17:10.713 ERROR oslo_db.sqlalchemy.exc_filters [-] DBAPIError 
exception wrapped from (pymysql.err.ProgrammingError) (1064, u"You have an 
error in your SQL syntax; check the manual that corresponds to your MySQL 
server version for the right syntax to use near 
'214748354764774747774747477536654545649' at line 4") [SQL: u'INSERT INTO 
shadow_instance_actions_events (created_at, updated_at, deleted_at, deleted, 
id, event, action_id, start_time, finish_time, result, traceback, host, 
details) SELECT instance_actions_events.created_at, 
instance_actions_events.updated_at, instance_actions_events.deleted_at, 
instance_actions_events.deleted, instance_actions_events.id, 
instance_actions_events.event, instance_actions_events.action_id, 
instance_actions_events.start_time, instance_actions_events.finish_time, 
instance_actions_events.result, instance_actions_events.traceback, 
instance_actions_events.host, instance_actions_events.details \nFROM 
instance_actions_events \nWHERE inst
 ance_actions_events.deleted != %s ORDER BY instance_actions_events.id \n LIMIT 
%s'] [parameters: (0, 214748354764774747774747477536654545649L)]
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters Traceback (most 
recent call last):
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1139, 
in _execute_context
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters context)
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 
450, in do_execute
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters 
cursor.execute(statement, parameters)
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/cursors.py", line 146, in 
execute
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters result = 
self._query(query)
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/cursors.py", line 296, in _query
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters conn.query(q)
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 781, in 
query
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters 
self._affected_rows = self._read_query_result(unbuffered=unbuffered)
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 942, in 
_read_query_result
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters result.read()
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 1138, in 
read
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters first_packet 
= self.connection._read_packet()
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 906, in 
_read_packet
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters 
packet.check_error()
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 367, in 
check_error
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters 
err.raise_mysql_exception(self._data)
  2016-02-09 22:17:10.713 TRACE oslo_db.sqlalchemy.exc_filters   File 

[Yahoo-eng-team] [Bug 1538896] [NEW] nova flavor-show raises 500 error if flavor is deleted

[Abhishek Kekane]

Public bug reported:

Reproducible on latest master.

Tried to show deleted flavor then it raises 500 error.

Steps to reproduce:

1. Create flavor
$ nova flavor-create m2.test 10 1200 12 8

2. Delete flavor
$ nova flavor-delete 10

3. Show deleted flavor
$ nova flavor-show 10

ERROR (ClientException): Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
 (HTTP 500) (Request-ID: req-
4f77f74c-2234-4beb-9875-157364bdd964)

Nova api logs:
-

 from (pid=31454) _http_log_response 
/usr/local/lib/python2.7/dist-packages/keystoneauth1/session.py:254
2016-01-27 15:28:14.067 DEBUG nova.api.openstack.wsgi 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] Calling method '>' from (pid=31454) _process_stack 
/opt/stack/nova/nova/api/openstack/wsgi.py:699
2016-01-27 15:28:14.082 ERROR nova.api.openstack.extensions 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] Unexpected exception in 
API method
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions Traceback (most 
recent call last):
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/extensions.py", line 478, in wrapped
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions return f(*args, 
**kwargs)
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/compute/flavors_extraspecs.py", line 60, in 
index
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions return 
self._get_extra_specs(context, flavor_id)
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/compute/flavors_extraspecs.py", line 39, in 
_get_extra_specs
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions flavor = 
common.get_flavor(context, flavor_id)
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/common.py", line 543, in get_flavor
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions raise 
exc.HTTPNotFound(explanation=error.format_message())
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions HTTPNotFound: 
Flavor 122 could not be found.
2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions
2016-01-27 15:28:14.085 INFO nova.api.openstack.wsgi 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] HTTP exception thrown: 
Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and 
attach the Nova API log if possible.

2016-01-27 15:28:14.086 DEBUG nova.api.openstack.wsgi 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] Returning 500 to user: 
Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and 
attach the Nova API log if possible.
 from (pid=31454) __call__ 
/opt/stack/nova/nova/api/openstack/wsgi.py:1070
2016-01-27 15:28:14.097 INFO nova.osapi_compute.wsgi.server 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] 10.69.4.177 "GET 
/v2.1/982e2fc081364cf889d959b27d4bd510/flavors/122/os-extra_specs HTTP/1.1" 
status: 500 len: 499 time: 0.1559708

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: nova
     Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  nova flavor-show  raises 500 error if flavor is deleted

Status in OpenStack Compute (nova):
  New

Bug description:
  Reproducible on latest master.

  Tried to show deleted flavor then it raises 500 error.

  Steps to reproduce:

  1. Create flavor
  $ nova flavor-create m2.test 10 1200 12 8

  2. Delete flavor
  $ nova flavor-delete 10

  3. Show deleted flavor
  $ nova flavor-show 10

  ERROR (ClientException): Unexpected API Error. Please report this at
  http://bugs.launchpad.net/nova/ and attach the Nova API log if
  possible.  (HTTP 500) (Request-ID:
  req-4f77f74c-2234-4beb-9875-157364bdd964)

  Nova api logs:
  -

   from (pid=31454) _http_log_response 
/usr/local/lib/python2.7/dist-packages/keystoneauth1/session.py:254
  2016-01-27 15:28:14.067 DEBUG nova.api.openstack.wsgi 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] Calling method '>' from (pid=31454) _process_stack 
/opt/stack/nova/nova/api/openstack/wsgi.py:699
  2016-01-27 15:28:14.082 ERROR nova.api.openstack.extensions 
[req-15b4f90e-332b-4e96-b839-8cd931605e42 admin demo] Unexpected exception in 
API method
  2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions Traceback (most 
recent call last):
  2016-01-27 15:28:14.082 TRACE nova.api.openstack.extensions   File 
"/opt/stack/nova/nova/api/openstack/extensions.py", line 478, in wrapped
  2016-01-27 15:28:14.082 TRACE nova.api.openstac

[Yahoo-eng-team] [Bug 1541691] [NEW] server boot with leading and trailing white spaces in name, displays weird error message

[Abhishek Kekane]

c1a\\\u0c1b\\\u0c1c\\\u0c1d\\\u0c1e\\\u0c1f\\\u0c20\\\u0c21\\\u0c22\\\u0c23\\\u0c24\\\u0c25\\\u0c26\\\u0c27\\\u0c28\\\u0c2a\\\u0c2b\\\u0c2c\\\u0c2d\\\u0c2e\\\u0c2f\\\u0c30\\\u0c31\\\u0c32\\\u0c33\\\u0c35\\\u0c36\\\u0c37\\\u0c38\\\u0c39\\\u0c3d\\\u0c3e\\\u0c3f\\\u0c40\\\u0c41\\\u0c42\\\u0c43\\\u0c44\\\u0c46\\\u0c47\\\u0c48\\\u0c4a\\\u0c4b\\\u0c4c\\\u0c4d\\\u0c55\\\u0c56\\\u0c58\\\u0c59\\\u0c60\\\u0c61\\\u0c62\\\u0c63\\\u0c66\\\u0c67\\\u0c68\
 
\\u0c69\\\u0c6a\\\u0c6b\\\u0c6c\\\u0c6d\\\u0c6e\\\u0c6f\\\u0c78\\\u0c79\\\u0c7a\\\u0c7b\\\u0c7c\\\u0c7d\\\u0c7e\\\u0c7f\\\u0c82\\\u0c83\\\u0c85\\\u0c86\\\u0c87\\\u0c88\\\u0c89\\\u0c8a\\\u0c8b\\\u0c8c\\\u0c8e\\\u0c8f\\\u0c90\\\u0c92\\\u0c93\\\u0c94\\\u0c95\\\u0c96\\\u0c97\\\u0c98\\\u0c99\\\u0c9a\\\u0c9b\\\u0c9c\\\u0c9d\\\u0c9e\\\u0c9f\\\u0ca0\\\u0ca1\\\u0ca2\\\u0ca3\\\u0ca4\\\u0ca5\\\u0ca6\\\u0ca7\\\u0ca8\\\u0caa\\\u0cab\\\u0cac\\\u0cad\\\u0cae\\\u0caf\\\u0cb0\\\u0cb1\\\u0cb2\\\u0cb3\\\u0cb5\\\u0cb6\\\u0cb7\\\u0cb8\\\u0cb9\\\u0cbc\\\u0cbd\\\u0cbe\\\u0cbf\\\u0cc0\\\u0cc1\\\u0cc2\\\u0cc3\\\u0cc4\\\u0cc6\\\u0cc7\\\u0cc8\\\u0cca\\\u0ccb\\\u0ccc\\\u0ccd\\\u0cd5\\\u0cd6\\\u0cde\\\u0ce0\\\u0ce1\\\u0ce2\\\u0ce3\\\u0ce6\\\u0ce7\\\u0ce8\\\u0ce9\\\u0cea\\\u0ceb\\\u0cec\\\u0ced\\\u0cee\\\u0cef\\\u0cf1\\\u0cf2\\\u0d02\\\u0d03\\\u0d05\\\u0d06\\\u0d07\\\u0d08\\\u0d09\\\u0d0a\\\u0d0b\\\u0d0c\\\u0d0e\\\u0d0f\\\u0d10\\\u0d12\\\u0d13\\\u0d14\\\u0d15\\\u0d16\\\u0d17\\\u0d18\\\u0d19\\\u0d1a\\\u0d1b\\\u0d
 
1c\\\u0d1d\\\u0d1e\\\u0d1f\\\u0d20\\\u0d21\\\u0d22\\\u0d23\\\u0d24\\\u0d25\\\u0d26\\\u0d27\\\u0d28\\\u0d2a\\\u0d2b\\\u0d2c\\\u0d2d\\\u0d2e\\\u0d2f\\\u0d30\\\u0d31\\\u0d32\\\u0d33\\\u0d34\\\u0d35\\\u0d36\\\u0d37\\\u0d38\\\u0d39\\\u0d3d\\\u0d3e\\\u0d3f\\\u0d40\\\u0d41\\\u0d42\\\u0d43\\\u0d44\\\u0d46\\\u0d47\\\u0d48\\\u0d4a\\\u0d4b\\\u0d4c\\\u0d4d\\\u0d57\\\u0d60\\\u0d61\\\u0d62\\\u0d63\\\u0d66\\\u0d67\\\u0d68\\\u0d69\\\u0d6a\\\u0d6b\\\u0d6c\\\u0d6d\\\u0d6e\\\u0d6f\\\u0d70\\\u0d71\\\u0d72\\\u0d73\\\u0d74\\*(?<![\\
 
\\\xa0\\\u1680\\\u180e\\\u2000\\\u2001\\\u2002\\\u2003\\\u2004\\\u2005\\\u2006\\\u2007\\\u2008\\\u2009\\\u200a\\\u202f\\\u205f\\\u3000])$'
 (HTTP 400) (Request-ID: req-7905c1ff-8f28-409a-a1d6-546697dafae2)


IMO, this message needs to be short and appropriate. This error is also logged 
in nova-api logs and any one can easily flood the logs by sending multiple 
requests to consume disk space.

NOTE:
I have trimmed 95% error message as I am not able to paste all.

** Affects: nova
 Importance: Undecided
 Assignee: Srushti Gadadare (srushti-gadadare)
 Status: New

** Changed in: nova
     Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
<a  rel="nofollow" href="https://bugs.launchpad.net/bugs/1541691">https://bugs.launchpad.net/bugs/1541691</a>

Title:
  server boot with leading and trailing white spaces in name, displays
  weird error message

Status in OpenStack Compute (nova):
  New

Bug description:
  If you pass only white space or leading or trailing white spaces in
  name while creating instance then it raises 400 bad request exception,
  but error message is weird and pretty big.

  Steps to reproduce:
  ---  

  Create instance using boot command with leading or trailing white spaces.
  $ nova boot --flavor <flavor-id> --image <image-id> "test  "

  
  ERROR (BadRequest): Invalid input for field/attribute name. Value: test  
. u'test  ' does not match u'^(?![\\ 
\\\xa0\\\u1680\\\u180e\\\u2000\\\u2001\\\u2002\\\u2003\\\u2004\\\u2005\\\u2006\\\u2007\\\u2008\\\u2009\\\u200a\\\u202f\\\u205f\\\u3000])[\\
 
\\!\\"\\#\\$\\%\\&\\\'\\(\\)\\*\\+\\,\\-\\.\\/0123456789\\:\\;\\<\\=\\>\\?\\@ABCDEFGHIJKLMNOPQRSTUVWXYZ\\[\\]\\^\\_\\`abcdefghijklmnopqrstuvwxyz\\{\\|\\}\\~\\\xa0\\\xa1\\\xa2\\\xa3\\\xa4\\\xa5\\\xa6\\\xa7\\\xa8\\\xa9\\\xaa\\\xab\\\xac\\\xae\\\xaf\\\xb0\\\xb1\\\xb2\\\xb3\\\xb4\\\xb5\\\xb6\\\xb7\\\xb8\\\xb9\\\xba\\\xbb\\\xbc\\\xbd\\\xbe\\\xbf\\\xc0\\\xc1\\\xc2\\\xc3\\\xc4\\\xc5\\\xc6\\\xc7\\\xc8\\\xc9\\\xca\\\xcb\\\xcc\\\xcd\\\xce\\\xcf\\\xd0\\\xd1\\\xd2\\\xd3\\\xd4\\\xd5\\\xd6\\\xd7\\\xd8\\\xd9\\\xda\\\xdb\\\xdc\\\xdd\\\xde\\\xdf\\\xe0\\\xe1\\\xe2\\\xe3\\\xe4\\\xe5\\\xe6\\\xe7\\\xe8\\\xe9\\\xea\\\xeb\\\xec\\\xed\\\xee\\\xef\\\xf0\\\xf1\\\xf2\\\xf3\\\xf4\\\xf5\\\xf6\\\xf7\\\xf8\\\xf9\\\xfa\\\xfb\\\xfc\\\xfd\\\xfe\\\xff\\\u0100
 
\\\u0101\\\u0102\\\u0103\\\u0104\\\u0105\\\u0106\\\u0107\\\u0108\\\u0109\\\u010a\\\u010b\\\u010c\\\u010d\\\u010e\\\u010f\\\u0110\\\u0111\\\u0112\\\u0113\\\u0114\\\u0115\\\u0116\\\u0117\\\u0118\\\u0119\\\u011a\\\u011b\\\u011c\\\u011d\\\u011e\\\u011f\\\u0120\\\u0121\\\u0122\\\u0123\\\u0124\\\u0125\\\u0126\\\u0127\\\u0128\\\u0129\\\u012a\\\u012b\\\u012c\\\u012d\\\u012e\\\u012f\\\u0130\\\u0131\\\u0132\\\u0133\\\u0134\\\u0135\\\u0136\\\u0137\\\u0138\\\u0139\\\u013a\\\u013b\\\u013c\\\u013d\\

[Yahoo-eng-team] [Bug 1537625] [NEW] invalid path for plugin skeleton in api_plugins.rst

[Abhishek Kekane]

Public bug reported:

In doc/source/api_plugins.rst invalid path [1] is given for plugin
skeleton example which is not exist.


[1]
https://github.com/openstack/nova/blob/master/doc/source/api_plugins.rst
#basic-plugin-structure

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  invalid path for plugin skeleton in api_plugins.rst

Status in OpenStack Compute (nova):
  New

Bug description:
  In doc/source/api_plugins.rst invalid path [1] is given for plugin
  skeleton example which is not exist.


  [1]
  https://github.com/openstack/nova/blob/master/doc/source/api_plugins.rst
  #basic-plugin-structure

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1537625/+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 1554412] [NEW] purge command fails due to foreign key constraint

[Abhishek Kekane]

ages/pymysql/connections.py", line 1285, in 
read
2016-03-08 08:25:16.127 TRACE glance first_packet = 
self.connection._read_packet()
2016-03-08 08:25:16.127 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 965, in 
_read_packet
2016-03-08 08:25:16.127 TRACE glance packet.check_error()
2016-03-08 08:25:16.127 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/connections.py", line 394, in 
check_error
2016-03-08 08:25:16.127 TRACE glance err.raise_mysql_exception(self._data)
2016-03-08 08:25:16.127 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/err.py", line 120, in 
raise_mysql_exception
2016-03-08 08:25:16.127 TRACE glance _check_mysql_exception(errinfo)
2016-03-08 08:25:16.127 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/err.py", line 112, in 
_check_mysql_exception
2016-03-08 08:25:16.127 TRACE glance raise errorclass(errno, errorvalue)
2016-03-08 08:25:16.127 TRACE glance DBReferenceError: 
(pymysql.err.IntegrityError) (1451, u'Cannot delete or update a parent row: a 
foreign key constraint fails (`glance`.`image_locations`, CONSTRAINT 
`image_locations_ibfk_1` FOREIGN KEY (`image_id`) REFERENCES `images` (`id`))') 
[SQL: u'DELETE FROM images WHERE images.id in (SELECT T1.id FROM (SELECT 
images.id \nFROM images \nWHERE images.deleted_at < %(deleted_at_1)s \n LIMIT 
%(param_1)s) as T1)'] [parameters: {u'deleted_at_1': datetime.datetime(2016, 3, 
7, 8, 25, 16, 92480), u'param_1': 1}]
2016-03-08 08:25:16.127 TRACE glance

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  purge command fails due to foreign key constraint

Status in Glance:
  New

Bug description:
  In our production environment some how we have encountered a issue in
  purge command. One of the example is, purge command fails if image is
  deleted but members entry for that particular image is not deleted.

  Steps to reproduce:

  1. Apply patch https://review.openstack.org/#/c/278870/7 (otherwise you will 
get subquery related error)
  2. Run purge command "glance-manage db purge 1 1"

  Purge command trace:

  2016-03-08 08:25:16.127 CRITICAL glance [req-7ce644e9-3c7d-
  4cd4-8377-77f7e1a689a5 None None] DBReferenceError:
  (pymysql.err.IntegrityError) (1451, u'Cannot delete or update a parent
  row: a foreign key constraint fails (`glance`.`image_locations`,
  CONSTRAINT `image_locations_ibfk_1` FOREIGN KEY (`image_id`)
  REFERENCES `images` (`id`))') [SQL: u'DELETE FROM images WHERE
  images.id in (SELECT T1.id FROM (SELECT images.id \nFROM images
  \nWHERE images.deleted_at < %(deleted_at_1)s \n LIMIT %(param_1)s) as
  T1)'] [parameters: {u'deleted_at_1': datetime.datetime(2016, 3, 7, 8,
  25, 16, 92480), u'param_1': 1}]

  2016-03-08 08:25:16.127 TRACE glance Traceback (most recent call last):
  2016-03-08 08:25:16.127 TRACE glance   File "/usr/local/bin/glance-manage", 
line 10, in 
  2016-03-08 08:25:16.127 TRACE glance sys.exit(main())
  2016-03-08 08:25:16.127 TRACE glance   File 
"/opt/stack/glance/glance/cmd/manage.py", line 344, in main
  2016-03-08 08:25:16.127 TRACE glance return 
CONF.command.action_fn(*func_args, **func_kwargs)
  2016-03-08 08:25:16.127 TRACE glance   File 
"/opt/stack/glance/glance/cmd/manage.py", line 165, in purge
  2016-03-08 08:25:16.127 TRACE glance db_api.purge_deleted_rows(ctx, 
age_in_days, max_rows)
  2016-03-08 08:25:16.127 TRACE glance   File 
"/opt/stack/glance/glance/db/sqlalchemy/api.py", line 1327, in 
purge_deleted_rows
  2016-03-08 08:25:16.127 TRACE glance result = 
session.execute(delete_statement)
  2016-03-08 08:25:16.127 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 1034, 
in execute
  2016-03-08 08:25:16.127 TRACE glance bind, 
close_with_result=True).execute(clause, params or {})
  2016-03-08 08:25:16.127 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 914, 
in execute
  2016-03-08 08:25:16.127 TRACE glance return meth(self, multiparams, 
params)
  2016-03-08 08:25:16.127 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/elements.py", line 323, 
in _execute_on_connection
  2016-03-08 08:25:16.127 TRACE glance return 
connection._execute_clauseelement(self, multiparams, params)
  2016-03-08 08:25:16.127 TRACE glance   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1010, 
in _execute_clauseelement
  2016-03-08 08:25

[Yahoo-eng-team] [Bug 1596933] [NEW] IntegrityError while archiving if consoles are not deleted

[Abhishek Kekane]

Public bug reported:

On deleting the instance its associated console entries will not be
deleted which will cause "IntegrityError" while archiving the deleted
records from database.

1. Create an instance.

$ nova boot test-1 --flavor 1 --image cirros-0.3.4-x86_64-uec

2. Create an entry in console table manually with the above created
instance_uuid.

insert into consoles (created_at, updated_at, instance_name, password,
port, instance_uuid, deleted) values ('2016-06-15 06:00:13', '2016-06-15
06:00:13', 'test-1', '12345', 8080, '326757a3-66da-455f-8ffa-
29775de1d5f5', 0);


3. Delete instance

$ nova delete 326757a3-66da-455f-8ffa-29775de1d5f5


4. Call db archive which raises following error

$ nova-manage db archive_deleted_rows 1000

2016-06-15 14:23:27.837 WARNING nova.db.sqlalchemy.api [-]
IntegrityError detected when archiving table instances:
(pymysql.err.IntegrityError) (1451, u'Cannot delete or update a parent
row: a foreign key constraint fails (`nova`.`consoles`, CONSTRAINT
`consoles_instance_uuid_fkey` FOREIGN KEY (`instance_uuid`) REFERENCES
`instances` (`uuid`))') [SQL: u'DELETE FROM instances WHERE instances.id
in (SELECT T1.id FROM (SELECT instances.id \nFROM instances \nWHERE
instances.deleted != %(deleted_1)s ORDER BY instances.id \n LIMIT
%(param_1)s) as T1)'] [parameters: {u'param_1': 979, u'deleted_1': 0}]

Note:
I have added db entry manually as console service is not enabled in my 
environment.

** Affects: nova
 Importance: Undecided
 Assignee: Bhagyashri Shewale (bhagyashri-shewale)
 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/1596933

Title:
  IntegrityError while archiving if consoles are not deleted

Status in OpenStack Compute (nova):
  New

Bug description:
  On deleting the instance its associated console entries will not be
  deleted which will cause "IntegrityError" while archiving the deleted
  records from database.

  1. Create an instance.

  $ nova boot test-1 --flavor 1 --image cirros-0.3.4-x86_64-uec

  2. Create an entry in console table manually with the above created
  instance_uuid.

  insert into consoles (created_at, updated_at, instance_name, password,
  port, instance_uuid, deleted) values ('2016-06-15 06:00:13',
  '2016-06-15 06:00:13', 'test-1', '12345', 8080, '326757a3-66da-455f-
  8ffa-29775de1d5f5', 0);

  
  3. Delete instance

  $ nova delete 326757a3-66da-455f-8ffa-29775de1d5f5

  
  4. Call db archive which raises following error

  $ nova-manage db archive_deleted_rows 1000

  2016-06-15 14:23:27.837 WARNING nova.db.sqlalchemy.api [-]
  IntegrityError detected when archiving table instances:
  (pymysql.err.IntegrityError) (1451, u'Cannot delete or update a parent
  row: a foreign key constraint fails (`nova`.`consoles`, CONSTRAINT
  `consoles_instance_uuid_fkey` FOREIGN KEY (`instance_uuid`) REFERENCES
  `instances` (`uuid`))') [SQL: u'DELETE FROM instances WHERE
  instances.id in (SELECT T1.id FROM (SELECT instances.id \nFROM
  instances \nWHERE instances.deleted != %(deleted_1)s ORDER BY
  instances.id \n LIMIT %(param_1)s) as T1)'] [parameters: {u'param_1':
  979, u'deleted_1': 0}]

  Note:
  I have added db entry manually as console service is not enabled in my 
environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1596933/+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 1671365] [NEW] Downloading image with --progress fails for python3

[Abhishek Kekane]

Public bug reported:

Downloading image with --progress fails for python3 with,
TypeError: 'IterableWithLength' object is not an iterator

Steps to reproduce:
Ensure OpenStack is installed for python3

$ glance -d image-download 2974158b-383d-4fe6-9671-5248b9a5d07d --file
bmc-base.qcow2 --progress

Output:
$ TypeError: 'IterableWithLength' object is not an iterator

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Downloading image with --progress fails for python3

Status in Glance:
  New

Bug description:
  Downloading image with --progress fails for python3 with,
  TypeError: 'IterableWithLength' object is not an iterator

  Steps to reproduce:
  Ensure OpenStack is installed for python3

  $ glance -d image-download 2974158b-383d-4fe6-9671-5248b9a5d07d --file
  bmc-base.qcow2 --progress

  Output:
  $ TypeError: 'IterableWithLength' object is not an iterator

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1671365/+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 1706586] [NEW] GET call to /info/import raises ResourceNotFound error

[Abhishek Kekane]

Public bug reported:

curl -g -i -X GET http://10.232.48.201/image/v2/info/import -H "X-Auth-
Token: " should return valid import-methods available if
config parameter 'enable_image_import' is set. As of now it raises 404
ResourceNotFound error.

Steps to reproduce:
1. Set 'enable_image_import' to True under DEFAULT section of glance-api.conf 
file
2. Restart glance-api service
3. Run,  curl -g -i -X GET http://10.232.48.201/image/v2/info/import -H 
"X-Auth-Token: 

** Affects: glance
 Importance: Critical
 Assignee: Erno Kuvaja (jokke)
 Status: In Progress

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

Title:
  GET call to /info/import raises ResourceNotFound error

Status in Glance:
  In Progress

Bug description:
  curl -g -i -X GET http://10.232.48.201/image/v2/info/import -H "X
  -Auth-Token: " should return valid import-methods available
  if config parameter 'enable_image_import' is set. As of now it raises
  404 ResourceNotFound error.

  Steps to reproduce:
  1. Set 'enable_image_import' to True under DEFAULT section of glance-api.conf 
file
  2. Restart glance-api service
  3. Run,  curl -g -i -X GET http://10.232.48.201/image/v2/info/import -H 
"X-Auth-Token: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1706586/+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 1705680] [NEW] nova compute does nothing on receiving sighup signal

[Abhishek Kekane]

Public bug reported:

Nova compute service does not listen to sighup signal actually it should
reload the configuration file.

Steps to reproduce:
1. Run nova compute service as a daemon
2. Send sighup signal "kill -1 $parent_id_of_compute_service" or "kill -HUP 
$parent_id_of_compute_service"

Whereas if you send sighup signal to nova-api or nova-conductor then it
reloads the configuration files.

** Affects: nova
 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/1705680

Title:
  nova compute does nothing on receiving sighup signal

Status in OpenStack Compute (nova):
  New

Bug description:
  Nova compute service does not listen to sighup signal actually it
  should reload the configuration file.

  Steps to reproduce:
  1. Run nova compute service as a daemon
  2. Send sighup signal "kill -1 $parent_id_of_compute_service" or "kill -HUP 
$parent_id_of_compute_service"

  Whereas if you send sighup signal to nova-api or nova-conductor then
  it reloads the configuration files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1705680/+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 1484566] Re: Images v2 api tasks documentation is missing

[Abhishek Kekane]

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

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

Title:
  Images v2 api tasks documentation is missing

Status in Glance:
  Fix Released

Bug description:
  Need to add the following to the glance developer docs:
  (1) why tasks were introduced, what use cases they are meant to solve, and 
the overall design philosophy
  (2) straightforward documentation of the tasks API calls
  (3) tasks info for glance developers who want to work on tasks
  (4) tasks info for deployers who want to use tasks (I suggest starting with 
this in the dev docs and then move it to one of the OpenStack operator manuals 
eventually)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1484566/+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 1521756] Re: race condition in test_upload_image_http_nonexistent_location_url: glance_store doesn't handle properly invalid HTTP reply

[Abhishek Kekane]

I have confirmed that this is not a failure any more by running these
tests in 6 different terminals and continuously 1 hour using "while
true; do tox -e py27 glance.tests.unit.v1.test_api || break; done"


** Changed in: glance
   Status: New => Invalid

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

Title:
  race condition in test_upload_image_http_nonexistent_location_url:
  glance_store doesn't handle properly invalid HTTP reply

Status in Glance:
  Invalid

Bug description:
  Victor asked for me to have a look at an intermittent failure he was
  seeing in https://review.openstack.org/#/c/250083/

  it shows up like so:
  Traceback (most recent call last):
File 
"/home/robertc/work/openstack/glance/.tox/py34/lib/python3.4/site-packages/eventlet/greenpool.py",
 line 82, in _spawn_n_impl
  func(*args, **kwargs)
File "/home/robertc/work/openstack/glance/glance/api/v1/images.py", line 
737, in _upload_and_activate
  location_data = self._upload(req, image_meta)
File "/home/robertc/work/openstack/glance/glance/api/v1/images.py", line 
671, in _upload
  {'status': 'saving'})
File 
"/home/robertc/work/openstack/glance/glance/registry/client/v1/api.py", line 
174, in update_image_metadata
  from_state=from_state)
File 
"/home/robertc/work/openstack/glance/glance/registry/client/v1/client.py", line 
209, in update_image
  headers=headers)
File 
"/home/robertc/work/openstack/glance/glance/registry/client/v1/client.py", line 
141, in do_request
  'exc_name': exc_name})
File 
"/home/robertc/work/openstack/glance/.tox/py34/lib/python3.4/site-packages/oslo_utils/excutils.py",
 line 204, in __exit__
  six.reraise(self.type_, self.value, self.tb)
File 
"/home/robertc/work/openstack/glance/.tox/py34/lib/python3.4/site-packages/six.py",
 line 686, in reraise
  raise value
File 
"/home/robertc/work/openstack/glance/glance/registry/client/v1/client.py", line 
124, in do_request
  **kwargs)
File "/home/robertc/work/openstack/glance/glance/common/client.py", line 
71, in wrapped
  return func(self, *args, **kwargs)
File "/home/robertc/work/openstack/glance/glance/common/client.py", line 
375, in do_request
  headers=copy.deepcopy(headers))
File "/home/robertc/work/openstack/glance/glance/common/client.py", line 
88, in wrapped
  return func(self, method, url, body, headers)
File "/home/robertc/work/openstack/glance/glance/common/client.py", line 
524, in _do_request
  raise exception.NotFound(res.read())
  glance.common.exception.NotFound: b'Image not found'
  ==
  FAIL: 
glance.tests.unit.v1.test_api.TestGlanceAPI.test_upload_image_http_nonexistent_location_url
  tags: worker-0
  --
  Traceback (most recent call last):
File 
"/home/robertc/work/openstack/glance/glance/tests/unit/v1/test_api.py", line 
1149, in test_upload_image_http_nonexistent_location_url
  self.assertEqual(404, res.status_int)
File 
"/home/robertc/work/openstack/glance/.tox/py34/lib/python3.4/site-packages/testtools/testcase.py",
 line 350, in assertEqual
  self.assertThat(observed, matcher, message)
File 
"/home/robertc/work/openstack/glance/.tox/py34/lib/python3.4/site-packages/testtools/testcase.py",
 line 435, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: 404 != 201

  
  and through bisection I can reproduce it with 75 tests - I'm working on 
shrinking the set but it takes a couple hundred runs to be sure its a false 
branch, so its not super fast.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1521756/+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 1702263] [NEW] nova conductor does not exits gracefully

[Abhishek Kekane]

Public bug reported:

When user sends sigkill or sigterm signal to nova-conductor parent
process, parent process is exits immediately. Child process which is
processing the request get killed after sometime (2-3 seconds) without
completing the current request.

Meantime if new request is sent then nova-conductor does not picks that
request from rabbitmq for processing. Once nova-conductor is up and
running again then it picks the pending requests from rabbitmq for
processing.

Expected behavior:
1. conductor should complete current request before exiting - Not Good
2. conductor should not accept new request for processing - Good

** Affects: nova
 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/1702263

Title:
  nova conductor does not exits gracefully

Status in OpenStack Compute (nova):
  New

Bug description:
  When user sends sigkill or sigterm signal to nova-conductor parent
  process, parent process is exits immediately. Child process which is
  processing the request get killed after sometime (2-3 seconds) without
  completing the current request.

  Meantime if new request is sent then nova-conductor does not picks
  that request from rabbitmq for processing. Once nova-conductor is up
  and running again then it picks the pending requests from rabbitmq for
  processing.

  Expected behavior:
  1. conductor should complete current request before exiting - Not Good
  2. conductor should not accept new request for processing - Good

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1702263/+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 1702268] [NEW] scheduler service does not exit gracefully on receiving sigkill signal

[Abhishek Kekane]

Public bug reported:

When user sends sigkill signal to nova-scheduler parent process, parent
process terminates immediately without processing the current request.
Old message remains in rabbitmq. If new request is sent then it remains
in rabbitmq.

When nova-scheduler is up again then it picks all requests from rabbitmq
for processing.

Note:
If user sends sigterm signal to nova-scheduler then parent process waits until 
current request is completed.

Expected behavior:
1. scheduler should complete current request before exiting - Not Good
2. scheduler should not accept new request for processing - Good

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 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/1702268

Title:
  scheduler service does not exit gracefully on receiving sigkill signal

Status in OpenStack Compute (nova):
  New

Bug description:
  When user sends sigkill signal to nova-scheduler parent process,
  parent process terminates immediately without processing the current
  request. Old message remains in rabbitmq. If new request is sent then
  it remains in rabbitmq.

  When nova-scheduler is up again then it picks all requests from
  rabbitmq for processing.

  Note:
  If user sends sigterm signal to nova-scheduler then parent process waits 
until current request is completed.

  Expected behavior:
  1. scheduler should complete current request before exiting - Not Good
  2. scheduler should not accept new request for processing - Good

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1702268/+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 1029950] Re: No limits on image size

[Abhishek Kekane]

** Changed in: glance
   Status: New => Opinion

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

Title:
  No limits on image size

Status in Glance:
  Opinion
Status in OpenStack Compute (nova):
  Opinion
Status in OpenStack Security Advisory:
  Won't Fix

Bug description:
  Using Epel Essex packages on RHEL 6.3

  Glance should impose configurable limits (or tenant quotas) on the
  size of the images it allows to be registered and/or uploaded.

  Two separate example exploits here
  1. Glance Denial of Service by file system exhaustion
  2. Nova Compute Denial of Service by file system exhaustion

  = 1 =

  Using the glance x-image-meta-property-copy-from header it is possible
  to get glance to keep downloading a large resource until it fills up
  the local harddrive e.g.

  $ glance add name="big image" disk_format=raw container_format=ovf 
copy_from=http://server/cgi-bin/t.cgi # [1]
  Failed to add image. Got error:
  The request returned a 413 Request Entity Too Large. This generally means 
that rate limiting or a quota threshold was breached.

  The response body:
  413 Request Entity Too Large

  The body of your request was too large for this server.

   Image storage media is full: There is not enough disk space on the image 
storage media.  
  Note: Your image metadata may still be in the registry, but the image's 
status will likely be 'killed'.

  $ ls -lh /var/lib/glance/images/f1db6d09-1eac-4ce4-86ff-8a34bfea33af
  -rw-r--r--. 1 glance glance 87G Jul 27 13:03 
/var/lib/glance/images/f1db6d09-1eac-4ce4-86ff-8a34bfea33af
  $ df -h /var/lib/glance/images/
  FilesystemSize  Used Avail Use% Mounted on
  /dev/mapper/vg_rheva8c03-lv_root
104G   98G  261M 100% /

  this would allow any authenticated user to preform a denial of service
  on a glance server, with a file system backend. I havn't looked into
  swift but will it just keep going until is starts filling up storage
  nodes?

  = 2 =

  Nova is also open to a similar exploit, by using the x-image-meta-
  location header in a glance add, a large resource can be registered
  with glance, any nova compute node that tries to use this image to
  start an instance can have its disk space very quickly exhausted with
  a singe instance

  # Registering an image 1TB in size (can go bigger if needs be)
  $ glance add name="big image" disk_format=raw container_format=ovf 
location=http://server/cgi-bin/t.cgi
  Added new image with ID: 1a528173-7ca9-4320-b0f3-dac127a1f337

  $ glance index
  ID   Name   Disk 
Format  Container Format Size  
   -- 
  --
  1a528173-7ca9-4320-b0f3-dac127a1f337 big image  raw   
   ovf   1099511627776

  $ nova boot --flavor 1 --image 1a528173-7ca9-4320-b0f3-dac127a1f337
  bigtest

  # the filesystem now fills up, the boot fails and nova deletes the partial 
download
  # next I check the apache logs to see how much nova downloaded. 
  "GET /cgi-bin/t.cgi HTTP/1.1" 200 93406637550 "-" "-"
  # Note : I know I will probably not get the same compute node next time but 
  # this will at least give me an idea of what size might be tolerated.
  # edit cgi script [1] to change the content length to something slightly 
smaller then 93406637550
  $ glance add name="smaller big image" disk_format=raw container_format=ovf 
location=http://server/cgi-bin/t.cgi
  Added new image with ID: a5eb1eab-1536-438f-82cf-4b642cf9d363
  $ glance index
  ID   Name   Disk 
Format  Container Format Size  
   -- 
  --
  a5eb1eab-1536-438f-82cf-4b642cf9d363 smaller big image  raw   
   ovf 90406637550
  1a528173-7ca9-4320-b0f3-dac127a1f337 big image  raw   
   ovf   1099511627776

  $ nova boot --flavor 1 --image a5eb1eab-1536-438f-82cf-4b642cf9d363
  bigtest_2

  $ ls -lh 
/var/lib/nova/instances/_base/7f9a4e3c2891c537a784391cd962e6a5527d0a27 
  -rw-r--r--. 1 qemu qemu 85G Jul 27 14:13 
/var/lib/nova/instances/_base/7f9a4e3c2891c537a784391cd962e6a5527d0a27
  $ df -h /var/lib/nova/instances/_base/
  FilesystemSize  Used Avail Use% Mounted on
  /dev/mapper/vg_rheva8c03-lv_root
104G   97G  1.1G  99% /
  $

  [1] Standard http cgi script used as the vm image
  #!/usr/bin/python
  import os, sys, uuid

  print "Content-Type: text/html"
  #print "Content-Length: 1099511627776" # this shouldn't be present for first 
exploit
  print

  

[Yahoo-eng-team] [Bug 1702270] [NEW] glance-api does not exit gracefully on sigkill and sigterm signal

[Abhishek Kekane]

Public bug reported:

When user sends either sigkill or sigterm signal to glance-api's parent
process then it exits immediately without completing the current
request. As per openstack serivce standards it should wait until current
request is completed and should not accept new request for processing
till exiting.

Note:
For kill signal parent process exits immediately where as child process keeps 
running forever whereas for terminate signal parent and child processes exits 
immediately.

Expected behavior:
1. glance-api should complete current request before exiting
2. glance-api should not accept new request for processing

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  glance-api does not exit gracefully on sigkill and sigterm signal

Status in Glance:
  New

Bug description:
  When user sends either sigkill or sigterm signal to glance-api's
  parent process then it exits immediately without completing the
  current request. As per openstack serivce standards it should wait
  until current request is completed and should not accept new request
  for processing till exiting.

  Note:
  For kill signal parent process exits immediately where as child process keeps 
running forever whereas for terminate signal parent and child processes exits 
immediately.

  Expected behavior:
  1. glance-api should complete current request before exiting
  2. glance-api should not accept new request for processing

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1702270/+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 1702260] [NEW] nova compute child process remains orphan after sending sigkill or sigterm signal to parent process

[Abhishek Kekane]

Public bug reported:

When user sends SIGKILL (kill -9) or SIGTERM (kill -15) signal to nova-
comupte parent process then parent process terminates immediately but
child process keeps running forever and keeps processing the requests
received from rabbitmq.

Steps to reproduce:

1. Identify running processes of nova-compute using "ps aux | grep nova-compute'
2. Send kill or terminate signal to parent process.
   $ kill -9  or kill -15 

3. Verify parent process is killed using "ps aux | grep nova-compute'

** Affects: nova
 Importance: Undecided
 Status: New

** Summary changed:

- nova compute child process remains orphan after sending kill or interrupt 
signal to parent process
+ nova compute child process remains orphan after sending sigkill or sigterm 
signal to parent process

** Description changed:

- When user sends SIGKILL (kill -9) or SIGINT (kill -15) signal to nova-
+ When user sends SIGKILL (kill -9) or SIGTERM (kill -15) signal to nova-
  comupte parent process then parent process terminates immediately but
  child process keeps running forever and keeps processing the requests
  received from rabbitmq.
  
  Steps to reproduce:
  
  1. Identify running processes of nova-compute using "ps aux | grep 
nova-compute'
  2. Send kill or terminate signal to parent process.
-$ kill -9  or kill -15 

+    $ kill -9  or kill -15 

  3. Verify parent process is killed using "ps aux | grep nova-compute'

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

Title:
  nova compute child process remains orphan after sending sigkill or
  sigterm signal to parent process

Status in OpenStack Compute (nova):
  New

Bug description:
  When user sends SIGKILL (kill -9) or SIGTERM (kill -15) signal to
  nova-comupte parent process then parent process terminates immediately
  but child process keeps running forever and keeps processing the
  requests received from rabbitmq.

  Steps to reproduce:

  1. Identify running processes of nova-compute using "ps aux | grep 
nova-compute'
  2. Send kill or terminate signal to parent process.
     $ kill -9  or kill -15 

  3. Verify parent process is killed using "ps aux | grep nova-compute'

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1702260/+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 1697403] [NEW] get API call for service raises ResourceNotFound error

[Abhishek Kekane]

Public bug reported:

As of now get service API (show) is not present and it returns the 404 
ResourceNotFound error.
As per api-wg guidelines [1] it should return 405 Method Not Allowed.

Steps to reproduce:

1. Use curl command to show service details.
   $ curl -g -i -X GET http://10.232.48.201:8774/v2.1/os-services/5 -H 
"OpenStack-API-Version: compute 2.46" -H "User-Agent: python-novaclient" -H 
"Accept: application/json" -H "X-OpenStack-Nova-API-Version: 2.46" -H 
"X-Auth-Token: f7acf40a4fd848bf885de53e606fa12c"

Output:

HTTP/1.1 404 Not Found
Content-Length: 112
Content-Type: application/json
X-Openstack-Request-Id: req-e8682adf-1013-4ff5-8903-16dc3a26984d
X-Compute-Request-Id: req-e8682adf-1013-4ff5-8903-16dc3a26984d
Date: Mon, 12 Jun 2017 09:49:24 GMT

{"message": "The resource could not be found.\n\n\n",
"code": "404 Not Found", "title": "Not Found"}

Expected output:

If a request is made to a known resource URI, but the HTTP method used
for the request is not supported for that resource, the return code
should be 405 Method Not Allowed.

[1] https://specs.openstack.org/openstack/api-wg/guidelines/http.html
#failure-code-clarifications

** Affects: nova
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: nova
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  get API call for service raises ResourceNotFound error

Status in OpenStack Compute (nova):
  New

Bug description:
  As of now get service API (show) is not present and it returns the 404 
ResourceNotFound error.
  As per api-wg guidelines [1] it should return 405 Method Not Allowed.

  Steps to reproduce:

  1. Use curl command to show service details.
 $ curl -g -i -X GET http://10.232.48.201:8774/v2.1/os-services/5 -H 
"OpenStack-API-Version: compute 2.46" -H "User-Agent: python-novaclient" -H 
"Accept: application/json" -H "X-OpenStack-Nova-API-Version: 2.46" -H 
"X-Auth-Token: f7acf40a4fd848bf885de53e606fa12c"

  Output:

  HTTP/1.1 404 Not Found
  Content-Length: 112
  Content-Type: application/json
  X-Openstack-Request-Id: req-e8682adf-1013-4ff5-8903-16dc3a26984d
  X-Compute-Request-Id: req-e8682adf-1013-4ff5-8903-16dc3a26984d
  Date: Mon, 12 Jun 2017 09:49:24 GMT

  {"message": "The resource could not be found.\n\n\n",
  "code": "404 Not Found", "title": "Not Found"}

  Expected output:

  If a request is made to a known resource URI, but the HTTP method used
  for the request is not supported for that resource, the return code
  should be 405 Method Not Allowed.

  [1] https://specs.openstack.org/openstack/api-wg/guidelines/http.html
  #failure-code-clarifications

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1697403/+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 1688189] [NEW] Member create raises 500 error for unicode charater values

[Abhishek Kekane]

Public bug reported:

If user passes member as Unicode character while creating member for
image then he will get HTTP 500 error.

Steps to reproduce:

1. Create image
2. Assign member to image using
   $ glance member-create e64f4347-51d6-4f97-8b6e-02e40c7ecb30 ܎

   or using curl
   $ curl -g -i -X POST 
http://10.232.48.198:9292/v2/images/e64f4347-51d6-4f97-8b6e-02e40c7ecb30/members
 -H "User-Agent: python-glanceclient" -H "Content-Type: application/json" -H 
"X-Auth-Token: 
gABZCs01HPjCjKDkYnWQECtu9dYOxySXXrMH-lH4xO9xZBtl4MXNIPbTwkuCWSQ4EOh0tKvOPz55DmMdyOM0RYziM-qNE2Jikncq2oExZvf6k8OZYj_Vad5Q04p_uCU0Rg-9b94mVFfv_HaImCnT9ofO6RQZyNLOf1zc-AOzQPOMnjv9e4g"
 -d '{"member": "܎"}'

Output:

 
  500 Internal Server Error
 
 
  500 Internal Server Error
  The server has either erred or is incapable of performing the requested 
operation.

 


API Logs:
500 Internal Server Error: The server has either erred or is incapable of 
performing the requested operation. (HTTP 500)

2017-05-04 12:18:14.460 TRACE glance.common.wsgi self._flush(objects)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 2259, 
in _flush
2017-05-04 12:18:14.460 TRACE glance.common.wsgi 
transaction.rollback(_capture_exception=True)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/langhelpers.py", line 
66, in __exit__
2017-05-04 12:18:14.460 TRACE glance.common.wsgi compat.reraise(exc_type, 
exc_value, exc_tb)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/session.py", line 2223, 
in _flush
2017-05-04 12:18:14.460 TRACE glance.common.wsgi flush_context.execute()
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 
389, in execute
2017-05-04 12:18:14.460 TRACE glance.common.wsgi rec.execute(self)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/unitofwork.py", line 
548, in execute
2017-05-04 12:18:14.460 TRACE glance.common.wsgi uow
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 
181, in save_obj
2017-05-04 12:18:14.460 TRACE glance.common.wsgi mapper, table, insert)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/persistence.py", line 
835, in _emit_insert_statements
2017-05-04 12:18:14.460 TRACE glance.common.wsgi execute(statement, params)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 945, 
in execute
2017-05-04 12:18:14.460 TRACE glance.common.wsgi return meth(self, 
multiparams, params)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/elements.py", line 263, 
in _execute_on_connection
2017-05-04 12:18:14.460 TRACE glance.common.wsgi return 
connection._execute_clauseelement(self, multiparams, params)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1053, 
in _execute_clauseelement
2017-05-04 12:18:14.460 TRACE glance.common.wsgi compiled_sql, 
distilled_params
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1189, 
in _execute_context
2017-05-04 12:18:14.460 TRACE glance.common.wsgi context)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1398, 
in _handle_dbapi_exception
2017-05-04 12:18:14.460 TRACE glance.common.wsgi 
util.raise_from_cause(newraise, exc_info)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/compat.py", line 203, 
in raise_from_cause
2017-05-04 12:18:14.460 TRACE glance.common.wsgi reraise(type(exception), 
exception, tb=exc_tb, cause=cause)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 1182, 
in _execute_context
2017-05-04 12:18:14.460 TRACE glance.common.wsgi context)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", line 
470, in do_execute
2017-05-04 12:18:14.460 TRACE glance.common.wsgi cursor.execute(statement, 
parameters)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/pymysql/cursors.py", line 166, in 
execute
2017-05-04 12:18:14.460 TRACE glance.common.wsgi result = self._query(query)
2017-05-04 12:18:14.460 TRACE glance.common.wsgi   File 

[Yahoo-eng-team] [Bug 1569122] Re: return 500 when referring an image with status "SAVING"

[Abhishek Kekane]

Not reproducible any more

** Changed in: python-glanceclient
   Status: New => Invalid

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

Title:
  return 500 when referring an image with status "SAVING"

Status in OpenStack Compute (nova):
  Confirmed
Status in Glance Client:
  Invalid

Bug description:
  When I referred an image which is "SAVING" state by using 'nova' command,
  it returns 500 error.

  [How to reproduce]
  1. Create empty image
  $ glance image-create --name test --visibility public --disk-format ari

  +--+--+
  | Property | Value|
  +--+--+
  | checksum | None |
  | container_format | None |
  | created_at   | 2016-04-12T01:27:49Z |
  | disk_format  | ari  |
  | id   | 6d1ce183-e6ed-4dd0-a799-2f1b5abc6b3b |
  | min_disk | 0|
  | min_ram  | 0|
  | name | test |
  | owner| 662765a438ed40a9bc85b82e9f2a2cab |
  | protected| False|
  | size | None |
  | status   | queued   |
  | tags | []   |
  | updated_at   | 2016-04-12T01:27:49Z |
  | virtual_size | None |
  | visibility   | public   |
  +--+--+

  2. Confirm the image status.
  $ nova image-list
  +--+--+++
  | ID   | Name | Status | Server |
  +--+--+++
  | 6d1ce183-e6ed-4dd0-a799-2f1b5abc6b3b | test | SAVING ||
  +--+--+++

  3. Execute 'nova image-show' or 'nova image-delete'
  (This is example of 'nova image-show')
  $ nova --debug image-show 6d1ce183-e6ed-4dd0-a799-2f1b5abc6b3b
  DEBUG (extension:157) found extension EntryPoint.parse('v2token = 
keystoneauth1.loading._plugins.identity.v2:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('admin_token = 
keystoneauth1.loading._plugins.admin_token:AdminToken')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcauthcode = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectAuthorizationCode')
  DEBUG (extension:157) found extension EntryPoint.parse('v2password = 
keystoneauth1.loading._plugins.identity.v2:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3password = 
keystoneauth1.loading._plugins.identity.v3:Password')
  DEBUG (extension:157) found extension EntryPoint.parse('v3oidcpassword = 
keystoneauth1.loading._plugins.identity.v3:OpenIDConnectPassword')
  DEBUG (extension:157) found extension EntryPoint.parse('token = 
keystoneauth1.loading._plugins.identity.generic:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('v3token = 
keystoneauth1.loading._plugins.identity.v3:Token')
  DEBUG (extension:157) found extension EntryPoint.parse('password = 
keystoneauth1.loading._plugins.identity.generic:Password')
  DEBUG (session:248) REQ: curl -g -i -X GET http://192.168.3.223:5000/v2.0 -H 
"Accept: application/json" -H "User-Agent: keystoneauth1/2.3.0 
python-requests/2.9.1 CPython/2.7.6"
  INFO (connectionpool:207) Starting new HTTP connection (1): 192.168.3.223
  DEBUG (connectionpool:387) "GET /v2.0 HTTP/1.1" 200 339
  DEBUG (session:277) RESP: [200] Content-Length: 339 Vary: X-Auth-Token 
Keep-Alive: timeout=5, max=100 Server: Apache/2.4.7 (Ubuntu) Connection: 
Keep-Alive Date: Tue, 12 Apr 2016
  01:28:44 GMT Content-Type: application/json x-openstack-request-id: 
req-bc96ffbe-fe92-4fbe-931e-51c071766609
  RESP BODY: {"version": {"status": "stable", "updated": 
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v2.0+json"
  }], "id": "v2.0", "links": [{"href": "http://192.168.3.223:5000/v2.0/;, 
"rel": "self"}, {"href": "http://docs.openstack.org/;, "type": "text/html", 
"rel": "describedby"}]}}

  DEBUG (v2:63) Making authentication request to 
http://192.168.3.223:5000/v2.0/tokens
  DEBUG (connectionpool:387) "POST /v2.0/tokens HTTP/1.1" 200 3569
  DEBUG (session:248) REQ: curl -g -i -X GET 
http://192.168.3.223:8774/v2.1/662765a438ed40a9bc85b82e9f2a2cab -H "User-Agent: 
python-novaclient" -H "Accept: application/json" -H "X-
  Auth-Token: {SHA1}d52cbbc7997c02255185fbf06a3c608866de4091"
  

[Yahoo-eng-team] [Bug 1653103] Re: "tox -e py34" command gives Error "InterpreterNotFound python2.7 python3.4"

[Abhishek Kekane]

Marking the bug as invalid as Python 3.4 is not supported after support
is added for python 3.5

** Changed in: glance
   Status: In Progress => Invalid

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

Title:
  "tox -e py34" command gives Error "InterpreterNotFound python2.7
  python3.4"

Status in Glance:
  Invalid

Bug description:
  For the current master code, I am facing "InterpreterNotFound
  python2.7 python3.4" error while running the tox for python34.

  Steps to reproduce :

  1.  $ tox -e py34

Error : py34 create: /opt/stack/glance/.tox/py34
ERROR: InterpreterNotFound: python2.7
python3.4

  
  Master code details: 

commit 74a3d147e3a7dcc4feec4c4633425a6db2a6185f
Merge: ebd6f07 ce3e7b3
Author: Jenkins 
Date:   Tue Dec 27 09:44:11 2016 +

Merge "Correct url in doc source"


  Recently patch[1] got merge which gives the above mentioned error.
  [1] "https://review.openstack.org/#/c/412617/;

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1653103/+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 1719269] [NEW] Unable to run individual test

[Abhishek Kekane]

Public bug reported:

If you try to run individual test using tox then it runs entire test
suit.

Steps to reproduce:
Run below command,

tox -e py27
glance.tests.unit.test_auth.TestKeystoneAuthPlugin.test_get_plugin_from_strategy_keystone

or

tox -e py35
glance.tests.unit.test_auth.TestKeystoneAuthPlugin.test_get_plugin_from_strategy_keystone

Instead of running single unit test it runs entire test suit.

Workaround:

Workaround so far is to mention -- -n while running single test like
below;

tox -e py27 -- -n
glance.tests.unit.test_auth.TestKeystoneAuthPlugin.test_get_plugin_from_strategy_keystone

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Unable to run individual test

Status in Glance:
  New

Bug description:
  If you try to run individual test using tox then it runs entire test
  suit.

  Steps to reproduce:
  Run below command,

  tox -e py27
  
glance.tests.unit.test_auth.TestKeystoneAuthPlugin.test_get_plugin_from_strategy_keystone

  or

  tox -e py35
  
glance.tests.unit.test_auth.TestKeystoneAuthPlugin.test_get_plugin_from_strategy_keystone

  Instead of running single unit test it runs entire test suit.

  Workaround:

  Workaround so far is to mention -- -n while running single test like
  below;

  tox -e py27 -- -n
  
glance.tests.unit.test_auth.TestKeystoneAuthPlugin.test_get_plugin_from_strategy_keystone

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1719269/+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 1702260] Re: nova compute child process remains orphan after sending sigkill or sigterm signal to parent process

[Abhishek Kekane]

nova-compute is using ServiceLauncher to launch the service which
doesn't require any changes to exit gracefully.

** Changed in: nova
   Status: Incomplete => Invalid

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

Title:
  nova compute child process remains orphan after sending sigkill or
  sigterm signal to parent process

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  When user sends SIGKILL (kill -9) or SIGTERM (kill -15) signal to
  nova-comupte parent process then parent process terminates immediately
  but child process keeps running forever and keeps processing the
  requests received from rabbitmq.

  Steps to reproduce:

  1. Identify running processes of nova-compute using "ps aux | grep 
nova-compute'
  2. Send kill or terminate signal to parent process.
     $ kill -9  or kill -15 

  3. Verify parent process is killed using "ps aux | grep nova-compute'

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1702260/+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 1723001] [NEW] DB Upgrade: expand command fails while upgrading from ocata to pike

[Abhishek Kekane]

Public bug reported:

If you try to run 'glance-manage db expand' command while upgrading from
ocata to pike then it fails with below error:

InternalError: (pymysql.err.InternalError) (1060, u"Duplicate column
name 'visibility'") [SQL: u"ALTER TABLE images ADD COLUMN visibility
ENUM('private','public','shared','community')"]

NOTE: Same issue is reproducible on current master as well. (On master
code if you run 'glance-manage db expand' command, then you will get
below error.)

Steps to reproduce:
1. Setup stable/ocata
2. Pulled stable/pike branch using 'git checkout stable/pike'
3. Ran 'glance-manage db expand' command

Error:
INFO  [alembic.runtime.migration] Context impl MySQLImpl.
INFO  [alembic.runtime.migration] Will assume non-transactional DDL.
INFO  [alembic.runtime.migration] Running upgrade mitaka02 -> ocata_expand01, 
add visibility to images
CRITI [glance] InternalError: (pymysql.err.InternalError) (1060, u"Duplicate 
column name 'visibility'") [SQL: u"ALTER TABLE images ADD COLUMN visibility 
ENUM('private','public','shared','community')"]
Traceback (most recent call last):
  File "./glance-manage", line 10, in 
sys.exit(main())
  File "/opt/stack/glance/glance/cmd/manage.py", line 510, in main
return CONF.command.action_fn(*func_args, **func_kwargs)
  File "/opt/stack/glance/glance/cmd/manage.py", line 183, in expand
self.sync(version=expand_head)
  File "/opt/stack/glance/glance/cmd/manage.py", line 159, in sync
alembic_command.upgrade(a_config, version)
  File "/usr/local/lib/python2.7/dist-packages/alembic/command.py", line 174, 
in upgrade
script.run_env()
  File "/usr/local/lib/python2.7/dist-packages/alembic/script/base.py", line 
416, in run_env
util.load_python_file(self.dir, 'env.py')
  File "/usr/local/lib/python2.7/dist-packages/alembic/util/pyfiles.py", line 
93, in load_python_file
module = load_module_py(module_id, path)
  File "/usr/local/lib/python2.7/dist-packages/alembic/util/compat.py", line 
79, in load_module_py
mod = imp.load_source(module_id, path, fp)
  File "/opt/stack/glance/glance/db/sqlalchemy/alembic_migrations/env.py", line 
89, in 
run_migrations_online()
  File "/opt/stack/glance/glance/db/sqlalchemy/alembic_migrations/env.py", line 
84, in run_migrations_online
context.run_migrations()
  File "", line 8, in run_migrations
  File "/usr/local/lib/python2.7/dist-packages/alembic/runtime/environment.py", 
line 807, in run_migrations
self.get_context().run_migrations(**kw)
  File "/usr/local/lib/python2.7/dist-packages/alembic/runtime/migration.py", 
line 321, in run_migrations
step.migration_fn(**kw)
  File 
"/opt/stack/glance/glance/db/sqlalchemy/alembic_migrations/versions/ocata_expand01_add_visibility.py",
 line 149, in upgrade
_add_visibility_column(meta)
  File 
"/opt/stack/glance/glance/db/sqlalchemy/alembic_migrations/versions/ocata_expand01_add_visibility.py",
 line 126, in _add_visibility_column
op.add_column('images', v_col)
  File "", line 8, in add_column
  File "", line 3, in add_column
  File "/usr/local/lib/python2.7/dist-packages/alembic/operations/ops.py", line 
1541, in add_column
return operations.invoke(op)
  File "/usr/local/lib/python2.7/dist-packages/alembic/operations/base.py", 
line 318, in invoke
return fn(self, operation)
  File "/usr/local/lib/python2.7/dist-packages/alembic/operations/toimpl.py", 
line 123, in add_column
schema=schema
  File "/usr/local/lib/python2.7/dist-packages/alembic/ddl/impl.py", line 172, 
in add_column
self._exec(base.AddColumn(table_name, column, schema=schema))
  File "/usr/local/lib/python2.7/dist-packages/alembic/ddl/impl.py", line 118, 
in _exec
return conn.execute(construct, *multiparams, **params)
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 
914, in execute
return meth(self, multiparams, params)
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/sql/ddl.py", line 68, 
in _execute_on_connection
return connection._execute_ddl(self, multiparams, params)
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 
968, in _execute_ddl
compiled
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 
1146, in _execute_context
context)
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 
1341, in _handle_dbapi_exception
exc_info
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/util/compat.py", line 
203, in raise_from_cause
reraise(type(exception), exception, tb=exc_tb, cause=cause)
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 
1139, in _execute_context
context)
  File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/default.py", 
line 450, in do_execute
cursor.execute(statement, parameters)
  File "/usr/local/lib/python2.7/dist-packages/pymysql/cursors.py", line 166, 
in execute
result = self._query(query)
  File 

[Yahoo-eng-team] [Bug 1733803] [NEW] Running image-import call on active image returns 500 internal server error

[Abhishek Kekane]

 devstack@g-api.service[14229]: ERROR 
glance.common.wsgi InvalidImageStatusTransition: Image status transition from 
active to importing is not allowed
Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR glance.common.wsgi

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Running image-import call on active image returns 500 internal server
  error

Status in Glance:
  New

Bug description:
  If you run image-import api on any image which is in active state will
  return 500 error as it raises InvalidImageStatusTransition because
  Image status transition from active to importing is not allowed.

  Ideally it should return HTTP 409 Conflict error to the user.

  Prerequisites:
  1. Ensure you have latest version of python-glanceclient (version 2.8.0) 
installed
  2. Due to isssue [1] to execute taskflow you need to modify line [2] as shown 
below and restart glance-api service
 -pool.spawn_n(import_task.run, task_executor)
 +import_task.run(task_executor)
 [1] https://bugs.launchpad.net/glance/+bug/1712463
 [2] 
https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L106

  Steps to reporoduce:
  1. Create image and upload data to it
  $ glance image-create --container-format ami --disk-format ami --name 
cirros_image --file cirros-0.3.4-x86_64-blank.img
  2. Ensure image is in active state
  3. Run image-import call
 $ glance image-import  --import-method 
glance-direct

  Output:
  500 Internal Server Error: The server has either erred or is incapable of 
performing the requested operation. (HTTP 500)

  
  Glance API Logs:

  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: pdict['tenant'] = 
self.tenant
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi [None req-2abf2e90-c810-44d4-bc21-ab8f0e6cc8de admin admin] 
Caught error: Image status transition from active to importing is not allowed: 
InvalidImageStatusTransition: Image status transition from active to importing 
is not allowed
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi Traceback (most recent call last):
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/common/wsgi.py", line 1222, 
in __call__
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi request, **action_args)
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/common/wsgi.py", line 1261, 
in dispatch
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi return method(*args, **kwargs)
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/common/utils.py", line 363, 
in wrapped
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi return func(self, req, *args, **kwargs)
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/api/v2/images.py", line 
107, in import_image
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi import_task.run(task_executor)
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 238, 
in run
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi self.base.run(executor)
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/notifier.py", line 581, in 
run
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi super(TaskProxy, self).run(executor)
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 238, 
in run
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi self.base.run(executor)
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 238, 
in run
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi self.base.run(executor)
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/__init__.py", line 
439, in run
  Nov 22 07:21:01 devstack devstack@g-api.service[14229]: ERROR 
glance.common.ws

[Yahoo-eng-team] [Bug 1733816] [NEW] Import api, image becomes active if disk-format and container format are not set

[Abhishek Kekane]

Public bug reported:

If you run image-import api on any image which is in saving state and
does not have container-format and/or disk-format set goes into active
state. Ideally image which does not have container-format or disk-format
set should raise bad request error.

Prerequisites:
1. Ensure you have latest version of python-glanceclient (version 2.8.0) 
installed
2. Due to isssue [1] to execute taskflow you need to modify line [2] as shown 
below and restart glance-api service
   -pool.spawn_n(import_task.run, task_executor)
   +import_task.run(task_executor)
   [1] https://bugs.launchpad.net/glance/+bug/1712463
   [2] 
https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L106
   

Steps to reporoduce:
1. Create an image without container format and disk-format
$ glance image-create --name cirros_image
2. Run stage call to upload data in staging area
$ glance image-stage  --file 
~/devstack/local.conf
3. Run image-import call
   $ glance image-import  --import-method 
glance-direct

Output:
+--+--+
| Property | Value|
+--+--+
| checksum | 527294ab8d1550529d6e5ef853cf1933 |
| container_format | None |
| created_at   | 2017-11-22T09:28:42Z |
| disk_format  | None |
| id   | 303e1af0-4273-4a40-a719-9bd2e6a89864 |
| min_disk | 0|
| min_ram  | 0|
| name | cirros_image |
| owner| 40ab3e7ce43e4b6bb31a912b434490b5 |
| protected| False|
| size | 314  |
| status   | active   |
| tags | []   |
| updated_at   | 2017-11-22T09:29:46Z |
| virtual_size | None |
| visibility   | shared   |
+--+--+

>From the above output you can easily figure out that image is in active
state and container_format and disk_format are set to None.

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Import api, image becomes active if disk-format and container format
  are not set

Status in Glance:
  New

Bug description:
  If you run image-import api on any image which is in saving state and
  does not have container-format and/or disk-format set goes into active
  state. Ideally image which does not have container-format or disk-
  format set should raise bad request error.

  Prerequisites:
  1. Ensure you have latest version of python-glanceclient (version 2.8.0) 
installed
  2. Due to isssue [1] to execute taskflow you need to modify line [2] as shown 
below and restart glance-api service
 -pool.spawn_n(import_task.run, task_executor)
 +import_task.run(task_executor)
 [1] https://bugs.launchpad.net/glance/+bug/1712463
 [2] 
https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L106
 

  Steps to reporoduce:
  1. Create an image without container format and disk-format
  $ glance image-create --name cirros_image
  2. Run stage call to upload data in staging area
  $ glance image-stage  --file 
~/devstack/local.conf
  3. Run image-import call
 $ glance image-import  --import-method 
glance-direct

  Output:
  +--+--+
  | Property | Value|
  +--+--+
  | checksum | 527294ab8d1550529d6e5ef853cf1933 |
  | container_format | None |
  | created_at   | 2017-11-22T09:28:42Z |
  | disk_format  | None |
  | id   | 303e1af0-4273-4a40-a719-9bd2e6a89864 |
  | min_disk | 0|
  | min_ram  | 0|
  | name | cirros_image |
  | owner| 40ab3e7ce43e4b6bb31a912b434490b5 |
  | protected| False|
  | size | 314  |
  | status   | active   |
  | tags | []   |
  | upda

[Yahoo-eng-team] [Bug 1733813] [NEW] Running image-import call on queued image having valid container and disk formats returns 500 internal server error

[Abhishek Kekane]

ce.common.wsgi self._run(task_id, task.type)
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/opt/stack/glance/glance/async/taskflow_executor.py", line 181, in _run
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi self.task_repo.save(task)
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi self.force_reraise()
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi six.reraise(self.type_, self.value, self.tb)
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/opt/stack/glance/glance/async/taskflow_executor.py", line 172, in _run
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi engine.run()
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", 
line 247, in run
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi for _state in self.run_iter(timeout=timeout):
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", 
line 340, in run_iter
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi failure.Failure.reraise_if_any(er_failures)
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 336, in 
reraise_if_any
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi failures[0].reraise()
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 343, in 
reraise
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi six.reraise(*self._exc_info)
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/executor.py", 
line 53, in _execute_task
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi result = task.execute(**arguments)
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/opt/stack/glance/glance/async/flows/api_image_import.py", line 239, in execute
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi image_import.set_image_data(image, file_path or 
self.uri, self.task_id)
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/opt/stack/glance/glance/common/scripts/image_import/main.py", line 154, in 
set_image_data
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi "task_id": task_id})
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi self.force_reraise()
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi six.reraise(self.type_, self.value, self.tb)
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File 
"/opt/stack/glance/glance/common/scripts/image_import/main.py", line 145, in 
set_image_data
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi data_iter = script_utils.get_image_data_iter(uri)
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/common/scripts/utils.py", 
line 139, in get_image_data_iter
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi return open(uri, "r")
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi IOError: [Errno 2] No such file or directory: 
'/tmp/staging/567bfb61-d9f7-47e5-aa1a-90b7797e70be'
Nov 22 09:12:57 devstack devstack@g-api.service[14229]: ERROR glance.common.wsgi

** Affects: glance
 Importance: Undecided
 Assigne

[Yahoo-eng-team] [Bug 1733810] [NEW] Running image-import call on queued image without container and disk format returns 500 internal server error

[Abhishek Kekane]

missing))
Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi ValueError: Properties disk_format, container_format must be 
set prior to saving data.
Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR glance.common.wsgi

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Summary changed:

- Running image-import call on queued image returns 500 internal server error
+ Running image-import call on queued image without container and disk format 
returns 500 internal server error

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

Title:
  Running image-import call on queued image without container and disk
  format returns 500 internal server error

Status in Glance:
  New

Bug description:
  If you run image-import api on any image which is in queued state and
  doesn't have container-format and disk-format set will return 500
  error as it raises ValueError: Properties disk_format,
  container_format must be set prior to saving data. Ideally it should
  return HTTP 400 BadRequest error to the user.

  Prerequisites:
  1. Ensure you have latest version of python-glanceclient (version 2.8.0) 
installed
  2. Due to isssue [1] to execute taskflow you need to modify line [2] as shown 
below and restart glance-api service
 -pool.spawn_n(import_task.run, task_executor)
 +import_task.run(task_executor)
 [1] https://bugs.launchpad.net/glance/+bug/1712463
 [2] 
https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L106
 

  Steps to reporoduce:
  1. Create an image without container format and disk-format
  $ glance image-create --name cirros_image
  2. Ensure image is in queued state
  3. Run image-import call
 $ glance image-import  --import-method 
glance-direct

  Output:
  500 Internal Server Error: The server has either erred or is incapable of 
performing the requested operation. (HTTP 500)

  
  Glance API Logs:

  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: pdict['tenant'] = 
self.tenant
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi [None req-4d0baee8-445e-4ed0-82b8-966e71636ddf admin admin] 
Caught error: Properties disk_format, container_format must be set prior to 
saving data.: ValueError: Properties disk_format, container_format must be set 
prior to saving data.
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi Traceback (most recent call last):
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/common/wsgi.py", line 1222, 
in __call__
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi request, **action_args)
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/common/wsgi.py", line 1261, 
in dispatch
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi return method(*args, **kwargs)
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/common/utils.py", line 363, 
in wrapped
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi return func(self, req, *args, **kwargs)
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/api/v2/images.py", line 
107, in import_image
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi import_task.run(task_executor)
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 238, 
in run
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi self.base.run(executor)
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/notifier.py", line 581, in 
run
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi super(TaskProxy, self).run(executor)
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 238, 
in run
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi self.base.run(executor)
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 238, 
in run
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.common.wsgi self.base.run(executor)
  Nov 22 09:04:17 devstack devstack@g-api.service[14229]: ERROR 
glance.com

[Yahoo-eng-team] [Bug 1734832] [NEW] Unreachable 'ImageSizeLimitExceeded' exception block in upload call

[Abhishek Kekane]

Public bug reported:

ImageSizeLimitExceeded exception block [1] is unreachable in upload because
it is caught at [1] and raised StorageQuotaFull exception from there.

Further as it raised StorageQuataFull exception it prints None as a size
in the glance-api logs.

Reference glance-api-logs:
Nov 28 07:04:13 devstack devstack@g-api.service[11453]: ERROR 
glance.api.v2.image_data [None req-17b243db-9b3d-46d9-97f0-05f74bc76e18 admin 
admin] Image exceeds the storage quota: The size of the data None will exceed 
the limit. None bytes remaining.: StorageQuotaFull: The size of the data None 
will exceed the limit. None bytes remaining.

To make it correct we need to remove code from [2] where
ImageSizeLimitExceeded is caught and StorageQuotaFull is raised so that
it will be reachable in the controller [1].

[1] 
https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L232
[2] 
https://github.com/openstack/glance/blob/master/glance/quota/__init__.py#L305

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Unreachable 'ImageSizeLimitExceeded' exception block in upload call

Status in Glance:
  New

Bug description:
  ImageSizeLimitExceeded exception block [1] is unreachable in upload because
  it is caught at [1] and raised StorageQuotaFull exception from there.

  Further as it raised StorageQuataFull exception it prints None as a
  size in the glance-api logs.

  Reference glance-api-logs:
  Nov 28 07:04:13 devstack devstack@g-api.service[11453]: ERROR 
glance.api.v2.image_data [None req-17b243db-9b3d-46d9-97f0-05f74bc76e18 admin 
admin] Image exceeds the storage quota: The size of the data None will exceed 
the limit. None bytes remaining.: StorageQuotaFull: The size of the data None 
will exceed the limit. None bytes remaining.

  To make it correct we need to remove code from [2] where
  ImageSizeLimitExceeded is caught and StorageQuotaFull is raised so
  that it will be reachable in the controller [1].

  [1] 
https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L232
  [2] 
https://github.com/openstack/glance/blob/master/glance/quota/__init__.py#L305

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1734832/+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 1736332] [NEW] Image verification returns 500 if invalid 'img_signature_certificate_uuid' is specified

[Abhishek Kekane]

k@g-api.service[25628]: ERROR 
glance.common.wsgi self.force_reraise()
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi six.reraise(self.type_, self.value, self.tb)
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/notifier.py", line 427, in 
set_data
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi self.repo.set_data(data, size)
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/api/policy.py", line 194, 
in set_data
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi return self.image.set_data(*args, **kwargs)
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/quota/__init__.py", line 
304, in set_data
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi self.image.set_data(data, size=size)
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/location.py", line 427, in 
set_data
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi img_signature_key_type=key_type
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/cursive/signature_utils.py", line 232, in 
get_verifier
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi signature_key_type)
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/cursive/signature_utils.py", line 287, in 
get_public_key
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi certificate = get_certificate(context, 
signature_certificate_uuid)
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/cursive/signature_utils.py", line 316, in 
get_certificate
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi cert = keymgr_api.get(context, 
signature_certificate_uuid)
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/castellan/key_manager/barbican_key_manager.py",
 line 564, in get
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi uuid=managed_object_id)
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi ManagedObjectNotFoundError: Key not found, uuid: 
fb67edd2-95ef-404b-9af2-910708c6d9b9
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.common.wsgi 
Dec 05 06:25:51 signature-test.rdocloud devstack@g-api.service[25628]: [pid: 
25630|app: 0|req: 108/214] 127.0.0.1 () {40 vars in 692 bytes} [Tue Dec  5 
06:25:51 2017] PUT /v2/images/c78598f5-23ac-46e8-8626-c908b5b830df/file => 
generated 228 bytes in 163 msecs (HTTP/1.1 500) 4 headers in 184 bytes (1 
switches on core 0)

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Image verification returns 500 if invalid
  'img_signature_certificate_uuid' is specified

Status in Glance:
  New

Bug description:
  If image signature verification is enabled then while creating the
  image if invalid (non-existing) 'img_signature_certificate_uuid' is
  specified then image creation fails and returns 500 internal server
  error to the user. The reason is it returns
  'anagedObjectNotFoundError: Key not found, uuid: '
  which is not caught.

  Ideally it should return HTTP 400 bad request to the user.

  Pre-requisites:
  1. Ensure Barbican is enabled
  2. Create Keys and Certificate (Reference  
https://etherpad.openstack.org/p/mitaka-glance-image-signing-instructions#90)
  3. Create Signature (Reference 
https://etherpad.openstack.org/p/mitaka-glance-image-signing-instructions#184) 
and note down output of 'signature_64'
  4. Create context and upload certificate using context (

[Yahoo-eng-team] [Bug 1736336] [NEW] Image data stays in backend if image signature verification fails

[Abhishek Kekane]

   
|
++--+
$ 400 Bad Request: Signature verification failed for image 
6e8bec71-2176-4bcc-a732-2f76c5ac589f: Signature verification failed (HTTP 400)

Expected Output:
$ 400 Bad Request: Signature verification failed for image 
6e8bec71-2176-4bcc-a732-2f76c5ac589f: Signature verification failed (HTTP 400)


NOTE: Image data stays in backend
$ ls -lah /opt/stack/data/glance/images/6e8bec71-2176-4bcc-a732-2f76c5ac589f

total 15M
drwxr-xr-x. 2 centos centos  270 Dec  5 07:04 .
drwxr-xr-x. 5 centos centos   46 Dec  5 04:42 ..
-rw-r--r--. 1 centos centos 420K Dec  5 07:04 
6e8bec71-2176-4bcc-a732-2f76c5ac589f


Glance-api logs:
Dec 05 07:04:38 signature-test.rdocloud devstack@g-api.service[25628]: ERROR 
glance.api.v2.image_data [None req-b81d5e9c-8d5c-4b48-b7c8-efe546c3aa97 demo 
admin] Signature verification failed for image 
6e8bec71-2176-4bcc-a732-2f76c5ac589f: Signature verification failed: 
SignatureVerificationError: Signature verification failed

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Image data stays in backend if image signature verification fails

Status in Glance:
  New

Bug description:
  If image signature verification is enabled then while creating the
  image if verfication fails then it returns vaild error, deletes image
  from the database but image data stays in the bakend forever.

  Ideally if image verfication fails then it should delete the data from
  the backend as well.

  Pre-requisites:
  1. Ensure Barbican is enabled
  2. Create Keys and Certificate (Reference  
https://etherpad.openstack.org/p/mitaka-glance-image-signing-instructions#90)
  3. Create Signature (Reference 
https://etherpad.openstack.org/p/mitaka-glance-image-signing-instructions#184) 
and note down output of 'signature_64'
  4. Create context and upload certificate using context (Reference 
https://etherpad.openstack.org/p/glance-image-signing-create-context) and note 
down output of 'cert_uuid'

  
  Steps to reproduce:
  1. Upload Image to Glance, with Signature Metadata
 img_signature_certificate_uuid = 'fb67edd2-95ef-404b-9af2-910708c6d9b7'
 img_signature_hash_method = 'SHA-256'
 img_signature_key_type = 'RSA-PSS'
 img_signature = 
'ezccBYtJEdj2gOrN09woioHwi2rDVvBsmRI0i+9EYAYdE7E6FV8jzJD9BImcq/m7Dm6yZZPkCUHz+y4HBKeYqK0+otcz921zaeqcKGBvU1t7J9AL0hEgJbWg0RY6RXqDXpsOQrrkrHuna4O+BUOp6sPwb3j2eFYbbsqW6d/obgM='
 (different which is noted in Pre-requisites section Point 4 as 'signature_64')

 $ glance image-create --property
  name=cirrosSignedImage_goodSignature --property is-public=true
  --container-format bare --disk-format qcow2 --property
  
img_signature='abcdBYtJEdj2gOrN09woioHwi2rDVvBsmRI0i+9EYAYdE7E6FV8jzJD9BImcq/m7Dm6yZZPkCUHz+y4HBKeYqK0+otcz921zaeqcKGBvU1t7J9AL0hEgJbWg0RY6RXqDXpsOQrrkrHuna4O+BUOp6sPwb3j2eFYbbsqW6d/obgM='
  --property img_signature_certificate_uuid='fb67edd2-95ef-404b-
  9af2-910708c6d9b7' --property img_signature_hash_method='SHA-256'
  --property img_signature_key_type='RSA-PSS' --file
  cirros-0.3.2-source.tar.gz

  Note:
  'img_signature' starts with 'ezcc...' but in create command I have passed as 
'abcd..'

  Actual Output:
  
++--+
  | Property   | Value  
  |
  
++--+
  | checksum   | None   
  |
  | container_format   | bare   
  |
  | created_at | 2017-12-05T07:04:38Z   
  |
  | disk_format| qcow2  
  |
  | id | 6e8bec71-2176-4bcc-a732-2f76c5ac589f   
  |
  | img_signature  | 
abcdBYtJEdj2gOrN09woioHwi2rDVvBsmRI0i+9EYAYdE7E6FV8jzJD9BImcq/m7Dm6yZZPkCUHz+y4H
 |
  || 
BKeYqK0+otcz921zaeqcKGBvU1t7J9AL0hEgJbWg0RY6RXqDXpsOQrrkrHuna4O+BUOp6sPwb3j2eFYb
 |
  || bsqW6d/obgM=   
  |
  | img_signature_certificate_u

[Yahoo-eng-team] [Bug 1737952] [NEW] 500 error if custom property key is greater than 255 characters

[Abhishek Kekane]

ce.common.wsgi util.raise_from_cause(newraise, exc_info)
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File 
"/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 203, in 
raise_from_cause
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi reraise(type(exception), exception, tb=exc_tb, 
cause=cause)
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File 
"/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1182, in 
_execute_context
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi context)
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File 
"/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 470, in 
do_execute
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi cursor.execute(statement, parameters)
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/pymysql/cursors.py", line 166, in execute
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi result = self._query(query)
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/pymysql/cursors.py", line 322, in _query
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi conn.query(q)
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/pymysql/connections.py", line 856, in query
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi self._affected_rows = 
self._read_query_result(unbuffered=unbuffered)
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/pymysql/connections.py", line 1057, in 
_read_query_result
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi result.read()
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/pymysql/connections.py", line 1340, in read
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi first_packet = self.connection._read_packet()
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/pymysql/connections.py", line 1014, in 
_read_packet
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi packet.check_error()
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/pymysql/connections.py", line 393, in 
check_error
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi err.raise_mysql_exception(self._data)
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi   File "/usr/lib/python2.7/site-packages/pymysql/err.py", 
line 107, in raise_mysql_exception
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi raise errorclass(errno, errval)
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR 
glance.common.wsgi DBDataError: (pymysql.err.DataError) (1406, u"Data too long 
for column 'name' at row 1") [SQL: u'INSERT INTO image_properties (created_at, 
updated_at, deleted_at, deleted, image_id, name, value) VALUES (%(created_at)s, 
%(updated_at)s, %(deleted_at)s, %(deleted)s, %(image_id)s, %(name)s, 
%(value)s)'] [parameters: {'name': 
u'abcc
 ... (150 characters truncated) ... 
ccccccccccccc',
 'deleted': 0, 'created_at': datetime.datetime(2017, 12, 13, 11, 2, 9, 508041), 
'updated_at': datetime.datetime(2017, 12, 13, 11, 2, 9, 508048), 'value': 
u'12434', 'image_id': 'e376fa83-0082-4125-a79a-60696a0e348d', 'deleted_at': 
None}]
Dec 13 11:02:09 devstack devstack@g-api.service[20154]: ERROR glance.common.wsgi

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  500 error if custom property key is greater than 255 characters

Status in Glance:
  New

Bug description:
  While

[Yahoo-eng-team] [Bug 1733512] [NEW] Stage call returns 500 internal server error when image is in saving state

[Abhishek Kekane]

 target), attr, value)
Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/__init__.py", line 
151, in status
Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi raise e
Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi InvalidImageStatusTransition: Image status transition from 
saving to uploading is not allowed
Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR glance.common.wsgi

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: In Progress

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Stage call returns 500 internal server error when image is in saving
  state

Status in Glance:
  In Progress

Bug description:
  If image upload (/file call) is in progress image is in saving state at that 
time.
  If user tries to make a /stage call on same image then it returns 500 
internal server error as Image transition from saving to uploading is not 
allowed.

  Ideally it should return 409 HTTConflict error to the user.

  Steps to reproduce:
  1. Create image
 $ glance image-create --container-format ami --disk-format ami --name 
cirros_image
  2. Upload data to image
 $ glance image-upload  --file 
  3. Ensure image is in saving state and run image-stage command
 $ glance image-stage  --file 

  Output:
  500 Internal Server Error: The server has either erred or is incapable of 
performing the requested operation. (HTTP 500)

  Glance API logs:

  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi [None req-f8f2ccf6-88af-4104-aa02-8077bf2670a2 admin admin] 
Caught error: Image status transition from saving to uploading is not allowed: 
InvalidImageStatusTransition: Image status transition from saving to uploading 
is not allowed
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi Traceback (most recent call last):
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/common/wsgi.py", line 1222, 
in __call__
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi request, **action_args)
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/common/wsgi.py", line 1261, 
in dispatch
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi return method(*args, **kwargs)
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/common/utils.py", line 363, 
in wrapped
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi return func(self, req, *args, **kwargs)
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/api/v2/image_data.py", line 
344, in stage
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi self._restore(image_repo, image)
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi self.force_reraise()
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi   File 
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi six.reraise(self.type_, self.value, self.tb)
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/api/v2/image_data.py", line 
300, in stage
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi image.status = 'uploading'
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 23, 
in set_attr
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi return setattr(getattr(self, target), attr, value)
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 23, 
in set_attr
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.wsgi return setattr(getattr(self, target), attr, value)
  Nov 21 07:28:46 devstack devstack@g-api.service[12621]: ERROR 
glance.common.w

[Yahoo-eng-team] [Bug 1733551] [NEW] Stage call returns 500 internal server error when image does not exists

[Abhishek Kekane]

Public bug reported:

If user tries to stage data to unexisting image then it fails with 500
internal server error.

Ideally it should return 404 HTTNotFound error to the user.

Steps to reproduce:

1. Run image-stage with any random id command
   $ glance image-stage abcd --file 

Output:
500 Internal Server Error: The server has either erred or is incapable of 
performing the requested operation. (HTTP 500)

Glance API logs:

Nov 21 10:12:29 devstack devstack@g-api.service[19195]: pdict['tenant'] = 
self.tenant
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data [None req-99abd47d-7c74-43ad-a92e-abf01d97f4c4 admin 
admin] Failed to stage image data due to internal error: ImageNotFound: No 
image found with ID abcd
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data Traceback (most recent call last):
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data   File 
"/opt/stack/glance/glance/api/v2/image_data.py", line 298, in stage
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data image = image_repo.get(image_id)
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data   File 
"/opt/stack/glance/glance/api/authorization.py", line 107, in get
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data image = self.image_repo.get(image_id)
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data   File "/opt/stack/glance/glance/domain/proxy.py", 
line 86, in get
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data return self.helper.proxy(self.base.get(item_id))
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data   File "/opt/stack/glance/glance/api/policy.py", line 
105, in get
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data image = super(ImageRepoProxy, self).get(image_id)
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data   File "/opt/stack/glance/glance/domain/proxy.py", 
line 86, in get
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data return self.helper.proxy(self.base.get(item_id))
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data   File "/opt/stack/glance/glance/domain/proxy.py", 
line 86, in get
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data return self.helper.proxy(self.base.get(item_id))
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data   File "/opt/stack/glance/glance/domain/proxy.py", 
line 86, in get
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data return self.helper.proxy(self.base.get(item_id))
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data   File "/opt/stack/glance/glance/db/__init__.py", line 
89, in get
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data raise exception.ImageNotFound(msg)
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data ImageNotFound: No image found with ID abcd
Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
     Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

** Description changed:

  If user tries to stage data to unexisting image then it fails with 500
  internal server error.
  
  Ideally it should return 404 HTTNotFound error to the user.
  
  Steps to reproduce:
  
  1. Run image-stage with any random id command
-$ glance image-stage abcd1234 --file 
+    $ glance image-stage abcd --file 
  
  Output:
  500 Internal Server Error: The server has either erred or is incapable of 
performing the requested operation. (HTTP 500)
  
  Glance API logs:
  
  Nov 21 10:12:29 devstack devstack@g-api.service[19195]: pdict['tenant'] = 
self.tenant
  Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data [None req-99abd47d-7c74-43ad-a92e-abf01d97f4c4 admin 
admin] Failed to stage image data due to internal error: ImageNotFound: No 
image found with ID abcd
  Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data Traceback (most recent call last):
  Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data   File 
"/opt/stack/glance/glance/api/v2/image_data.py", line 298, in stage
  Nov 21 10:12:29 devstack devstack@g-api.service[19195]: ERROR 
glance.api.v2.image_data image = image_repo

[Yahoo-eng-team] [Bug 1733274] [NEW] Second stage call (re-staging) fails with 500 Internal server error

[Abhishek Kekane]

t/stack/glance/glance/domain/proxy.py", line 23, 
in set_attr
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi return setattr(getattr(self, target), attr, value)
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 23, 
in set_attr
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi return setattr(getattr(self, target), attr, value)
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 23, 
in set_attr
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi return setattr(getattr(self, target), attr, value)
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 23, 
in set_attr
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi return setattr(getattr(self, target), attr, value)
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 23, 
in set_attr
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi return setattr(getattr(self, target), attr, value)
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/proxy.py", line 23, 
in set_attr
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi return setattr(getattr(self, target), attr, value)
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi   File "/opt/stack/glance/glance/domain/__init__.py", line 
151, in status
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi raise e
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR 
glance.common.wsgi InvalidImageStatusTransition: Image status transition from 
uploading to uploading is not allowed
Nov 20 06:16:54 devstack devstack@g-api.service[15827]: ERROR glance.common.wsgi

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Second stage call (re-staging) fails with 500 Internal server error

Status in Glance:
  New

Bug description:
  When user calls stage command again then it fails with 500 internal server 
error.
  This is because after stage call image status changes to 'uploading' and for 
second call it again tries to set status to 'uploading' and fails with 
'InvalidImageStatusTransition: Image status transition from uploading to 
uploading is not allowed' exception which is not caught at the controller side.

  Steps to reproduce:
  1. Create image
 $ glance image-create --container-format ami --disk-format ami --name 
cirros_image
  2. Add image to staging area using stage call
 $ glance image-stage 
  3. Again run the same call
 $ glance image-stage 

  Output:
  Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/glanceclient/shell.py", line 699, in 
main
  OpenStackImagesShell().main(argv)
File "/usr/lib/python2.7/site-packages/glanceclient/shell.py", line 603, in 
main
  args.func(client, args)
File "/usr/lib/python2.7/site-packages/glanceclient/v2/shell.py", line 410, 
in do_image_stage
  gc.images.stage(args.id, image_data, args.size)
File "/usr/lib/python2.7/site-packages/glanceclient/common/utils.py", line 
545, in inner
  return RequestIdProxy(wrapped(*args, **kwargs))
File "/usr/lib/python2.7/site-packages/glanceclient/v2/images.py", line 
252, in stage
  u_url=url)
File "/usr/lib/python2.7/site-packages/glanceclient/common/utils.py", line 
545, in inner
  return RequestIdProxy(wrapped(*args, **kwargs))
File "/usr/lib/python2.7/site-packages/glanceclient/v2/images.py", line 
232, in upload
  resp, body = self.http_client.put(url, headers=hdrs, data=body)
File "/usr/lib/python2.7/site-packages/keystoneauth1/adapter.py", line 313, 
in put
  return self.request(url, 'PUT', **kwargs)
File "/usr/lib/python2.7/site-packages/glanceclient/common/http.py", line 
349, in request
  return self._handle_response(resp)
File "/usr/lib/python2.7/site-packages/glanceclient/common/http.py", line 
98, in _handle_response
  raise exc.from_response(resp, resp.content)
  HTTPInternalServerError: 500 Internal Server Error: The server has either 
erred or is 

[Yahoo-eng-team] [Bug 1732830] [NEW] Unreachable 'ImageSizeLimitExceeded' exception block in stage call

[Abhishek Kekane]

Public bug reported:

ImageSizeLimitExceeded exception block [1] is unreachable in stage because
we are using sotre_backend.add (filesystem.add in this case) and it will
raise 'exceptions.StorageFull()' [2] if image file is too large (errno.EFBIG).

[1] 
https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L323
[2] 
https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/filesystem.py#L691

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Unreachable 'ImageSizeLimitExceeded' exception block in stage call

Status in Glance:
  New

Bug description:
  ImageSizeLimitExceeded exception block [1] is unreachable in stage because
  we are using sotre_backend.add (filesystem.add in this case) and it will
  raise 'exceptions.StorageFull()' [2] if image file is too large (errno.EFBIG).

  [1] 
https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L323
  [2] 
https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/filesystem.py#L691

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1732830/+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 1732835] [NEW] Stage call fails with TypeError

[Abhishek Kekane]

Public bug reported:

If store_backend denies writing to store then glance_store will raise 
'StorageWriteDenied' error.
After catching this exception at glance side, unstage call [1] will fail with 
TypeError as it requires 3 arguments and only two were provided.

Actual call:
self._unstage(image_repo, image)

Expected call:
self._unstage(image_repo, image, staging_store)

[1]
https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L335

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Stage call fails with TypeError

Status in Glance:
  New

Bug description:
  If store_backend denies writing to store then glance_store will raise 
'StorageWriteDenied' error.
  After catching this exception at glance side, unstage call [1] will fail with 
TypeError as it requires 3 arguments and only two were provided.

  Actual call:
  self._unstage(image_repo, image)

  Expected call:
  self._unstage(image_repo, image, staging_store)

  [1]
  
https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L335

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1732835/+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 1770325] [NEW] Remove glance-direct from enabled_import_methods config option

[Abhishek Kekane]

Public bug reported:

Glance added the support for interoperable image imports. Image uploads are 
done using a two-step approach:
first uploading it to the Glance API using a local staging area, and then 
triggering an upload from the staging area to the storage backend.

In the case of an HA setup (ie with 3 controller nodes) this requires a
shared consistent filesystem across the controller nodes. Otherwise it
might happen that the image is uploaded to one node, and triggering the
import is executed on a different node - where the image does not exist.

Therefore we need to remove 'glance-direct' from the default, thus
operators need to enable it explicitly if they have a shared filesystem
across the controller nodes (for example using NFS).

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Remove glance-direct from enabled_import_methods config option

Status in Glance:
  New

Bug description:
  Glance added the support for interoperable image imports. Image uploads are 
done using a two-step approach:
  first uploading it to the Glance API using a local staging area, and then 
triggering an upload from the staging area to the storage backend.

  In the case of an HA setup (ie with 3 controller nodes) this requires
  a shared consistent filesystem across the controller nodes. Otherwise
  it might happen that the image is uploaded to one node, and triggering
  the import is executed on a different node - where the image does not
  exist.

  Therefore we need to remove 'glance-direct' from the default, thus
  operators need to enable it explicitly if they have a shared
  filesystem across the controller nodes (for example using NFS).

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1770325/+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 1775782] [NEW] glance-image-import.conf not parsed when running under wsgi

[Abhishek Kekane]

Public bug reported:

When development environment is set to run under wsgi mode (by setting
WSGI_MODE=mod_wsgi in local.conf) glance-image-import.conf file is not
parsed.

It is working properly if glance is running under uwsgi.

Steps to reproduce:
NOTE: Here I am trying to use plugin "inject_image_metadata" to inject metadata 
properties to the image.

1. Add glance-image-import.conf as mentioned at /etc/glance
   [image_import_opts]
   image_import_plugins = ["inject_image_metadata"]

   [inject_metadata_properties]
   inject = "property1":"value"
   ignore_user_roles = demo

2. Restart glance api service using "devstack@g-api.service"
3. Source using admin credentials (as we are ignoring demo role in 
glance-image-import.conf)
   $ source devstack/openrc admin admin
3. Create image using import api
   $ glance image-create-via-import --container-format bare --disk-format qcow2 
--name ceph_image_default --file temp.qcow2

Expected Output:
Properties mentioned in glance-image-import.conf should be injected to the image

Actual Output:
Properties are not injected as plugin is not loaded.

** Affects: glance
 Importance: Undecided
 Status: New

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

Title:
  glance-image-import.conf not parsed when running under wsgi

Status in Glance:
  New

Bug description:
  When development environment is set to run under wsgi mode (by setting
  WSGI_MODE=mod_wsgi in local.conf) glance-image-import.conf file is not
  parsed.

  It is working properly if glance is running under uwsgi.

  Steps to reproduce:
  NOTE: Here I am trying to use plugin "inject_image_metadata" to inject 
metadata properties to the image.

  1. Add glance-image-import.conf as mentioned at /etc/glance
 [image_import_opts]
 image_import_plugins = ["inject_image_metadata"]

 [inject_metadata_properties]
 inject = "property1":"value"
 ignore_user_roles = demo

  2. Restart glance api service using "devstack@g-api.service"
  3. Source using admin credentials (as we are ignoring demo role in 
glance-image-import.conf)
 $ source devstack/openrc admin admin
  3. Create image using import api
 $ glance image-create-via-import --container-format bare --disk-format 
qcow2 --name ceph_image_default --file temp.qcow2

  Expected Output:
  Properties mentioned in glance-image-import.conf should be injected to the 
image

  Actual Output:
  Properties are not injected as plugin is not loaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1775782/+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 1778645] [NEW] 500 response for incorrect node_staging_uri in glance-api.conf

[Abhishek Kekane]

Public bug reported:

node_staging_uri configuration option needs a value which always starts with 
file:///.
If by mistake operator sets value of node_staging_uri without file:/// then 
import api fails with 500 internal server error.

Steps to reproduce:
1. set below value to node_staging_uri in glance.api.conf
   node_staging_uri = /opt/stack/data/glance/staging
2. Restart glance-api service
3. Import image using below command
   $ glance image-create-via-import --disk-format qcow2 --container-format bare 
--name test --import-method 'glance-direct' --file  

Expected output:
Image should be imported successfully and should be in active state.

Actual output:
500 Internal Server Error: The server has either erred or is incapable of 
performing the requested operation. (HTTP 500)
Image remains in queued state.


glance-api logs:

Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data 
[None req-696e90ed-1592-4287-a84c-eeaa395852a8 admin admin] Failed to stage 
image data due to internal error: StoreAddDisabled: Configuration for store 
failed. Adding images to this store is disabled.
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data 
Traceback (most recent call last):
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data   
File "/opt/stack/glance/glance/api/v2/image_data.py", line 321, in stage
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data
 utils.CooperativeReader(data), CONF.image_size_cap), 0)
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data   
File "/usr/local/lib/python2.7/dist-packages/glance_store/capabilities.py", 
line 223, in op_checker
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data
 raise op_exec_map[op](**kwargs)
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data 
StoreAddDisabled: Configuration for store failed. Adding images to this store 
is disabled.
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.api.v2.image_data 
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi [None 
req-696e90ed-1592-4287-a84c-eeaa395852a8 admin admin] Caught error: 
Configuration for store failed. Adding images to this store is disabled.: 
StoreAddDisabled: Configuration for store failed. Adding images to this store 
is disabled.
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
Traceback (most recent call last):
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi   File 
"/opt/stack/glance/glance/common/wsgi.py", line 1274, in __call__
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
request, **action_args)
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi   File 
"/opt/stack/glance/glance/common/wsgi.py", line 1317, in dispatch
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
return method(*args, **kwargs)
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi   File 
"/opt/stack/glance/glance/common/utils.py", line 417, in wrapped
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
return func(self, req, *args, **kwargs)
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi   File 
"/opt/stack/glance/glance/api/v2/image_data.py", line 370, in stage
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
self._restore(image_repo, image)
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in 
__exit__
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
self.force_reraise()
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in 
force_reraise
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
six.reraise(self.type_, self.value, self.tb)
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi   File 
"/opt/stack/glance/glance/api/v2/image_data.py", line 321, in stage
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
utils.CooperativeReader(data), CONF.image_size_cap), 0)
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi   File 
"/usr/local/lib/python2.7/dist-packages/glance_store/capabilities.py", line 
223, in op_checker
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
raise op_exec_map[op](**kwargs)
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
StoreAddDisabled: Configuration for store failed. Adding images to this store 
is disabled.
Jun 26 06:28:11 ubuntu-old glance-api[24600]: ERROR glance.common.wsgi 
Jun 26 06:28:11 ubuntu-old glance-api[24600]: INFO eventlet.wsgi.server [None 
req-696e90ed-1592-4287-a84c-eeaa395852a8 

[Yahoo-eng-team] [Bug 1748117] [NEW] Incorrect version information if enable_image_import is false

[Abhishek Kekane]

Public bug reported:

If enable_image_import is false then 2.6 API should not be listed in the
response.

curl -g -i -X GET http://192.168.0.9/image/versions/ -H "Content-Type:
application/octet-stream" -H "X-Auth-Token:
6f54401ade9a44c7ab8e91e5587c9e8f"

Actual response:
{"versions": [{"status": "CURRENT", "id": "v2.6", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.5", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}, 
{"status": "SUPPORTED", "id": "v2.4", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.3", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}, 
{"status": "SUPPORTED", "id": "v2.2", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.1", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}, 
{"status": "SUPPORTED", "id": "v2.0", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}]}


Expected response:
{"versions": [{"status": "SUPPORTED", "id": "v2.5", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.4", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}, 
{"status": "SUPPORTED", "id": "v2.3", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.2", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}, 
{"status": "SUPPORTED", "id": "v2.1", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.0", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}]}

** Affects: glance
 Importance: High
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
   Importance: Undecided => High

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

** Changed in: glance
Milestone: None => queens-rc1

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

Title:
  Incorrect version information if enable_image_import is false

Status in Glance:
  New

Bug description:
  If enable_image_import is false then 2.6 API should not be listed in
  the response.

  curl -g -i -X GET http://192.168.0.9/image/versions/ -H "Content-Type:
  application/octet-stream" -H "X-Auth-Token:
  6f54401ade9a44c7ab8e91e5587c9e8f"

  Actual response:
  {"versions": [{"status": "CURRENT", "id": "v2.6", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.5", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}, 
{"status": "SUPPORTED", "id": "v2.4", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.3", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}, 
{"status": "SUPPORTED", "id": "v2.2", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.1", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}, 
{"status": "SUPPORTED", "id": "v2.0", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}]}

  
  Expected response:
  {"versions": [{"status": "SUPPORTED", "id": "v2.5", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.4", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}, 
{"status": "SUPPORTED", "id": "v2.3", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.2", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}, 
{"status": "SUPPORTED", "id": "v2.1", "links": [{"href": 
"http://192.168.0.9/image/v2/;, "rel": "self"}]}, {"status": "SUPPORTED", "id": 
"v2.0", "links": [{"href": "http://192.168.0.9/image/v2/;, "rel": "self"}]}]}

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1748117/+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 1749640] [NEW] db sync fails for mysql while adding triggers

[Abhishek Kekane]

3, in 
_execute_context",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "  File 
\"/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py\", line 507, 
in do_execute",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "cursor.execute(statement, parameters)",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "  File 
\"/usr/lib/python2.7/site-packages/pymysql/cursors.py\", line 166, in execute",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "result = self._query(query)",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "  File 
\"/usr/lib/python2.7/site-packages/pymysql/cursors.py\", line 322, in _query",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "conn.query(q)",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "  File 
\"/usr/lib/python2.7/site-packages/pymysql/connections.py\", line 856, in 
query",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "self._affected_rows = 
self._read_query_result(unbuffered=unbuffered)",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "  File 
\"/usr/lib/python2.7/site-packages/pymysql/connections.py\", line 1057, in 
_read_query_result",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "result.read()",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "  File 
\"/usr/lib/python2.7/site-packages/pymysql/connections.py\", line 1340, in 
read",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "first_packet = self.connection._read_packet()",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "  File 
\"/usr/lib/python2.7/site-packages/pymysql/connections.py\", line 1014, in 
_read_packet",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "packet.check_error()",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "  File 
\"/usr/lib/python2.7/site-packages/pymysql/connections.py\", line 393, in 
check_error",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "err.raise_mysql_exception(self._data)",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "  File 
\"/usr/lib/python2.7/site-packages/pymysql/err.py\", line 107, in 
raise_mysql_exception",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "raise errorclass(errno, errval)",
Feb 15 03:20:31 upstream-centos-7-2-node-rdo-cloud-tripleo-30309-6332 
os-collect-config[2239]: "DBError: (pymysql.err.InternalError) (1419, u'You do 
not have the SUPER privilege and binary logging is enabled (you *might* want to 
use the less safe log_bin_trust_function_creators variable)') [SQL: 
u\"\\nCREATE TRIGGER insert_visibility BEFORE INSERT ON images\\nFOR EACH 
ROW\\nBEGIN\\n-- NOTE(abashmak):\\n-- The following IF/ELSE block 
implements a priority decision tree.\\n-- Strict order MUST be followed to 
correctly cover all the edge cases.\\n\\n-- Edge case: neither is_public 
nor visibility specified\\n--(or both specified as NULL):\\n
IF NEW.is_public <=> NULL AND NEW.visibility <=> NULL THEN\\nSIGNAL 
SQLSTATE '45000' SET MESSAGE_TEXT = 'Invalid visibility value';\\n-- Edge 
case: both is_public and visibility specified:\\nELSEIF NOT(NEW.is_public 
<=> NULL OR NEW.visibility <=> NULL) THEN\\nSIGNAL SQLSTATE '45000' SET 
MESSAGE_TEXT = 'Invalid visibility value';\\n-- Inserting with is_public, 
set visibility accordingly:\\nELSEIF NOT NEW.is_public <=> NULL THEN\\n 
   IF NEW.is_public = 1 THEN\\nSET NEW.visibility = 'public';\\n
ELSE\\nSET NEW.visibility = 'shared';\\nEND IF;\\n
-- Inserting with visibility, set is_public accordingly:\\nELSEIF NOT 
NEW.visibility <=> NULL THEN\\nIF NEW.visibility = 'public' THEN\\n 
   SET NEW.is_public = 1;\\nELSE\\nSET NEW.is_public = 
0;\\nEND IF;\\n-- Edge case: either one of: is_public or 
visibility,\\n--is explicitly set to NULL:\\n

[Yahoo-eng-team] [Bug 1670464] Re: Downloading image with --progress fails with "RequestIdProxy object is not an iterator"

[Abhishek Kekane]

** Changed in: glance
   Status: Triaged => Fix Released

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

Title:
  Downloading image with --progress fails with "RequestIdProxy object is
  not an iterator"

Status in Glance:
  Fix Released

Bug description:
  I'm seeing this on a recent devstack.  Without --progress it seems to
  work fine.

  [bnemec@Arisu ~]$ glance -d image-download 
2974158b-383d-4fe6-9671-5248b9a5d07d --file bmc-base.qcow2 --progress
  DEBUG:keystoneauth.session:REQ: curl -g -i -X GET http://11.1.1.78:5000/v3 -H 
"Accept: application/json" -H "User-Agent: glance keystoneauth1/2.18.0 
python-requests/2.12.5 CPython/2.7.13"
  DEBUG:requests.packages.urllib3.connectionpool:Starting new HTTP connection 
(1): 11.1.1.78
  DEBUG:requests.packages.urllib3.connectionpool:http://11.1.1.78:5000 "GET /v3 
HTTP/1.1" 200 252
  DEBUG:keystoneauth.session:RESP: [200] Date: Mon, 06 Mar 2017 18:37:02 GMT 
Server: Apache/2.4.25 (Fedora) OpenSSL/1.0.2k-fips mod_wsgi/4.4.23 
Python/2.7.13 Content-Length: 252 Vary: X-Auth-Token x-openstack-request-id: 
req-1fdae4f6-857c-4032-a4fb-1ecd08d1e90d Keep-Alive: timeout=5, max=100 
Connection: Keep-Alive Content-Type: application/json 
  RESP BODY: {"version": {"status": "stable", "updated": 
"2017-02-22T00:00:00Z", "media-types": [{"base": "application/json", "type": 
"application/vnd.openstack.identity-v3+json"}], "id": "v3.8", "links": 
[{"href": "http://11.1.1.78/identity/v3/;, "rel": "self"}]}}

  DEBUG:keystoneauth.session:GET call to None for http://11.1.1.78:5000/v3 used 
request id req-1fdae4f6-857c-4032-a4fb-1ecd08d1e90d
  DEBUG:keystoneauth.identity.v3.base:Making authentication request to 
http://11.1.1.78/identity/v3/auth/tokens
  DEBUG:requests.packages.urllib3.connectionpool:Starting new HTTP connection 
(1): 11.1.1.78
  DEBUG:requests.packages.urllib3.connectionpool:http://11.1.1.78:80 "POST 
/identity/v3/auth/tokens HTTP/1.1" 201 3438
  DEBUG:keystoneauth.identity.v3.base:{"token": {"is_domain": false, "methods": 
["password"], "roles": [{"id": "fcd99b843dfb4deca4f0fd5096360c22", "name": 
"admin"}], "expires_at": "2017-06-30T12:23:41.00Z", "project": {"domain": 
{"id": "default", "name": "Default"}, "id": "45c03ec02978498db7a12de812cc4b18", 
"name": "admin"}, "catalog": [{"endpoints": [{"url": 
"http://11.1.1.78:8774/v2/45c03ec02978498db7a12de812cc4b18;, "interface": 
"public", "region": "RegionOne", "region_id": "RegionOne", "id": 
"5c473dd798dd4206b529cfce030bfef2"}], "type": "compute_legacy", "id": 
"18a8bab02dd74eebb1b6308b15bf461a", "name": "nova_legacy"}, {"endpoints": 
[{"url": "http://11.1.1.78:8004/v1/45c03ec02978498db7a12de812cc4b18;, 
"interface": "public", "region": "RegionOne", "region_id": "RegionOne", "id": 
"631a5450741443d4a94128aaa159b5e9"}, {"url": 
"http://11.1.1.78:8004/v1/45c03ec02978498db7a12de812cc4b18;, "interface": 
"admin", "region": "RegionOne", "region_id": "RegionOne", "id": 
"a83e3e461d0e442fa8e2464f06dd535f"}, {"url": 
"http://11.1.1.78:8004/v1/45c03ec02978498db7a12de812cc4b18;, "interface": 
"internal", "region": "RegionOne", "region_id": "RegionOne", "id": 
"d3a005ac8848461896d85ea0ed8323a6"}], "type": "orchestration", "id": 
"207ce855fbe7474db0a2b7d5fc0e9c9f", "name": "heat"}, {"endpoints": [{"url": 
"http://11.1.1.78:8000/v1;, "interface": "public", "region": "RegionOne", 
"region_id": "RegionOne", "id": "0c2a56c5c6c648ada5698536e1d6b850"}, {"url": 
"http://11.1.1.78:8000/v1;, "interface": "internal", "region": "RegionOne", 
"region_id": "RegionOne", "id": "12e59772754e41149f3be25805ea11c9"}, {"url": 
"http://11.1.1.78:8000/v1;, "interface": "admin", "region": "RegionOne", 
"region_id": "RegionOne", "id": "939d5746405c4571ace5cfc5d1fe5bdc"}], "type": 
"cloudformation", "id": "34ccb229f8e14a05bfe668094c927126", "name": 
"heat-cfn"}, {"endpoints": [{"url": "http://11.1.1.78/identity_admin;, 
"interface": "admin", "region": "RegionOne", "region_id": "RegionOne", "id": 
"d924181ce443443aa425bb740249f09a"}, {"url": "http://11.1.1.78/identity;, 
"interface": "public", "region": "RegionOne", "region_id": "RegionOne", "id": 
"e38adbef3cb14649b775646d5f383942"}], "type": "identity", "id": 
"54ab5a716ae0465286a6da5ff78c5b0b", "name": "keystone"}, {"endpoints": [{"url": 
"http://11.1.1.78:8774/v2.1;, "interface": "public", "region": "RegionOne", 
"region_id": "RegionOne", "id": "5b12864e38ec4d8b88955e50e9ff9839"}], "type": 
"compute", "id": "78e758f7be8d44529a56e05a53a1355c", "name": "nova"}, 
{"endpoints": [{"url": "http://11.1.1.78/placement;, "interface": "public", 
"region": "RegionOne", "region_id": "RegionOne", "id": 
"eeea1c9001bd40a88042017221e81c1a"}], "type": "placement", "id": 
"b68c8f2103124c44988fb683a634ec94", "name": "placement"}, {"endpoints": 
[{"url": "http://11.1.1.78:9696/;, "interface": "public", "region": 
"RegionOne", "region_id": "RegionOne", "id": 

[Yahoo-eng-team] [Bug 1750555] [NEW] Revisit database rolling upgrade documentation

[Abhishek Kekane]

Public bug reported:

Since db_sync is now internally using EMC pattern we need to revisit the
entire database rolling upgrades documentation.

** Affects: glance
 Importance: High
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

** Changed in: glance
   Importance: Undecided => High

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

Title:
  Revisit database rolling upgrade documentation

Status in Glance:
  New

Bug description:
  Since db_sync is now internally using EMC pattern we need to revisit
  the entire database rolling upgrades documentation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1750555/+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 1789351] Re: Glance deployment with python3 + "keystone" paste_deploy flavor Fails

[Abhishek Kekane]

Fixed in keystonemiddleware.

** Changed in: glance
   Status: New => Invalid

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

Title:
  Glance deployment with python3 + "keystone" paste_deploy flavor Fails

Status in Glance:
  Invalid
Status in keystonemiddleware:
  In Progress
Status in oslo.config:
  New

Bug description:
  This happens with oslo.config >= 6.3.0([1]) + python3 + "keystone" 
paste_deploy + current glance(before 
https://review.openstack.org/#/c/532503/10/glance/common/store_utils.py@30 it 
works)
  Testing in devstack: https://review.openstack.org/#/c/596380/

  The glance api service fails to start with below Error, reproducing here: 
https://review.openstack.org/#/c/596380/:-
  ERROR: dictionary changed size during iteration , see logs below

  Failure logs from job:- http://logs.openstack.org/80/596380/2/check
  /tempest-full-
  py3/514fa29/controller/logs/screen-g-api.txt.gz#_Aug_27_07_26_10_698243

  
  The Runtime Error is returned at keystonemiddleware:- 
https://github.com/openstack/keystonemiddleware/blob/master/keystonemiddleware/auth_token/__init__.py#L551
  Adding code snippet here:-
  if self._conf.oslo_conf_obj != cfg.CONF:   <-- Fails here
  oslo_cache.configure(self._conf.oslo_conf_obj)

  So with pdb found that an additional key(fatal_deprecations) was added
  to cfg.CONF at ^^, so Error is returned in python3. With python2 same
  key is added but no Error.

  There are multiple ways to avoid it, like use the paste_deploy configuration 
that works(ex: keystone+cachemanagement), use oslo.config <= 6.2.0, Use python2 
or update 
glance(https://review.openstack.org/#/c/532503/10/glance/common/store_utils.py@30
 as use_user_token is deprecated since long)
  with keystone+cachemanagement, all the config items were added before 
reaching the Failure point in keystonemiddleware and self._conf.oslo_conf_obj 
!= cfg.CONF didn't raised an error and returned Boolean. Don't know why.

  But it seems a real issue to me as it may happen in python3 at different 
places. So it would be good if Teams from affected projects(oslo.config, 
keystonemiddleware, glance) can look at it and fix(not avoid) at the best place.
  To me it looks like keystonemiddleware is not handling(comparing the dict) it 
properly for python3, as the conf is dynamically updated(how ? and when ?).

  - so can oslo.config Team check if glance and keystonmiddleware are 
handling/using oslo.config properly.
  - i checked keystone+cachemanagement is default in devstack from last 6 
years, is "keystone" flavor supported? if yes it should be fixed. Also it would 
be good to cleanup the deprecated options those are deprecated since Mitaka.
  - If it's wrongly used in keystonemiddleware/glance, it would be good to fix 
there.

  
  Initially detected while testing with Fedora[2], but later digged on why it's 
working in CI with Ubuntu and started [3].

  
  [1] https://review.openstack.org/#/c/560094/
  [2] https://review.rdoproject.org/r/#/c/14921/
  [3] https://review.openstack.org/#/c/596380/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1789351/+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 1753964] [NEW] Image remains in queued state for web-download if node_staging_uri is not set

[Abhishek Kekane]

rify_requirements,
Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/usr/local/lib/python2.7/dist-packages/stevedore/extension.py", line 227, in 
_load_one_plugin
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: obj = plugin(*invoke_args, 
**invoke_kwds)
Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/opt/stack/glance/glance/async/flows/api_image_import.py", line 323, in 
get_flow
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: file_uri = 
separator.join((CONF.node_staging_uri, str(image_id)))
Mar 07 09:26:07 ubuntu-16 glance-api[3499]: UnboundLocalError: local variable 
'separator' referenced before assignment

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

** Summary changed:

- 500 Error for web-download if node_staging_uri is not set 
+ Image remains in queued state for web-download if node_staging_uri is not set

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

Title:
  Image remains in queued state for web-download if node_staging_uri is
  not set

Status in Glance:
  New

Bug description:
  If operator does not set 'node_staging_uri' in glance-api.conf then
  importing image using web-download remains in queued state.

  Steps to reproduce:
  1. Ensure glance-api is running under mod_wsgi (add WSGI_MODE=mod_wsgi in 
local.conf and run stack.sh)
  2. Do not set node_staging_uri in glance-api.conf

  3. Create image using below curl command:
  curl -i -X POST -H "x-auth-token: " 
http://192.168.0.13:9292/v2/images -d 
'{"container_format":"bare","disk_format":"raw","name":"Import web-download"}'

  4. Import image using below curl command:
  curl -i -X POST -H "Content-type: application/json" -H "x-auth-token: 
" 
http://192.168.0.13:9292/v2/images//import -d 
'{"method":{"name":"web-download","uri":"https://www.openstack.org/assets/openstack-logo/2016R/OpenStack-Logo-Horizontal.eps.zip"}}'

  Expected result:
  Image should be in active state.

  Actual result:
  Image remains in queued state.

  API Logs:
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: DEBUG glance_store.backend [-] 
Attempting to import store file {{(pid=3506) _load_store 
/usr/local/lib/python2.7/dist-packages/glance_store/backend.py:231}}
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: DEBUG glance_store.capabilities 
[-] Store glance_store._drivers.filesystem.Store doesn't support updating 
dynamic storage capabilities. Please overwrite 'update_capabilities' method of 
the store to implement updating logics if needed. {{(pid=3506) 
update_capabilities 
/usr/local/lib/python2.7/dist-packages/glance_store/capabilities.py:97}}
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: Traceback (most recent call last):
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/usr/local/lib/python2.7/dist-packages/eventlet/greenpool.py", line 82, in 
_spawn_n_impl
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: func(*args, **kwargs)
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/opt/stack/glance/glance/domain/proxy.py", line 238, in run
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self.base.run(executor)
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/opt/stack/glance/glance/notifier.py", line 581, in run
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: super(TaskProxy, 
self).run(executor)
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/opt/stack/glance/glance/domain/proxy.py", line 238, in run
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self.base.run(executor)
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/opt/stack/glance/glance/domain/proxy.py", line 238, in run
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self.base.run(executor)
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/opt/stack/glance/glance/domain/__init__.py", line 438, in run
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: 
executor.begin_processing(self.task_id)
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/opt/stack/glance/glance/async/taskflow_executor.py", line 144, in 
begin_processing
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: super(TaskExecutor, 
self).begin_processing(task_id)
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/opt/stack/glance/glance/async/__init__.py", line 63, in begin_processing
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: self._run(task_id, task.type)
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]:   File 
"/opt/stack/glance/glance/async/taskflow_executor.py", line 165, in _run
  Mar 07 09:26:07 ubuntu-16 glance-api[3499]: flow = self._get_fl

[Yahoo-eng-team] [Bug 1761544] [NEW] Add missing functional tests for Image Import

[Abhishek Kekane]

Public bug reported:

Add missing functional tests for glance-direct and web-download import
methods of new Image Import API.

** Affects: glance
 Importance: High
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: In Progress

** Affects: glance/queens
 Importance: High
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: Triaged


** Tags: queens-backport-potential

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  Add missing functional tests for Image Import

Status in Glance:
  In Progress
Status in Glance queens series:
  Triaged

Bug description:
  Add missing functional tests for glance-direct and web-download import
  methods of new Image Import API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1761544/+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 1765309] [NEW] 500 error on image-download if image is not present at any location

[Abhishek Kekane]

ot;, line 216, in __call__
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance return 
app(environ, start_response)
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 145, in __call__
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance return 
resp(environ, start_response)
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/routes/middleware.py", line 141, in 
__call__
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance 
response = self.app(environ, start_response)
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 145, in __call__
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance return 
resp(environ, start_response)
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 145, in __call__
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance return 
resp(environ, start_response)
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance TypeError: 
'ImageProxy' object is not callable
Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance

** Affects: glance
 Importance: Undecided
 Assignee: Abhishek Kekane (abhishek-kekane)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Abhishek Kekane (abhishek-kekane)

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

Title:
  500 error on image-download if image is not present at any location

Status in Glance:
  New

Bug description:
  As of now for downloading the image it iterates through all the
  locations and if data (image) is not present at any of the location in
  the end it Logs the error message as "Glance tried all active
  locations to get data for image  but all have failed."
  Further it fails with 500 error.

  This issue can occur either if image is not available in any of the
  location or any error occured during the download process.

  NOTE:
  To reproduce this issue I have manually added 'continue' statement at [1] to 
assume that image is not available at any of the location.
  [1] https://github.com/openstack/glance/blob/master/glance/location.py#L470

  Steps to reproduce:
  1. Modify glance/location.py as mentioned in NOTE
  2. Restart glance-api service
  3. Download image using:
 $ glance image-download  --file downloaded_image 

  Expected Result:
  Image data should be downloaded and saved in 'downloaded_image' file

  Actual Result:
  glance image-download 780ffe26-b95a-4b6f-b2c0-c38803bed73a --file abcdUnable 
to download image '780ffe26-b95a-4b6f-b2c0-c38803bed73a'. (502 Proxy Error: 
Proxy Error: The proxy server received an invalid: response from an upstream 
server.: The proxy server could not handle the request 
GET/image/v2/images/780ffe26-b95a-4b6f-b2c0-c38803bed73a/file.: Reason: 
Error reading from remote server: Apache/2.4.18 (Ubuntu) Server at 192.168.0.6 
Port 80 (HTTP 502))

  
  Glance API logs:
  Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance.location 
[None req-cfca70d4-d9a7-495f-9762-0fb2a8eee769 admin admin] Glance tried all 
active locations to get data for image 780ffe26-b95a-4b6f-b2c0-c38803bed73a but 
all have failed.
  Apr 19 06:37:58 signature devstack@g-api.service[5419]: CRITICAL glance [None 
req-cfca70d4-d9a7-495f-9762-0fb2a8eee769 admin admin] Unhandled error: 
TypeError: 'ImageProxy' object is not callable
  Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance 
Traceback (most recent call last):
  Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 131, in __call__
  Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance resp 
= self.call_func(req, *args, **self.kwargs)
  Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 196, in call_func
  Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance 
return self.func(req, *args, **kwargs)
  Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/oslo_middleware/base.py", line 131, in 
__call__
  Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance 
response = req.get_response(self.application)
  Apr 19 06:37:58 signature devstack@g-api.service[5419]: ERROR glance   File 
"/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1327, in send
  Apr 19 06:37:58

[Yahoo-eng-team] [Bug 1256593] Re: image size should not be overwritten when using --copy-from

[Abhishek Kekane]

This bug is reported for v1 api which is deprecated and will be removed
during rocky cycle, so marking this as invalid.

** Changed in: glance
   Status: In Progress => Invalid

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

Title:
  image size should not be overwritten when using --copy-from

Status in Glance:
  Won't Fix

Bug description:
  when uploading a new image using either stdin or --file we return 500
  if the size passed in the request does not match what we gather from
  the backing store

  the --copy-from option behaves inconsistently as it overwrites the
  size passed by the uploader with the value from the store so we don't
  enforce the aforementioned check

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1256593/+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 1381365] Re: SSL Version and cipher selection not possible

[Abhishek Kekane]

** Changed in: glance
   Status: New => Won't Fix

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

Title:
  SSL Version and cipher selection not possible

Status in Cinder:
  Won't Fix
Status in Glance:
  Won't Fix
Status in OpenStack Identity (keystone):
  Won't Fix
Status in OpenStack Compute (nova):
  Won't Fix
Status in OpenStack Security Advisory:
  Won't Fix

Bug description:
  We configure keystone to use SSL always. Due to the poodle issue, I was 
trying to configure keystone to disable SSLv3 completely. 
  
http://googleonlinesecurity.blogspot.fi/2014/10/this-poodle-bites-exploiting-ssl-30.html
  https://www.openssl.org/~bodo/ssl-poodle.pdf

  It seems that keystone has no support for configring SSL versions, nor
  ciphers.

  If I'm not mistaken the relevant code is in the start function in
  common/environment/eventlet_server.py

  It calls 
  eventlet.wrap_ssl
  but with no SSL version nor cipher options. Since the interface is identical, 
I assume it uses ssl.wrap_socket. The default here seems to be  PROTOCOL_SSLv23 
(SSL2 disabled), which would make this vulnerable to the poodle issue.

  SSL conifgs should probably be possible to be set in the config file
  (with sane defaults), so that current and newly detected weak ciphers
  can be disabled without code changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1381365/+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 1404082] Re: rbd_store_chunk_size Sets to Bytes instead of kB

[Abhishek Kekane]

Fixed in glance_store with patch
https://review.openstack.org/#/c/121992/

** Changed in: glance
   Status: New => Invalid

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

Title:
  rbd_store_chunk_size Sets to Bytes instead of kB

Status in Glance:
  Invalid

Bug description:
  In Juno-Release I am experiancing rbd_store_chunk_size setting the
  image object size to bytes rather than kB resulting in much much more
  objects being created

  Icehouse Install
  root@node-1:~# rbd info images/62e06da9-2d39-4c7f-a2d8-d869953b9996@snap
  rbd image '62e06da9-2d39-4c7f-a2d8-d869953b9996':
  size 4096 MB in 512 objects
  order 23 (8192 kB objects)
  block_name_prefix: rbd_data.6a282e18d096
  format: 2
  features: layering
  protected: True

  Juno Install
  root@hvm003 ~]# rbd info images/136dd921-f6a2-432f-b4d6-e9902f71baa6@snap
  rbd image '136dd921-f6a2-432f-b4d6-e9902f71baa6':
  size 4096 MB in 524288 objects
  order 13 (8192 bytes objects)
  block_name_prefix: rbd_data.10d73ac85fb6
  format: 2
  features: layering
  protected: True

  Either the documentation needs updating or rbd_store_chunk_size needs
  to be changed to set the object size in kB. Currently the workaround
  to get back to 8MB object size is 'rbd_store_chunk_size = 8192'

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1404082/+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 1379774] Re: 017_quote_encrypted_swift_credentials is a NOOP

[Abhishek Kekane]

Not really a issue, just a INFO message for admin.

** Changed in: glance
   Status: New => Invalid

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

Title:
  017_quote_encrypted_swift_credentials is a NOOP

Status in Glance:
  Invalid

Bug description:
  After running glance-manage db_sync I saw the following entry in the
  log messages. I am not sure if this is intended. I have not configured
  Swift as a storage adapter. But I think that should not change the
  database schema?

  2014-10-10 12:16:10.362 12396 INFO
  017_quote_encrypted_swift_credentials [-] 'metadata_encryption_key'
  was not specified in the config file or a config file was not
  specified. This means that this migration is a NOOP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1379774/+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 1269634] Re: Glance reports NO ERROR for failed upload

[Abhishek Kekane]

This bug is reported for v1 api which is deprecated and will be removed
during rocky cycle, so marking this as invalid.

** Changed in: glance
   Status: New => Invalid

** Changed in: glance
   Status: Invalid => Won't Fix

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

Title:
  Glance reports NO ERROR for failed upload

Status in Glance:
  Won't Fix

Bug description:
  On a 0.12.0 client, attempt to upload an image to glance:
  $ glance -d -v image-create --name=Test --disk-format=qcow2 
--container-format=bare --file test.img
  Error communicating with http://example.com:9292 [Errno 35] Resource 
temporarily unavailable

  In debug mode:
  curl -i -X POST -H 'x-image-meta-container_format: bare' -H 
'Transfer-Encoding: chunked' -H 'User-Agent: python-glanceclient' -H 
'x-image-meta-size: 13147648' -H 'x-image-meta-is_public: False' -H 
'X-Auth-Token: tokentoken' -H 'Content-Type: application/octet-stream' -H 
'x-image-meta-disk_format: qcow2' -H 'x-image-meta-name: Test' -d '' http://example.com:9292/v1/images

  Relevant glance logs:
  http://paste.openstack.org/show/61317/

  The bug is that no errors are reported on the failure in glance-api or
  glance-registry. This should at least raise a warning and return a
  non-200 status back to the client.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1269634/+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 1272464] Re: changing image owner is broken in swift multi tenant mode (v1)

[Abhishek Kekane]

This bug is reported for v1 api which is deprecated and will be removed
during rocky cycle, so marking this as invalid.

** Changed in: glance
   Status: In Progress => Invalid

** Changed in: glance
   Status: Invalid => Won't Fix

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

Title:
  changing image owner is broken in swift multi tenant mode (v1)

Status in Glance:
  Won't Fix

Bug description:
  Hi,

  In v1 and when using swift (multi tenant) as backend, 
  If we change the image owner, the new owner is not granted read acl on the 
swift container holding the image.

  as a result, the new owner is able to list the image but unable to use
  it.

  example here : http://paste.openstack.org/show/61841/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1272464/+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 1273171] Re: On Glance API, "changes-since" parameter filters out images which have been update at the same date as the specified timestamp

[Abhishek Kekane]

This bug is reported for v1 api which is deprecated and will be removed
during rocky cycle, so marking this as won't fix.

** Changed in: glance
   Status: In Progress => Won't Fix

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

Title:
  On Glance API, "changes-since" parameter filters out images which have
  been update at the same date as the specified timestamp

Status in Glance:
  Won't Fix

Bug description:
  environment:
Openstack deployed by devstack.

  
  Steps to reproduce:
1. Check "image" tables.

2. Request glance API whith "changes-since" parameter, whose
  value is the same as "update_at" of an image in "images" table.

3.filters out images whose "update_at" is the same of "changes-since"
  parameter.

  Expected result:
in step3, images are'nt filtered out.

  Remark:
this is simillar to https://review.openstack.org/#/c/60157/.

  example)
-execution:
  $mysql -u root glance
  $select * from images;

  +--+---+-+
  | id   |***| updated_at  |
  +--+---+-+
  | 1d88c716-ecd8-4ca1-9fc5-3bda1cf5affc |***| 2014-01-24 17:18:23 |
  | b7bc3608-f19e-4eb1-a178-f3c59af2ba22 |***| 2014-01-24 17:18:24 |
  | ca15b4d7-6c8b-4d7e-a4bd-a6186373e4d9 |***| 2014-01-24 17:18:25 |
  +--+---+-+

  $curl *** 
http://192.168.0.10:9292/v1/images/detail?changes-since=2014-01-24T17:18:25
  HTTP/1.1 200 OK
  ***
  {"images": []}

-Expected result:
image whose id is "ca15b4d7-6c8b-4d7e-a4bd-a6186373e4d9" is filter out.
this image should'nt be filtered out from the viewpoint of its name
 which includes "since".

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1273171/+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 1264639] Re: Glance v1 unit test code can do with some refactoring

[Abhishek Kekane]

V1 tests has been removed in rocky cycle,  no need to act on this
anymore.

** Changed in: glance
   Status: In Progress => Invalid

** Changed in: glance
   Status: Invalid => Won't Fix

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

Title:
  Glance v1 unit test code can do with some refactoring

Status in Glance:
  Won't Fix

Bug description:
  The Glance v1 unit test code (tests/unit/v1/test_api.py) can do with
  some refactoring - there are lots of repeated patterns throughout the
  code. Refactoring it can help with understanding and maintaining the
  code and also make adding future tests simpler.

  This bug is an action item to track the review comment for
  https://review.openstack.org/#/c/64079/4 raised by Steve Kowalik.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1264639/+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 1389110] Re: 'glance member-list' CLI lists information with wrong tenant-id

[Abhishek Kekane]

Glance does not validates the tenant-id so for invalid tenant-id it
returns the available tenants.

** Changed in: glance
   Status: New => Invalid

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

Title:
  'glance member-list' CLI lists information with wrong tenant-id

Status in Glance:
  Invalid

Bug description:
  "glance member-list" CLI with wrong tenant-id returns "200 OK"  and
  generate information while it is expected 404 Not Found.

  Below are the command execution logs-

  $ keystone tenant-list
  +--+--+-+
  |id|   name   | enabled |
  +--+--+-+
  | a1c37cc595024369aa2124b50adaa0b8 |  admin   |   True  |
  | 31dd5bdca08e4ce0b208ef618142875b | cephtest |   True  |
  | 944ffc3c82f088eb7f61bc77bef0 |   demo   |   True  |
  | ed34d901e2314ab6a93e01ebad44e445 | service  |   True  |
  +--+--+-+

  
  $ glance --debug member-list  --tenant-id 31dd5bd
  curl -i -X GET -H 'User-Agent: python-glanceclient' -H 'Content-Type: 
application/octet-stream' -H 'Accept-Encoding: gzip, deflate, compress' -H 
'Accept: */*' -H 'X-Auth-Token: {SHA1}bf02401aa8b7a79b29e5db2c015bee9d111ea600' 
http://controller:9292/v1/shared-images/31dd5bd

  HTTP/1.1 200 OK
  date: Tue, 04 Nov 2014 07:44:49 GMT
  content-length: 21
  content-type: application/json; charset=UTF-8
  x-openstack-request-id: req-398f3434-d5d1-4d22-a126-c4edcd6b7cfd

  {"shared_images": []}

  +--+---+---+
  | Image ID | Member ID | Can Share |
  +--+---+---+
  +--+---+---+

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1389110/+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 1388912] Re: Snapshot with image size 0 bits

[Abhishek Kekane]

Not encountered by anyone else since reported.

** Changed in: glance
   Status: New => Invalid

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

Title:
  Snapshot with image size 0 bits

Status in Glance:
  Invalid

Bug description:
  Hello,

  We have a problem when we generate a snapshot.

  Informations:
  - nova --version 2.17.0
  - cinder --version 1.0.8
  - glance --version 0.12.0

  Our problem:

  To create a snapshot, we use the CLI by nova image-create.

  To verify the snapshot, we go in Images tab et click on the image of
  the snapshot, but in the specification we have a size of 0 bits :

  Spécifications

  Taille 
  0 octet 
  Format du Conteneur 
  AUCUN 
  Format du Disque 
  AUCUN 

  With the cli, we see the lvm snapshot but we can't found any image of the 
snapshot (qcow i presume).
  With glance image-list or cinder list, we can't see the snapshot to.

  To backup our VM, whe use cinder in CLI with cinder upload-image,
  that's okay, it's worked.

  I activate debug/verbose for nova/cinder/glance but we haven't any
  explicit error in the log files.

  When we create a snapshot, i took some logs of nova, cinder and
  glance.

  Do you have an idea of the problem?

  Logs for Nova:
  2014-10-31 16:40:52.533 3777 DEBUG keystoneclient.middleware.auth_token [-] 
Authenticating user token __call__ 
/usr/lib/python2.7/dist-packages/keystoneclient/middleware/auth_token.py:666
  2014-10-31 16:40:52.534 3777 DEBUG keystoneclient.middleware.auth_token [-] 
Removing headers from request environment: 
X-Identity-Status,X-Domain-Id,X-Domain-Name,X-Project-Id,X-Project-Name,X-Project-Domain-Id,X-Project-Domain-Name,X-User-Id,X-User-Name,X-User-Domain-Id,X-User-Domain-Name,X-Roles,X-Service-Catalog,X-User,X-Tenant-Id,X-Tenant-Name,X-Tenant,X-Role
 _remove_auth_headers 
/usr/lib/python2.7/dist-packages/keystoneclient/middleware/auth_token.py:725
  2014-10-31 16:40:52.534 3777 DEBUG keystoneclient.middleware.auth_token [-] 
Returning cached token _cache_get 
/usr/lib/python2.7/dist-packages/keystoneclient/middleware/auth_token.py:1124
  2014-10-31 16:40:52.535 3777 DEBUG keystoneclient.middleware.auth_token [-] 
Storing token in cache _cache_put 
/usr/lib/python2.7/dist-packages/keystoneclient/middleware/auth_token.py:1234
  2014-10-31 16:40:52.535 3777 DEBUG keystoneclient.middleware.auth_token [-] 
Received request from user: 1e7cb96667d049ccbcbd4aac84ca71b2 with project_id : 
003048198aa94a0bb07b00802931d332 and roles: _member_  _build_user_headers 
/usr/lib/python2.7/dist-packages/keystoneclient/middleware/auth_token.py:1021
  2014-10-31 16:40:52.537 3777 DEBUG routes.middleware [-] Matched GET 
/003048198aa94a0bb07b00802931d332/servers/5749c7ac-7567-4b4d-a3ec-9bf248e4c450 
__call__ /usr/lib/python2.7/dist-packages/routes/middleware.py:100
  2014-10-31 16:40:52.537 3777 DEBUG routes.middleware [-] Route path: 
'/{project_id}/servers/:(id)', defaults: {'action': u'show', 'controller': 
} __call__ 
/usr/lib/python2.7/dist-packages/routes/middleware.py:102
  2014-10-31 16:40:52.537 3777 DEBUG routes.middleware [-] Match dict: 
{'action': u'show', 'controller': , 'project_id': u'003048198aa94a0bb07b00802931d332', 'id': 
u'5749c7ac-7567-4b4d-a3ec-9bf248e4c450'} __call__ 
/usr/lib/python2.7/dist-packages/routes/middleware.py:103
  2014-10-31 16:40:52.538 3777 DEBUG nova.api.openstack.wsgi 
[req-06cc551d-72f8-4fa7-b65d-022fa03b656e 1e7cb96667d049ccbcbd4aac84ca71b2 
003048198aa94a0bb07b00802931d332] Calling method '>' 
(Content-type='None', Accept='application/json') _process_stack 
/usr/lib/python2.7/dist-packages/nova/api/openstack/wsgi.py:945
  2014-10-31 16:40:52.595 3777 INFO nova.osapi_compute.wsgi.server 
[req-06cc551d-72f8-4fa7-b65d-022fa03b656e 1e7cb96667d049ccbcbd4aac84ca71b2 
003048198aa94a0bb07b00802931d332] 62.210.200.76 "GET 
/v2/003048198aa94a0bb07b00802931d332/servers/5749c7ac-7567-4b4d-a3ec-9bf248e4c450
 HTTP/1.1" status: 200 len: 1920 time: 0.0621860
  2014-10-31 16:40:57.563 3777 DEBUG keystoneclient.middleware.auth_token [-] 
Authenticating user token __call__ 
/usr/lib/python2.7/dist-packages/keystoneclient/middleware/auth_token.py:666
  2014-10-31 16:40:57.564 3777 DEBUG keystoneclient.middleware.auth_token [-] 
Removing headers from request environment: 
X-Identity-Status,X-Domain-Id,X-Domain-Name,X-Project-Id,X-Project-Name,X-Project-Domain-Id,X-Project-Domain-Name,X-User-Id,X-User-Name,X-User-Domain-Id,X-User-Domain-Name,X-Roles,X-Service-Catalog,X-User,X-Tenant-Id,X-Tenant-Name,X-Tenant,X-Role
 _remove_auth_headers 
/usr/lib/python2.7/dist-packages/keystoneclient/middleware/auth_token.py:725
  2014-10-31 16:40:57.564 3777 DEBUG keystoneclient.middleware.auth_token [-] 
Returning cached token _cache_get 
/usr/lib/python2.7/dist-packages/keystoneclient/middleware/auth_token.py:1124
  2014-10-31 16:40:57.565 3777 DEBUG keystoneclient.middleware.auth_token [-]