[Yahoo-eng-team] [Bug 1608980] Re: Remove MANIFEST.in as it is not explicitly needed by PBR

[Nikhil Komawar]

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

** Changed in: glance
   Importance: Undecided => Low

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

** Changed in: glance
Milestone: None => pike-1

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

Title:
  Remove MANIFEST.in as it is not explicitly needed by PBR

Status in anvil:
  Invalid
Status in craton:
  Fix Released
Status in DragonFlow:
  Fix Released
Status in ec2-api:
  Fix Released
Status in gce-api:
  Fix Released
Status in Glance:
  In Progress
Status in Karbor:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in Kosmos:
  Fix Released
Status in Magnum:
  Fix Released
Status in masakari:
  Fix Released
Status in networking-midonet:
  New
Status in networking-odl:
  New
Status in neutron:
  Fix Released
Status in Neutron LBaaS Dashboard:
  Confirmed
Status in octavia:
  Fix Released
Status in os-vif:
  Fix Released
Status in python-searchlightclient:
  In Progress
Status in OpenStack Search (Searchlight):
  Fix Released
Status in Solum:
  Fix Released
Status in Swift Authentication:
  Fix Released
Status in OpenStack Object Storage (swift):
  In Progress
Status in Tricircle:
  Fix Released
Status in OpenStack DBaaS (Trove):
  Fix Released
Status in watcher:
  Fix Released
Status in Zun:
  Fix Released

Bug description:
  PBR do not explicitly require MANIFEST.in, so it can be removed.

  
  Snippet from: http://docs.openstack.org/infra/manual/developers.html

  Manifest

  Just like AUTHORS and ChangeLog, why keep a list of files you wish to
  include when you can find many of these in git. MANIFEST.in generation
  ensures almost all files stored in git, with the exception of
  .gitignore, .gitreview and .pyc files, are automatically included in
  your distribution. In addition, the generated AUTHORS and ChangeLog
  files are also included. In many cases, this removes the need for an
  explicit ‘MANIFEST.in’ file

To manage notifications about this bug go to:
https://bugs.launchpad.net/anvil/+bug/1608980/+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 1616938] Re: XenAPI: failed to create image from volume backed instance with glance v2

[Nikhil Komawar]

I think the xen driver needs a code to check the container and disk
formats supported at that glance installation.

A check using the schema call will do the trick

https://github.com/openstack/glance/blob/7c7dd626896d732d75c6b802a33b9462aee885fd/glance/api/v2/images.py#L980

https://github.com/openstack/glance/blob/7c7dd626896d732d75c6b802a33b9462aee885fd/glance/api/v2/images.py#L837

https://github.com/openstack/glance/blob/7c7dd626896d732d75c6b802a33b9462aee885fd/glance/api/v2/images.py#L887-L895

** Changed in: glance
   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/1616938

Title:
  XenAPI: failed to create image from volume backed instance with glance
  v2

Status in Glance:
  Invalid
Status in OpenStack Compute (nova):
  Incomplete

Bug description:
  XenServer with dirver XenAPI, it always fails to create image from
  volume.

  Tempest test:
  
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPatternV2.test_create_ebs_image_and_check_boot

  2016-08-24 08:13:24.636 27347 DEBUG nova.compute.api 
[req-fd7afac4-a2ee-41cb-b785-02766806db26 
tempest-TestVolumeBootPatternV2-1645487335 
tempest-TestVolumeBootPatternV2-1645487335] [instance: 
5d5a8b10-655c-457e-8ad9-edbfb6ecd278] Creating snapshot from volume 
9953359c-327a-41bf-abec-f3c3da416390. snapshot_volume_backed 
/opt/stack/new/nova/nova/compute/api.py:2445^M
  2016-08-24 08:13:25.964 27347 INFO os_vif 
[req-fd7afac4-a2ee-41cb-b785-02766806db26 
tempest-TestVolumeBootPatternV2-1645487335 
tempest-TestVolumeBootPatternV2-1645487335] Loaded VIF plugin class '' with name 'ovs'^M
  2016-08-24 08:13:25.965 27347 INFO os_vif 
[req-fd7afac4-a2ee-41cb-b785-02766806db26 
tempest-TestVolumeBootPatternV2-1645487335 
tempest-TestVolumeBootPatternV2-1645487335] Loaded VIF plugin class '' with name 
'linux_bridge'^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions 
[req-fd7afac4-a2ee-41cb-b785-02766806db26 
tempest-TestVolumeBootPatternV2-1645487335 
tempest-TestVolumeBootPatternV2-1645487335] Unexpected exception in API method^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions Traceback 
(most recent call last):^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/api/openstack/extensions.py", line 338, in wrapped^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/api/openstack/common.py", line 372, in inner^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions return 
f(*args, **kwargs)^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/api/validation/__init__.py", line 73, in wrapper^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/api/validation/__init__.py", line 73, in wrapper^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions return 
func(*args, **kwargs)^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/api/openstack/compute/servers.py", line 1072, in 
_action_create_image^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions 
metadata)^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/compute/api.py", line 146, in inner^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions return 
f(self, context, instance, *args, **kw)^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/compute/api.py", line 2463, in 
snapshot_volume_backed^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions return 
self.image_api.create(context, image_meta)^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/image/api.py", line 106, in create^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions return 
session.create(context, image_info, data=data)^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/image/glance.py", line 626, in create^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions data, 
force_activate)^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 
"/opt/stack/new/nova/nova/image/glance.py", line 658, in _create_v2^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions 
context, 2, 'create', **sent_service_image_meta)^M
  2016-08-24 08:13:26.049 27347 ERROR nova.api.openstack.extensions   File 

[Yahoo-eng-team] [Bug 1624973] Re: Not possible to allow non "admin" user to change owner on image

[Nikhil Komawar]

I think the use case is reasonable. I would prefer a spec-lite for this
change, it's a feature more than a bug.


You can file one here:
https://github.com/openstack/glance-specs/blob/master/specs/ocata/approved/glance/lite-specs.rst

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

** Changed in: glance
   Importance: Undecided => Wishlist

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

Title:
  Not possible to allow non "admin" user to change owner on image

Status in Glance:
  Opinion

Bug description:
  I want to allow a special role to update the owner attribute of an
  image.

  It looks as if this action is hard coded to only allow context
  "is_admin" to to this operation.

  This should be configurable via policy

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1624973/+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 1226250] Re: periodic checking is needed to stabilize DB state

[Nikhil Komawar]

I have moved it to Opinion. As per the discussion on the spec
https://review.openstack.org/#/c/242682/ , we've come to an agreement
that such clean up doesn't belong in Glance.

You are welcome to open a new lite-spec with link to this bug to get
wider input.

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

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

Title:
  periodic checking is needed to stabilize DB state

Status in Glance:
  Opinion

Bug description:
  We found that glance's DB state may remain inconsistent/confusing
  without proper periodic checking, in case faults occur.

  Below are two examples:

  1. When "glance image-create" is issued with "copy-from=http://...;
  option, the image state transits from "queued" to "saving," before the
  image is copied from http backend to the glance host. If the exeuction
  is interrupted at this time, then the image will stay in "saving"
  state.

  While in such case, glance does return an error code to the external
  user who issued the command, we believe that keeping the image in the
  "saving" state may confuse other external users. It would be better to
  differentiate a failed image uploading with the case where an image is
  being uploaded. A periodic check may help in this case. Alternatively,
  one can trigger the state transition at the time when the image upload
  is believed to have failed.

  2. If the execution related to a "glance image-delete" request is
  interrupted, then it is possible that the "status" in DB table
  "glance.images" has transited to "deleted" but the "deleted" field
  remains to be False. Since this case clearly indicates the occurance
  of an error, we think it may be better to periodically check the
  existence of such inconsistent states, transit "deleted" to True
  accordingly, and mark the occurance of error probably in a dedicated
  error DB table.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1226250/+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 1620363] [NEW] report nginx or non-eventlet based strategies for deploying glance

[Nikhil Komawar]

Public bug reported:

Recently, more than a few people have asked about different ways a
glance service can be deployed:

  * eventlet based
  * nginx based
  * other ways (like say using repose)

It would be good to document this in our developer docs or specs and
create a FAQ page in our launchpad project page for people to refer and
then discuss further.

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: doc documentation low-hanging-fruit

** Tags added: documentation

** Tags added: doc low-hanging-fruit

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

Title:
  report nginx or non-eventlet based strategies for deploying glance

Status in Glance:
  New

Bug description:
  Recently, more than a few people have asked about different ways a
  glance service can be deployed:

* eventlet based
* nginx based
* other ways (like say using repose)

  It would be good to document this in our developer docs or specs and
  create a FAQ page in our launchpad project page for people to refer
  and then discuss further.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1620363/+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 1599123] Re: Glance API doesn't work in IPv6 only environment

[Nikhil Komawar]

Have you tried this trick
https://github.com/openstack/glance/blob/11cfe49b8f88f68d83028b5920891bb16792da72/glance/cmd/__init__.py#L23-L49
?

I think that'd work for you and we may have to update the documentation
using this bug as an example to update the docs!

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

** Changed in: glance
   Importance: Undecided => Medium

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

Title:
  Glance API doesn't work in IPv6 only environment

Status in Glance:
  Opinion

Bug description:
  When using IPv6 only deployment, including communication between
  glance-api and glance-registry, glance client itself can make glance
  image-list without problems, however, nova image-list fails with error
  500. Same applies is glance client is called by using v1 API:

  root@ubuntu1604-openstack:~# glance --os-image-api-version 2 image-list
  +--+-+
  | ID   | Name|
  +--+-+
  | f32fd367-a451-4c09-b4fa-b2a60195aa38 | cirros  |
  | ad83b2f0-b99e-4340-b191-27f61de9955d | testimg |
  +--+-+
  root@ubuntu1604-openstack:~# glance --os-image-api-version 1 image-list
  500 Internal Server Error: The server has either erred or is incapable of 
performing the requested operation. (HTTP 500)
  root@ubuntu1604-openstack:~# nova image-list
  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-279e9161-ec28-40af-a312-b2a5de829aef)

  Snippet from glance-registry.conf:
  bind_host = fd00:0:0:0::b00

  Snippet form glance-api.conf:
  registry_host = fd00:0:0:0::b00

  When symbolic name of the node is used in glance-api.conf, everything
  works fine.

  The log says:
  2016-07-05 13:11:24.858 3742 DEBUG eventlet.wsgi.server [-] (3742) accepted 
('fd00:0:0:0::b00', 47916, 0, 0) server 
/usr/lib/python2.7/dist-packages/eventlet/wsgi.py:867
  2016-07-05 13:11:24.861 3742 DEBUG glance.api.middleware.version_negotiation 
[-] Determining version of request: GET /v1/images/detail Accept: */* 
process_request 
/usr/local/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:46
  2016-07-05 13:11:24.862 3742 DEBUG glance.api.middleware.version_negotiation 
[-] Using url versioning process_request 
/usr/local/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:58
  2016-07-05 13:11:24.864 3742 DEBUG glance.api.middleware.version_negotiation 
[-] Matched version: v1 process_request 
/usr/local/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:70
  2016-07-05 13:11:24.865 3742 DEBUG glance.api.middleware.version_negotiation 
[-] new path /v1/images/detail process_request 
/usr/local/lib/python2.7/dist-packages/glance/api/middleware/version_negotiation.py:71
  2016-07-05 13:11:25.131 3742 DEBUG glance.common.client 
[req-7c1cf0e3-40e3-4ae2-bd3d-4f2923510386 f2875bc77df6479ea0a55ab4471c2ec0 
4ef8aba5c14c4ff99fe71d9588fcbdfc - - -] Constructed URL: 
http://fd00:0:0:0::b00:9191/images/detail?sort_key=name_dir=asc=20 
_construct_url 
/usr/local/lib/python2.7/dist-packages/glance/common/client.py:398
  2016-07-05 13:11:25.137 3742 ERROR glance.registry.client.v1.client 
[req-7c1cf0e3-40e3-4ae2-bd3d-4f2923510386 f2875bc77df6479ea0a55ab4471c2ec0 
4ef8aba5c14c4ff99fe71d9588fcbdfc - - -] Registry client request GET 
/images/detail raised ClientConnectionError

  
  From where it is obvious that wrong URL is constructed:
  http://fd00:0:0:0::b00:9191/images/...

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1599123/+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 1611154] Re: Glance v2 gives 403 instead of 409 on Conflict

[Nikhil Komawar]

@Lyle: are you using the schemas to validate your request?

I see how a 409 is more convenient.

I'm on the fence for this -- my opinion is that 403 is the right call
from glance's perspective as you are trying to update the reserved
attribute and have some knowledge of the image (using the id).

Though, at the same time for a `save` in your case makes sense to first
check for id and then for other attributes. So, we will have to discuss
this on the review itself. If you'd like to propose a review on this, it
would be quite helpful.

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

** Changed in: glance
   Importance: Undecided => Medium

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

Title:
  Glance v2 gives 403 instead of 409 on Conflict

Status in Glance:
  Opinion

Bug description:
  Background:

  I'm working on fixing some issues around the handling of Glance V2 in
  the Ruby fog-openstack gem: https://github.com/fog/fog-
  openstack/pull/170. One of these issues was the implementation of a
  `save` method that creates an object if it doesn't exist, otherwise it
  updates the object. Normally the presence of an ID causes the `update`
  method to be called, but Glance V2 allows an ID to be specified on
  `create`. To implement this `save` method, I'd like to always call
  `create`, then rescue and call `update` on a 409 Conflict. However,
  I'm seeing the following behavior.

  Bug:

  Attempt to POST a new image with an conflicting ID (ID already
  exists), but with a read-only attribute set, e.g. `self`.

  ```
  curl -v \
-H "Content-Type: application/json" \
-H "X-Auth-Token: MY_TOKEN" \
-X POST \
-d '{
  "id": "EXISTING_IMAGE_ID",
  "name": "my-image",
  "self": "/v2/foo"
}' \
https://OPENSTACK_HOSTNAME:9292/v2/images
  ```

  Expected to receive "409 Conflict" HTTP response, but was "403
  Forbidden", "Attribute 'self' is read-only.". Removing the `self` from
  the request makes things work as expected, but the lack of the 409
  response code makes it difficult to implement a "create or update"
  method as described above.

  Thanks!

  - Lyle

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1611154/+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 1618260] Re: Image signature base64 don't wrap lines

[Nikhil Komawar]

I doubt if we need doc change for this as the commit itself made the doc
change.

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

** Changed in: glance
   Importance: Undecided => Wishlist

** Changed in: glance
   Importance: Wishlist => Low

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

Title:
  Image signature base64 don't wrap lines

Status in Glance:
  Opinion

Bug description:
  https://review.openstack.org/360411
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/glance" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 5663196c9c30f13a61a44ac7bfd625379d3165f4
  Author: Darren White 
  Date:   Tue Aug 23 14:56:31 2016 +0100

  Image signature base64 don't wrap lines
  
  In the image signature documentation, base64 should not use line
  wrapping (defaults to 76). Disable using -w 0. With line wrapping
  enabled Nova will fail to boot the image.
  
  Added a note to inform users to use -w 0 with Glance v1 but is
  optional for v2.
  
  DocImpact
  
  Closes-Bug: 1617258
  Change-Id: I3585c5cc90e6ea738ff7ecb5a5574cbb0e737511

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1618260/+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 1612742] [NEW] incorrect references of s3 in migration scripts

[Nikhil Komawar]

Public bug reported:

We have removed s3 references in patch
https://review.openstack.org/#/c/348507/

However there are a few incorrect references of s3 in the below
mentioned migration scripts.

We have a project policy to not modify the migration scripts unless a
significant impact exists.
http://docs.openstack.org/developer/glance/contributing/minor-code-
changes.html#database-migration-scripts

So, this bug has been opened to gather feedback / opinions on the need
for this change.

https://github.com/openstack/glance/blob/d0f4316752d313bffeafd2be0283201813e1e9a2/glance/db/sqlalchemy/migrate_repo/versions/015_quote_swift_credentials.py#L157

https://github.com/openstack/glance/blob/d0f4316752d313bffeafd2be0283201813e1e9a2/glance/db/sqlalchemy/migrate_repo/versions/017_quote_encrypted_swift_credentials.py#L219

** Affects: glance
 Importance: Low
 Status: New

** Changed in: glance
   Importance: Undecided => Low

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

Title:
  incorrect references of s3 in migration scripts

Status in Glance:
  New

Bug description:
  We have removed s3 references in patch
  https://review.openstack.org/#/c/348507/

  However there are a few incorrect references of s3 in the below
  mentioned migration scripts.

  We have a project policy to not modify the migration scripts unless a
  significant impact exists.
  http://docs.openstack.org/developer/glance/contributing/minor-code-
  changes.html#database-migration-scripts

  So, this bug has been opened to gather feedback / opinions on the need
  for this change.

  
https://github.com/openstack/glance/blob/d0f4316752d313bffeafd2be0283201813e1e9a2/glance/db/sqlalchemy/migrate_repo/versions/015_quote_swift_credentials.py#L157

  
https://github.com/openstack/glance/blob/d0f4316752d313bffeafd2be0283201813e1e9a2/glance/db/sqlalchemy/migrate_repo/versions/017_quote_encrypted_swift_credentials.py#L219

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1612742/+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 1609571] Re: version negotiation api middleware is NOT up to date to include v2.3 as CURRENT version

[Nikhil Komawar]

Backports proposed here:

https://review.openstack.org/#/q/I4018af408fa45f3ac0ad6e9c8229428a9f87089f,n,z

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

** Also affects: glance/mitaka
   Importance: Critical
 Assignee: Nikhil Komawar (nikhil-komawar)
   Status: Fix Released

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

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

** Changed in: glance/newton
   Status: New => Fix Released

** Changed in: glance/liberty
   Status: New => In Progress

** Changed in: glance/liberty
   Importance: Undecided => Critical

** Changed in: glance/newton
   Importance: Undecided => Critical

** Changed in: glance/liberty
 Assignee: (unassigned) => Nikhil Komawar (nikhil-komawar)

** Changed in: glance/newton
 Assignee: (unassigned) => Nikhil Komawar (nikhil-komawar)

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

Title:
  version negotiation api middleware is NOT up to date to include v2.3
  as CURRENT version

Status in Glance:
  In Progress
Status in Glance liberty series:
  In Progress
Status in Glance mitaka series:
  In Progress
Status in Glance newton series:
  Fix Released

Bug description:
  Glance API is at v2.3 listed to be CURRENT version but the version
  negotiation middleware lists only v2, v2.0, v2.1, v2.2.


  version negotiation middleware and related tests should include v2.3

  
https://github.com/openstack/glance/blob/9ef5ed125cfaedfa9657510fbe2e8a2c01d692d9/glance/api/middleware/version_negotiation.py#L80-L84

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1609571/+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 1609571] [NEW] version negotiation api middleware is NOT up to date to include v2.3 as CURRENT version

[Nikhil Komawar]

Public bug reported:

Glance API is at v2.3 listed to be CURRENT version but the version
negotiation middleware lists only v2, v2.0, v2.1, v2.2.


version negotiation middleware and related tests should include v2.3

https://github.com/openstack/glance/blob/9ef5ed125cfaedfa9657510fbe2e8a2c01d692d9/glance/api/middleware/version_negotiation.py#L80-L84

** Affects: glance
 Importance: Critical
 Assignee: Nikhil Komawar (nikhil-komawar)
 Status: Triaged

** Changed in: glance
   Importance: Undecided => Medium

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

** Changed in: glance
   Importance: Medium => Critical

** Changed in: glance
 Assignee: (unassigned) => Nikhil Komawar (nikhil-komawar)

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

Title:
  version negotiation api middleware is NOT up to date to include v2.3
  as CURRENT version

Status in Glance:
  Triaged

Bug description:
  Glance API is at v2.3 listed to be CURRENT version but the version
  negotiation middleware lists only v2, v2.0, v2.1, v2.2.


  version negotiation middleware and related tests should include v2.3

  
https://github.com/openstack/glance/blob/9ef5ed125cfaedfa9657510fbe2e8a2c01d692d9/glance/api/middleware/version_negotiation.py#L80-L84

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1609571/+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 1214176] Re: Fix copyright headers to be compliant with Foundation policies

[Nikhil Komawar]

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

** Changed in: glance
   Importance: Undecided => Low

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

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

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

Title:
  Fix copyright headers to be compliant with Foundation policies

Status in Ceilometer:
  Fix Released
Status in Cinder:
  In Progress
Status in devstack:
  Fix Released
Status in Glance:
  Triaged
Status in heat:
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in Murano:
  In Progress
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in PBR:
  In Progress
Status in python-ceilometerclient:
  Fix Released
Status in python-cinderclient:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-heatclient:
  Fix Released
Status in python-keystoneclient:
  Fix Released
Status in python-manilaclient:
  In Progress
Status in python-neutronclient:
  Fix Released
Status in python-troveclient:
  In Progress
Status in OpenStack Object Storage (swift):
  Fix Released
Status in tempest:
  Fix Released
Status in OpenStack DBaaS (Trove):
  Fix Released

Bug description:
  Correct the copyright headers to be consistent with the policies
  outlined by the OpenStack Foundation at http://www.openstack.org/brand
  /openstack-trademark-policy/

  Remove references to OpenStack LLC, replace with OpenStack Foundation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1214176/+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 1589264] [NEW] developer-api-ref for v2 shows incorrect response style for a GET on images/image_id

[Nikhil Komawar]

Public bug reported:

Matt Riedmann reported on IRC that the developer api reference for a
show call on an image http://developer.openstack.org/api-ref-
image-v2.html#showImage-v2 shows incorrect response.

Specifically, the expected outcome has a flat structure to the response
and the non-base-properties are indicated to be returned as a part of a
nested 'properties' dictionary. That's not correct as those properties
will be returned in the json response in the flat namespace like the
test indicates here
https://github.com/openstack/glance/blob/8dd23d0b9c7ca9bb521f56407f6f601db84771f9/glance/tests/functional/v2/test_images.py#L146

This is a bug specifically only to the api-ref and the work of WADL
transition makes it applicable to Glance and not documentation project.
We should fix this while the docs are being ported glance's tree.

** Affects: glance
 Importance: High
 Assignee: Brian Rosmaita (brian-rosmaita)
 Status: Triaged

** Changed in: glance
   Importance: Undecided => High

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

** Changed in: glance
 Assignee: (unassigned) => Brian Rosmaita (brian-rosmaita)

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

Title:
  developer-api-ref for v2 shows incorrect response style for a GET on
  images/image_id

Status in Glance:
  Triaged

Bug description:
  Matt Riedmann reported on IRC that the developer api reference for a
  show call on an image http://developer.openstack.org/api-ref-
  image-v2.html#showImage-v2 shows incorrect response.

  Specifically, the expected outcome has a flat structure to the
  response and the non-base-properties are indicated to be returned as a
  part of a nested 'properties' dictionary. That's not correct as those
  properties will be returned in the json response in the flat namespace
  like the test indicates here
  
https://github.com/openstack/glance/blob/8dd23d0b9c7ca9bb521f56407f6f601db84771f9/glance/tests/functional/v2/test_images.py#L146

  This is a bug specifically only to the api-ref and the work of WADL
  transition makes it applicable to Glance and not documentation
  project. We should fix this while the docs are being ported glance's
  tree.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1589264/+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 1536226] Re: Not all .po files compiled

[Nikhil Komawar]

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

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

** Changed in: glance
   Importance: Undecided => High

** Changed in: glance
 Assignee: (unassigned) => Sven Anderson (ansiwen)

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

Title:
  Not all .po files compiled

Status in Glance:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in openstack i18n:
  New

Bug description:
  python setup.py compile_catalog only compiles one .po file per
  language to a .mo file. By default  is the project
  name, that is nova.po. This means all other nova-log-*.po files are
  never compiled. The only way to get setup.py compile the other files
  is calling it several times with different domains set, like for
  instance `python setup.py --domain nova-log-info` and so on. Since
  this is not usual, it can be assumed that the usual packages don't
  contain all the .mo files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1536226/+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 1584350] [NEW] etc/glance-registry.conf sample file has redundant store section

[Nikhil Komawar]

Public bug reported:

Currently, the oslo config generator takes glance_store configs in
consideration while generating sample configs for the registry. Registry
doesn't really need these configs.

It would be better to get them removed.

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

Title:
  etc/glance-registry.conf sample file has redundant store section

Status in Glance:
  New

Bug description:
  Currently, the oslo config generator takes glance_store configs in
  consideration while generating sample configs for the registry.
  Registry doesn't really need these configs.

  It would be better to get them removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1584350/+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 1521236] Re: Missing list of stores in glance-api.conf

[nikhil komawar]

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

** Changed in: glance-store
   Status: Confirmed => 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/1521236

Title:
  Missing list of stores in glance-api.conf

Status in Glance:
  Invalid
Status in glance_store:
  Invalid
Status in glance_store liberty series:
  Confirmed

Bug description:
  We used to give some indication of which stores could be configured:

   [glance_store]
   # List of which store classes and store class locations are
   # currently known to glance at startup.
   # Deprecated group/name - [DEFAULT]/known_stores
   # Existing but disabled stores:
   #  glance.store.rbd.Store,
   #  glance.store.s3.Store,
   #  glance.store.swift.Store,
   #  glance.store.sheepdog.Store,
   #  glance.store.cinder.Store,
   #  glance.store.gridfs.Store,
   #  glance.store.vmware_datastore.Store,
   #stores = glance.store.filesystem.Store,
   # glance.store.http.Store

  
  We don't seem to have a full list of stores in etc/glance-api.conf any more:

   [glance_store]

   #
   # From glance.store
   #

   # List of stores enabled (list value)
   #stores = file,http

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1521236/+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 1502850] Re: Location add does not catch BadStoreUri

[nikhil komawar]

** Changed in: glance
   Importance: Undecided => Medium

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

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

** Changed in: glance/kilo
   Importance: Undecided => Medium

** Changed in: glance/liberty
   Importance: Undecided => Medium

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

Title:
  Location add does not catch BadStoreUri

Status in Glance:
  In Progress
Status in Glance kilo series:
  New
Status in Glance liberty series:
  New

Bug description:
  Overview:
  If you create an image and then use location-add to add a bad uri, the server 
returns a 500. As the BadStoreUri is not caught.

  How to produce:
  glance image-create

  glance location-add de6d8022-6954-4039-b53a-042e2fc909de --url file://
  500 Internal Server Error: The server has either erred or is incapable of 
performing the requested operation. (HTTP 500)

  2015-10-05 10:31:54.015 TRACE glance.common.wsgi raise 
exceptions.BadStoreUri(uri=uri)
  2015-10-05 10:31:54.015 TRACE glance.common.wsgi BadStoreUri: The Store URI 
was malformed: http://

  Output:
  500

  Expected:
  400

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1502850/+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 1297451] Re: Image uploads to the filesystem driver are not fully atomic

[nikhil komawar]

** Project changed: glance => glance-store

** Changed in: glance-store
   Importance: Undecided => Wishlist

** Tags added: 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/1297451

Title:
  Image uploads to the filesystem driver are not fully atomic

Status in glance_store:
  In Progress

Bug description:
  When uploading to the filesystem store, the image is uploaded,
  checksummed, and added to the database, with appropriate rollback
  operations in place in case of failures.  This is all good, but there
  are various corner-cases where partially-uploaded files can be left
  lying around in the filesystem_store_datadir.

  Mostly this kind of thing interferes with operational processes we
  have that are external to Glance and not Glance itself.  e.g., we have
  a monitoring process to reconcile the list/checksums of glance images
  against what's on-disk, and this occasionally goes funny on us.
  Additionally, we have a side-band backup/replication process that ends
  up occasionally transferring partial files for no reason.

  Using a temporary upload space and moving the file into place on the
  filesystem store would cause a lot of our co-processes to work more
  cleanly, as well as reducing the risk of the _delete_partial job
  deleting the wrong thing should it go sideways.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance-store/+bug/1297451/+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 1511061] Re: Images in inconsistent state when calls to registry fail during image deletion

[nikhil komawar]

1. I agree, the image deletion operation should be atomic.

2. Image data left behind means there is a potential risk of filling up
storage quota and resulting into a DoS; be mindful that it's a denial of
service but NOT a exploit as it is dependent on the operators' failure
scenarios of g-api <-> reg communication.

3. The original description has information related to failure scenarios
for only v1. So, a check is needed for the v2 as applicable.

** Description changed:

  [0] shows a sample image that was left in an inconsistent state when a
  call to registry failed during image deletion.
  
- Glance API makes two registry calls when deleting an image.
+ Glance v1 API makes two registry calls when deleting an image.
  The first call [1] is made to to set the status of an image to 
deleted/pending_delete.
  And, the other [2], to delete the rest of the metadata, which sets 
'deleted_at' and 'deleted' fields in the db.
  
  If the first call fails, the image deletion request fails and the image is 
left intact in it's previous status.
  However, if the first call succeeds and the second one fails, the image is 
left in an inconsistent status where it's status is set to 
pending_delete/deleted but it's 'deleted_at' and 'deleted' fields are not set.
  
  If delayed delete is turned on, these images are never collected by the 
scrubber as they won't appear as deleted images because their deleted field is 
not set. So, these images will continue to occupy storage in the backend.
  Also, further attempts at deleting these images will fail with a 404 because 
the status is already set to pending_delete/deleted.
  
  [0] http://paste.openstack.org/show/477577/
  [1]: 
https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L1115-L1116
  [2]: 
https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L1132

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

** Changed in: glance
   Importance: Undecided => Critical

** Changed in: glance
Milestone: None => mitaka-1

** Changed in: glance
 Assignee: (unassigned) => Hemanth Makkapati (hemanth-makkapati)

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

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

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

** Information type changed from Public to Public Security

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

Title:
  Images in inconsistent state when calls to registry fail during image
  deletion

Status in Glance:
  Triaged
Status in Glance juno series:
  New
Status in Glance kilo series:
  New
Status in Glance liberty series:
  New

Bug description:
  [0] shows a sample image that was left in an inconsistent state when a
  call to registry failed during image deletion.

  Glance v1 API makes two registry calls when deleting an image.
  The first call [1] is made to to set the status of an image to 
deleted/pending_delete.
  And, the other [2], to delete the rest of the metadata, which sets 
'deleted_at' and 'deleted' fields in the db.

  If the first call fails, the image deletion request fails and the image is 
left intact in it's previous status.
  However, if the first call succeeds and the second one fails, the image is 
left in an inconsistent status where it's status is set to 
pending_delete/deleted but it's 'deleted_at' and 'deleted' fields are not set.

  If delayed delete is turned on, these images are never collected by the 
scrubber as they won't appear as deleted images because their deleted field is 
not set. So, these images will continue to occupy storage in the backend.
  Also, further attempts at deleting these images will fail with a 404 because 
the status is already set to pending_delete/deleted.

  [0] http://paste.openstack.org/show/477577/
  [1]: 
https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L1115-L1116
  [2]: 
https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L1132

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1511061/+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 1505356] Re: Can't upload images in Python 3.4

[nikhil komawar]

You can close this bug as it's not related to py34 (99% sure).

The invalid literal and the decoding errors usually happen during
hickups in the connection while trying to upload data.

Here's the conversation I had with Hemanth who sees them a lot in his
cloud.

---

10:44:48 nikhil
rosmaita:  hemanthm: stevemar_ pointed out the error we observe in the upload 
process -- ValueError: invalid literal for int() with base 16: '' . 
http://logs.openstack.org/33/188033/7/check/gate-heat-dsvm-functional-orig-mysql/9eaf0e2/logs/screen-g-api.txt.gz?level=ERROR
 . I remember it to be an issue with corruption of local data. Can any of you 
confirm? (The error happens at the wsgi level that's being used by swift store.)

10:45:47 hemanthm
nikhil: from what I've seen it's dom0 timing out

10:46:13 hemanthm
not saying there can't be other reaons for it

10:46:19 nikhil
hemanthm: in this case, it's doing a straight upload from data local node

10:46:40 nikhil
hemanthm: so, guess it's the local node getting intermittent hickups?

10:46:59 hemanthm
nikhil: possible

10:47:33 hemanthm
essentially, from a glance perspective the upload hasn't finished yet and it 
tries to read data from the input  stream

10:48:17 hemanthm
and when it can't read further data, it throws that and barfs

---

The error is being raised when eventlet.wsgi ((under glance_store's
swift store drivers' (py-swiftclient's) import modules)) tried to decode
the stream being sent and find inconsistency in the data stream.

I looked at some of the links shared on IRC and could not find evidence
of this being related to py34. Though, if this happens more often and
people are not able to get their patches in, I am definitely willing to
take a much more closer look.


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

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

Title:
  Can't upload images in Python 3.4

Status in Glance:
  Opinion
Status in python-openstackclient:
  New

Bug description:
  Trying to upload images via the OSC fails with: 'ascii' codec can't
  decode byte 0xea in position 0: ordinal not in range(128)

  2015-10-09 16:37:17.960 | ++ openstack --os-cloud=devstack-admin image create 
cirros-0.3.4-x86_64-uec-kernel --public --container-format aki --disk-format aki
  2015-10-09 16:37:17.960 | ++ grep ' id '
  2015-10-09 16:37:17.960 | ++ get_field 2
  2015-10-09 16:37:17.961 | ++ local data field
  2015-10-09 16:37:17.961 | ++ read data
  2015-10-09 16:37:20.712 | 'ascii' codec can't decode byte 0xea in position 0: 
ordinal not in range(128)
  2015-10-09 16:37:20.848 | + kernel_id=
  2015-10-09 16:37:20.848 | + '[' -n 
/opt/stack/new/devstack/files/images/cirros-0.3.4-x86_64-uec/cirros-0.3.4-x86_64-initrd
 ']'
  2015-10-09 16:37:20.849 | ++ openstack --os-cloud=devstack-admin image create 
cirros-0.3.4-x86_64-uec-ramdisk --public --container-format ari --disk-format 
ari
  2015-10-09 16:37:20.850 | ++ grep ' id '
  2015-10-09 16:37:20.850 | ++ get_field 2
  2015-10-09 16:37:20.851 | ++ local data field
  2015-10-09 16:37:20.851 | ++ read data
  2015-10-09 16:37:22.459 | 'ascii' codec can't decode byte 0x8b in position 1: 
ordinal not in range(128)
  2015-10-09 16:37:22.555 | + ramdisk_id=
  2015-10-09 16:37:22.555 | + openstack --os-cloud=devstack-admin image create 
cirros-0.3.4-x86_64-uec --public --container-format ami --disk-format ami
  2015-10-09 16:37:24.055 | 'ascii' codec can't decode byte 0xcc in position 
1032: ordinal not in range(128)

  
  
http://logs.openstack.org/33/188033/7/check/gate-heat-dsvm-functional-orig-mysql/9eaf0e2/logs/devstacklog.txt.gz#_2015-10-09_16_37_17_960
 > FWIW, the gate job installs the python 3 version of all the clients when 
building devstack.

  Also, noticed some failures in glance trying to upload an image:
  http://logs.openstack.org/33/188033/7/check/gate-heat-dsvm-functional-
  orig-mysql/9eaf0e2/logs/screen-g-api.txt.gz?level=ERROR

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1505356/+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] Re: error message not clear when image-delete is called on deactivated image

[nikhil komawar]

I think we can backport it to Kilo and don;t see any reason why not.

THoughts?

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

** Tags added: liberty-rc-potential

-- 
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-delete is called on deactivated
  image

Status in Glance:
  Triaged
Status in Glance kilo series:
  Triaged

Bug description:
  Glance should allow to delete de-activated images

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

  Actual message:
  glance image-delete 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 output:
  Deactivated image should be deleted successfully.

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 1505218] Re: Image schema doesn't contain 'deactivated' status

[nikhil komawar]

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

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

** No longer affects: glance/liberty

** Tags added: liberty-rc-potential

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

Title:
  Image schema doesn't contain 'deactivated' status

Status in Glance:
  Triaged
Status in Glance kilo series:
  New

Bug description:
  Currently glance image schema doesn't contain 'deactivated' in the
  list of statuses, which leads to the fact that client cannot validate
  it .

  1. mfedosin@wdev:~$ glance image-list
  +--+-+
  | ID   | Name|
  +--+-+
  | 5cd380ce-a570-4270-b4d1-e328e6f49cb6 | cirros-0.3.4-x86_64-uec |
  | 9f430c9d-9649-4bc3-9ec9-1013e9c9da13 | cirros-0.3.4-x86_64-uec-kernel  |
  | e36a70f7-db13-4c3a-91a6-1308b74eebde | cirros-0.3.4-x86_64-uec-ramdisk |
  +--+-+

  2. mfedosin@wdev:~$ curl -H "X-Auth-Token:
  2c2e3bc5f0d541418a98deeabb27ac5e" -X POST
  
http://127.0.0.1:9292/v2/images/5cd380ce-a570-4270-b4d1-e328e6f49cb6/actions/deactivate

  3. mfedosin@wdev:~$ glance image-show
  5cd380ce-a570-4270-b4d1-e328e6f49cb6

  Expected result:
  There will be output with the image info

  Actual result:
  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'

  Related to bug: https://bugs.launchpad.net/glance/+bug/1505134

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1505218/+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 1476770] Re: _translate_from_glance fails with "AttributeError: id" in grenade

[nikhil komawar]

** Changed in: python-glanceclient
   Status: Fix Released => 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/1476770

Title:
  _translate_from_glance fails with "AttributeError: id" in grenade

Status in Glance:
  Invalid
Status in OpenStack-Gate:
  Fix Committed
Status in oslo.vmware:
  Fix Released
Status in python-glanceclient:
  New

Bug description:
  http://logs.openstack.org/28/204128/2/check/gate-grenade-
  dsvm/80607dc/logs/old/screen-n-api.txt.gz?level=TRACE

  2015-07-21 17:05:37.447 ERROR nova.api.openstack 
[req-9854210d-b9fc-47ff-9f00-1a0270266e2a tempest-ServersTestJSON-34270062 
tempest-ServersTestJSON-745803609] Caught error: id
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack Traceback (most recent 
call last):
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/opt/stack/old/nova/nova/api/openstack/__init__.py", line 125, in __call__
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return 
req.get_response(self.application)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1317, in send
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack application, 
catch_exc_info=False)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/webob/request.py", line 1281, in 
call_application
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack app_iter = 
application(self.environ, start_response)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return 
resp(environ, start_response)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py",
 line 634, in __call__
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return 
self._call_app(env, start_response)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/keystonemiddleware/auth_token/__init__.py",
 line 554, in _call_app
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return 
self._app(env, _fake_start_response)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return 
resp(environ, start_response)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return 
resp(environ, start_response)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/routes/middleware.py", line 136, in 
__call__
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack response = 
self.app(environ, start_response)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 144, in __call__
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return 
resp(environ, start_response)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 130, in __call__
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack resp = 
self.call_func(req, *args, **self.kwargs)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/usr/local/lib/python2.7/dist-packages/webob/dec.py", line 195, in call_func
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return 
self.func(req, *args, **kwargs)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/opt/stack/old/nova/nova/api/openstack/wsgi.py", line 756, in __call__
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack content_type, 
body, accept)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/opt/stack/old/nova/nova/api/openstack/wsgi.py", line 821, in _process_stack
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack action_result = 
self.dispatch(meth, request, action_args)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/opt/stack/old/nova/nova/api/openstack/wsgi.py", line 911, in dispatch
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack return 
method(req=request, **action_args)
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 
"/opt/stack/old/nova/nova/api/openstack/compute/servers.py", line 636, in create
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack 
self._handle_create_exception(*sys.exc_info())
  2015-07-21 17:05:37.447 21251 TRACE nova.api.openstack   File 

[Yahoo-eng-team] [Bug 1501672] Re: v2 image download returns 403 when 'get_image_locations' policy set

[nikhil komawar]

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

** Changed in: glance/kilo
   Status: New => In Progress

** Changed in: glance/kilo
   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/1501672

Title:
  v2 image download returns 403 when 'get_image_locations' policy set

Status in Glance:
  Fix Committed
Status in Glance kilo series:
  In Progress

Bug description:
  when get_image_location is set role:admin a regular users sees:

   $ glance --os-image-api-version 2 image-download 
33fd3f1a-4924-4078-9d57-d7f6db4d015b
   403 Forbidden: You are not authorized to complete this action. (HTTP 403)

  v1 works ok.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1501672/+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 1500361] Re: Generated config files are completely wrong

[nikhil komawar]

RC2 is yet to be out, so I updated the status to Fix Committed from FIx
Released. This will be released when RC2 is out; that is either tomorrow
(Friday Oct 2) or next week.

** Changed in: glance
   Status: Fix Released => Fix Committed

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

Title:
  Generated config files are completely wrong

Status in Glance:
  Fix Committed

Bug description:
  The files generated using oslo-config-generator are completely wrong.
  For example, it is missing [keystone_authtoken] and many more. This
  shows on the example config in git (ie: etc/glance-api.conf in
  Glance's git repo).

  I believe the generator's config files is missing --namespace
  keystonemiddleware.auth_token (maybe instead of
  keystoneclient.middleware.auth_token).

  IMO, this is a critical issue, which should be addressed with highest
  priority. This blocks me from testing Liberty rc1 in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1500361/+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 1453047] Re: ValueError: Tables "artifact_blob_locations, artifact_blobs, artifact_dependencies, artifact_properties, artifact_tags, artifacts, image_locations, image_members, im

[nikhil komawar]

This has become non-relevant so, lowering priority and removing
milestone target.

The status has been moved to opinion until we get back to it next time.
If no more updates exists it will be won't fix then.

** Changed in: glance
   Importance: High => Wishlist

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

** Changed in: glance
Milestone: liberty-rc1 => None

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

Title:
  ValueError: Tables
  "artifact_blob_locations,artifact_blobs,artifact_dependencies,
  artifact_properties,artifact_tags,artifacts,
  image_locations,image_members,image_properties,image_tags,
  images,metadef_namespace_resource_types,
  metadef_namespaces,metadef_objects,metadef_properties,
  metadef_resource_types,metadef_tags,task_info,tasks" have non utf8
  collation, please make sure all tables are CHARSET=utf8

Status in Glance:
  Opinion

Bug description:
  A new sanity_check has been enabled in oslo.db, which verifies the
  table charset. We need to make the switch to utf8 explicit in our
  models definition. The current error in the gate is:

  
  Traceback (most recent call last):
File 
"/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/test_migrations.py",
 line 572, in test_models_sync
  self.db_sync(self.get_engine())
File "glance/tests/unit/test_migrations.py", line 1686, in db_sync
  migration.db_sync(engine=engine)
File "glance/db/migration.py", line 65, in db_sync
  init_version=init_version)
File 
"/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/migration.py",
 line 84, in db_sync
  _db_schema_sanity_check(engine)
File 
"/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/migration.py",
 line 114, in _db_schema_sanity_check
  ) % ','.join(table_names))
  ValueError: Tables 
"artifact_blob_locations,artifact_blobs,artifact_dependencies,artifact_properties,artifact_tags,artifacts,image_locations,image_members,image_properties,image_tags,images,metadef_namespace_resource_types,metadef_namespaces,metadef_objects,metadef_properties,metadef_resource_types,metadef_tags,task_info,tasks"
 have non utf8 collation, please make sure all tables are CHARSET=utf8

  
  And the fix required should consist in adding `'charset': 'utf-8'` to our 
GlanceBase model.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1453047/+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 1482301] Re: 'X-Openstack-Request-ID' lenght limited only by header size

[nikhil komawar]

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

** Also affects: glance/juno
   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/1482301

Title:
  'X-Openstack-Request-ID' lenght limited only by header size

Status in Glance:
  In Progress
Status in Glance juno series:
  New
Status in Glance kilo series:
  New

Bug description:
  Glance accepts 'X-Openstack-Request-ID' header and includes the value
  in log-files. The length of the Request ID is limited only by
  max_header_line parameter that defaults to 16384. This opens
  possibility to flood the logs.

  Public as this vulnerability was already discussed today on Glance
  weekly meeting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1482301/+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 1418061] Re: Images: 256 character limit isn't accurate for create image

[nikhil komawar]

** Changed in: glance
   Status: New = Fix Committed

** Changed in: glance
   Status: Fix Committed = Opinion

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

Title:
  Images: 256 character limit isn't accurate for create image

Status in OpenStack Image Registry and Delivery Service (Glance):
  Opinion
Status in OpenStack Dashboard (Horizon):
  Fix Released

Bug description:
  The 256 characters limit for Images doesn't seem quite accurate. If
  you try to set up a long name with special characters (less than 256
  characters, but more than 256 bytes?) it fails.

  A user reported:

  1. Create a image and the name of the image should be more than 256
  bytes. For example:
  
を引き続きご使用になるお客様はを引き続きご使用になるお客様はを引き続きご使用になるお客様はを引き続きご使用になるお客様はを引き続きご使用になるお客様はを引き続きご使用になるお客様はを引き続きご使用になるお客様はを引き続きご使用になるお客様はを引き続きご使用になるお客様は

  2. Horizon fails with a generic error.

  But actually it is the same with e.g. just creating a new image (The
  error returned is the generic: Unable to create new image. )

  We see this in the logs:

  [Tue Jan 20 16:40:45.594430 2015] [:error] [pid 17230] Recoverable error: 
html
  [Tue Jan 20 16:40:45.594454 2015] [:error] [pid 17230] head
  [Tue Jan 20 16:40:45.594458 2015] [:error] [pid 17230] title400 Bad 
Request/title
  [Tue Jan 20 16:40:45.594460 2015] [:error] [pid 17230] /head
  [Tue Jan 20 16:40:45.594462 2015] [:error] [pid 17230] body
  [Tue Jan 20 16:40:45.594465 2015] [:error] [pid 17230] h1400 Bad 
Request/h1
  [Tue Jan 20 16:40:45.594467 2015] [:error] [pid 17230] Image name too long: 
405br /br /
  [Tue Jan 20 16:40:45.594469 2015] [:error] [pid 17230]
  [Tue Jan 20 16:40:45.594472 2015] [:error] [pid 17230] /body
  [Tue Jan 20 16:40:45.594474 2015] [:error] [pid 17230] /html (HTTP 400)

  So Glance does return a more meaningful error, that we should try to
  present to the user.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1418061/+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 1402632] Re: issue with glance python client in Icehouse

[nikhil komawar]

https://review.openstack.org/#/c/171180/

** Project changed: glance = python-glanceclient

** Changed in: python-glanceclient
   Status: Invalid = Fix Committed

** Changed in: python-glanceclient
   Importance: Undecided = Low

** Changed in: python-glanceclient
Milestone: None = 0.19.0

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

Title:
  issue with glance python client in Icehouse

Status in Python client library for Glance:
  Fix Committed
Status in Ubuntu:
  New

Bug description:
  I installed glance client (0.15.0) on Ubuntu 14.04.1 LTS via pip
  install python-glanceclient. When i try to do something with this
  client i almost allways get back:

  root@anyhost:~/anydir# glance image-list
  1 is not a supported API version. Example values are 1 or 2.

  Environment (OS_USERNAME, OS_PASSWORD, ...) seems to be fine cause i'm
  able to list all from keystone with those credantials.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-glanceclient/+bug/1402632/+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 1202785] Re: Authentication is not checked before sending potentially large request bodies

[nikhil komawar]

** Changed in: glance
   Status: Triaged = Confirmed

** Changed in: glance
   Status: Confirmed = Won't Fix

** Changed in: glance
   Importance: High = Undecided

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

Title:
  Authentication is not checked before sending potentially large request
  bodies

Status in OpenStack Image Registry and Delivery Service (Glance):
  Won't Fix
Status in OpenStack Identity  (Keystone) Middleware:
  Incomplete
Status in OpenStack Security Advisories:
  Won't Fix
Status in Python client library for Keystone:
  Invalid

Bug description:
  When making an HTTP request with a body to an api using the keystone
  auth_token middleware and no request size limiting then an
  unauthorized user can send a very large request that will not fail
  with a 401 until after all of the data is sent. This means that anyone
  who can hit an api could make many requests with large bodies and not
  be denied until after all of that data has been sent, wasting lots/all
  of the resources on the api node essentially bringing it down.

  This issue can be mitigated for apis like nova by having middleware or
  using the webserver to limit the maximum size of a request. In the
  case of the glance-api however, large requests such as image uploads
  need to occur. Perhaps the auth_token middleware should look at
  request headers and perform authN and authZ before accepting all of
  the request body. It's also very inefficient and time consuming to
  wait until all the data is sent before receiving a 401.

  I am not sure of the level of impact this could have for most
  deployers and the different APIs.

  Here is an example of requests to glance and devstack with a bad token
  and their times to complete. Nova-api on devstack also accepted large
  bodies before returning a 401.


  1 Meg Image

  [ameade@ameade-dev:~]
  [17:30:16] $ time glance --debug --os-auth-token 'gah' image-create --name 
test 1meg.img 
  curl -i -X POST -H 'Transfer-Encoding: chunked' -H 'User-Agent: 
python-glanceclient' -H 'x-image-meta-size: 1048576' -H 
'x-image-meta-is_public: False' -H 'X-Auth-Token: gah' -H 'Content-Type: 
application/octet-stream' -H 'x-image-meta-name: test' -d 'open file 
'stdin', mode 'r' at 0x7f8d762bd150' http://50.56.173.46:9292/v1/images

  HTTP/1.1 401 Unauthorized
  date: Thu, 18 Jul 2013 17:30:30 GMT
  content-length: 253
  content-type: text/plain; charset=UTF-8

  401 Unauthorized

  This server could not verify that you are authorized to access the
  document you requested. Either you supplied the wrong credentials
  (e.g., bad password), or your browser does not understand how to
  supply the credentials required.


  Request returned failure status.
  Invalid OpenStack Identity credentials.

  real0m0.766s
  user0m0.312s
  sys 0m0.164s


  100 meg

  
  [ameade@ameade-dev:~]
  [17:31:35] $ time glance --debug --os-auth-token 'gah' image-create --name 
test 100meg.img 
  curl -i -X POST -H 'Transfer-Encoding: chunked' -H 'User-Agent: 
python-glanceclient' -H 'x-image-meta-size: 104857600' -H 
'x-image-meta-is_public: False' -H 'X-Auth-Token: gah' -H 'Content-Type: 
application/octet-stream' -H 'x-image-meta-name: test' -d 'open file 
'stdin', mode 'r' at 0x7f6af9768150' http://50.56.173.46:9292/v1/images

  HTTP/1.1 401 Unauthorized
  date: Thu, 18 Jul 2013 17:31:40 GMT
  content-length: 253
  content-type: text/plain; charset=UTF-8

  401 Unauthorized

  This server could not verify that you are authorized to access the
  document you requested. Either you supplied the wrong credentials
  (e.g., bad password), or your browser does not understand how to
  supply the credentials required.


  Request returned failure status.
  Invalid OpenStack Identity credentials.

  real0m1.441s
  user0m0.420s
  sys 0m0.344s


  10 gig

  [ameade@ameade-dev:~]
  [17:16:23] 1 $ time glance --debug --os-auth-token 'gah' image-create --name 
test 10g.img
  curl -i -X POST -H 'Transfer-Encoding: chunked' -H 'User-Agent: 
python-glanceclient' -H 'x-image-meta-size: 100' -H 
'x-image-meta-is_public: False' -H 'X-Auth-Token: gah' -H 'Content-Type: 
application/octet-stream' -H 'x-image-meta-name: test' -d 'open file 
'stdin', mode 'r' at 0x7f768c151150' http://50.56.173.46:9292/v1/images

  HTTP/1.1 401 Unauthorized
  date: Thu, 18 Jul 2013 17:16:28 GMT
  content-length: 253
  content-type: text/plain; charset=UTF-8

  401 Unauthorized

  This server could not verify that you are authorized to access the
  document you requested. Either you supplied the wrong credentials
  (e.g., bad password), or your browser does not understand how to
  supply the credentials required.


  Request returned failure status.
  Invalid OpenStack Identity credentials.

  real0m56.082s
  user0m6.308s
  sys 0m17.669s

To manage notifications about this bug go to:

[Yahoo-eng-team] [Bug 1414532] Re: asserts used in cache.py

[nikhil komawar]

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

** Changed in: glance/juno
   Status: New = Fix Committed

** Changed in: glance/juno
   Importance: Undecided = Low

** Changed in: glance/juno
 Assignee: (unassigned) = Ian Cordasco (icordasc)

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

Title:
  asserts used in cache.py

Status in OpenStack Image Registry and Delivery Service (Glance):
  Fix Released
Status in Glance juno series:
  Fix Committed
Status in OpenStack Security Advisories:
  Won't Fix
Status in OpenStack Security Notes:
  Fix Released

Bug description:
  The asserts in the snippet below check at #2 to see if the HTTP method
  match the HTTP methods actually specified in the patterns at #1.

  /opt/stack/glance/glance/api/middleware/cache.py

  PATTERNS = {   --- #1
  ('v1', 'GET'): re.compile(r'^/v1/images/([^\/]+)$'),
  ('v1', 'DELETE'): re.compile(r'^/v1/images/([^\/]+)$'),
  ('v2', 'GET'): re.compile(r'^/v2/images/([^\/]+)/file$'),
  ('v2', 'DELETE'): re.compile(r'^/v2/images/([^\/]+)$')
  }

  ...

  @staticmethod
  def _match_request(request):
  Determine the version of the url and extract the image id

  :returns tuple of version and image id if the url is a
  cacheable,
   otherwise None
  
  for ((version, method), pattern) in PATTERNS.items():
  match = pattern.match(request.path_info)
  try:
  assert request.method == method  --- #2
  image_id = match.group(1)
  # Ensure the image id we got looks like an image id to
  filter
  # out a URI like /images/detail. See LP Bug #879136
  assert image_id != 'detail'
  except (AttributeError, AssertionError):
  continue
  else:
  return (version, method, image_id)

  As stated in the Python documentation assert statements will not be evaluated
  when the Python code is compiled with optimization flags. This means that 
these
  checks will not be properly executed and one can in that case call a specific
  method with a completely different HTTP verb. This can result in security
  issues.

  For example think of having some filtering in place in front of the glance API
  to maybe allow only certain API queries to come from certain IP addresses. For
  example: 'the HTTP verb DELETE may only be executed from this IP range'.  An
  attacker can now specify a completely different HTTP verb such as GET and make
  sure he still matches regular expressions at #1 and then bypass the firewall.

  It's a bit of a hypothetical scenario but in general one should never ever do
  error checking with assert statemetns. This should only be done for things
  which can never realistically fail and that is simply not an assumption one 
can
  hold when it comes to untrusted input from the network.

  For more information see
  https://docs.python.org/2/reference/simple_stmts.html#the-assert-statement and
  https://docs.python.org/2/using/cmdline.html#envvar-PYTHONOPTIMIZE

  
  This seems to be related to https://bugs.launchpad.net/cinder/+bug/1199354  
but it's not fixed and maybe it should even be a security issue hence why I 
reported it again and tagged as a security vulnerability. I am not familiar 
enough with the code base to make that call.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1414532/+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 1422699] Re: glance api doesn't abort start up on Store configuration errors

[nikhil komawar]

** Changed in: glance-store
   Status: Fix Committed = 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/1422699

Title:
  glance api doesn't abort start up on Store configuration errors

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

Bug description:
  Glance api service does not abort start up when errors in glance-api.cfg file 
are encountered.
  It would make sense to abort service start up when a BadStoreConfiguration 
exception is encountered, instead of just sending the error to the logs and 
disabling adding images to that Store.

  For example if a Filesystem Storage Backend with multiple store is configured 
with a duplicate directory:
  filesystem_store_datadirs=/mnt/nfs1/images/:200
  filesystem_store_datadirs=/mnt/nfs1/images/:100

  Logs will have the error:
  ERROR glance_store._drivers.filesystem [-] Directory /mnt/nfs1/image 
specified multiple times in filesystem_store_datadirs option of filesystem 
configuration
  TRACE glance_store._drivers.filesystem None
  TRACE glance_store._drivers.filesystem
  WARNING glance_store.driver [-] Failed to configure store correctly: None 
Disabling add method.

  Service will start and when client tries to add an image he will
  receive a 410 Gone error saying: Error in store configuration. Adding
  images to store is disabled.

  This affects not only the filesystem storage backend but all glance-
  storage drivers that encounter an error in the configuration and raise
  a BadStoreConfiguration exception.

  How reproducible:
  Every time

  Steps to Reproduce:
  1. Configure Glance to use  Filesystem Storage Backend with multiple store 
and duplicate a filesystem_storage_datadirs.
  2. Run glance api

  Expected behavior:
  Glance api service should not have started and should have reported that the 
directory was specified multiple times.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1422699/+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 1449639] Re: RBD: On image creation error, image is not deleted

[nikhil komawar]

** Changed in: glance-store
   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/1449639

Title:
  RBD: On image creation error, image is not deleted

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

Bug description:
  When an exception rises while adding/creating an image, and the image
  has been created, this new image is not properly deleted.

  The fault lies in the `_delete_image` call of the Store.add method
  that is providing incorrect arguments.

  This also affects Glance (Icehouse), since back then glance_store
  functionality was included there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1449639/+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 1452447] [NEW] is_public is not v2 reserved prop but domain marks it otherwise

[nikhil komawar]

Public bug reported:

https://review.openstack.org/#/c/154704/ modifies is_public to be non-
reserved.

However, the list --
_reserved_properties = ['owner', 'is_public', 'locations',
does not have it removed.

https://github.com/openstack/glance/blob/master/glance/domain/__init__.py#L56

** Affects: glance
 Importance: Undecided
 Status: New

** Summary changed:

- is_public is not v2 reserved prop by domain marks it otherwise
+ is_public is not v2 reserved prop but domain marks it otherwise

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

Title:
  is_public is not v2 reserved prop but domain marks it otherwise

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

Bug description:
  https://review.openstack.org/#/c/154704/ modifies is_public to be non-
  reserved.

  However, the list --
  _reserved_properties = ['owner', 'is_public', 'locations',
  does not have it removed.

  https://github.com/openstack/glance/blob/master/glance/domain/__init__.py#L56

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1452447/+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 1447327] [NEW] Glance v1 should now be in SUPPORTED status

[nikhil komawar]

Public bug reported:

As per title

** Affects: glance
 Importance: Critical
 Assignee: Fei Long Wang (flwang)
 Status: In Progress


** Tags: kilo-rc-potential

** Tags added: kilo-rc-potential

** Changed in: glance
   Importance: Undecided = Critical

** Changed in: glance
   Status: New = Triaged

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

Title:
  Glance v1 should now be in SUPPORTED status

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

Bug description:
  As per title

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1447327/+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 1446286] Re: Exporting a deactivated image returns a generic task failure message

[nikhil komawar]

How can this be a bug if export is not even a implemented task yet?

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

Title:
  Exporting a deactivated image returns a generic task failure message

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

Bug description:
  Overview:
  When a user attempts to export a deactivated image, the operation fails as 
expected, but the message that is returned explaining why it failed is very 
generic.

  Steps to reproduce:
  1) Import an image as user A
  2) Deactivate the image as admin
  3) Export the image as user A
  4) Notice the export task fails, but with a generic error message

  Expected:
  A more detailed error message as to why the export task failed for a 
deactivated image

  Actual:
  A generic error message reading Unknown error occurred during import export 
is returned.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1446286/+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 1446326] [NEW] 403 response from Nova when making a DELETE call for an image in pending_delete

[nikhil komawar]

Public bug reported:

Context and information:
--
Currently, 404 is seen by the user when image-delete call is made via the 
Glance API or through the Images API of Nova for an Image in deleted status.

However, if an Image is in pending_delete and a user with the UUID of
that Image tries image-delete call from the Nova API, she gets a back
a 403 which is not consistent. The user should get a 404 back.

Notes:
--
* The user needs to specify the UUID, name is not sufficient.
* For image-show call the user is able to see the Image in DELETED status 
with the appropriate metadata for Image in deleted or pending_delete status 
in Glance as nova passes-in the force_show_deleted=True flag by default.

Feedback needed and action to be taken:
---
Nova should be able to return a 404 back to the user while issuing a 
image-delete call if the Image is flagged deleted in the Glance DB 
(deleted=True), irrespective of the Image status in deleted or 
pending_delete.

** Affects: glance
 Importance: Medium
 Status: New

** Affects: nova
 Importance: Undecided
 Status: New

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

** Changed in: glance
   Importance: Undecided = Medium

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

Title:
  403 response from Nova when making a DELETE call for an image in
  pending_delete

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

Bug description:
  Context and information:
  --
  Currently, 404 is seen by the user when image-delete call is made via the 
Glance API or through the Images API of Nova for an Image in deleted status.

  However, if an Image is in pending_delete and a user with the UUID
  of that Image tries image-delete call from the Nova API, she gets a
  back a 403 which is not consistent. The user should get a 404 back.

  Notes:
  --
  * The user needs to specify the UUID, name is not sufficient.
  * For image-show call the user is able to see the Image in DELETED status 
with the appropriate metadata for Image in deleted or pending_delete status 
in Glance as nova passes-in the force_show_deleted=True flag by default.

  Feedback needed and action to be taken:
  ---
  Nova should be able to return a 404 back to the user while issuing a 
image-delete call if the Image is flagged deleted in the Glance DB 
(deleted=True), irrespective of the Image status in deleted or 
pending_delete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1446326/+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 1221274] Re: allow sorting with more than one field

[nikhil komawar]

Glance change was merge in kilo-3

Glance client change is in tag 0.17.0

** Changed in: glance
   Status: In Progress = Fix Committed

** Also affects: python-glanceclient
   Importance: Undecided
   Status: New

** Changed in: python-glanceclient
   Status: New = Fix Released

** Changed in: python-glanceclient
   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/1221274

Title:
  allow sorting with more than one field

Status in OpenStack Image Registry and Delivery Service (Glance):
  Fix Committed
Status in Python client library for Glance:
  Fix Released

Bug description:
  when running glance image-list --sort-key we only get to use one sort field. 
  it would be helpful if I was able to sort with more than one field (as in, 
first name, than size, than status).

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1221274/+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 1420707] Re: Update help for glance member-update v2 api

[nikhil komawar]

** Changed in: glance
   Importance: Undecided = Wishlist

** Also affects: python-glanceclient
   Importance: Undecided
   Status: New

** Changed in: python-glanceclient
 Assignee: (unassigned) = Yamini Sardana (yamini-sardana)

** Changed in: python-glanceclient
   Importance: Undecided = Wishlist

** Changed in: python-glanceclient
   Status: New = In Progress

** No longer affects: glance

** Changed in: python-glanceclient
Milestone: None = v0.16.1

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

Title:
  Update help for glance member-update v2 api

Status in Python client library for Glance:
  In Progress

Bug description:
  The output for glance --os-image-api-version 2 help member-update
  should display the options available for MEMBER STATUS field
  (Accepted, Rejected, Pending)

  At the moment it does not display the available options.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-glanceclient/+bug/1420707/+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 1398838] Re: Errors should not print json

[nikhil komawar]

** Changed in: python-glanceclient
   Status: Fix Committed = 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/1398838

Title:
  Errors should not print json

Status in OpenStack Image Registry and Delivery Service (Glance):
  Triaged
Status in Python client library for Glance:
  Fix Released

Bug description:
  When I try to use glanceclient to upload an image and it does not
  work, glanceclient should not print json.

  mordred@mordred-irc:~/system-config$ glance image-create 
--name=test-monty-ubuntu --disk-format=vhd --container-format=bare 
--file=ubuntu.vhd 
  {
  overLimit : {
  code : 413,
  message : OverLimit Retry...,
  details : Error Details...,
  retryAt : 2014-12-03T13:33:06Z
  }
  } (HTTP 413)

  A nice error message would be better.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1398838/+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 1425617] Re: Glance's swift driver unable to delete image data stored as SLO

[nikhil komawar]

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

** No longer affects: glance

** Changed in: glance-store
   Status: New = Triaged

** Changed in: glance-store
   Importance: Undecided = Medium

** Changed in: glance-store
 Assignee: (unassigned) = Hemanth Makkapati (hemanth-makkapati)

** Changed in: glance-store
Milestone: None = v0.1.12

** Changed in: glance-store
   Status: Triaged = 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/1425617

Title:
  Glance's swift driver unable to delete image data stored as SLO

Status in OpenStack Glance backend store-drivers library (glance_store):
  In Progress

Bug description:
  Glance's swift driver provides the capability to delete image data
  from Swift backend when an image is deleted. However, as of today, the
  swift driver is only capable of deleting image data that is stored as
  a regular swift object or dynamic large object(DLO). When image data
  is stored as static large object(SLO), it fails to delete the image
  data completely. Currently, for an SLO, the swift driver just deletes
  the manifest and leaves the segments behind. This leads to stale data
  sitting around in the cluster.

  A point to note here would be: Glance itself never uploads an image as
  SLO. It either uploads the image as one object or DLO. However, this
  doesn't eliminate the possibility of a user creating an image with '--
  file' that points to a swift SLO. So, even though Glance itself may
  not upload data as DLO, it should be able to delete data that is
  stored as SLO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance-store/+bug/1425617/+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 1379798] Re: Glance returns HTTPInternalServerError 500 in case of image server is down

[nikhil komawar]

** Changed in: glance-store
   Status: In Progress = Fix Released

** Changed in: glance
Milestone: None = kilo-3

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

Title:
  Glance returns HTTPInternalServerError 500 in case of image server is
  down

Status in OpenStack Image Registry and Delivery Service (Glance):
  In Progress
Status in OpenStack Glance backend store-drivers library (glance_store):
  Fix Released

Bug description:
  HTTPInternalServerError 500 response is returned to the user while image 
server is down during downloading the image.
  When user tries to download the image from the remote location (image server) 
which is down, Connection refused ECONNREFUSED error is raised on the glance 
server.

  Ideally it should return 503 HTTPServiceUnavailable response to the
  user.

  Steps to reproduce:

  1. Create a file 'test_image.py' at any location. example: /home/openstack/
  2. Run Simple HTTP server using python -m SimpleHTTPServer 8050 from 
location mentioned in step 1.
  3. Create an image using location parameter.
  example: glance image-create --name myimage --disk-format=raw 
--container-format=bare --location http://10.69.4.178:8050/test_image.py
  4. Stop Simple HTTP server.
  5. Download image using  glance image-download image_id created in step 3.

  Please refer http://paste.openstack.org/show/120165/ for v1 and v2 api
  logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1379798/+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...

[nikhil komawar]

** Changed in: glance-store
   Importance: Undecided = Medium

** Changed in: glance-store
   Status: Fix Committed = 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/1316137

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

Status in OpenStack Image Registry and Delivery Service (Glance):
  In Progress
Status in OpenStack Glance backend store-drivers library (glance_store):
  Fix Released

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
  

[Yahoo-eng-team] [Bug 1412802] Re: copy-from broken for large files and swift

[nikhil komawar]

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

** Changed in: glance-store
   Status: New = In Progress

** Changed in: glance-store
 Assignee: (unassigned) = Stuart McLaren (stuart-mclaren)

** Changed in: glance-store
Milestone: None = v0.1.11

** Changed in: glance-store
   Importance: Undecided = Critical

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

Title:
  copy-from broken for large files and swift

Status in OpenStack Image Registry and Delivery Service (Glance):
  Fix Released
Status in Glance icehouse series:
  In Progress
Status in Glance juno series:
  In Progress
Status in OpenStack Glance backend store-drivers library (glance_store):
  In Progress

Bug description:
  Glance may loose some image data while transferring it to the backing
  store thus corrupting the image when ALL the following conditions are
  met:

  - Image is being created by copying data from remote source (--copy-from CLI 
parameter or appropriate API call)
  - Backing store is Swift
  - Image size is larger then configured swift_store_large_object_size

  In such scenarios the last chunk stored in Swift will have the size
  significantly less then expected. An attempt to download the image
  will result in a checksum verification error, however the checksum
  stored in Glance (with image metadata) is correct, and so is the size.

  This is easily reproducible even on devstack (if the devstack is
  configured to run Swift as Glance backend). Just decrease
  'swift_store_large_object_size' to some reasonably low value (i.e. 200
  Mb) and try to copy-from any image which is larger then that value.
  After the upload is successful, check the object size in swift (by
  either summing the sizes of all the chunks or by looking to the size
  of virtual large object) - they will be lower then expected:

  
  glance image-create --name tst --disk-format qcow2 --container-format bare 
--copy-from http://192.168.56.1:8000/F18-x86_64-cfntools.qcow2

  ...

  glance image-list
  
+--+-+-+--+---++
  | ID   | Name| 
Disk Format | Container Format | Size  | Status |
  
+--+-+-+--+---++
  | fc34ec49-4bd3-40dd-918f-44d3254f2ac9 | tst | 
qcow2   | bare | 536412160 | active |
  
+--+-+-+--+---++

  ...

  swift stat glance fc34ec49-4bd3-40dd-918f-44d3254f2ac9 --os-tenant-name 
service --os-username admin
 Account: AUTH_cce6e9c12fa34c63b64ef29e84861554
   Container: glance
  Object: fc34ec49-4bd3-40dd-918f-44d3254f2ac9
Content Type: application/octet-stream
  Content Length: 509804544  see, the size is 
different!
   Last Modified: Mon, 19 Jan 2015 15:52:18 GMT
ETag: 6d0612f82db9a531b34d25823a45073d
Manifest: glance/fc34ec49-4bd3-40dd-918f-44d3254f2ac9-
   Accept-Ranges: bytes
 X-Timestamp: 1421682737.01148
  X-Trans-Id: tx01a19f7476a541808c9a1-0054bd28e1

  

  glance image-download tst --file out.qcow2
  [Errno 32] Corrupt image download. Checksum was 
0eeddae1007f01b0029136d28518f538 expected 3ecddfe0787a392960d230c87a421c6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1412802/+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 1401778] Re: 500 error returned while uploading image using multi filesystem store and 'filesystem_store_metadata_file' option enabled

[nikhil komawar]

** Changed in: glance
   Importance: Undecided = High

** Changed in: glance-store
   Importance: Undecided = High

** Changed in: glance-store
   Status: In Progress = Fix Committed

** Changed in: glance
   Status: Fix Released = Triaged

** Changed in: glance
Milestone: kilo-2 = None

** Changed in: glance-store
Milestone: None = v0.1.11

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

Title:
  500 error returned while uploading image using multi filesystem store
  and 'filesystem_store_metadata_file' option enabled

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

Bug description:
  When we try to upload image with multi filesystem store enabled and 
'filesystem_store_metadata_file' 
  (containing list of all directories configured for multi filesystem store) is 
provided
  then glance throws 'HTTPInternalServerError (HTTP 500)' error.

  - Glance Configuration:

  1. /etc/glance/glance-api.conf

  [DEFAULT]
  show_multiple_locations = True
  filesystem_store_metadata_file = /etc/glance/metadata.json

  [glance_store]
  filesystem_store_datadirs = /var/lib/glance/images1/:1
  filesystem_store_datadirs = /var/lib/glance/images2/:2

  
  2. /etc/glance/metadata.json

  [
  {
  id: f0781415-cf81-47cd-8860-b83f9c2a415c,
  mountpoint: /var/lib/glance/images1/ 
  },
  {
  id: 5d2dd1db-8684-46bb-880f-b94a1942cfd2,
  mountpoint: /var/lib/glance/images2/ 
  }
  ]

  3. 'df -ha' command result:

  openstack@openstack:/opt/stack$ df -ha
  Filesystem   Size  Used Avail Use% Mounted on
  proc0 0 0- /proc
  sysfs   0 0 0- /sys
  tmpfs799M  600K  798M   1% /run
  /dev/sda1236M   41M  183M  19% /boot
  nfsd0 0 0- /proc/fs/nfsd
  10.69.4.173:/export/images2  443G   23G  398G   6% 
/var/lib/glance/images2
  10.69.4.172:/export/images1  447G  8.7G  415G   3% 
/var/lib/glance/images1
  openstack@openstack:/opt/stack$

  
  - Steps to reproduce:

  1. Create image:
  glance --os-image-api-version 2 image-create --name Test123 --disk-format raw 
--container-format ami

  2. Upload image data:
   
  openstack@openstack-150:~$ glance --os-image-api-version 2 image-upload 
47d39050-cc7e-498a-a800-4faf80a72c93  /home/openstack/workbook/test.py

  HTTPInternalServerError (HTTP 500)
  openstack@openstack-150:~$

  
  - glance-api.log :

  2014-12-11 22:16:59.586 3495 ERROR glance_store.backend 
[95987e95-dcae-4516-b57e-87fbd9135ff3 0080647f6a2145f8a40bace67654a058 
48f94106d3b24ca2a0a9e2951c505bf9 - - -] The storage driver 
glance_store._drivers.filesystem.Store
   object at 0x7fa1b184e390 returned invalid metadata [{u'mountpoint': 
u'/opt/stack/data/glance/images/', u'id': 
u'f0781415-cf81-47cd-8860-b83f9c2a415c'}, {u'mountpoint': 
u'/opt/stack/data/glance/images1/', u'id': u'5d2dd1db-
  8684-46bb-880f-b94a1942cfd2'}]. This must be a dictionary type
  2014-12-11 22:16:59.591 3495 ERROR glance.api.v2.image_data 
[95987e95-dcae-4516-b57e-87fbd9135ff3 0080647f6a2145f8a40bace67654a058 
48f94106d3b24ca2a0a9e2951c505bf9 - - -] Failed to upload image data due to 
internal error
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data Traceback (most 
recent call last):
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data File 
/opt/stack/glance/glance/api/v2/image_data.py, line 74, in upload
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data 
image.set_data(data, size)
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data File 
/opt/stack/glance/glance/domain/proxy.py, line 160, in set_data
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data 
self.base.set_data(data, size)
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data File 
/opt/stack/glance/glance/notifier.py, line 252, in set_data
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data 
self.notifier.error('image.upload', msg)
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data File 
/usr/local/lib/python2.7/dist-packages/oslo/utils/excutils.py, line 82, in 
__exit
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data 
six.reraise(self.type_, self.value, self.tb)
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data File 
/opt/stack/glance/glance/notifier.py, line 201, in set_data
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data 
self.image.set_data(data, size)
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data File 
/opt/stack/glance/glance/api/policy.py, line 176, in set_data
  2014-12-11 22:16:59.591 3495 TRACE glance.api.v2.image_data 

[Yahoo-eng-team] [Bug 1402354] Re: Broken Pipe in vsphere store due to inactive session

[nikhil komawar]

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

** Changed in: glance-store
   Status: New = In Progress

** Changed in: glance-store
   Importance: Undecided = High

** Changed in: glance-store
 Assignee: (unassigned) = Sabari Murugesan (smurugesan)

** Changed in: glance-store
Milestone: None = v0.1.11

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

Title:
  Broken Pipe in vsphere store due to inactive session

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

Bug description:
  We are seeing the following error in glance-api configured with
  vsphere store. This happens after letting glance-api run for a while.

  
  2014-12-03 15:06:08.641 3005 DEBUG glance.api.v1.images [-] Uploading image 
data for image 10908257-eb9a-47cf-aaba-afa203c3e9f0 to vsphere store _upload 
/opt/stack/glance/glance/api/v1/images.py:630
  send: 'PUT 
/folder/openstack_glance/10908257-eb9a-47cf-aaba-afa203c3e9f0%3FdsName%3Dstore2%26dcPath%3DDatacenter1
 HTTP/1.1\r\nHost: 10.20.116.124\r\nAccept-Encoding: 
identity\r\nContent-Length: 41126400\r\nCookie: 
vmware_soap_session=523fa07a-301c-5312-a35b-7fb99d822720\r\n\r\n'
  send: glance_store._drivers.vmware_datastore._Reader object at 
0x7f238c1d74d0
  sendIng a read()able
  2014-12-03 15:06:08.677 3005 ERROR glance_store._drivers.vmware_datastore [-] 
Failed to upload content of image 10908257-eb9a-47cf-aaba-afa203c3e9f0
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
Traceback (most recent call last):
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /opt/stack/glance_store/glance_store/_drivers/vmware_datastore.py, line 
351, in add
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
content=image_file)
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /opt/stack/glance_store/glance_store/_drivers/vmware_datastore.py, line 
502, in _get_http_conn
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
conn.request(method, url, content, headers)
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /usr/lib/python2.7/httplib.py, line 973, in request
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
self._send_request(method, url, body, headers)
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /usr/lib/python2.7/httplib.py, line 1007, in _send_request
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
self.endheaders(body)
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /usr/lib/python2.7/httplib.py, line 969, in endheaders
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
self._send_output(message_body)
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /usr/lib/python2.7/httplib.py, line 833, in _send_output
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
self.send(message_body)
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /usr/lib/python2.7/httplib.py, line 802, in send
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
self.sock.sendall(datablock)
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /usr/local/lib/python2.7/dist-packages/eventlet/green/ssl.py, line 137, 
in sendall
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
v = self.send(data[count:])
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /usr/local/lib/python2.7/dist-packages/eventlet/green/ssl.py, line 113, 
in send
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
super(GreenSSLSocket, self).send, data, flags)
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /usr/local/lib/python2.7/dist-packages/eventlet/green/ssl.py, line 80, 
in _call_trampolining
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
return func(*a, **kw)
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore   
File /usr/lib/python2.7/ssl.py, line 298, in send
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
v = self._sslobj.write(data)
  2014-12-03 15:06:08.677 3005 TRACE glance_store._drivers.vmware_datastore 
error: [Errno 32] Broken pipe

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

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

[Yahoo-eng-team] [Bug 1413852] Re: VMware store: Attribute error while retrying image upload

[nikhil komawar]

** Changed in: glance
   Importance: Undecided = Medium

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

** Changed in: glance-store
 Assignee: (unassigned) = Sabari Murugesan (smurugesan)

** Changed in: glance-store
   Status: New = In Progress

** Changed in: glance-store
   Importance: Undecided = High

** Changed in: glance
   Status: In Progress = Opinion

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

Title:
  VMware store: Attribute error while retrying image upload

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

Bug description:
  In case of unauthenticated session, vmware store retries to upload the
  image data but fails when seeking to reposition the file.

  2015-01-22 19:12:31.883 20624 ERROR glance.api.v1.upload_utils 
[e5be8f01-4bbb-4a1c-9721-495615e5e5cb 65dc7965ee13438e9ae706d4d42d2f65 
087a197802df458dac65c1060a8e4cd4 - - -] Failed to upload image 
fa4a3308-917a-4899-8905-66333955cdfb
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils Traceback 
(most recent call last):
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils   File 
/opt/stack/glance/glance/api/v1/upload_utils.py, line 107, in 
upload_data_to_store
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils 
context=req.context)
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils   File 
/opt/stack/glance_store/glance_store/backend.py, line 318, in 
store_add_to_backend
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils 
context=context)
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils   File 
/opt/stack/glance_store/glance_store/_drivers/vmware_datastore.py, line 359, 
in add
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils 
image_file.rewind()
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils   File 
/opt/stack/glance_store/glance_store/_drivers/vmware_datastore.py, line 124, 
in rewind
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils 
self.data.seek(0)
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils 
AttributeError: 'CooperativeReader' object has no attribute 'seek'
  2015-01-22 19:12:31.883 20624 TRACE glance.api.v1.upload_utils

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1413852/+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 1383973] Re: image data cannot be removed when deleting a saving status image

[nikhil komawar]

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

** This bug is no longer a duplicate of bug 1188532
   image download process won't terminate after deleting image from dashboard
** This bug has been marked a duplicate of bug 1398830
   Glance image leak when in saving state (CVE-2014-9623)

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

Title:
  image data cannot be removed when deleting a saving status image

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

Bug description:
  The image data in /var/lib/glance/images/ cannot be removed when I
  delete a image that status is saving.

  1. create a image
   glance image-create --name image-v1 --disk-format raw --container-format 
bare --file xx.image --is-public true

  2. list the created image, the status is saving
  [root@node2 ~]# glance image-list
  
+--+--+-+--+--++
  | ID   | Name | Disk Format | Container 
Format | Size | Status |
  
+--+--+-+--+--++
  | 00ec3d8d-41a5-4f7c-9448-694099a39bcf | image-v1 | raw | bare
 | 18   | saving |
  
+--+--+-+--+--++

  3. delete the created image
  glance image-delete image-v1

  4. the image has been deleted but the image data still exists
  [root@node2 ~]# glance image-list
  ++--+-+--+--++
  | ID | Name | Disk Format | Container Format | Size | Status |
  ++--+-+--+--++
  ++--+-+--+--++

  [root@node2 ~]# ls /var/lib/glance/images
  00ec3d8d-41a5-4f7c-9448-694099a39bcf

  This problem exists in both v1 and v2 API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1383973/+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 1410494] [NEW] sqlalchemy-migrate0.9.1 and 0.9.5 causes glance test failures

[nikhil komawar]

Public bug reported:

The error is seen as

OperationalError: (OperationalError) cannot start a transaction within a
transaction u'/*\n * This is necessary because SQLite does not support\n
* RENAME INDEX or ALTER TABLE CHANGE COLUMN.\n */\nBEGIN TRANSACTION;'
()

More info at:
http://paste.openstack.org/show/157276/

** Affects: glance
 Importance: Critical
 Status: Triaged

** Affects: sqlalchemy-migrate
 Importance: Undecided
 Status: Confirmed

** Also affects: sqlalchemy-migrate
   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/1410494

Title:
  sqlalchemy-migrate0.9.1 and 0.9.5 causes glance test failures

Status in OpenStack Image Registry and Delivery Service (Glance):
  Triaged
Status in Database schema migration for SQLAlchemy:
  Confirmed

Bug description:
  The error is seen as

  OperationalError: (OperationalError) cannot start a transaction within
  a transaction u'/*\n * This is necessary because SQLite does not
  support\n * RENAME INDEX or ALTER TABLE CHANGE COLUMN.\n */\nBEGIN
  TRANSACTION;' ()

  More info at:
  http://paste.openstack.org/show/157276/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1410494/+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 1377012] Re: Can't delete an image in deleted status

[nikhil komawar]

Unfortunately, we cannot re-delete Image via the API by design.

Another approach for this real issue might be to use the scrubber to
keep track of such leftover data and retry deletes. Please provide your
suggestions here: https://review.openstack.org/#/c/125156/

** Changed in: glance
   Status: Triaged = Won't Fix

** Changed in: glance
   Importance: Medium = Undecided

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

Title:
  Can't delete an image in deleted status

Status in OpenStack Image Registry and Delivery Service (Glance):
  Won't Fix

Bug description:
  I'm trying to delete an image that has a status of deleted

  It's not deleted as I can do an image-show and it returns plus I can
  see it in image_locations and it exists in the backend which for us is
  swift

  glance image-show 17c6077c-99f0-41c7-9bd2-175216330990
  
+---+--+
  | Property  | Value   
 |
  
+---+--+
  | checksum  | 
c9ef771d317595fd3654ca69a4be5f31 |
  | container_format  | bare
 |
  | created_at| 2014-05-22T07:58:23 
 |
  | deleted   | True
 |
  | deleted_at| 2014-05-23T02:16:53 
 |
  | disk_format   | raw 
 |
  | id| 
17c6077c-99f0-41c7-9bd2-175216330990 |
  | is_public | True
 |
  | min_disk  | 10  
 |
  | min_ram   | 0   
 |
  | name  | XX|
  | owner | X |
  | protected | False   
 |
  | size  | 10737418240 
 |
  | status| deleted 
 |
  | updated_at| 2014-05-23T02:16:53 
 |
  
+---+--+

  glance image-delete 17c6077c-99f0-41c7-9bd2-175216330990
  Request returned failure status.
  404 Not Found
  Image 17c6077c-99f0-41c7-9bd2-175216330990 not found.
  (HTTP 404): Unable to delete image 17c6077c-99f0-41c7-9bd2-175216330990

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1377012/+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 1395069] [NEW] Prevent upload data bits to a non-queued image

[nikhil komawar]

Public bug reported:

Currently, it's possible to upload data to an image which is not in
queued state; and while attempting to update it status to active the 409
conflict is raised. [1, 2, 3]

We'd prevent this as it could potentially mean bandwidth usage for the
user.

[1] https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L625
[2] 
https://github.com/openstack/glance/blob/master/glance/registry/api/v1/images.py#L454
[3] 
https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/api.py#L725

** Affects: glance
 Importance: Medium
 Status: Confirmed

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

Title:
  Prevent upload data bits to a non-queued image

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

Bug description:
  Currently, it's possible to upload data to an image which is not in
  queued state; and while attempting to update it status to active the
  409 conflict is raised. [1, 2, 3]

  We'd prevent this as it could potentially mean bandwidth usage for the
  user.

  [1] 
https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L625
  [2] 
https://github.com/openstack/glance/blob/master/glance/registry/api/v1/images.py#L454
  [3] 
https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/api.py#L725

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1395069/+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 1395069] Re: Prevent upload data bits to a non-queued image

[nikhil komawar]

** Changed in: glance
   Status: Confirmed = Invalid

** Changed in: glance
   Importance: Medium = Undecided

** Changed in: glance
 Assignee: nikhil komawar (nikhil-komawar) = (unassigned)

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

Title:
  Prevent upload data bits to a non-queued image

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

Bug description:
  Currently, it's possible to upload data to an image which is not in
  queued state; and while attempting to update it status to active the
  409 conflict is raised. [1, 2, 3]

  We'd prevent this as it could potentially mean bandwidth usage for the
  user.

  [1] 
https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L625
  [2] 
https://github.com/openstack/glance/blob/master/glance/registry/api/v1/images.py#L454
  [3] 
https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/api.py#L725

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1395069/+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 1392270] Re: POST /v2/images succeds without any POST data

[nikhil komawar]

This is by design: http://docs.openstack.org/api/openstack-image-
service/2.0/content/upload-image-file.html

** Changed in: glance
   Status: Confirmed = 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/1392270

Title:
  POST /v2/images succeds without any POST data

Status in OpenStack Image Registry and Delivery Service (Glance):
  Won't Fix

Bug description:
  The exact request is:

  curl -i -X POST -H 'User-Agent: python-glanceclient' -H 'Content-Type:
  application/json' -H 'Accept-Encoding: gzip, deflate' -H 'Accept: */*'
  -H 'X-Auth-Token: {SHA1}2d5b305e1ea690482d697a6971130f1efd04fbc2' -d
  '{}' http://127.0.0.1:9292/v2/images

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1392270/+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 1362766] Re: ConnectionFailed: Connection to neutron failed: 'HTTPSConnectionPool' object has no attribute 'insecure'

[nikhil komawar]

https://review.openstack.org/#/c/110574/9

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

** Also affects: python-glanceclient
   Importance: Undecided
   Status: New

** No longer affects: glance

** Changed in: python-glanceclient
   Status: New = In Progress

** Changed in: python-glanceclient
 Assignee: (unassigned) = Flavio Percoco (flaper87)

** Changed in: python-glanceclient
   Importance: Undecided = Medium

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

Title:
  ConnectionFailed: Connection to neutron failed: 'HTTPSConnectionPool'
  object has no attribute 'insecure'

Status in Python client library for Glance:
  In Progress
Status in Python client library for Neutron:
  Incomplete

Bug description:
  While compute manager was trying to authenticate with neutronclient,
  we see the following:

  2014-08-28 05:03:33.052 29982 TRACE powervc_nova.compute.manager Traceback 
(most recent call last):
  2014-08-28 05:03:33.052 29982 TRACE powervc_nova.compute.manager   File 
/usr/lib/python2.7/site-packages/powervc_nova/compute/manager.py, line 672, 
in _populate_admin_context
  2014-08-28 05:03:33.052 29982 TRACE powervc_nova.compute.manager 
nclient.authenticate()
  2014-08-28 05:03:33.052 29982 TRACE powervc_nova.compute.manager   File 
/usr/lib/python2.7/site-packages/neutronclient/client.py, line 231, in 
authenticate
  2014-08-28 05:03:33.052 29982 TRACE powervc_nova.compute.manager 
self._authenticate_keystone()
  2014-08-28 05:03:33.052 29982 TRACE powervc_nova.compute.manager   File 
/usr/lib/python2.7/site-packages/neutronclient/client.py, line 209, in 
_authenticate_keystone
  2014-08-28 05:03:33.052 29982 TRACE powervc_nova.compute.manager 
allow_redirects=True)
  2014-08-28 05:03:33.052 29982 TRACE powervc_nova.compute.manager   File 
/usr/lib/python2.7/site-packages/neutronclient/client.py, line 113, in 
_cs_request
  2014-08-28 05:03:33.052 29982 TRACE powervc_nova.compute.manager raise 
exceptions.ConnectionFailed(reason=e)
  2014-08-28 05:03:33.052 29982 TRACE powervc_nova.compute.manager 
ConnectionFailed: Connection to neutron failed: 'HTTPSConnectionPool' object 
has no attribute 'insecure'

  Setting a pdb breakpoint and stepping into the code, I see that the
  requests library is getting a connection object from a pool.  The
  interesting thing is that the connection object is actually from
  glanceclient.common.https.HTTPSConnectionPool.  It seems odd to me
  that neutronclient is using a connection object from glanceclient
  pool, but I do not know this requests code.  Here is the stack just
  before failure:

/usr/lib/python2.7/site-packages/neutronclient/client.py(234)authenticate()
  - self._authenticate_keystone()

/usr/lib/python2.7/site-packages/neutronclient/client.py(212)_authenticate_keystone()
  - allow_redirects=True)
/usr/lib/python2.7/site-packages/neutronclient/client.py(106)_cs_request()
  - resp, body = self.request(*args, **kargs)
/usr/lib/python2.7/site-packages/neutronclient/client.py(151)request()
  - **kwargs)
/usr/lib/python2.7/site-packages/requests/api.py(44)request()
  - return session.request(method=method, url=url, **kwargs)
/usr/lib/python2.7/site-packages/requests/sessions.py(335)request()
  - resp = self.send(prep, **send_kwargs)
/usr/lib/python2.7/site-packages/requests/sessions.py(438)send()
  - r = adapter.send(request, **kwargs)
/usr/lib/python2.7/site-packages/requests/adapters.py(292)send()
  - timeout=timeout
/usr/lib/python2.7/site-packages/urllib3/connectionpool.py(454)urlopen()
  - conn = self._get_conn(timeout=pool_timeout)
/usr/lib/python2.7/site-packages/urllib3/connectionpool.py(272)_get_conn()
  - return conn or self._new_conn()
   
/usr/lib/python2.7/site-packages/glanceclient/common/https.py(100)_new_conn()
  - return VerifiedHTTPSConnection(host=self.host,

  The code about to run there is this:

  class HTTPSConnectionPool(connectionpool.HTTPSConnectionPool):
  
  HTTPSConnectionPool will be instantiated when a new
  connection is requested to the HTTPSAdapter.This
  implementation overwrites the _new_conn method and
  returns an instances of glanceclient's VerifiedHTTPSConnection
  which handles no compression.

  ssl_compression is hard-coded to False because this will
  be used just when the user sets --no-ssl-compression.
  

  scheme = 'https'

  def _new_conn(self):
  self.num_connections += 1
  return VerifiedHTTPSConnection(host=self.host,
 port=self.port,
 key_file=self.key_file,
 cert_file=self.cert_file,
 cacert=self.ca_certs,
 insecure=self.insecure,
   

[Yahoo-eng-team] [Bug 1316234] Re: Image delete calls slow due to synchronous wait on backend store delete

[nikhil komawar]

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

Title:
  Image delete calls slow due to synchronous wait on backend store
  delete

Status in OpenStack Image Registry and Delivery Service (Glance):
  Won't Fix

Bug description:
  Issue:-
  ---
  Currently, the image delete calls can be very slow if the image being delete 
is large (consisting of multiple chunks esp. in case of swift) or if the 
backend store has slow response time.

  Solution:-
  -
  Make image delete call asynchronous

  Specifically, for v1, call on this line
  https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L1012

  and for v2,  waiting on a fix for the bug
  https://bugs.launchpad.net/glance/+bug/1316233 to enable asynchronous
  deletion of image data from the store.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1316234/+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 1364570] [NEW] missing registry api tests for glance tasks

[nikhil komawar]

Public bug reported:

Although,
https://github.com/openstack/glance/blob/master/glance/db/registry/api.py#L262
has code for db/registry there are missing tests in
https://github.com/openstack/glance/blob/master/glance/tests/functional/db/test_registry.py

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

Title:
  missing registry api tests for glance tasks

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

Bug description:
  Although,
  https://github.com/openstack/glance/blob/master/glance/db/registry/api.py#L262
  has code for db/registry there are missing tests in
  
https://github.com/openstack/glance/blob/master/glance/tests/functional/db/test_registry.py

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1364570/+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 1358904] [NEW] Warning for image_locations.id being empty while running tests

[nikhil komawar]

Public bug reported:

sqlalchemy/sql/default_comparator.py:35: SAWarning: The IN-predicate on 
image_locations.id was invoked with an empty sequence. This results in a 
contradiction, which nonetheless can be expensive to evaluate.  Consider 
alternative strategies for improved performance.
  return o[0](self, self.expr, op, *(other + o[1:]), **kwargs)

warning is shown.

Not sure if this is a bug, need some confirmation.

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

Title:
  Warning for image_locations.id being empty while running tests

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

Bug description:
  sqlalchemy/sql/default_comparator.py:35: SAWarning: The IN-predicate on 
image_locations.id was invoked with an empty sequence. This results in a 
contradiction, which nonetheless can be expensive to evaluate.  Consider 
alternative strategies for improved performance.
return o[0](self, self.expr, op, *(other + o[1:]), **kwargs)

  warning is shown.

  Not sure if this is a bug, need some confirmation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1358904/+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 1356573] [NEW] test_task_schema_api fails with _StringException on OSX

[nikhil komawar]

Public bug reported:

==
FAIL: 
glance.tests.integration.v2.test_tasks_api.TestTasksApi.test_task_schema_api
--
Traceback (most recent call last):
_StringException


This is the result of the failing test.

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

Title:
  test_task_schema_api fails with _StringException on OSX

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

Bug description:
  ==
  FAIL: 
glance.tests.integration.v2.test_tasks_api.TestTasksApi.test_task_schema_api
  --
  Traceback (most recent call last):
  _StringException

  
  This is the result of the failing test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1356573/+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 1346463] [NEW] Glance registry needs notifications config after using oslo.messaging

[nikhil komawar]

Public bug reported:

A good example of this use case is
https://review.openstack.org/#/c/107594 where the notifications need to
be added to the sample config file provided in Glance so that, the patch
would work with devstack.

However, g-reg does not send any notifications so, we need to either
find a way to remove the need for them or merge the g-api and g-reg
configs to avoid this situation.

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

Title:
  Glance registry needs notifications config after using oslo.messaging

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

Bug description:
  A good example of this use case is
  https://review.openstack.org/#/c/107594 where the notifications need
  to be added to the sample config file provided in Glance so that, the
  patch would work with devstack.

  However, g-reg does not send any notifications so, we need to either
  find a way to remove the need for them or merge the g-api and g-reg
  configs to avoid this situation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1346463/+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 1342811] [NEW] Bump up the min version of keystonemiddleware

[nikhil komawar]

Public bug reported:

As per the question on this change :-

https://review.openstack.org/#/c/102352/4/requirements.txt

we could potentially have a invalid version installed in the
environment.

The answer to that question lead us to make the change in the global
requirements:-

https://review.openstack.org/#/c/102352/5/requirements.txt

Keeping this bug open for the further discussion.

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

Title:
  Bump up the min version of keystonemiddleware

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

Bug description:
  As per the question on this change :-

  https://review.openstack.org/#/c/102352/4/requirements.txt

  we could potentially have a invalid version installed in the
  environment.

  The answer to that question lead us to make the change in the global
  requirements:-

  https://review.openstack.org/#/c/102352/5/requirements.txt

  Keeping this bug open for the further discussion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1342811/+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 1339879] Re: gate tests fail due to intermittent failures

[nikhil komawar]

Thanks Clark, for the feedback. Seems like nova/glance bug, removing it
from infra bug list.

** No longer affects: openstack-ci

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

Title:
  gate tests fail due to intermittent failures

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

Bug description:
  Tests in the Glance gate seem to be failing due to the following
  error:-

  Details: The server has either erred or is incapable of performing the
  requested operation.

  2014-07-09 16:38:38.863 | ==
  2014-07-09 16:38:38.863 | Failed 1 tests - output below:
  2014-07-09 16:38:38.863 | ==
  2014-07-09 16:38:38.863 | 
  2014-07-09 16:38:38.863 | 
tempest.api.compute.images.test_images.ImagesTestXML.test_delete_saving_image[gate]
  2014-07-09 16:38:38.864 | 
---
  2014-07-09 16:38:38.864 | 
  2014-07-09 16:38:38.864 | Captured traceback:
  2014-07-09 16:38:38.864 | ~~~
  2014-07-09 16:38:38.864 | Traceback (most recent call last):
  2014-07-09 16:38:38.864 |   File 
tempest/api/compute/images/test_images.py, line 42, in 
test_delete_saving_image
  2014-07-09 16:38:38.864 | resp, body = 
self.client.delete_image(image['id'])
  2014-07-09 16:38:38.864 |   File 
tempest/services/compute/xml/images_client.py, line 136, in delete_image
  2014-07-09 16:38:38.864 | return self.delete(images/%s % 
str(image_id))
  2014-07-09 16:38:38.864 |   File tempest/common/rest_client.py, line 
224, in delete
  2014-07-09 16:38:38.864 | return self.request('DELETE', url, 
extra_headers, headers, body)
  2014-07-09 16:38:38.865 |   File tempest/common/rest_client.py, line 
430, in request
  2014-07-09 16:38:38.865 | resp, resp_body)
  2014-07-09 16:38:38.865 |   File tempest/common/rest_client.py, line 
526, in _error_checker
  2014-07-09 16:38:38.865 | raise exceptions.ServerFault(message)
  2014-07-09 16:38:38.865 | ServerFault: Got server fault
  2014-07-09 16:38:38.865 | Details: The server has either erred or is 
incapable of performing the requested operation.
  2014-07-09 16:38:38.865 | 


  ref. http://logs.openstack.org/51/105751/1/check/check-tempest-dsvm-
  full/5f646ca/console.html#_2014-07-09_16_38_38_863

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1339879/+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 1336488] [NEW] Incorrect example url in glance.store.swift

[nikhil komawar]

Public bug reported:

Following the change the way we store glance location as per
https://review.openstack.org/#/c/98722

we need to modify the example url in SingleTenantStore and
MultiTenantStore to indicate all appropriate urls as per the
situtation..

https://github.com/openstack/glance/blob/master/glance/store/swift.py#L647
https://github.com/openstack/glance/blob/master/glance/store/swift.py#L729

** Affects: glance
 Importance: Undecided
 Status: New

** Description changed:

  Following the change the way we store glance location as per
+ https://review.openstack.org/#/c/98722
  
  we need to modify the example url in SingleTenantStore and
  MultiTenantStore to indicate all appropriate urls as per the
  situtation..
  
  https://github.com/openstack/glance/blob/master/glance/store/swift.py#L647
  https://github.com/openstack/glance/blob/master/glance/store/swift.py#L729

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

Title:
  Incorrect example url in glance.store.swift

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

Bug description:
  Following the change the way we store glance location as per
  https://review.openstack.org/#/c/98722

  we need to modify the example url in SingleTenantStore and
  MultiTenantStore to indicate all appropriate urls as per the
  situtation..

  https://github.com/openstack/glance/blob/master/glance/store/swift.py#L647
  https://github.com/openstack/glance/blob/master/glance/store/swift.py#L729

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1336488/+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 1316234] [NEW] Image delete calls slow due to synchronous wait on backend store delete

[nikhil komawar]

Public bug reported:

Issue:-
---
Currently, the image delete calls can be very slow if the image being delete is 
large (consisting of multiple chunks esp. in case of swift) or if the backend 
store has slow response time.

Solution:-
-
Make image delete call asynchronous

Specifically, for v1, call on this line
https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L1012

and for v2,  waiting on a fix for the bug
https://bugs.launchpad.net/glance/+bug/1316233 to enable asynchronous
deletion of image data from the store.

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

Title:
  Image delete calls slow due to synchronous wait on backend store
  delete

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

Bug description:
  Issue:-
  ---
  Currently, the image delete calls can be very slow if the image being delete 
is large (consisting of multiple chunks esp. in case of swift) or if the 
backend store has slow response time.

  Solution:-
  -
  Make image delete call asynchronous

  Specifically, for v1, call on this line
  https://github.com/openstack/glance/blob/master/glance/api/v1/images.py#L1012

  and for v2,  waiting on a fix for the bug
  https://bugs.launchpad.net/glance/+bug/1316233 to enable asynchronous
  deletion of image data from the store.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1316234/+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 1316233] [NEW] image data not deleted while deleting image in v2 api

[nikhil komawar]

Public bug reported:

This is reopen for the bug 1039897 (
https://bugs.launchpad.net/glance/+bug/1039897 ). Description as per the
old bugs description.

Seems the code has been changed since that got merged in and needs a fix
again.

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

Title:
  image data not deleted while deleting image in v2 api

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

Bug description:
  This is reopen for the bug 1039897 (
  https://bugs.launchpad.net/glance/+bug/1039897 ). Description as per
  the old bugs description.

  Seems the code has been changed since that got merged in and needs a
  fix again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1316233/+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 1294775] [NEW] Image needs to be created before uploading the data bits

[nikhil komawar]

Public bug reported:

Currently, we need to have a Image object (or record) to be able to set
it's data bits.

We need an alternative mechanism for Image creation in cases where
failure in uploading data bits should fail Image creation.

Example use case:
- Say an import task fails while uploading data bits to the data store. The 
Image would be stuck in the saving/queued state indefinitely resulting in 
superfluous Image entries in the users Image list.

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

Title:
  Image needs to be created before uploading the data bits

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

Bug description:
  Currently, we need to have a Image object (or record) to be able to
  set it's data bits.

  We need an alternative mechanism for Image creation in cases where
  failure in uploading data bits should fail Image creation.

  Example use case:
  - Say an import task fails while uploading data bits to the data store. The 
Image would be stuck in the saving/queued state indefinitely resulting in 
superfluous Image entries in the users Image list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1294775/+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 1287951] [NEW] incorrect response for DELETE /v2/tasks/{task_id}

[nikhil komawar]

Public bug reported:

A call to DELETE /v2/tasks/{task_id} for an existing task_id returns a
404 (which is obviously incorrect because a GET on the same URL returns
a task detail response).

The response should be 405 (Method Not Allowed). From the spec:
The method specified in the Request-Line is not allowed for the resource 
identified by the Request-URI. The response MUST include an Allow header 
containing a list of valid methods for the requested resource.

Note that an Allow header must be included in the response.

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

Title:
  incorrect response for DELETE /v2/tasks/{task_id}

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

Bug description:
  A call to DELETE /v2/tasks/{task_id} for an existing task_id returns a
  404 (which is obviously incorrect because a GET on the same URL
  returns a task detail response).

  The response should be 405 (Method Not Allowed). From the spec:
  The method specified in the Request-Line is not allowed for the resource 
identified by the Request-URI. The response MUST include an Allow header 
containing a list of valid methods for the requested resource.

  Note that an Allow header must be included in the response.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1287951/+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 1285257] [NEW] glance-cache-pruner does not account incomplete dir when checking for cache size to prune

[nikhil komawar]

Public bug reported:

Proxy on behalf of Sulochan Acharya ( sulochan.acha...@rackspace.co.uk
):-

Taking in to account incomplete dir when the pruner is run will create a case 
where if we delete old images taking the new incomplete image in account, and 
the new incomplete image fails, then we basically (wastefully ?) deleted cached 
image for something that failed. This is not really good. But if the image goes 
though then we will end up deleting those cache anyway, so i guess it a give 
and take scenario. And we gain by deleting taking incomplete into account, so 
that the disk does not get full. 
Any thoughts ?

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

Title:
  glance-cache-pruner does not account incomplete dir when checking for
  cache size to prune

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

Bug description:
  Proxy on behalf of Sulochan Acharya ( sulochan.acha...@rackspace.co.uk
  ):-

  Taking in to account incomplete dir when the pruner is run will create a case 
where if we delete old images taking the new incomplete image in account, and 
the new incomplete image fails, then we basically (wastefully ?) deleted cached 
image for something that failed. This is not really good. But if the image goes 
though then we will end up deleting those cache anyway, so i guess it a give 
and take scenario. And we gain by deleting taking incomplete into account, so 
that the disk does not get full. 
  Any thoughts ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1285257/+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 1284975] [NEW] methods succeed and fail in Task class reference non-existent var

[nikhil komawar]

Public bug reported:

https://github.com/openstack/glance/blob/master/glance/domain/__init__.py line 
376 -- result is referenced however, does not exist in the class definition
and
https://github.com/openstack/glance/blob/master/glance/domain/__init__.py line 
382 -- message is referenced however, does not exist in the class definition

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

Title:
  methods succeed and fail in Task class reference non-existent var

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

Bug description:
  https://github.com/openstack/glance/blob/master/glance/domain/__init__.py 
line 376 -- result is referenced however, does not exist in the class 
definition
  and
  https://github.com/openstack/glance/blob/master/glance/domain/__init__.py 
line 382 -- message is referenced however, does not exist in the class 
definition

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1284975/+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 1275062] Re: image location is logged when authentication to store fails

[nikhil komawar]

Thanks for pointing that out ttx, however we do not have this issue in
stable/grizzly.

Please find the code for grizzly here:
https://github.com/openstack/glance/blob/stable/grizzly/glance/store/__init__.py#L393

** Changed in: glance/grizzly
   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/1275062

Title:
  image location is logged when authentication to store fails

Status in OpenStack Image Registry and Delivery Service (Glance):
  Fix Committed
Status in Glance grizzly series:
  Invalid
Status in Glance havana series:
  In Progress
Status in OpenStack Security Advisories:
  Triaged

Bug description:
  WARNING glance.store [-] Get image UUID data from {'url':
  u'swift+https://X@my_auth_url.com/v2.0/my-images/uuid,
  'metadata': {}} failed: Auth GET failed: https://my_auth_url.com
  RESP_CODE

  19:13:05.027  ERROR glance.store [-] Glance tried all locations to get
  data for image UUID but all have failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1275062/+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 1258691] Re: don't ignore H306 while running tests

[nikhil komawar]

This has been resolved by https://review.openstack.org/#/c/62321/ .
However, that MP did not link to the bug.

** Changed in: glance
   Status: Confirmed = Fix Released

** Changed in: glance
   Status: Fix Released = Fix Committed

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

Title:
  don't ignore H306 while running tests

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

Bug description:
  we should ensure that the imports are in alphabetical order and remove
  H306 ignore flag from tox.ini

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1258691/+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 1258691] [NEW] don't ignore H306 while running tests

[nikhil komawar]

Public bug reported:

we should ensure that the imports are in alphabetical order and remove
H306 ignore flag from tox.ini

** Affects: glance
 Importance: Undecided
 Assignee: nikhil komawar (nikhil-komawar)
 Status: New

** Changed in: glance
 Assignee: (unassigned) = nikhil komawar (nikhil-komawar)

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

Title:
  don't ignore H306 while running tests

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

Bug description:
  we should ensure that the imports are in alphabetical order and remove
  H306 ignore flag from tox.ini

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1258691/+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 1257949] [NEW] fix task.owner to be nullable=False in models.py

[nikhil komawar]

Public bug reported:

We currently, do not allow NULL owner for tasks and models.py lets it be
NULL however, the tasks table ensures that it does not set NULL owner.

So, we do not need migration - just need fix in the code patch for this.

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

Title:
  fix task.owner to be nullable=False in models.py

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

Bug description:
  We currently, do not allow NULL owner for tasks and models.py lets it
  be NULL however, the tasks table ensures that it does not set NULL
  owner.

  So, we do not need migration - just need fix in the code patch for
  this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1257949/+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