[Yahoo-eng-team] [Bug 1710890] [NEW] Image is not available when launch instance

[Kairat Kushaev]

Public bug reported:

it was reproduced against master.
Steps to reproduce:
1. Go to Horizon-> Images under admin
2. Create public image of any type
3. push [Launch] button on created image.
4. go to source tab.
5. Choose Boot source= Image
6. Try to find image created in "Select one" table  
AR: created image is not listed in the table
ER: created image is available in the table.

** Affects: horizon
 Importance: Undecided
 Status: New

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

Title:
  Image is not available when launch instance

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  it was reproduced against master.
  Steps to reproduce:
  1. Go to Horizon-> Images under admin
  2. Create public image of any type
  3. push [Launch] button on created image.
  4. go to source tab.
  5. Choose Boot source= Image
  6. Try to find image created in "Select one" table  
  AR: created image is not listed in the table
  ER: created image is available in the table.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1710890/+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 1638193] [NEW] Cannot specify endpoint type when managing glance cache

[Kairat Kushaev]

Public bug reported:

When we pass internalURL for glance-cache-manage by exporting environment 
variable "GLANCE_ENDPOINT_TYPE=internalURL",
it doesn't get the endpoint for internalURL from glance, rather it gets public 
endpoint.

The code snippet from the below link:

https://github.com/openstack/glance/blob/stable/mitaka/glance/common/auth.py#L215-L217

Here while retrieving endpoint for glance service, there is no
feasibility to pass endpoint_type, so it fetches by default
endpoint_type which is publicURL. In most cases cache manage and other
APIs communicates with internalURL/adminURL only and should not
communicate to publicURL. So it is required to allow users to specify
which endpoint to choose.

** Affects: glance
 Importance: Undecided
 Assignee: Kairat Kushaev (kkushaev)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  Cannot specify endpoint type when managing glance cache

Status in Glance:
  New

Bug description:
  When we pass internalURL for glance-cache-manage by exporting environment 
variable "GLANCE_ENDPOINT_TYPE=internalURL",
  it doesn't get the endpoint for internalURL from glance, rather it gets 
public endpoint.

  The code snippet from the below link:

  
https://github.com/openstack/glance/blob/stable/mitaka/glance/common/auth.py#L215-L217

  Here while retrieving endpoint for glance service, there is no
  feasibility to pass endpoint_type, so it fetches by default
  endpoint_type which is publicURL. In most cases cache manage and other
  APIs communicates with internalURL/adminURL only and should not
  communicate to publicURL. So it is required to allow users to specify
  which endpoint to choose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1638193/+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 1491823] Re: Glance return 405 error when we try update element in bloblist

[Kairat Kushaev]

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

Title:
  Glance return 405 error when we try update element in bloblist

Status in Glance:
  Won't Fix

Bug description:
  ENVIRONMENT: devstack, Glance (master, 03.09.2015)

  STEPS TO REPRODUCE:
  We have artifact:
  {"description": null, "published_at": null, "tags": [], "created_at": 
"2015-09-02T09:29:27.00", "type_name": "MyArtifact", "updated_at": 
"2015-09-02T09:29:27.00", "visibility": "private", "id": 
"917ec8d2-44fb-4445-abb7-e28b65f7f07b", "type_version": "2.0", "state": 
"creating", "version": "12.0.0", "prop1": null, "prop2": null, "owner": 
"13db150f0268414ca7f2d81ea60a8205", "image_file": null, "deleted_at": null, 
"screenshots": [{"checksum": "db78f300f6509d4fc131cb4a23fd9356", 
"download_link": 
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/0/download",
 "size": 14}, {"checksum": "6807f2db24acbf20a715b41665c99a18", "download_link": 
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/1/download",
 "size": 14}, {"checksum": "db78f300f6509d4fc131cb4a23fd9356", "download_link": 
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/2/download",
 "size": 14}], "int_list": null, "name": "artifact1"}

  Send request:
  curl -H "X-Auth-Token: 3309284e1ff543e89ac57f9b0a643ad3" -H 
"Content-Type:octet-stream"  -X PUT -d '{"data": "new_data"}' 
http://172.18.76.44:9292/v3/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/0
 -i

  EXPECTED RESULT:
  status code 200 and update the element in screenshots

  ACTUAL RESULT:
  HTTP/1.1 405 Method Not Allowed
  Content-Length: 187
  Content-Type: text/html; charset=UTF-8
  X-Openstack-Request-Id: req-ad97df1c-0fb6-4244-9ce6-6fada6bf38a7
  Date: Thu, 03 Sep 2015 12:30:45 GMT

  
   
    405 Method Not Allowed
   
   
    405 Method Not Allowed
    The method PUT is not allowed for this resource. 

   
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1491823/+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 1489941] Re: v2 client sorts on name in wrong direction

[Kairat Kushaev]

Marked as Won't fix. See reason in comment #10. Also python-glanceclient
is going to be deprecated in favor of openstackclient. So the bug marked
as won't fix for glanceclient too.

** Changed in: glance
   Status: In Progress => Won't Fix

** Changed in: python-glanceclient
   Status: New => 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/1489941

Title:
  v2 client sorts on name in wrong direction

Status in Glance:
  Won't Fix
Status in python-glanceclient:
  Won't Fix

Bug description:
  
  The v1 client sorts images by name alphabetically:

  
  $ glance --os-image-api-version 1 image-list  --sort-key name 
  
+--+-+-+--+---++
  | ID   | Name| Disk Format | 
Container Format | Size  | Status |
  
+--+-+-+--+---++
  | 7d1923d7-68e8-4a8e-b23e-a7c77f8117fd | | raw | 
bare | 1034  | active |
  | 5e9dc64e-7c05-431c-b81f-ae6a212353e8 | | qcow2   | 
bare |   | queued |
  | 6802e222-6eac-45c6-8c9f-0d62aed26406 | | qcow2   | 
bare | 145   | active |
  | 7af0d66b-5b48-48a6-a6d9-c2cd3eafa83e | | |  
|   | queued |
  | dde89c3c-c8af-46a4-87b0-f39ed6c61c42 | | raw | 
bare | 2 | active |
  | 262ac5aa-e580-4bec-a3b2-580924425fd5 | | raw | 
bare | 2 | active |
  | 4cc5b305-43a7-495e-8e67-16d95629621e | | raw | 
bare | 2 | active |

  The v2 client sorts in reverse alphabetical:

  $ glance --os-image-api-version 2 image-list  --sort-key name
  +--+-+
  | ID   | Name|
  +--+-+
  | b16dbfb2-f435-40a8-aa08-2aadaee99cd1 | trusty2 |
  | cc658de9-039a-46d7-829a-dc1f08cac153 | test1   |
  | 2fa0f342-623e-423f-8faa-70f000b3e4cc | test1   |
  | c95a4ee7-28d0-4fd5-86c6-fe9816fcef23 | test1   |
  | d75354ed-ef63-4f41-9d53-a0d67394d1a3 | test1   |
  | ecc24d0d-140c-484d-ae42-427e60be9270 | test1   |
  | f3b996a9-469c-4882-864b-fef0cd24429d | test1   |

  
  adding the sort dir gives the same result as v1:

  $ glance --os-image-api-version 2 image-list  --sort-key name --sort-dir asc 
  +--+-+
  | ID   | Name|
  +--+-+
  | 7d1923d7-68e8-4a8e-b23e-a7c77f8117fd | |
  | 5e9dc64e-7c05-431c-b81f-ae6a212353e8 | |
  | 6802e222-6eac-45c6-8c9f-0d62aed26406 | |
  | 7af0d66b-5b48-48a6-a6d9-c2cd3eafa83e | |
  | dde89c3c-c8af-46a4-87b0-f39ed6c61c42 | |
  | 262ac5aa-e580-4bec-a3b2-580924425fd5 | |
  | 4cc5b305-43a7-495e-8e67-16d95629621e | |

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1489941/+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 1493833] Re: Glance returns 500 error when trying to replace non-exising blob item in artifact blob-list

[Kairat Kushaev]

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

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

Title:
  Glance returns 500 error when trying to replace non-exising blob item
  in artifact blob-list

Status in Glance:
  Invalid

Bug description:
  Steps to reproduce:
  1. Create an artifact (type=MyArtifact)
  2. Update artifact blob list with some value:
  curl -H "X-Auth-Token: 1d5532fa812548f6a41bfd422f0d36a9" -H 
"Content-Type:application/octet-stream" -X POST -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/6d16c3e9-26d6-4abd-8ad6-e70e66e31aab/screenshots
 -i
  3. Try to replace non-existing blob item in blob list
  curl -H "X-Auth-Token: 1d5532fa812548f6a41bfd422f0d36a9" -H 
"Content-Type:application/octet-stream" -X PUT -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/6d16c3e9-26d6-4abd-8ad6-e70e66e31aab/screenshots/1
 -i
  AR: Internal Server Error
  ER: BadRequest Error

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1493833/+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 1491815] Re: Glance return 404 error when we try delete element in bloblist/blob

[Kairat Kushaev]

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

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

Title:
  Glance return 404 error when we try delete element in bloblist/blob

Status in Glance:
  Invalid

Bug description:
  ENVIRONMENT: devstack, Glance (master, 03.09.2015)

  STEPS TO REPRODUCE:
  We have artifact:
  {"description": null, "published_at": null, "tags": [], "created_at": 
"2015-09-02T09:29:27.00", "type_name": "MyArtifact", "updated_at": 
"2015-09-02T09:29:27.00", "visibility": "private", "id": 
"917ec8d2-44fb-4445-abb7-e28b65f7f07b", "type_version": "2.0", "state": 
"creating", "version": "12.0.0", "prop1": null, "prop2": null, "owner": 
"13db150f0268414ca7f2d81ea60a8205", "image_file": null, "deleted_at": null, 
"screenshots": [{"checksum": "db78f300f6509d4fc131cb4a23fd9356", 
"download_link": 
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/0/download",
 "size": 14}, {"checksum": "6807f2db24acbf20a715b41665c99a18", "download_link": 
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/1/download",
 "size": 14}, {"checksum": "db78f300f6509d4fc131cb4a23fd9356", "download_link": 
"/artifacts/myartifact/v2.0/917ec8d2-44fb-4445-abb7-e28b65f7f07b/screenshots/2/download",
 "size": 14}], "int_list": null, "name": "artifact1"}

  Send request:
  curl -H "X-Auth-Token: 3309284e1ff543e89ac57f9b0a643ad3" -X DELETE 
http://172.18.76.44:9292/v3/artifacts/myartifact/v2.0/917ec8d2-44fb-444528b65f7f07b/screenshots/0
 -i

  EXPECTED RESULT:
  status code 204 and delete the item in screenshots

  ACTUAL RESULT:
  HTTP/1.1 404 Not Found
  Content-Length: 154
  Content-Type: text/html; charset=UTF-8
  X-Openstack-Request-Id: req-adc1f847-fca2-4419-bda0-058eebb9f8da
  Date: Thu, 03 Sep 2015 12:21:24 GMT

  
   
404 Not Found
   
   
404 Not Found
The resource could not be found.


   
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1491815/+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 1493826] Re: Glance doesn't replace blob property correctly in artifacts

[Kairat Kushaev]

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

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

Title:
  Glance doesn't replace blob property correctly in artifacts

Status in Glance:
  Invalid

Bug description:
  Version: glance liberty master (latest 04.09.15)
  Steps to reproduce:
  1. Create an artifact(type=MyArtifact) with blob property (image_file)
  2. Update blob property image_file with some value:
  curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H 
"Content-Type:application/octet-stream" -X POST -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/e4e58687-dbb9-4fa2-af53-b4addc15bc99/image_file
 -i
  3. Request blob property replace:
  curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H 
"Content-Type:application/octet-stream" -X PUT -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/e4e58687-dbb9-4fa2-af53-b4addc15bc99/image_file
 -i
  AR: 405 Method not allowed
  ER: 200 OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1493826/+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 1576621] Re: Snapshots are alway made in raw and not qcow2

[Kairat Kushaev]

Hello Mark,
glance does not convert images during the upload. It just stores bits.
If you look at the Ceph documentation looks like there is troubles with qcow2:
http://docs.ceph.com/docs/master/rbd/rbd-openstack/

Ceph doesn’t support QCOW2 for hosting a virtual machine disk. Thus if
you want to boot virtual machines in Ceph (ephemeral backend or boot
from volume), the Glance image format must be RAW.

So I guess nova(or Cinder or other component that provides bits for
Glance image) always specifies RAW format always when ceph is used.

I hope this thread also help you.

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

Title:
  Snapshots are alway made in raw and not qcow2

Status in Glance:
  Invalid

Bug description:
  Hi,
  I am using the same version of openstack in two deployments. When I take a 
snapshot in one environment its is saved in qcow2 but in the other it is saved 
as raw. The raw format saves an image with the size of the flavour. qcow2 
format saves an image the size of the actual used disk space. 

  The version I am using of openstack is: Version: 2015.1.1

  The version of Glance is: 0.17.1

  I could not ascertain any difference between the glance configuration
  in both environments. The only difference is that the CEPH file system
  is used in the deployment where snapshots are saved in raw. However we
  are able to upload images in qcow2 nonetheless.

  Thank you,
  Mark Donovan

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1576621/+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 1489059] Re: "db type could not be determined" running py34

[Kairat Kushaev]

Fixed in Glance 12.0.0.0b3

** No longer affects: glance-store

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

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

Title:
  "db type could not be determined" running py34

Status in Aodh:
  Fix Released
Status in Barbican:
  Fix Released
Status in Bareon:
  Fix Released
Status in Cinder:
  In Progress
Status in cloudkitty:
  Fix Committed
Status in Fuel for OpenStack:
  In Progress
Status in Glance:
  Fix Released
Status in hacking:
  Fix Released
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-lib:
  Fix Committed
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystoneauth:
  Fix Released
Status in keystonemiddleware:
  Fix Released
Status in kolla:
  Fix Released
Status in Manila:
  Fix Released
Status in networking-midonet:
  Fix Released
Status in networking-ofagent:
  Fix Released
Status in neutron:
  Fix Released
Status in python-glanceclient:
  Fix Released
Status in python-keystoneclient:
  Fix Released
Status in python-muranoclient:
  Fix Released
Status in python-solumclient:
  Fix Released
Status in python-swiftclient:
  In Progress
Status in Rally:
  Fix Released
Status in Sahara:
  Fix Released
Status in OpenStack Search (Searchlight):
  Fix Released
Status in senlin:
  Fix Released
Status in tap-as-a-service:
  Fix Released
Status in tempest:
  Fix Released
Status in zaqar:
  Fix Released
Status in python-ironicclient package in Ubuntu:
  Fix Committed

Bug description:
  When running tox for the first time, the py34 execution fails with an
  error saying "db type could not be determined".

  This issue is know to be caused when the run of py27 preceeds py34 and
  can be solved erasing the .testrepository and running "tox -e py34"
  first of all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1489059/+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 1398314] Re: The API doesn't return nullable fields when they're null

[Kairat Kushaev]

Won't fix due to Flavio's comment.

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

Title:
  The API doesn't return nullable fields when they're null

Status in Glance:
  Fix Released
Status in python-glanceclient:
  Won't Fix

Bug description:
  The schema filter method removes all fields that are null from the
  object schema. This is causing incompatibilities from the client side
  and it also makes glance's responses inconsistent.

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

[Kairat Kushaev]

Fix released in glanceclient 0.17.3 as per Matt's comment:
https://review.openstack.org/#/c/246996/

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

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

Status in Glance:
  Invalid
Status in keystonemiddleware:
  Fix Released
Status in openstack-ansible:
  Fix Released
Status in openstack-ansible kilo series:
  Fix Released
Status in openstack-ansible liberty series:
  Fix Released
Status in openstack-ansible trunk series:
  Fix Released
Status in OpenStack-Gate:
  Fix Committed
Status in oslo.vmware:
  Fix Released
Status in python-glanceclient:
  Fix Released

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, 

[Yahoo-eng-team] [Bug 1563174] Re: Using LOG.warning replace LOG.warn

[Kairat Kushaev]

https://review.openstack.org/#/c/262237/ - see comments here. Oslo.log
did that work for us=)

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

Title:
  Using LOG.warning replace LOG.warn

Status in Glance:
  Invalid

Bug description:
  Python 3 deprecated the logger.warn method [1] so I prefer to use warning to 
avoid DeprecationWarning. 
  If we are using logger from oslo.log, warn is still valid [2]. But i think 
switching to LOG.warning is better.

  [1] https://docs.python.org/3/library/logging.html#logging.warning
  [2] https://github.com/openstack/oslo.log/blob/master/oslo_log/log.py#L85

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1563174/+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 1552132] [NEW] keystone not found when using single tenant store with keystone v2

[Kairat Kushaev]

Public bug reported:

recent patch in glance is breaking RDO CI and Puppet OpenStack CI
our configuration is here: 
http://logs.openstack.org/45/286845/2/check/gate-puppet-openstack-integration-scenario002-tempest-dsvm-centos7/3c59ce2/logs/etc/glance/
we use swift backend FYI
the error is here: 
http://logs.openstack.org/45/286845/2/check/gate-puppet-openstack-integration-scenario002-tempest-dsvm-centos7/3c59ce2/logs/glance/api.txt.gz#_2016-03-01_22_30_41_926
we're not sure but we think it's related to 
https://github.com/openstack/glance_store/commit/1b782cee8552ec02f7303ee6f9ba9d1f2c180d07
 if one of you can have a look, that would be cool
maybe we do something wrong in Puppet manifests

** Affects: glance-store
 Importance: Undecided
 Assignee: Kairat Kushaev (kkushaev)
 Status: New

** Project changed: glance => glance-store

** Changed in: glance-store
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  keystone not found when using single tenant store with keystone v2

Status in glance_store:
  New

Bug description:
  recent patch in glance is breaking RDO CI and Puppet OpenStack CI
  our configuration is here: 
http://logs.openstack.org/45/286845/2/check/gate-puppet-openstack-integration-scenario002-tempest-dsvm-centos7/3c59ce2/logs/etc/glance/
  we use swift backend FYI
  the error is here: 
http://logs.openstack.org/45/286845/2/check/gate-puppet-openstack-integration-scenario002-tempest-dsvm-centos7/3c59ce2/logs/glance/api.txt.gz#_2016-03-01_22_30_41_926
  we're not sure but we think it's related to 
https://github.com/openstack/glance_store/commit/1b782cee8552ec02f7303ee6f9ba9d1f2c180d07
   if one of you can have a look, that would be cool
  maybe we do something wrong in Puppet manifests

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance-store/+bug/1552132/+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 1538482] Re: url_for does not exists for service catalog

[Kairat Kushaev]

Looks like passing Service Catalog requires some kind of spec.
So I am deleting Glance as affected project.

** No longer affects: glance

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

Title:
  url_for does not exists for service catalog

Status in glance_store:
  Fix Released

Bug description:
  Here we introduced url_for method for service_catalog:
  https://review.openstack.org/#/c/250857/

  Unfortunately, we are parsing service_catalog and passing it to glance_store 
as a list in context:
  
https://github.com/openstack/glance/blob/master/glance/api/middleware/context.py#L117

  Because of this current glance_store master is broken when swift multi-tenant 
store is enabled with an error like this:
  list doesn't have an attribute url_for.
  That happens every time somebody would like to download/upload images.

  
  We also need to pass ServiceCatalog from glance to glance_store. It is better 
than initializing ServiceCatalog in glance_store. It alos saves a lot time when 
upgrading from Keystone v2 to v3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance-store/+bug/1538482/+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 1544469] [NEW] Use Keystone Service catalog to search endpoints

[Kairat Kushaev]

Public bug reported:

Glance uses custom function to search endpoint in service catalog:
https://github.com/openstack/glance/blob/master/glance/common/auth.py#L259
But that functionality is also available in python-keystoneclient:
https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/service_catalog.py#L352
So we can reduce code duplication and just simply use the logic from 
keystoneclient to search endpoint.

P.S. Looks like we need to initialize ServiceCatalog in request context.
It looks like we need separate attribute for ServiceCatalog(and
deprecate current attribute in request context) so need some additional
work.

** Affects: glance
 Importance: Undecided
 Assignee: Kairat Kushaev (kkushaev)
 Status: In Progress

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  Use Keystone Service catalog to search endpoints

Status in Glance:
  In Progress

Bug description:
  Glance uses custom function to search endpoint in service catalog:
  https://github.com/openstack/glance/blob/master/glance/common/auth.py#L259
  But that functionality is also available in python-keystoneclient:
  
https://github.com/openstack/python-keystoneclient/blob/master/keystoneclient/service_catalog.py#L352
  So we can reduce code duplication and just simply use the logic from 
keystoneclient to search endpoint.

  P.S. Looks like we need to initialize ServiceCatalog in request
  context. It looks like we need separate attribute for
  ServiceCatalog(and deprecate current attribute in request context) so
  need some additional work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1544469/+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 1521581] Re: v2 - "readOnly" key should be used in schemas

[Kairat Kushaev]

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

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

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

** Changed in: python-glanceclient
 Assignee: (unassigned) => zwei (suifeng20)

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

Title:
  v2 - "readOnly" key should be used in schemas

Status in Glance:
  Fix Released
Status in python-glanceclient:
  In Progress

Bug description:
  Currently, the way object properties are labelled read-only is through
  the description, like so:

  "status": {
  "enum": [
  "queued",
  "saving",
  "active",
  "killed",
  "deleted",
  "pending_delete",
  "deactivated"
  ],
  "type": "string",
  "description": "Status of the image (READ-ONLY)"
  }

  
  This is not the recommended way to indicate read-only status. The "readOnly" 
property should be used instead:

  "status": {
  "enum": [
  "queued",
  "saving",
  "active",
  "killed",
  "deleted",
  "pending_delete",
  "deactivated"
  ],
  "type": "string",
  "readOnly": true,
  "description": "Status of the image"
  }

  
  Further link for reference: 
http://json-schema.org/latest/json-schema-hypermedia.html#anchor15

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1521581/+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 1442682] Re: Gate problems with gate-tempest-dsvm-neutron-src-python-glanceclient-juno

[Kairat Kushaev]

Juno is EOL, so marking this as Won't Fix.

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

Title:
  Gate problems with gate-tempest-dsvm-neutron-src-python-glanceclient-
  juno

Status in Glance:
  Won't Fix

Bug description:
  
  Not sure which project to log this against. Going with 'glance' for now.

  Seen on a couple of separate client changes, only 'gate-tempest-dsvm-
  neutron-src-python-glanceclient-juno' failing (I assume this is
  against the juno stable server?)

  
  eg 
http://logs.openstack.org/58/115958/6/check/gate-tempest-dsvm-neutron-src-python-glanceclient-juno/8381e11/logs/devstacklog.txt.gz

  
   2015-04-10 08:49:50.238 | WARNING: urllib3.connectionpool HttpConnectionPool 
is full, discarding connection: 127.0.0.1
   2015-04-10 08:49:50.241 | ERROR: openstack 400 Bad Request: Client 
disconnected before sending all data to backend (HTTP  400)
   2015-04-10 08:49:50.274 | + ramdisk_id=
   2015-04-10 08:49:50.274 | + openstack --os-token 
6c7c8feefd304cdab694b24c7168c1dc --os-url http://127.0.0.1:9292 image  create 
cirros-0.3.2-x86_64-uec --public --container-format ami --disk-format ami
   2015-04-10 08:50:23.688 | WARNING: urllib3.connectionpool HttpConnectionPool 
is full, discarding connection: 127.0.0.1
   2015-04-10 08:50:23.689 | ERROR: openstack 400 Bad Request: Client 
disconnected before sending all data to backend (HTTP 400)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1442682/+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 1535231] Re: md-meta with case insensitive string has problem when creating

[Kairat Kushaev]

We can add some additional info about case-insensitivity to exception
message but that must be fixed in glance.

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

** No longer affects: python-glanceclient

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

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

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  md-meta with case insensitive string has problem when creating

Status in Glance:
  Confirmed

Bug description:
  [Summary]
  md-meta with case sensitive has problem when creating

  [Topo]
  devstack all-in-one node

  [Description and expect result]
  can create case sensitive md-meta

  [Reproduceable or not]
  reproduceable 

  [Recreate Steps]
  1) there is a md-tag named "ab" for namespace "new-ns":
  stack@45-59:~/devstack$ glance md-tag-create --name ab new-ns
  ++--+
  | Property   | Value|
  ++--+
  | created_at | 2016-01-18T16:36:13Z |
  | name   | ab   |
  | updated_at | 2016-01-18T16:36:13Z |
  ++--+
  stack@45-59:~/devstack$ glance md-tag-list new-ns
  +--+
  | name |
  +--+
  | ab   |
  +--+

  
  2)if create a new md-tag named "AB", conflict occur:   >>>ISSUE
  stack@45-59:~/devstack$ glance md-tag-create --name AB new-ns
  409 Conflict: A metadata tag with name=AB already exists in namespace=new-ns.
  stack@45-59:~/devstack$ 

  3)but if there is no md-tag "ab", the md-tag "AB" can be created.
  stack@45-59:~/devstack$ glance md-tag-delete new-ns ab
  stack@45-59:~/devstack$ 
  stack@45-59:~/devstack$ glance md-tag-list new-ns
  +--+
  | name |
  +--+
  +--+
  stack@45-59:~/devstack$ glance md-tag-create --name AB new-ns
  ++--+
  | Property   | Value|
  ++--+
  | created_at | 2016-01-18T16:37:20Z |
  | name   | AB   |
  | updated_at | 2016-01-18T16:37:20Z |
  ++--+

  [Configration]
  reproduceable bug, no need

  [logs]
  reproduceable bug, no need

  [Root cause anlyze or debug inf]
  reproduceable bug

  [Attachment]
  None

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1535231/+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 1387055] Re: glanceclient/shell.py:592: raise exc.CommandError("Invalid OpenStack Identity credentials.")

[Kairat Kushaev]

Closing due to inactivity. Latest devstack has been installed
successfully.

** Changed in: glance
   Status: New => Won't Fix

** Changed in: python-glanceclient
   Status: New => 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/1387055

Title:
  glanceclient/shell.py:592:raise exc.CommandError("Invalid
  OpenStack Identity credentials.")

Status in devstack:
  New
Status in Glance:
  Won't Fix
Status in python-glanceclient:
  Won't Fix

Bug description:
  When using DevStack to install OpenStack, I got the following error:

  2014-10-29 15:06:45.890 | ++ glance --os-auth-token 
12a7b1359dc044ff9e9e1c81a2390152 --os-image-url http://192.168.56.101:9292 
image-create --name cirros-0.3.1-x86_64-uec-kernel --is-public True 
--container-format aki --disk-format aki
  2014-10-29 15:06:45.915 | ++ read data
  2014-10-29 15:06:50.456 | Invalid OpenStack Identity credentials.
  2014-10-29 15:06:50.584 | + KERNEL_ID=
  2014-10-29 15:06:50.640 | + '[' -n 
/home/xtrutri/Work/devstack/files/images/cirros-0.3.1-x86_64-uec/cirros-0.3.1-x86_64-initrd
 ']'
  2014-10-29 15:06:50.657 | ++ glance --os-auth-token 
12a7b1359dc044ff9e9e1c81a2390152 --os-image-url http://192.168.56.101:9292 
image-create --name cirros-0.3.1-x86_64-uec-ramdisk --is-public True 
--container-format ari --disk-format ari
  2014-10-29 15:06:50.681 | ++ grep ' id '
  2014-10-29 15:06:50.690 | ++ get_field 2
  2014-10-29 15:06:50.699 | ++ read data
  2014-10-29 15:06:55.658 | Invalid OpenStack Identity credentials.
  2014-10-29 15:06:55.733 | + RAMDISK_ID=
  2014-10-29 15:06:55.783 | + glance --os-auth-token 
12a7b1359dc044ff9e9e1c81a2390152 --os-image-url http://192.168.56.101:9292 
image-create --name cirros-0.3.1-x86_64-uec --is-public True --container-format 
ami --disk-format ami
  2014-10-29 15:07:00.966 | Invalid OpenStack Identity credentials.
  xtrutri@ubuntu:~/Work/devstack$ 2014-10-29 15:07:01.061 | + exit_trap


  DevStack version: at commit 8cedabcea8bb446f1c29aab42fbcbf5a87218f7f (Sat May 
10 12:24:16 2014 +)
  KeyStone version: 2014.2.rc1-106-gf45b3e5
  GlanceClient version: 0.14.1-11-gcfe0623
  Glance version: 2014.2.rc1-91-gded0852

  
  Here is the traceback:

  2014-10-29 15:06:57.263 16394 DEBUG glance.api.middleware.version_negotiation 
[-] Using url versioning process_request 
/opt/stack_stable_juno/glance/glance/api/middleware/version_negotiation.py:57
  2014-10-29 15:06:57.265 16394 DEBUG glance.api.middleware.version_negotiation 
[-] Matched version: v1 process_request 
/opt/stack_stable_juno/glance/glance/api/middleware/version_negotiation.py:69
  2014-10-29 15:06:57.266 16394 DEBUG glance.api.middleware.version_negotiation 
[-] new path /v1/images process_request 
/opt/stack_stable_juno/glance/glance/api/middleware/version_negotiation.py:70
  2014-10-29 15:06:57.267 16394 DEBUG keystoneclient.session [-] REQ: curl -i 
-X GET http://127.0.0.1:35357/ -H "Accept: application/json" -H "User-Agent: 
python-keystoneclient" _http_log_request 
/opt/stack_stable_juno/python-keystoneclient/keystoneclient/session.py:162
  2014-10-29 15:06:57.270 16394 WARNING keystonemiddleware.auth_token [-] 
Retrying on HTTP connection exception: Unable to establish connection to 
http://127.0.0.1:35357/
  2014-10-29 15:06:57.772 16394 DEBUG keystoneclient.session [-] REQ: curl -i 
-X GET http://127.0.0.1:35357/ -H "Accept: application/json" -H "User-Agent: 
python-keystoneclient" _http_log_request 
/opt/stack_stable_juno/python-keystoneclient/keystoneclient/session.py:162
  2014-10-29 15:06:57.775 16394 WARNING keystonemiddleware.auth_token [-] 
Retrying on HTTP connection exception: Unable to establish connection to 
http://127.0.0.1:35357/
  2014-10-29 15:06:58.777 16394 DEBUG keystoneclient.session [-] REQ: curl -i 
-X GET http://127.0.0.1:35357/ -H "Accept: application/json" -H "User-Agent: 
python-keystoneclient" _http_log_request 
/opt/stack_stable_juno/python-keystoneclient/keystoneclient/session.py:162
  2014-10-29 15:06:58.782 16394 WARNING keystonemiddleware.auth_token [-] 
Retrying on HTTP connection exception: Unable to establish connection to 
http://127.0.0.1:35357/
  2014-10-29 15:07:00.793 16394 DEBUG keystoneclient.session [-] REQ: curl -i 
-X GET http://127.0.0.1:35357/ -H "Accept: application/json" -H "User-Agent: 
python-keystoneclient" _http_log_request 
/opt/stack_stable_juno/python-keystoneclient/keystoneclient/session.py:162
  2014-10-29 15:07:00.803 16394 ERROR keystonemiddleware.auth_token [-] HTTP 
connection exception: Unable to establish connection to http://127.0.0.1:35357/
  2014-10-29 15:07:00.807 16394 WARNING keystonemiddleware.auth_token [-] 
Authorization failed for token

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

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

[Yahoo-eng-team] [Bug 1538482] Re: url_for does not exists for service catalog

[Kairat Kushaev]

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

** Description changed:

  Here we introduced url_for method for service_catalog:
  https://review.openstack.org/#/c/250857/
  
  Unfortunately, we are parsing service_catalog and passing it to glance_store 
as a list in context:
  
https://github.com/openstack/glance/blob/master/glance/api/middleware/context.py#L117
  
  Because of this current glance_store master is broken when swift multi-tenant 
store is enabled with an error like this:
  list doesn't have an attribute url_for.
  That happens every time somebody would like to download/upload images.
+ 
+ 
+ We also need to pass ServiceCatalog from glance to glance_store. It is better 
than initializing ServiceCatalog in glance_store. It alos saves a lot time when 
upgrading from Keystone v2 to v3.

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  url_for does not exists for service catalog

Status in Glance:
  New
Status in glance_store:
  In Progress

Bug description:
  Here we introduced url_for method for service_catalog:
  https://review.openstack.org/#/c/250857/

  Unfortunately, we are parsing service_catalog and passing it to glance_store 
as a list in context:
  
https://github.com/openstack/glance/blob/master/glance/api/middleware/context.py#L117

  Because of this current glance_store master is broken when swift multi-tenant 
store is enabled with an error like this:
  list doesn't have an attribute url_for.
  That happens every time somebody would like to download/upload images.

  
  We also need to pass ServiceCatalog from glance to glance_store. It is better 
than initializing ServiceCatalog in glance_store. It alos saves a lot time when 
upgrading from Keystone v2 to v3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1538482/+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 1532656] Re: Duplicated content in "Using Glance’s Image Public APIs" page

[Kairat Kushaev]

The first section is related to HEAD request that simply returns image metadata.
The second section is related to GET request that returns image metadata and 
image itself. So the sections are different, not the same. 

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

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

Title:
  Duplicated content in "Using Glance’s Image Public APIs" page

Status in Glance:
  Invalid

Bug description:
  In "Using Glance’s Image Public APIs", the content for the section:

  "Retrieve Raw Image Data"
  (http://docs.openstack.org/developer/glance/glanceapi.html#retrieve-
  raw-image-data)

  is simply a dupe of  the section:

  "Retrieve Image Metadata"
  (http://docs.openstack.org/developer/glance/glanceapi.html#retrieve-
  image-metadata)

  Please fix it with the correct documentation for retrieving image
  data.

  Here is the text-snapshot of these two sections in case the live site
  is not available for any reason:
  http://paste.openstack.org/show/483381/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1532656/+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 1496822] Re: v2 reports instance-uuid as an option to image create

[Kairat Kushaev]

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

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

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  v2 reports instance-uuid as an option to image create

Status in Glance:
  Confirmed
Status in python-glanceclient:
  In Progress

Bug description:
  Users are confused why this command isn't working:

   $ glance image-create --instance-uuid d098a027-5e40-4750-aab9-0dcc7a763196 
--name "via glance image-create 1"
   +--+--+
   | Property | Value|
   +--+--+
   | checksum | None |
   | container_format | None |
   | created_at   | 2015-09-16T18:14:23Z |
   | disk_format  | None |
   | id   | xxx |
   | instance_uuid| d098a027-5e40-4750-aab9-0dcc7a763196  |
   | min_disk | 0|
   | min_ram  | 0|
   | name | via glance image-create 1|
   | owner| xxx |
   | protected| False|
   | size | None |
   | status   | queued   |
   | tags | []   |
   | updated_at   | 2015-09-16T18:14:23Z |
   | virtual_size | None |
   | visibility   | private  |
   +--+--+

  Note 'instance_uuid d098a027-5e40-4750-aab9-0dcc7a763196' in the
  output.

  It is reported/explained in the help:

   $ glance help image-create
   usage: glance image-create [--architecture ]
 [--protected [True|False]] [--name ]
 [--instance-uuid ]
 [--min-disk ] [--visibility ]
 [--kernel-id ]
 [--tags  [ ...]]
 [--os-version ]
 [--disk-format ] [--self ]
 [--os-distro ] [--id ]
 [--owner ] [--ramdisk-id ]
 [--min-ram ]
 [--container-format ]
 [--property 

[Yahoo-eng-team] [Bug 1395368] Re: ExternalNetworksTest[JSON, XML].test_delete_external_networks_with_floating_ip failures

[Kairat Kushaev]

Looks like Neutron bug, not related to glanceclient.

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

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

Title:
  ExternalNetworksTest[JSON,XML].test_delete_external_networks_with_floating_ip
  failures

Status in neutron:
  Fix Released
Status in python-glanceclient:
  Invalid
Status in tempest:
  Invalid

Bug description:
  I'm unsure as to the root cause (looking through the basic neutron,
  nova api logs didn't show much usefulness around the times these
  failed)...

  Here is the full log and link though:

  http://logs.openstack.org/51/136551/2/check/gate-tempest-dsvm-neutron-
  src-taskflow-icehouse/8e0bb9f/

  2014-11-22 18:50:53.315 | {1}
  
tempest.api.network.admin.test_external_network_extension.ExternalNetworksTestJSON.test_delete_external_networks_with_floating_ip
  [0.984493s] ... FAILED

  ft333.2: 
tempest.api.network.admin.test_external_network_extension.ExternalNetworksTestXML.test_delete_external_networks_with_floating_ip_StringException:
 pythonlogging:'': {{{
  2014-11-22 18:54:54,689 2113 DEBUG[tempest.common.rest_client] Request 
(ExternalNetworksTestXML:test_delete_external_networks_with_floating_ip): 201 
POST http://127.0.0.1:9696/v2.0/networks 0.080s
  Request - Headers: {'Content-Type': 'application/xml', 'Accept': 
'application/xml', 'X-Auth-Token': ''}
  Body: 
  http://www.w3.org/2001/XMLSchema-instance; 
xmlns:router="http://docs.openstack.org/ext/neutron/router/api/v1.0;>True
  Response - Headers: {'status': '201', 'content-length': '805', 
'connection': 'close', 'date': 'Sat, 22 Nov 2014 18:54:54 GMT', 'content-type': 
'application/xml; charset=UTF-8', 'x-openstack-request-id': 
'req-9d70cf16-d0ae-46e6-9f40-9c68cc50a2f0'}
  Body: 
  http://openstack.org/quantum/api/v2.0; 
xmlns:provider="http://docs.openstack.org/ext/provider/api/v1.0; 
xmlns:quantum="http://openstack.org/quantum/api/v2.0; 
xmlns:router="http://docs.openstack.org/ext/neutron/router/api/v1.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>ACTIVETruea3451f42641c4a3ab319253134e5a036localTrueFalse0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc
  2014-11-22 18:54:54,789 2113 DEBUG[tempest.common.rest_client] Request 
(ExternalNetworksTestXML:test_delete_external_networks_with_floating_ip): 201 
POST http://127.0.0.1:9696/v2.0/subnets 0.098s
  Request - Headers: {'Content-Type': 'application/xml', 'Accept': 
'application/xml', 'X-Auth-Token': ''}
  Body: 
  http://www.w3.org/2001/XMLSchema-instance;>40b8004ad-7e9d-4b8c-9de1-efa8177f6dfc10.100.0.0/2810.100.0.1
  Response - Headers: {'status': '201', 'content-length': '729', 
'connection': 'close', 'date': 'Sat, 22 Nov 2014 18:54:54 GMT', 'content-type': 
'application/xml; charset=UTF-8', 'x-openstack-request-id': 
'req-4f27ac74-c53f-4dd7-bd90-7bb217c82626'}
  Body: 
  http://openstack.org/quantum/api/v2.0; 
xmlns:quantum="http://openstack.org/quantum/api/v2.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>True0b8004ad-7e9d-4b8c-9de1-efa8177f6dfca3451f42641c4a3ab319253134e5a03610.100.0.210.100.0.14410.100.0.110.100.0.0/2849d84272-4d7e-49fd-bf72-0dcf7c923db6
  2014-11-22 18:54:54,877 2113 DEBUG[tempest.common.rest_client] Request 
(ExternalNetworksTestXML:test_delete_external_networks_with_floating_ip): 201 
POST http://127.0.0.1:9696/v2.0/floatingips 0.087s
  Request - Headers: {'Content-Type': 'application/xml', 'Accept': 
'application/xml', 'X-Auth-Token': ''}
  Body: 
  http://www.w3.org/2001/XMLSchema-instance;>0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc
  Response - Headers: {'status': '201', 'content-length': '560', 
'connection': 'close', 'date': 'Sat, 22 Nov 2014 18:54:54 GMT', 'content-type': 
'application/xml; charset=UTF-8', 'x-openstack-request-id': 
'req-f287a723-e173-4c69-b063-c0574860abfc'}
  Body: 
  http://openstack.org/quantum/api/v2.0; 
xmlns:quantum="http://openstack.org/quantum/api/v2.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;>0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc10.100.0.2a3451f42641c4a3ab319253134e5a036DOWNded008db-5868-45c9-9186-0b700211f0ef
  2014-11-22 18:54:54,888 2113 DEBUG[tempest.common.rest_client] Request 
(ExternalNetworksTestXML:test_delete_external_networks_with_floating_ip): 200 
GET 
http://127.0.0.1:9696/v2.0/floatingips?network=0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc
 0.009s
  Request - Headers: {'Content-Type': 'application/xml', 'Accept': 
'application/xml', 'X-Auth-Token': ''}
  Body: None
  Response - Headers: {'status': '200', 'content-length': '587', 
'content-location': 
'http://127.0.0.1:9696/v2.0/floatingips?network=0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc',
 'connection': 'close', 'date': 'Sat, 22 Nov 2014 18:54:54 GMT', 
'content-type': 'application/xml; charset=UTF-8', 'x-openstack-request-id': 

[Yahoo-eng-team] [Bug 1240355] Re: Broken pipe error when copying image from glance to vSphere

[Kairat Kushaev]

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

** This bug has been marked a duplicate of bug 1402354
   Broken Pipe in vsphere store due to inactive session

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

Title:
  Broken pipe error when copying image from glance to vSphere

Status in glance_store:
  Confirmed
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Using the VMwareVCDriver on the latest nova (6affe67067) from master,
  launching an image for the first time is failing when copying image
  from Glance to vSphere. The error that shows in the nova log is:

  Traceback (most recent call last):
File "/opt/stack/nova/nova/virt/vmwareapi/io_util.py", line 176, in _inner
  self.output.write(data)
File "/opt/stack/nova/nova/virt/vmwareapi/read_write_util.py", line 143, in 
write
  self.file_handle.send(data)
File "/usr/lib/python2.7/httplib.py", line 790, in send
  self.sock.sendall(data)
File "/usr/local/lib/python2.7/dist-packages/eventlet/green/ssl.py", line 
131, in sendall
  v = self.send(data[count:])
File "/usr/local/lib/python2.7/dist-packages/eventlet/green/ssl.py", line 
107, in send
  super(GreenSSLSocket, self).send, data, flags)
File "/usr/local/lib/python2.7/dist-packages/eventlet/green/ssl.py", line 
77, in 
  return func(*a, **kw)
File "/usr/lib/python2.7/ssl.py", line 198, in send
  v = self._sslobj.write(data)
  error: [Errno 32] Broken pipe

  To reproduce, launch an instance using an image that has not yet been
  uploaded to vSphere. I have attached the full log here:
  http://paste.openstack.org/show/48536/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance-store/+bug/1240355/+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 1327154] Re: Can't create image with "default_store = vsphere"

[Kairat Kushaev]

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

** This bug is no longer a duplicate of bug 1240355
   Broken pipe error when copying image from glance to vSphere
** This bug has been marked a duplicate of bug 1402354
   Broken Pipe in vsphere store due to inactive session

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

Title:
  Can't create image with "default_store = vsphere"

Status in Glance:
  New

Bug description:
  
-===
  Can't create image with "default_store = vsphere"

  I have tried to create image using the vsphere as the default store in
  below 2 ways: both don't work.

  1) touch /tmp/m.vmdk
  glance image-create --name test_template  --is-public=True 
--container-format=bare --disk-format=vmdk --property vmware_disktype=thin 
--property template_name= < /tmp/m.vmdk

  This is failing with

  Request returned failure status.
  500 Internal Server Error
  GL-F9EE247 Failed to upload image ea14f049-1172-4167-bcb4-31e9bdcfc0bc
      (HTTP 500)

  Below is the error stack:
  2014-06-04 18:32:35.181 11151 ERROR glance.store.vmware_datastore 
[2e6bb6a1-e25e-4e74-811b-38ba14ee7b2e ed37da8c71184ac1a28da5e30e0a82c9 
ad9aba13a40e473abfcbb69d2eda313d - - -] GL-6FC93E4 Failed to upload content of 
image 5011db19-04fc-4699-b850-6f6efe9439d7
  2014-06-04 18:32:35.183 11151 ERROR glance.api.v1.upload_utils 
[2e6bb6a1-e25e-4e74-811b-38ba14ee7b2e ed37da8c71184ac1a28da5e30e0a82c9 
ad9aba13a40e473abfcbb69d2eda313d - - -] GL-F9EE247 Failed to upload image 
5011db19-04fc-4699-b850-6f6efe9439d7
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils Traceback 
(most recent call last):
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils   File 
"/usr/lib/python2.6/site-packages/glance/api/v1/upload_utils.py", line 99, in 
upload_data_to_store
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils store)
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils   File 
"/usr/lib/python2.6/site-packages/glance/store/__init__.py", line 382, in 
store_add_to_backend
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils (location, 
size, checksum, metadata) = store.add(image_id, data, size)
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils   File 
"/usr/lib/python2.6/site-packages/glance/store/vmware_datastore.py", line 292, 
in add
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils 
body=res.read())
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils 
UnexpectedStatus: GL-ECBEA55 The request returned an unexpected status: 404.
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils 
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils The response 
body:
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils 
  2014-06-04 18:32:35.183 11151 TRACE glance.api.v1.upload_utils 

  2) glance image-create --name debian-2.6.32 --disk-format vmdk
  --container-format bare --is-public true --property
  vmware_adaptertype="lsiLogic" --property
  vmware_disktype="preallocated" --property hypervisor_type="vmware"
  --property vmware_ostype="ubuntu64Guest" <
  /images/debian-2.6.32-i686.vmdk

  This is failing with

  Request returned failure status.
  400 Bad Request
  GL-4314F1B Client disconnected before sending all data to backend
      (HTTP 400) 
  Below is the error stack:
  2014-06-04 18:33:05.594 11151 ERROR glance.store.vmware_datastore 
[74fe0f17-92e8-421c-b573-97876cda64ad ed37da8c71184ac1a28da5e30e0a82c9 
ad9aba13a40e473abfcbb69d2eda313d - - -] GL-6FC93E4 Failed to upload content of 
image 4b35fc6a-e60d-4194-8974-c37a9bec370b
  2014-06-04 18:33:05.594 11151 TRACE glance.store.vmware_datastore Traceback 
(most recent call last):
  2014-06-04 18:33:05.594 11151 TRACE glance.store.vmware_datastore   File 
"/usr/lib/python2.6/site-packages/glance/store/vmware_datastore.py", line 276, 
in add
  2014-06-04 18:33:05.594 11151 TRACE glance.store.vmware_datastore 
content=image_file)
  2014-06-04 18:33:05.594 11151 TRACE glance.store.vmware_datastore   File 
"/usr/lib/python2.6/site-packages/glance/store/vmware_datastore.py", line 408, 
in _get_http_conn
  2014-06-04 18:33:05.594 11151 TRACE glance.store.vmware_datastore 
conn.request(method, url, content, headers)
  2014-06-04 18:33:05.594 11151 TRACE glance.store.vmware_datastore   File 
"/usr/lib64/python2.6/httplib.py", line 920, in request
  2014-06-04 18:33:05.594 11151 TRACE glance.store.vmware_datastore 
self._send_request(method, url, body, headers)
  2014-06-04 18:33:05.594 11151 TRACE glance.store.vmware_datastore   File 
"/usr/lib64/python2.6/httplib.py", line 954, in _send_request
  2014-06-04 18:33:05.594 11151 TRACE glance.store.vmware_datastore 

[Yahoo-eng-team] [Bug 1530027] Re: Bad request when create_image in Citrix XenServer CI

[Kairat Kushaev]

Marking this as Invalid until there will be reproducible case.

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

Title:
  Bad request when create_image in Citrix XenServer CI

Status in Glance:
  Invalid
Status in tempest:
  Invalid

Bug description:
  In this gate test[2], Bad request raise when Citrix XenServer CI
  failed.

  detail show in here [1].

  
  [1] 
http://dd6b71949550285df7dc-dda4e480e005aaa13ec303551d2d8155.r49.cf1.rackcdn.com/34/252234/4/21189/run_tests.log
  [2] https://review.openstack.org/#/c/252234/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1530027/+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 1533536] Re: glance api v2 cannot check image checksum

[Kairat Kushaev]

Glance does have out-of-the box parameter 'checksum'. I guess that's why you 
cannot create the custom parameter with the same name. Just execute glance 
image-show  and you will see the checksum here:
+--+--+
| Property | Value|
+--+--+
| checksum | eb9139e4942121f22bbc2afc0400b2a4 |
| container_format | ami  |
| created_at   | 2015-12-10T10:52:43Z |
| disk_format  | ami  |
| id   | b3eb6179-43f6-4956-8ed3-010e03bccd83 |
| kernel_id| 1f9fb6bc-b3b0-47d7-8160-633a88a893e9 |
| min_disk | 0|
| min_ram  | 0|
| name | cirros-0.3.4-x86_64-uec  |
| owner| c838177f128c4defa5fe6a6d5b1da48c |
| protected| False|
| ramdisk_id   | 349095ef-002e-4001-b033-1fe21ac1ad44 |
| size | 25165824 |
| status   | active   |
| tags | []   |
| updated_at   | 2015-12-10T10:52:44Z |
| virtual_size | None |
| visibility   | public   |
+--+--+
Does it satisfy your goals?
If not please re-open an issue and provide more details about, we will try to 
help you.
Now I am marking this as Invalid.

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

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

Title:
  glance api v2 cannot check image checksum

Status in Glance:
  Invalid

Bug description:
  Issue:

  I cannot create an image by Glance V2 API, specifying parameter "checksum". 
  the checksum is important for user,  will  can be used  to  check the 
integrity of the image.
  but now, the glance V2 API  in create image interface cannot specifying 
parameter "checksum", and can not check the 'checksum'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1533536/+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 1524205] Re: To set "image_cache_subdirectory_name=_base$my_ip", and create a instance failed.

[Kairat Kushaev]

AFAIK, glance image cache is transparent to the user: so the user don't know if 
he is using cache or not.
It also doesn't have any dependencies on nova caching implementation. 
AFAIU caching in nova is managed by Nova so please change affected projects. 
Please, reopen a bug if there is glance dependencies on it.

** Project changed: glance => nova

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

Title:
  To set "image_cache_subdirectory_name=_base$my_ip",  and create a
  instance failed.

Status in OpenStack Compute (nova):
  New

Bug description:
  If I set "mage_cache_subdirectory_name=_base$my_ip" in nova.conf  for
  using glance cache function.  Then I create a instance failed.

  [DEFAULT]
  verbose = True
  dhcpbridge_flagfile=/etc/nova/nova.conf
  dhcpbridge=/usr/bin/nova-dhcpbridge
  logdir=/var/log/nova
  state_path=/var/lib/nova
  lock_path=/var/lock/nova
  force_dhcp_release=True
  libvirt_use_virtio_for_bridges=True
  verbose=True
  ec2_private_dns_show_ip=True
  api_paste_config=/etc/nova/api-paste.ini
  enabled_apis=ec2,osapi_compute,metadata
  rpc_backend = rabbit
  auth_strategy = keystone
  my_ip = 10.10.10.30
  network_api_class = nova.network.neutronv2.api.API
  security_group_api = neutron
  linuxnet_interface_driver = nova.network.linux_net.LinuxOVSInterfaceDriver
  firewall_driver = nova.virt.firewall.NoopFirewallDriver

  image_cache_subdirectory_name = _base$my_ip
  [oslo_messaging_rabbit]
  rabbit_host = 10.10.10.10
  rabbit_userid = openstack
  rabbit_password = 123qwe

  [keystone_authtoken]
  auth_uri = http://10.10.10.10:5000
  auth_url = http://10.10.10.10:35357
  auth_plugin = password
  project_domain_id = default
  user_domain_id = default
  project_name = service
  username = nova
  password = 123qwe

  [vnc]
  enabled = True
  vncserver_listen = 0.0.0.0
  vncserver_proxyclient_address = 10.10.10.30
  novncproxy_base_url = http://10.10.10.10:6080/vnc_auto.html

  [glance]
  host = 10.10.10.10

  [oslo_concurrency]
  lock_path = /var/lib/nova/tmp

  [neutron]
  url = http://10.10.10.10:9696
  auth_url = http://10.10.10.10:35357
  auth_plugin = password
  project_domain_id = default
  user_domain_id = default
  region_name = RegionOne
  project_name = service
  username = neutron
  password = 123qwe

  [xenserver]
  cache_images = all

  
  I found some error informations in /var/log/nova/nova-compute.log

  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a] Traceback (most recent call last):
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2155, in 
_build_resources
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a] yield resources
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a]   File 
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2009, in 
_build_and_run_instance
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a] block_device_info=block_device_info)
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2444, in 
spawn
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a] block_device_info=block_device_info)
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 4519, in 
_create_domain_and_network
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a] xml, pause=pause, power_on=power_on)
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 4449, in 
_create_domain
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a] guest.launch(pause=pause)
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a]   File 
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/guest.py", line 141, in 
launch
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a] self._encoded_xml, errors='ignore')
  2015-10-27 10:23:16.719 39365 ERROR nova.compute.manager [instance: 
1e208e90-a6cd-415f-be9c-7f7af3cec69a]   File 
"/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 195, in __exit__
  

[Yahoo-eng-team] [Bug 1518431] Re: Glance failed to upload image to swift storage

[Kairat Kushaev]

It took some amount of time to debug this issue for Glance.
It turned out that both Glance and Swift support chunked requests. 
Unfortunately, chunked uploading is not supported mod_fastcgi that is used by 
RadosGW. It is very typical for Apache to response with 411 error because some 
cgi (or wsgi) frameworks always require Content-length to be specified. 
Request  with transfer-encoding=chunked is a part of Http spec so glance_store 
prepares correct request here.
So I would recommend to deploy RadosGW under different CGI (for example 
mod_proxy_fcgi) that supports chunked requests.
I will mark this as Invalid for Glance, please re-open the bug if you don't 
agree.

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  Glance failed to upload image to swift storage

Status in Glance:
  Invalid

Bug description:
  When glance configured with swift backend, and swift API provides via
  RadosGW is unable to upload image.

  Command:
  glance --debug image-create --name trusty_ext4 --disk-format raw 
--container-format bare --file trusty-server-cloudimg-amd64.img --visibility 
public --progress
  Logs:
  http://paste.openstack.org/show/479621/

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1518431/+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 1524849] [NEW] Cannot use trusts with fernet tokens

[Kairat Kushaev]

Public bug reported:

Master, devstack (installed today). 
1. Enable fernet tokens in Keystone
2. Add the following lib to glance/common/ folder:
http://paste.openstack.org/show/481480/
3. Replace upload method in glance/api/v2/image_data.py with the following:
http://paste.openstack.org/show/481489/
NOTE: it is just example of the code to demonstrate that fernet tokens can't 
work well with trusts.
4. Restart glance
5. Try to upload any image.
You will get the following error when deleting the trust: 
http://paste.openstack.org/show/481493/
When you try to upload big image that requires more than hour (or reduce token 
expiration)
you will get the following: http://paste.openstack.org/show/481492/
Apparently, refreshed token rejected by keystone-middleware.

I faced with the issue when implementing trusts for Glance but it seems that 
Heat and other services have the same troubles.
UUID tokens works as expected.

** Affects: keystone
 Importance: Undecided
 Status: New

** Summary changed:

- Cannot delete trust when using fernet tokens
+ Cannot use trusts with fernet tokens

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

Title:
  Cannot use trusts with fernet tokens

Status in OpenStack Identity (keystone):
  New

Bug description:
  Master, devstack (installed today). 
  1. Enable fernet tokens in Keystone
  2. Add the following lib to glance/common/ folder:
  http://paste.openstack.org/show/481480/
  3. Replace upload method in glance/api/v2/image_data.py with the following:
  http://paste.openstack.org/show/481489/
  NOTE: it is just example of the code to demonstrate that fernet tokens can't 
work well with trusts.
  4. Restart glance
  5. Try to upload any image.
  You will get the following error when deleting the trust: 
http://paste.openstack.org/show/481493/
  When you try to upload big image that requires more than hour (or reduce 
token expiration)
  you will get the following: http://paste.openstack.org/show/481492/
  Apparently, refreshed token rejected by keystone-middleware.

  I faced with the issue when implementing trusts for Glance but it seems that 
Heat and other services have the same troubles.
  UUID tokens works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1524849/+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 1489059] Re: "db type could not be determined" running py34

[Kairat Kushaev]

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

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

** Changed in: python-glanceclient
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  "db type could not be determined" running py34

Status in Aodh:
  In Progress
Status in cloudkitty:
  Fix Committed
Status in Glance:
  New
Status in glance_store:
  In Progress
Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-lib:
  In Progress
Status in OpenStack Identity (keystone):
  In Progress
Status in keystoneauth:
  In Progress
Status in keystonemiddleware:
  In Progress
Status in Manila:
  Fix Committed
Status in neutron:
  Fix Committed
Status in python-glanceclient:
  New
Status in python-keystoneclient:
  In Progress
Status in Sahara:
  Fix Committed
Status in senlin:
  Fix Committed
Status in tap-as-a-service:
  New
Status in tempest:
  In Progress

Bug description:
  When running tox for the first time, the py34 execution fails with an
  error saying "db type could not be determined".

  This issue is know to be caused when the run of py27 preceeds py34 and
  can be solved erasing the .testrepository and running "tox -e py34"
  first of all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/aodh/+bug/1489059/+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 1482436] Re: Support for compressed/archive file is broken with image-create

[Kairat Kushaev]

You can upload a compressed image to glance but it is not possible to boot an 
instance from zipped image because it is not supported by Nova.
Glance support zip compression when transmitting an image from Glance to Nova 
but it is decompressed/compressed by wsgi application (not Glance) and that 
wsgi app have no idea about source image encoding.
So I am marking this as Invalid.

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

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

Title:
  Support for compressed/archive file is broken with image-create

Status in Glance:
  Invalid

Bug description:
  Discovered via Horizon bug:
  https://bugs.launchpad.net/horizon/+bug/1479966

  Creating image from archive file appears to be broken, evident by
  instance launched from it fails to boot (error: "No bootable device").

  Steps to reproduce:

  1. Have a tar.gz version of a qcow image available locally and/or
  remotely accessible via HTTP.

  2.1 Create an image using copy-from:
  
  $ glance image-create --name="test-remote-compressed" --is-public=true 
--disk-format=qcow2 --container-format=bare --is-public=True --copy-from 
http://example.com/cirros-0.3.0-i386-disk.img.tar.gz
  

  2.2 Create an image from a local file:
  
  $ glance image-create --name="test-remote-compressed2" --is-public=true 
--disk-format=qcow2 --container-format=bare --is-public=True < 
cirros-0.3.0-i386-disk.img.tar.gz
  

  3. Launch instances from created images.

  Expected:

  1. Instances launched and boot successfully.

  Actual:

  1. Console outputs the following:
  
  Booting from Hard Disk...
  Boot failed: not a bootable disk

  No bootable device.
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1482436/+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 1506842] Re: Glanceclient + SSL - Show warnings in console

[Kairat Kushaev]

this is not glance bug.

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

Title:
  Glanceclient + SSL - Show warnings in console

Status in Glance:
  Invalid
Status in python-glanceclient:
  In Progress

Bug description:
  If we use glanceclient with ssl, console displays few "extra" warnings
  like this:

  /usr/lib/python2.7/dist-packages/urllib3/util/ssl_.py:90: 
InsecurePlatformWarning: A true SSLContext object is not available. This 
prevents urllib3 from configuring SSL appropriately and may cause certain SSL 
connections to fail. For more information, see 
https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
InsecurePlatformWarning
  /usr/lib/python2.7/dist-packages/urllib3/connection.py:251: SecurityWarning: 
Certificate has no `subjectAltName`, falling back to check for a `commonName` 
for now. This feature is being removed by major browsers and deprecated by RFC 
2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
SecurityWarning

  or that:

  /usr/lib/python2.7/dist-packages/urllib3/util/ssl_.py:90: 
InsecurePlatformWarning: A true SSLContext object is not available. This 
prevents urllib3 from configuring SSL appropriately and may cause certain SSL 
connections to fail. For more information, see 
https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
InsecurePlatformWarning
  /usr/lib/python2.7/dist-packages/urllib3/connectionpool.py:770: 
InsecureRequestWarning: Unverified HTTPS request is being made. Adding 
certificate verification is strongly advised. See: 
https://urllib3.readthedocs.org/en/latest/security.html
InsecureRequestWarning)

  Affected: python-glanceclient (and CLI).

  Steps to reproduce:

  1. Deploy openstack with enabling services in HTTPS mode (using TLS).
  2. Try to use this command: glance image-list

  Actual result: Displays a list of images with some warnings.

  root@node-1:~# glance image-list
  /usr/lib/python2.7/dist-packages/urllib3/util/ssl_.py:90: 
InsecurePlatformWarning: A true SSLContext object is not available. This 
prevents urllib3 from configuring SSL appropriately and may cause certain SSL 
connections to fail. For more information, see 
https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
InsecurePlatformWarning
  /usr/lib/python2.7/dist-packages/urllib3/connection.py:251: SecurityWarning: 
Certificate has no `subjectAltName`, falling back to check for a `commonName` 
for now. This feature is being removed by major browsers and deprecated by RFC 
2818. (See https://github.com/shazow/urllib3/issues/497 for details.)
SecurityWarning
  +--++
  | ID   | Name   |
  +--++
  | 43c99677-94b4-4356-b3ee-cd3690f26fdc | TestVM |
  +--++

  Excepted result: Displays a list of images without any warnings.

  root@node-1:~# glance image-list

  +--++
  | ID   | Name   |
  +--++
  | 43c99677-94b4-4356-b3ee-cd3690f26fdc | TestVM |
  +--++

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1506842/+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 1470918] Re: Glance uses glance_store from git master

[Kairat Kushaev]

Not valid anymore:
https://github.com/openstack/glance/blob/master/requirements.txt

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

Title:
  Glance uses glance_store from git master

Status in Glance:
  Invalid

Bug description:
  Since https://review.openstack.org/#/c/197766/, glance_store is pulled
  in from git master. This is so we can have a voting py34 job, but
  needs to be changed back to a released version when we cut the next
  glance_store release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1470918/+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 1486115] Re: Show metadata properties with empty value

[Kairat Kushaev]

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

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

Title:
  Show metadata properties with empty value

Status in Glance:
  Invalid

Bug description:
  Test case to reproduce:
  1. Create any image with empty property i.e.
  --property dummy_property=
  2. Request detailed image information
  glance image-show 

  AR: dummy_property is not in output
  ER: dummy_property should be shown by the command.

  Glance API v1
  master

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1486115/+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 1508880] [NEW] Safely encode checksum to use glance with apache

[Kairat Kushaev]

Public bug reported:

When trying to download any image under apache+mod_wsgi glance logs responses 
with Type Error: expected byte str, got unicode without any useful information.
It seems that one of headers is decoded as unicode which can cause problem on 
different web-servers (apache is one of examples).
Steps to reproduce:
1. Deploy glance-api under apache
2. try to download any image
ER: Type Error: expected byte str, got 
AR: all good

** Affects: glance
 Importance: Undecided
 Assignee: Kairat Kushaev (kkushaev)
 Status: In Progress

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  Safely encode checksum to use glance with apache

Status in Glance:
  In Progress

Bug description:
  When trying to download any image under apache+mod_wsgi glance logs responses 
with Type Error: expected byte str, got unicode without any useful information.
  It seems that one of headers is decoded as unicode which can cause problem on 
different web-servers (apache is one of examples).
  Steps to reproduce:
  1. Deploy glance-api under apache
  2. try to download any image
  ER: Type Error: expected byte str, got 
  AR: all good

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1508880/+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 1505157] [NEW] Glance doesn't validate deactivated image correctly

[Kairat Kushaev]

Public bug reported:

This bug was found by Abhishek Kekane in one of review to glance docs.
With python glanceclient (v2)
1. Create an active image
2. De-activate image
3. Delete image
AR: 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'
ER: everything is good.

Looks like our schema for v2 does not have deactivated status in
validation list.

** Affects: glance
 Importance: Undecided
 Assignee: Kairat Kushaev (kkushaev)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  Glance doesn't validate deactivated image correctly

Status in Glance:
  New

Bug description:
  This bug was found by Abhishek Kekane in one of review to glance docs.
  With python glanceclient (v2)
  1. Create an active image
  2. De-activate image
  3. Delete image
  AR: 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'
  ER: everything is good.

  Looks like our schema for v2 does not have deactivated status in
  validation list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1505157/+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 1502369] Re: Jenkins/tox fails to generate docs

[Kairat Kushaev]

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

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

Title:
  Jenkins/tox fails to generate docs

Status in devstack:
  New
Status in Glance:
  Fix Released

Bug description:
  Hi,

  When we run "tox" in fresh clone of glance-specs repo, it fails with
  the below error (full log can be found here:
  http://paste.openstack.org/show/475234/):

  running build_ext
    Traceback (most recent call last):
  File "", line 1, in 
  File "/tmp/pip-build-OfhUFL/Pillow/setup.py", line 767, in 
    zip_safe=not debug_build(),
  File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
    dist.run_commands()
  File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
    cmd_obj.run()
  File 
"/home/dramakri/glance-specs/.tox/py27/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
 line 175, in run
    self.run_command('build')
  File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
    cmd_obj.run()
  File "/usr/lib/python2.7/distutils/command/build.py", line 128, in run
    self.run_command(cmd_name)
  File "/usr/lib/python2.7/distutils/cmd.py", line 326, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
    cmd_obj.run()
  File "/usr/lib/python2.7/distutils/command/build_ext.py", line 337, in run
    self.build_extensions()
  File "/tmp/pip-build-OfhUFL/Pillow/setup.py", line 515, in 
build_extensions
    % (f, f))
    ValueError: --enable-jpeg requested but jpeg not found, aborting.

    
    Failed building wheel for Pillow
  Failed to build Pillow

  This causes Jenkins also to fail on any submission. I noticed this issue when 
I tried to upload a new spec (https://review.openstack.org/#/c/230679/) to the 
Glance-specs folder and it failed.
  Link to the Jenkins log for the failed run: 
http://logs.openstack.org/79/230679/1/check/gate-glance-specs-docs/e34dc8b/console.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1502369/+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 1502133] [NEW] 403 error when get_image_location policy is set to "role:admin"

[Kairat Kushaev]

Public bug reported:

glance master
steps to reproduce:
1. add role:admin to /etc/glance/policy.json
2. as demo user execute glance image-list
AR: 403 Forbidden
ER: list of images.
v1 api is working correctly and returns list of images.

** Affects: glance
 Importance: Undecided
 Assignee: Kairat Kushaev (kkushaev)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  403 error when get_image_location policy is set to "role:admin"

Status in Glance:
  New

Bug description:
  glance master
  steps to reproduce:
  1. add role:admin to /etc/glance/policy.json
  2. as demo user execute glance image-list
  AR: 403 Forbidden
  ER: list of images.
  v1 api is working correctly and returns list of images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1502133/+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 1501046] Re: v2 API: Not possible to "retire" disk formats

[Kairat Kushaev]

So this behavior happens when glanceclient already received image information. 
You can at least get an info trhough API as workaround.
The root cause is in schema validation after receiving this info. Need to think 
more about this case.

** Project changed: glance => python-glanceclient

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

Title:
  v2 API: Not possible to "retire" disk formats

Status in python-glanceclient:
  New

Bug description:
  Use case:

  We tried to remove QCOW2 from the list of supported disk_formats in
  some of our deployments, because the conversion overhead of using them
  was making for a sub-wonderful user experience.

  After removing "qcow2" from the disk_formats parameter, the Glance v2
  API started returning 404 errors on extant QCOW2 images.  This means
  that we effectively cannot "retire" this disk format and block new
  image uploads, since Glance will immediately disavow all knowledge of
  any QCOW2 images in its purview.

  Steps to Reproduce:

  1.  Stand up a devstack
  2.  Upload a QCOW2 image
  3.  glance --os-image-api-version 2 image-show IMAGE_ID
  4.  Reconfigure glance-api to only allow e.g., "raw" disk_formats:
  [image_format]
  disk_formats = raw,ami,ari,aki,iso
  5.  Restart glance-api
  6. glance --os-image-api-version 2 image-show IMAGE_ID

  Expected results:

  The "glance image-show" command works both times

  Actual results:

  The second "glance image-show" command fails.

  Errata:

  The "glance image-show" using the v1 API does work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-glanceclient/+bug/1501046/+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 1487086] Re: Pagination doesn't work with v2 API image-list

[Kairat Kushaev]

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

** Project changed: glance => python-glanceclient

** Changed in: python-glanceclient
   Status: New => 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/1487086

Title:
  Pagination doesn't work with v2 API image-list

Status in python-glanceclient:
  In Progress

Bug description:
  It would useful to allow users to output list of images by pages.
  But right now it is not possible because glance client v2 doesn't have marker 
parameter defined.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-glanceclient/+bug/1487086/+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 1498460] [NEW] Create image from empty locations leads to internal server error

[Kairat Kushaev]

Public bug reported:

master, devstack, API v1
Steps to reproduce:
1. Create an image from empty location 
glance image-create --location ''
ER: Bad Request
AR: internal server Error

** Affects: glance
 Importance: Undecided
 Assignee: Kairat Kushaev (kkushaev)
 Status: New

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  Create image from empty locations leads to internal server error

Status in Glance:
  New

Bug description:
  master, devstack, API v1
  Steps to reproduce:
  1. Create an image from empty location 
  glance image-create --location ''
  ER: Bad Request
  AR: internal server Error

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1498460/+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 1480021] Re: execute "glance image-create" is not return error

[Kairat Kushaev]

So I propose to mark this as invalid as per wangxiyuan comment.

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

Title:
  execute "glance image-create" is not return error

Status in Glance:
  Invalid

Bug description:
  glance version is 0.14.2

  If i create image from command "glance image-list" and no
  parameters,it is success.

  [root@xx ~(keystone_admin)]# glance image-create
  +--+--+
  | Property | Value|
  +--+--+
  | checksum | None |
  | container_format | None |
  | created_at   | 2015-07-31T01:55:34  |
  | deleted  | False|
  | deleted_at   | None |
  | disk_format  | None |
  | id   | 20767e02-5a45-4818-a976-3789634b5719 |
  | is_public| False|
  | min_disk | 0|
  | min_ram  | 0|
  | name | None |
  | owner| 1a999ee4874640ba902769311cf7727a |
  | protected| False|
  | size | 0|
  | status   | queued   |
  | updated_at   | 2015-07-31T01:55:34  |
  | virtual_size | None |
  +--+--+

  if size is zero and no parameters we should not allow create image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1480021/+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 1493826] [NEW] Glance doesn't replace blob property correctly in artifacts

[Kairat Kushaev]

Public bug reported:

Version: glance liberty master (latest 04.09.15)
Steps to reproduce:
1. Create an artifact(type=MyArtifact) with blob property (image_file)
2. Update blob property image_file with some value:
curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H 
"Content-Type:application/octet-stream" -X POST -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/e4e58687-dbb9-4fa2-af53-b4addc15bc99/image_file
 -i
3. Request blob property replace:
curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H 
"Content-Type:application/octet-stream" -X PUT -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/e4e58687-dbb9-4fa2-af53-b4addc15bc99/image_file
 -i
AR: 405 Method not allowed
ER: 200 OK

** Affects: glance
 Importance: Undecided
 Status: New


** Tags: artifacts

** Description changed:

  Version: glance liberty master (latest 04.09.15)
  Steps to reproduce:
  1. Create an artifact(type=MyArtifact) with blob property (image_file)
  2. Update blob property image_file with some value:
  curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H 
"Content-Type:application/octet-stream" -X POST -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/e4e58687-dbb9-4fa2-af53-b4addc15bc99/image_file
 -i
  3. Request blob property replace:
  curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H 
"Content-Type:application/octet-stream" -X PUT -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/e4e58687-dbb9-4fa2-af53-b4addc15bc99/image_file
 -i
  AR: 405 Method not allowed
- ER: 200
+ ER: 200 OK

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

Title:
  Glance doesn't replace blob property correctly in artifacts

Status in Glance:
  New

Bug description:
  Version: glance liberty master (latest 04.09.15)
  Steps to reproduce:
  1. Create an artifact(type=MyArtifact) with blob property (image_file)
  2. Update blob property image_file with some value:
  curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H 
"Content-Type:application/octet-stream" -X POST -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/e4e58687-dbb9-4fa2-af53-b4addc15bc99/image_file
 -i
  3. Request blob property replace:
  curl -H "X-Auth-Token: 6b2e3dccf35642b89099465e7492a42a" -H 
"Content-Type:application/octet-stream" -X PUT -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/e4e58687-dbb9-4fa2-af53-b4addc15bc99/image_file
 -i
  AR: 405 Method not allowed
  ER: 200 OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1493826/+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 1493833] [NEW] Glance returns 500 error when trying to replace non-exising blob item in artifact blob-list

[Kairat Kushaev]

Public bug reported:

Steps to reproduce:
1. Create an artifact (type=MyArtifact)
2. Update artifact blob list with some value:
curl -H "X-Auth-Token: 1d5532fa812548f6a41bfd422f0d36a9" -H 
"Content-Type:application/octet-stream" -X POST -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/6d16c3e9-26d6-4abd-8ad6-e70e66e31aab/screenshots
 -i
3. Try to replace non-existing blob item in blob list
curl -H "X-Auth-Token: 1d5532fa812548f6a41bfd422f0d36a9" -H 
"Content-Type:application/octet-stream" -X PUT -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/6d16c3e9-26d6-4abd-8ad6-e70e66e31aab/screenshots/1
 -i
AR: Internal Server Error
ER: BadRequest Error

** Affects: glance
 Importance: Undecided
 Assignee: Kairat Kushaev (kkushaev)
 Status: New


** Tags: artifacts

** Changed in: glance
 Assignee: (unassigned) => Kairat Kushaev (kkushaev)

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

Title:
  Glance returns 500 error when trying to replace non-exising blob item
  in artifact blob-list

Status in Glance:
  New

Bug description:
  Steps to reproduce:
  1. Create an artifact (type=MyArtifact)
  2. Update artifact blob list with some value:
  curl -H "X-Auth-Token: 1d5532fa812548f6a41bfd422f0d36a9" -H 
"Content-Type:application/octet-stream" -X POST -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/6d16c3e9-26d6-4abd-8ad6-e70e66e31aab/screenshots
 -i
  3. Try to replace non-existing blob item in blob list
  curl -H "X-Auth-Token: 1d5532fa812548f6a41bfd422f0d36a9" -H 
"Content-Type:application/octet-stream" -X PUT -d '{"data": 
"someupdates_datawithtretrtrt"}' 
http://127.0.0.1:9292/v3/artifacts/myartifact/v2.0/6d16c3e9-26d6-4abd-8ad6-e70e66e31aab/screenshots/1
 -i
  AR: Internal Server Error
  ER: BadRequest Error

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1493833/+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 1440773] Re: Remove WritableLogger as eventlet has a real logger interface in 0.17.2

[Kairat Kushaev]

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

** Changed in: glance
 Assignee: (unassigned) = Kairat Kushaev (kkushaev)

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

Title:
  Remove WritableLogger as eventlet has a real logger interface in
  0.17.2

Status in Cinder:
  Fix Released
Status in Glance:
  New
Status in Manila:
  Fix Released
Status in neutron:
  New
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo.log:
  Fix Released

Bug description:
  Info from Sean on IRC:

  the patch to use a real logger interface in eventlet has been released
  in 0.17.2, which means we should be able to phase out
  https://github.com/openstack/oslo.log/blob/master/oslo_log/loggers.py

  Eventlet PR was:
  https://github.com/eventlet/eventlet/pull/75

  thanks,
  dims

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1440773/+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 1487086] [NEW] Pagination doesn't work with v2 API image-list

[Kairat Kushaev]

Public bug reported:

It seems that glance client doesn't have pagination for image-list correctly 
implemented:
1) glance client v2 doesn't have marker parameter defined
2) glance client ignores page-size parameter when specifying image-list.
glance image-list --page-size 1 returns all images.

** Affects: glance
 Importance: Undecided
 Assignee: Kairat Kushaev (kkushaev)
 Status: New

** Changed in: glance
 Assignee: (unassigned) = Kairat Kushaev (kkushaev)

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

Title:
  Pagination doesn't work with v2 API image-list

Status in Glance:
  New

Bug description:
  It seems that glance client doesn't have pagination for image-list correctly 
implemented:
  1) glance client v2 doesn't have marker parameter defined
  2) glance client ignores page-size parameter when specifying image-list.
  glance image-list --page-size 1 returns all images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1487086/+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 1485792] [NEW] Glance create an image with incorrect location

[Kairat Kushaev]

Public bug reported:

I tried to upload images from location by way like using SCP:

# glance image-create --name LINUX-64 --is-public True --disk-format iso
--container-format bare --progress --location
http://fuel_ip:~/ubuntu-14.04.2-server-amd64.iso

# glance image-create --name LINUX-64-2 --is-public True --disk-format
iso --container-format bare --progress --copy-from
http://fuel_ip:~/ubuntu-14.04.2-server-amd64.iso

Glance client accepted wrong location and as result i got images in Glance with 
Active status and 0 size.
Same behavior noticed with aki and ari images.

Expected that Glance client will prevent creation of image from
malformed source.

** Affects: glance
 Importance: Undecided
 Assignee: Kairat Kushaev (kkushaev)
 Status: New

** Changed in: glance
 Assignee: (unassigned) = Kairat Kushaev (kkushaev)

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

Title:
  Glance create an image with incorrect location

Status in Glance:
  New

Bug description:
  I tried to upload images from location by way like using SCP:

  # glance image-create --name LINUX-64 --is-public True --disk-format
  iso --container-format bare --progress --location
  http://fuel_ip:~/ubuntu-14.04.2-server-amd64.iso

  # glance image-create --name LINUX-64-2 --is-public True --disk-format
  iso --container-format bare --progress --copy-from
  http://fuel_ip:~/ubuntu-14.04.2-server-amd64.iso

  Glance client accepted wrong location and as result i got images in Glance 
with Active status and 0 size.
  Same behavior noticed with aki and ari images.

  Expected that Glance client will prevent creation of image from
  malformed source.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1485792/+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 1303802] Re: qemu image convert fails in snapshot

[Kairat Kushaev]

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

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

Title:
  qemu image convert fails in snapshot

Status in Orchestration API (Heat):
  New
Status in OpenStack Compute (Nova):
  New

Bug description:
  Periodically in the gate we see a failure by qemu image convert in
  snapshot:

  2014-04-07 01:31:29.470 29554 TRACE oslo.messaging.rpc.dispatcher   File 
/opt/stack/new/nova/nova/openstack/common/processutils.py, line 193, in 
execute
  2014-04-07 01:31:29.470 29554 TRACE oslo.messaging.rpc.dispatcher cmd=' 
'.join(cmd))
  2014-04-07 01:31:29.470 29554 TRACE oslo.messaging.rpc.dispatcher 
ProcessExecutionError: Unexpected error while running command.
  2014-04-07 01:31:29.470 29554 TRACE oslo.messaging.rpc.dispatcher Command: 
qemu-img convert -f qcow2 -O qcow2 
/opt/stack/data/nova/instances/4ff6dc10-eac8-41d2-a645-3a0e0ba07c8a/disk 
/opt/stack/data/nova/instances/snapshots/tmpcVpCxJ/33eb0bb2b49648c69770b47db3211a86
  2014-04-07 01:31:29.470 29554 TRACE oslo.messaging.rpc.dispatcher Exit code: 1
  2014-04-07 01:31:29.470 29554 TRACE oslo.messaging.rpc.dispatcher Stdout: ''
  2014-04-07 01:31:29.470 29554 TRACE oslo.messaging.rpc.dispatcher Stderr: 
'qemu-img: error while reading sector 0: Input/output error\n'

  qemu-img is very obtuse on what the actual issue is, so it's unclear
  if this is a corrupt disk, or a totally missing disk.

  The user visible face of this is on operations like shelve where the
  instance will believe that it's still in active state -
  http://logs.openstack.org/02/85602/1/gate/gate-tempest-dsvm-
  full/20ed964/console.html#_2014-04-07_01_44_29_309

  Even though everything is broken instead.

  Logstash query:
  
http://logstash.openstack.org/#eyJzZWFyY2giOiJcInFlbXUtaW1nOiBlcnJvclwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxMzk2ODc2MTQ4NDc3fQ==

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