[Yahoo-eng-team] [Bug 1528637] Re: (Import Refactor) Mark the `/file` endpoint as deprecated
marking as invalid as we've decided not to deprecate this endpoint ** 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/1528637 Title: (Import Refactor) Mark the `/file` endpoint as deprecated Status in Glance: Invalid Bug description: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ One of the goals of this spec is to improve the image import process and allow for other background operations to be executed when the image data is added. To do this without breaking the existing API, we're adding a new `/stage` endpoint that supersedes the existing `/file` endpoint where the image data is currently uploaded. Eventually, we'd like to completely deprecate (and perhaps delete) that endpoint. Definitely disable it. This lite spec is to mark that endpoint as deprecated and recommend deployers to disable it and have users move forward to the new `/stage` endpoint. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1528637/+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 1551037] Re: HTTP 409 error being masked as HTTP 500 on image delete
** Also affects: glance/mitaka Importance: High Assignee: Danny Al-Gaaf (danny-al-gaaf) Status: Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1551037 Title: HTTP 409 error being masked as HTTP 500 on image delete Status in Glance: Confirmed Status in Glance mitaka series: Confirmed Bug description: Using ceph for image storage. When calling image-delete on an in-use image: 500 Internal Server Error 500 Internal Server Error The server has either erred or is incapable of performing the requested operation. (HTTP 500) Though the log shows: glance.common.wsgi InUseByStore: The image cannot be deleted because it is in use through the backend store outside of Glance. I would expect that this return HTTP 409. In the code (images.py), I see an except clause for exception.InUseByStore, but the RBD driver is raising a different type of exception. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1551037/+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 1472449] Re: download error when the image status is not active
** Also affects: python-glanceclient/liberty Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1472449 Title: download error when the image status is not active Status in Glance: Fix Released Status in Glance liberty series: New Status in python-glanceclient: Fix Released Status in python-glanceclient liberty series: New Bug description: When the locations is blank, downloading image will show python error, but the error message is not correct. [root@vm134 pe]# glance image-show 9be94a27-367f-4a26-ae7a-045db3cb7332 +--+--+ | Property | Value| +--+--+ | checksum | None | | container_format | None | | created_at | 2015-07-02T09:09:22Z | | disk_format | None | | id | 9be94a27-367f-4a26-ae7a-045db3cb7332 | | locations| [] | | min_disk | 0| | min_ram | 0| | name | test | | owner| e4b36a5b654942328943a835339a6289 | | protected| False| | size | None | | status | queued | | tags | [] | | updated_at | 2015-07-02T09:09:22Z | | virtual_size | None | | visibility | private | +--+--+ [root@vm134 pe]# glance image-download 9be94a27-367f-4a26-ae7a-045db3cb7332 --file myimg iter() returned non-iterator of type 'NoneType' To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1472449/+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 1537626] Re: `glance location-update` deletes locations and backend images
** Also affects: glance/liberty
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1537626
Title:
`glance location-update` deletes locations and backend images
Status in Glance:
In Progress
Status in Glance liberty series:
New
Status in python-glanceclient:
In Progress
Bug description:
Hi all,
I am having trouble using `glance location-update --url
--metadata ` to update the metadata of a location. When
I try run the command, the locations become a blank list and the image
is deleted from my backend (swift+https). I have traced it down to the
following:
When doing a location-update, glanceclient actually sends two patch
commands:
[{'op': 'replace', 'path': '/locations', 'value': []},
{'op': 'replace',
'path': '/locations',
'value': [{u'metadata': {u'key': 'value'},
{u'url': u'swift+https://image1'}]}]
This is due to a note in python-
glanceclient/glanceclient/v2/images.py, update_location():
# NOTE: The server (as of now) doesn't support modifying individual
# location entries. So we must:
# 1. Empty existing list of locations.
# 2. Send another request to set 'locations' to the new list
# of locations.
However, at the server end, the _do_replace_locations() function which
handles this call, actually deletes the locations and images when it
gets the first call with the empty values
(glance/glance/api/v2/images.py) ???
def _do_replace_locations(self, image, value):
if len(image.locations) > 0 and len(value) > 0:
msg = _("Cannot replace locations from a non-empty "
"list to a non-empty list.")
raise webob.exc.HTTPBadRequest(explanation=msg)
if len(value) == 0:
# NOTE(zhiyan): this actually deletes the location
# from the backend store.
del image.locations[:]
if image.status == 'active':
image.status = 'queued'
This seems to result in the first call deleting all the locations from
the backend store, and the second call throwing an error because there
is no location any more.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1537626/+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 1537721] Re: Image corrupts when upload
** Also affects: glance/liberty Importance: Undecided Status: New ** Changed in: glance Importance: Undecided => High ** Changed in: glance/liberty Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1537721 Title: Image corrupts when upload Status in Glance: In Progress Status in Glance liberty series: New Bug description: After this commit https://github.com/openstack/glance_store/commit/a0572ef672512a8ed7ef203816ec256eafd5f9de image uploads works incorrect. Steps to reproduce: 1. Upload image (1.47GB) md5sum virtual_ubuntu_trasty_ext4_demo fa9ec35d64d43aefd6356150d361ec24 virtual_ubuntu_trasty_ext4_demo glance image-create --disk-format raw --container-format bare --file virtual_ubuntu_trasty_ext4_demo --progress --name ubuntu_upload_with_fix [=>] 100% +--+--+ | Property | Value| +--+--+ | checksum | fa9ec35d64d43aefd6356150d361ec24 | | container_format | bare | | created_at | 2016-01-25T11:06:15Z | | disk_format | raw | | id | 5b955bce-61ab-4c55-afd9-8bd6012cf1ab | | min_disk | 0| | min_ram | 0| | name | ubuntu_upload_with_fix | | owner| e885a6c5e87c45d38a274de4388241e6 | | protected| False| | size | 1476395008 | | status | active | | tags | [] | | updated_at | 2016-01-25T11:10:49Z | | virtual_size | None | | visibility | private | +--+--+ 2. It has 10 obects in Swift, but should has only one (size is less than 5G) swift list glance 5b955bce-61ab-4c55-afd9-8bd6012cf1ab 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-1 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-2 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-3 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-4 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-5 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-6 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-7 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-8 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-9 Image splitted by 7 chunks of 200MB + 1*47MB + 1 zero length chunk. swift stat glance 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-7 Account: v1 Container: glance Object: 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-7 Content Type: binary/octet-stream Content Length: 20480 Last Modified: Mon, 25 Jan 2016 11:10:42 GMT ETag: eda9a9889837ac4bc81d6387d92c1bec Accept-Ranges: bytes Server: Apache X-Timestamp: 1453720242.0 X-Trans-Id: txda5cc-0056a6064c-5e81-default swift stat glance 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-8 Account: v1 Container: glance Object: 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-8 Content Type: binary/octet-stream Content Length: 42795008 Last Modified: Mon, 25 Jan 2016 11:10:49 GMT ETag: f3c9b36eceea8d2192996ca931f1fa55 Accept-Ranges: bytes Server: Apache X-Timestamp: 1453720249.0 X-Trans-Id: txd8c0e-0056a60655-377d-default swift stat glance 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-9 Account: v1 Container: glance Object: 5b955bce-61ab-4c55-afd9-8bd6012cf1ab-9 Content Type: binary/octet-stream Content Length: 0 Last Modified: Mon, 25 Jan 2016 11:10:49 GMT ETag: d41d8cd98f00b204e9800998ecf8427e Accept-Ranges: bytes Server: Apache X-Timestamp: 1453720249.0 X-Trans-Id: txda39b-0056a60660-85c1-default 3. Download image glance image-download 5b955bce-61ab-4c55-afd9-8bd6012cf1ab --file ubuntu_download_with_fix --progress [=>] 100%[Errno 32] Corrupt image download. Checksum was 9253e738cabf6a3c0beace1a3b07e623 expected fa9ec35d64d43aefd6356150d361ec24 Image is corrupted, and original and result files has difference in lenght (1754 bytes) ls -l virtual_ubuntu_trasty_ext4_demo -rw-r--r-- 1 root root 1476395008 Jan 25 11:04 virtual_ubuntu_trasty_ext4_demo ls -l ubuntu_download_with_fix -rw-r--r-- 1 root root 1476393254 Jan 25 11:17 ubuntu_download_with_fix To manage notifications about this bug go to:
[Yahoo-eng-team] [Bug 1498460] Re: Create image from empty locations leads to internal server error
** Also affects: glance/kilo Importance: Undecided Status: New ** Also affects: glance/liberty Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1498460 Title: Create image from empty locations leads to internal server error Status in Glance: In Progress Status in Glance kilo series: New Status in Glance liberty series: 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 1533150] Re: Downloading empty file with enabled cache management leads to 500 error
** Also affects: glance/liberty
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1533150
Title:
Downloading empty file with enabled cache management leads to 500
error
Status in Glance:
In Progress
Status in Glance liberty series:
New
Bug description:
When I tried to download an empty image file from glance with enabled
cache management I got 500 error:
mfedosin@wdev:~$ glance --debug image-download
0af7b2e8-8e31-427b-a99f-9117f45418ef --file empty_file
curl -g -i -X GET -H 'Accept-Encoding: gzip, deflate' -H 'Accept: */*' -H
'User-Agent: python-glanceclient' -H 'Connection: keep-alive' -H 'X-Auth-Token:
{SHA1}c91066a8c438769ed454eebd759b4f8b1e488cb6' -H 'Content-Type:
application/octet-stream'
http://10.0.2.15:9292/v2/images/0af7b2e8-8e31-427b-a99f-9117f45418ef/file
Request returned failure status 500.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/glanceclient/shell.py", line
605, in main
args.func(client, args)
File "/usr/local/lib/python2.7/dist-packages/glanceclient/v2/shell.py",
line 277, in do_image_download
body = gc.images.data(args.id)
File "/usr/local/lib/python2.7/dist-packages/glanceclient/v2/images.py",
line 194, in data
resp, body = self.http_client.get(url)
File "/usr/local/lib/python2.7/dist-packages/glanceclient/common/http.py",
line 284, in get
return self._request('GET', url, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/glanceclient/common/http.py",
line 276, in _request
resp, body_iter = self._handle_response(resp)
File "/usr/local/lib/python2.7/dist-packages/glanceclient/common/http.py",
line 93, in _handle_response
raise exc.from_response(resp, resp.content)
HTTPInternalServerError: HTTPInternalServerError (HTTP 500)
HTTPInternalServerError (HTTP 500)
Without cache management everything works fine.
Steps to reproduce on devstack:
1. Set flavor to 'keystone+cachemanagement' in glance-api.conf (flavor =
keystone+cachemanagement)
2. Restart glance-api server
3. Create an image with empty file (file size is 0)
4. Try to download the image file from glance.
Expected result: new empty file will be created in local folder.
Actual result: HTTPInternalServerError (HTTP 500)
Logs from glance-api: http://paste.openstack.org/show/483545/
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1533150/+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 1533270] Re: Adding remote image in v2 when cache is enabled results 500 error
** Also affects: glance/liberty Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1533270 Title: Adding remote image in v2 when cache is enabled results 500 error Status in Glance: In Progress Status in Glance liberty series: New Bug description: To reproduce the issue: 1) Add an image without specifying the size 2) Enable caching 3) Get image data. This will succeed because the Content-Length is pulled from the remote store (i.e. swift). At this point, the image will be properly cached. 4) Get image data again with v2 api. This will fail with 500 error http://paste.openstack.org/show/483545/ It happens for the reason cache middleware couldn't assign value to image_meta['size'] because it expects a dictionary (as it was in v1 api), but in v2 api it's ImageTarget object. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1533270/+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 1472449] Re: download error when the image status is not active
** Also affects: glance/liberty Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1472449 Title: download error when the image status is not active Status in Glance: Fix Released Status in Glance liberty series: New Status in python-glanceclient: Fix Released Bug description: When the locations is blank, downloading image will show python error, but the error message is not correct. [root@vm134 pe]# glance image-show 9be94a27-367f-4a26-ae7a-045db3cb7332 +--+--+ | Property | Value| +--+--+ | checksum | None | | container_format | None | | created_at | 2015-07-02T09:09:22Z | | disk_format | None | | id | 9be94a27-367f-4a26-ae7a-045db3cb7332 | | locations| [] | | min_disk | 0| | min_ram | 0| | name | test | | owner| e4b36a5b654942328943a835339a6289 | | protected| False| | size | None | | status | queued | | tags | [] | | updated_at | 2015-07-02T09:09:22Z | | virtual_size | None | | visibility | private | +--+--+ [root@vm134 pe]# glance image-download 9be94a27-367f-4a26-ae7a-045db3cb7332 --file myimg iter() returned non-iterator of type 'NoneType' To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1472449/+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 1512416] Re: Glance doesn't catches exception NotFound from glance_store
** Also affects: glance/kilo Importance: Undecided Status: New ** Also affects: glance/liberty Importance: Undecided Status: New ** Changed in: glance/kilo Importance: Undecided => Medium ** Changed in: glance Importance: Undecided => Medium ** Changed in: glance/liberty Importance: Undecided => Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1512416 Title: Glance doesn't catches exception NotFound from glance_store Status in Glance: In Progress Status in Glance kilo series: New Status in Glance liberty series: New Bug description: Glance doesn't catches exception NotFound from glance_store when upload images https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L83, it results to errors http://paste.openstack.org/show/477804/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1512416/+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 1528637] [NEW] (Import Refactor) Mark the `/file` endpoint as deprecated
Public bug reported: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ One of the goals of this spec is to improve the image import process and allow for other background operations to be executed when the image data is added. To do this without breaking the existing API, we're adding a new `/stage` endpoint that supersedes the existing `/file` endpoint where the image data is currently uploaded. Eventually, we'd like to completely deprecate (and perhaps delete) that endpoint. Definitely disable it. This lite spec is to mark that endpoint as deprecated and recommend deployers to disable it and have users move forward to the new `/stage` endpoint. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1528637 Title: (Import Refactor) Mark the `/file` endpoint as deprecated Status in Glance: New Bug description: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ One of the goals of this spec is to improve the image import process and allow for other background operations to be executed when the image data is added. To do this without breaking the existing API, we're adding a new `/stage` endpoint that supersedes the existing `/file` endpoint where the image data is currently uploaded. Eventually, we'd like to completely deprecate (and perhaps delete) that endpoint. Definitely disable it. This lite spec is to mark that endpoint as deprecated and recommend deployers to disable it and have users move forward to the new `/stage` endpoint. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1528637/+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 1527716] [NEW] (Import Refactor) Make tasks API admin only
Public bug reported: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ One of the goals of this spec is to improve the image import process and allow for other background operations to be executed when the image data is added. This supersedes the need of the task endpoint that we'll slowly deprecate. As part of this spec, we should make it admin only and warn deployers that this API is going to be deprecated. ** Affects: glance Importance: Wishlist Status: New ** Tags: mitaka-new-import-process -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1527716 Title: (Import Refactor) Make tasks API admin only Status in Glance: New Bug description: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ One of the goals of this spec is to improve the image import process and allow for other background operations to be executed when the image data is added. This supersedes the need of the task endpoint that we'll slowly deprecate. As part of this spec, we should make it admin only and warn deployers that this API is going to be deprecated. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1527716/+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 1526675] Re: test_models_sync fails with 'Models and migration scripts aren't in sync'
** Also affects: glance/kilo
Importance: Undecided
Status: New
** Changed in: glance/kilo
Assignee: (unassigned) => Flavio Percoco (flaper87)
** Changed in: glance/liberty
Assignee: (unassigned) => Flavio Percoco (flaper87)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1526675
Title:
test_models_sync fails with 'Models and migration scripts aren't in
sync'
Status in Glance:
Fix Released
Status in Glance kilo series:
New
Status in Glance liberty series:
Fix Committed
Status in neutron:
Fix Released
Status in OpenStack Compute (nova):
Fix Committed
Status in OpenStack Compute (nova) liberty series:
Confirmed
Status in oslo.db:
In Progress
Bug description:
2015-12-16 08:06:12.907 | 2015-12-16 08:06:12.889 |
neutron.tests.functional.db.test_migrations.TestModelsMigrationsMysql.test_models_sync
2015-12-16 08:06:12.907 | 2015-12-16 08:06:12.891 |
--
2015-12-16 08:06:12.908 | 2015-12-16 08:06:12.892 |
2015-12-16 08:06:12.908 | 2015-12-16 08:06:12.894 | Captured traceback:
2015-12-16 08:06:12.908 | 2015-12-16 08:06:12.896 | ~~~
2015-12-16 08:06:12.909 | 2015-12-16 08:06:12.897 | Traceback (most
recent call last):
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.899 | File
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/test_migrations.py",
line 603, in test_models_sync
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.900 | "Models and
migration scripts aren't in sync:\n%s" % msg)
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.901 | File
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/unittest2/case.py",
line 690, in fail
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.903 | raise
self.failureException(msg)
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.904 | AssertionError:
Models and migration scripts aren't in sync:
2015-12-16 08:06:12.917 | 2015-12-16 08:06:12.905 | [ [ ( 'modify_type',
2015-12-16 08:06:12.918 | 2015-12-16 08:06:12.907 | None,
2015-12-16 08:06:12.920 | 2015-12-16 08:06:12.908 | 'floatingips',
2015-12-16 08:06:12.921 | 2015-12-16 08:06:12.909 |
'standard_attr_id',
2015-12-16 08:06:12.930 | 2015-12-16 08:06:12.911 | {
'existing_nullable': False,
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.912 |
'existing_server_default': False},
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.913 |
BIGINT(display_width=20),
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.915 | Variant())],
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.916 | [ ( 'modify_type',
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.918 | None,
2015-12-16 08:06:12.932 | 2015-12-16 08:06:12.919 | 'networks',
2015-12-16 08:06:12.933 | 2015-12-16 08:06:12.921 |
'standard_attr_id',
2015-12-16 08:06:12.934 | 2015-12-16 08:06:12.922 | {
'existing_nullable': False,
2015-12-16 08:06:12.935 | 2015-12-16 08:06:12.923 |
'existing_server_default': False},
2015-12-16 08:06:12.937 | 2015-12-16 08:06:12.925 |
BIGINT(display_width=20),
2015-12-16 08:06:12.938 | 2015-12-16 08:06:12.926 | Variant())],
2015-12-16 08:06:12.940 | 2015-12-16 08:06:12.927 | [ ( 'modify_type',
2015-12-16 08:06:12.941 | 2015-12-16 08:06:12.929 | None,
2015-12-16 08:06:12.942 | 2015-12-16 08:06:12.930 | 'ports',
2015-12-16 08:06:12.944 | 2015-12-16 08:06:12.932 |
'standard_attr_id',
2015-12-16 08:06:12.945 | 2015-12-16 08:06:12.933 | {
'existing_nullable': False,
2015-12-16 08:06:12.946 | 2015-12-16 08:06:12.935 |
'existing_server_default': False},
2015-12-16 08:06:12.948 | 2015-12-16 08:06:12.936 |
BIGINT(display_width=20),
2015-12-16 08:06:12.949 | 2015-12-16 08:06:12.938 | Variant())],
2015-12-16 08:06:12.951 | 2015-12-16 08:06:12.939 | [ ( 'modify_type',
2015-12-16 08:06:12.952 | 2015-12-16 08:06:12.941 | None,
2015-12-16 08:06:12.954 | 2015-12-16 08:06:12.942 | 'routers',
2015-12-16 08:06:12.955 | 2015-12-16 08:06:12.943 |
'standard_attr_id',
2015-12-16 08:06:12.957 | 2015-12-16 08:06:12.945 | {
'existing_nullable': False,
2015-12-16 08:06:12.958 | 2015-12-16 08:06:12.946 |
'existing_server_default': False},
2015-12-16 08:06:12.959 | 2015-12-16 08:06:12.947 |
BIGINT(display_width=20),
2015-12-16 08:06:12.961 | 2015-12-16 08:06:12.949 | Variant())],
2015-12-16 08:06:12.962 | 2015-12-16 08:06:12.950 | [ ( 'modify_type',
2015-12-16 08:06:12.963 | 2015-12-16 08:06:12.9
[Yahoo-eng-team] [Bug 1526675] Re: test_models_sync fails with 'Models and migration scripts aren't in sync'
** Also affects: glance
Importance: Undecided
Status: New
** Changed in: glance
Assignee: (unassigned) => Flavio Percoco (flaper87)
** Changed in: glance
Importance: Undecided => Critical
** Changed in: glance
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1526675
Title:
test_models_sync fails with 'Models and migration scripts aren't in
sync'
Status in Glance:
Triaged
Status in neutron:
Fix Released
Status in OpenStack Compute (nova):
In Progress
Status in OpenStack Compute (nova) liberty series:
Confirmed
Status in oslo.db:
New
Bug description:
2015-12-16 08:06:12.907 | 2015-12-16 08:06:12.889 |
neutron.tests.functional.db.test_migrations.TestModelsMigrationsMysql.test_models_sync
2015-12-16 08:06:12.907 | 2015-12-16 08:06:12.891 |
--
2015-12-16 08:06:12.908 | 2015-12-16 08:06:12.892 |
2015-12-16 08:06:12.908 | 2015-12-16 08:06:12.894 | Captured traceback:
2015-12-16 08:06:12.908 | 2015-12-16 08:06:12.896 | ~~~
2015-12-16 08:06:12.909 | 2015-12-16 08:06:12.897 | Traceback (most
recent call last):
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.899 | File
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/test_migrations.py",
line 603, in test_models_sync
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.900 | "Models and
migration scripts aren't in sync:\n%s" % msg)
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.901 | File
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/unittest2/case.py",
line 690, in fail
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.903 | raise
self.failureException(msg)
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.904 | AssertionError:
Models and migration scripts aren't in sync:
2015-12-16 08:06:12.917 | 2015-12-16 08:06:12.905 | [ [ ( 'modify_type',
2015-12-16 08:06:12.918 | 2015-12-16 08:06:12.907 | None,
2015-12-16 08:06:12.920 | 2015-12-16 08:06:12.908 | 'floatingips',
2015-12-16 08:06:12.921 | 2015-12-16 08:06:12.909 |
'standard_attr_id',
2015-12-16 08:06:12.930 | 2015-12-16 08:06:12.911 | {
'existing_nullable': False,
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.912 |
'existing_server_default': False},
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.913 |
BIGINT(display_width=20),
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.915 | Variant())],
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.916 | [ ( 'modify_type',
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.918 | None,
2015-12-16 08:06:12.932 | 2015-12-16 08:06:12.919 | 'networks',
2015-12-16 08:06:12.933 | 2015-12-16 08:06:12.921 |
'standard_attr_id',
2015-12-16 08:06:12.934 | 2015-12-16 08:06:12.922 | {
'existing_nullable': False,
2015-12-16 08:06:12.935 | 2015-12-16 08:06:12.923 |
'existing_server_default': False},
2015-12-16 08:06:12.937 | 2015-12-16 08:06:12.925 |
BIGINT(display_width=20),
2015-12-16 08:06:12.938 | 2015-12-16 08:06:12.926 | Variant())],
2015-12-16 08:06:12.940 | 2015-12-16 08:06:12.927 | [ ( 'modify_type',
2015-12-16 08:06:12.941 | 2015-12-16 08:06:12.929 | None,
2015-12-16 08:06:12.942 | 2015-12-16 08:06:12.930 | 'ports',
2015-12-16 08:06:12.944 | 2015-12-16 08:06:12.932 |
'standard_attr_id',
2015-12-16 08:06:12.945 | 2015-12-16 08:06:12.933 | {
'existing_nullable': False,
2015-12-16 08:06:12.946 | 2015-12-16 08:06:12.935 |
'existing_server_default': False},
2015-12-16 08:06:12.948 | 2015-12-16 08:06:12.936 |
BIGINT(display_width=20),
2015-12-16 08:06:12.949 | 2015-12-16 08:06:12.938 | Variant())],
2015-12-16 08:06:12.951 | 2015-12-16 08:06:12.939 | [ ( 'modify_type',
2015-12-16 08:06:12.952 | 2015-12-16 08:06:12.941 | None,
2015-12-16 08:06:12.954 | 2015-12-16 08:06:12.942 | 'routers',
2015-12-16 08:06:12.955 | 2015-12-16 08:06:12.943 |
'standard_attr_id',
2015-12-16 08:06:12.957 | 2015-12-16 08:06:12.945 | {
'existing_nullable': False,
2015-12-16 08:06:12.958 | 2015-12-16 08:06:12.946 |
'existing_server_default': False},
2015-12-16 08:06:12.959 | 2015-12-16 08:06:12.947 |
BIGINT(display_width=20),
2015-12-16 08:06:12.961 | 2015-12-16 08:06:12.949 | Variant())],
2015-12-16 08:06:12.962 | 2015-12-16 08:06:12.950 | [ ( 'modify_type',
2015-12-16 08:06:12.963 | 2015-12-16 08:06:12.952 | None,
2015-12-16 08:06:12.965 | 2015-12-16 08:06:12.953 |
[Yahoo-eng-team] [Bug 1526675] Re: test_models_sync fails with 'Models and migration scripts aren't in sync'
** Also affects: glance/liberty
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1526675
Title:
test_models_sync fails with 'Models and migration scripts aren't in
sync'
Status in Glance:
Triaged
Status in Glance liberty series:
New
Status in neutron:
Fix Released
Status in OpenStack Compute (nova):
In Progress
Status in OpenStack Compute (nova) liberty series:
Confirmed
Status in oslo.db:
New
Bug description:
2015-12-16 08:06:12.907 | 2015-12-16 08:06:12.889 |
neutron.tests.functional.db.test_migrations.TestModelsMigrationsMysql.test_models_sync
2015-12-16 08:06:12.907 | 2015-12-16 08:06:12.891 |
--
2015-12-16 08:06:12.908 | 2015-12-16 08:06:12.892 |
2015-12-16 08:06:12.908 | 2015-12-16 08:06:12.894 | Captured traceback:
2015-12-16 08:06:12.908 | 2015-12-16 08:06:12.896 | ~~~
2015-12-16 08:06:12.909 | 2015-12-16 08:06:12.897 | Traceback (most
recent call last):
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.899 | File
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/test_migrations.py",
line 603, in test_models_sync
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.900 | "Models and
migration scripts aren't in sync:\n%s" % msg)
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.901 | File
"/opt/stack/new/neutron/.tox/dsvm-functional/local/lib/python2.7/site-packages/unittest2/case.py",
line 690, in fail
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.903 | raise
self.failureException(msg)
2015-12-16 08:06:12.916 | 2015-12-16 08:06:12.904 | AssertionError:
Models and migration scripts aren't in sync:
2015-12-16 08:06:12.917 | 2015-12-16 08:06:12.905 | [ [ ( 'modify_type',
2015-12-16 08:06:12.918 | 2015-12-16 08:06:12.907 | None,
2015-12-16 08:06:12.920 | 2015-12-16 08:06:12.908 | 'floatingips',
2015-12-16 08:06:12.921 | 2015-12-16 08:06:12.909 |
'standard_attr_id',
2015-12-16 08:06:12.930 | 2015-12-16 08:06:12.911 | {
'existing_nullable': False,
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.912 |
'existing_server_default': False},
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.913 |
BIGINT(display_width=20),
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.915 | Variant())],
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.916 | [ ( 'modify_type',
2015-12-16 08:06:12.931 | 2015-12-16 08:06:12.918 | None,
2015-12-16 08:06:12.932 | 2015-12-16 08:06:12.919 | 'networks',
2015-12-16 08:06:12.933 | 2015-12-16 08:06:12.921 |
'standard_attr_id',
2015-12-16 08:06:12.934 | 2015-12-16 08:06:12.922 | {
'existing_nullable': False,
2015-12-16 08:06:12.935 | 2015-12-16 08:06:12.923 |
'existing_server_default': False},
2015-12-16 08:06:12.937 | 2015-12-16 08:06:12.925 |
BIGINT(display_width=20),
2015-12-16 08:06:12.938 | 2015-12-16 08:06:12.926 | Variant())],
2015-12-16 08:06:12.940 | 2015-12-16 08:06:12.927 | [ ( 'modify_type',
2015-12-16 08:06:12.941 | 2015-12-16 08:06:12.929 | None,
2015-12-16 08:06:12.942 | 2015-12-16 08:06:12.930 | 'ports',
2015-12-16 08:06:12.944 | 2015-12-16 08:06:12.932 |
'standard_attr_id',
2015-12-16 08:06:12.945 | 2015-12-16 08:06:12.933 | {
'existing_nullable': False,
2015-12-16 08:06:12.946 | 2015-12-16 08:06:12.935 |
'existing_server_default': False},
2015-12-16 08:06:12.948 | 2015-12-16 08:06:12.936 |
BIGINT(display_width=20),
2015-12-16 08:06:12.949 | 2015-12-16 08:06:12.938 | Variant())],
2015-12-16 08:06:12.951 | 2015-12-16 08:06:12.939 | [ ( 'modify_type',
2015-12-16 08:06:12.952 | 2015-12-16 08:06:12.941 | None,
2015-12-16 08:06:12.954 | 2015-12-16 08:06:12.942 | 'routers',
2015-12-16 08:06:12.955 | 2015-12-16 08:06:12.943 |
'standard_attr_id',
2015-12-16 08:06:12.957 | 2015-12-16 08:06:12.945 | {
'existing_nullable': False,
2015-12-16 08:06:12.958 | 2015-12-16 08:06:12.946 |
'existing_server_default': False},
2015-12-16 08:06:12.959 | 2015-12-16 08:06:12.947 |
BIGINT(display_width=20),
2015-12-16 08:06:12.961 | 2015-12-16 08:06:12.949 | Variant())],
2015-12-16 08:06:12.962 | 2015-12-16 08:06:12.950 | [ ( 'modify_type',
2015-12-16 08:06:12.963 | 2015-12-16 08:06:12.952 | None,
2015-12-16 08:06:12.965 | 2015-12-16 08:06:12.953 |
'securitygrouprules',
2015-12-16 08:06:12.966 | 2015-12-16 08:06:12.954 |
'standard_attr_id',
2015-12-16 08:06:12.967 | 2015-12-16 08:06:12.956 | {
[Yahoo-eng-team] [Bug 1518431] Re: Glance failed to upload image to swift storage
Stuart, Kairat, This bug is hard to reproduce, TBH. The race happens in a combination of Glance's v2 behavior and swift's driver. This is not *entirely* Glance's fault, though. The Glance "weird" part is not being able to recognize "0-sized" chunks before submitting them. However, this is being refactored a bit by one of our current swift specs (need to find the link). The swift issue is that the DELETE is hitting the swift node before the last chunk is written/available. This could be caused by unsynchronized clocks or just a race condition. I've managed to reproduce it in one of our installers CI systems with some frequency but I have yet to find a deterministic way to do so. Meanwhile, I can confirm this issue exists. While it's true that part of this code is being refactored by the "buffered chunk writer" spec, I still think we should fix it as it's eligible for backport. Hope the above helps clarifying a bit the real problem ** Also affects: glance/liberty Importance: Undecided Status: New ** Changed in: glance Importance: Undecided => Medium ** Changed in: glance/liberty Importance: Undecided => Medium ** Changed in: glance/liberty Status: New => Triaged ** Changed in: glance/liberty Assignee: (unassigned) => Cyril Roelandt (cyril-roelandt) -- 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: In Progress Status in Glance liberty series: Triaged 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 1523941] [NEW] (Import Refactor) Header changes
Public bug reported: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ This spec requires new headers to be added to some of our calls. For example, the image-create call should return the upload path for the image data as it was discussed in the spec. This bug likely depends on this one: https://bugs.launchpad.net/glance/+bug/1523937 ** Affects: glance Importance: Wishlist Status: New ** Tags: mitaka-new-import-process -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1523941 Title: (Import Refactor) Header changes Status in Glance: New Bug description: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ This spec requires new headers to be added to some of our calls. For example, the image-create call should return the upload path for the image data as it was discussed in the spec. This bug likely depends on this one: https://bugs.launchpad.net/glance/+bug/1523937 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1523941/+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 1523955] [NEW] (Import Refactor) Implement `import` call
Public bug reported: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ The final `import` call, as it was discussed in the spec so far, will finalize the image import process and trigger the task engine. Most of this triggering logic has been implemented already during Kilo but it will have to be tight to the import process. This work depends on: https://bugs.launchpad.net/glance/+bug/1523937 ** Affects: glance Importance: Wishlist Status: New ** Tags: mitaka-new-import-process -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1523955 Title: (Import Refactor) Implement `import` call Status in Glance: New Bug description: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ The final `import` call, as it was discussed in the spec so far, will finalize the image import process and trigger the task engine. Most of this triggering logic has been implemented already during Kilo but it will have to be tight to the import process. This work depends on: https://bugs.launchpad.net/glance/+bug/1523937 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1523955/+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 1523935] [NEW] API Version Bump
Public bug reported: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ In order to implement this spec, we need to bump the API version. This bug will track that work ** Affects: glance Importance: Wishlist Status: New ** Tags: mitaka-new-import-process -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1523935 Title: API Version Bump Status in Glance: New Bug description: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ In order to implement this spec, we need to bump the API version. This bug will track that work To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1523935/+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 1523934] [NEW] API Version Bump
Public bug reported: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ In order to implement this spec, we need to bump the API version. This bug will track that work ** Affects: glance Importance: Wishlist Status: New ** Tags: mitaka-new-import-process -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1523934 Title: API Version Bump Status in Glance: New Bug description: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ In order to implement this spec, we need to bump the API version. This bug will track that work To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1523934/+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 1523944] [NEW] (Import Refactor) Implement discoverability calls
Public bug reported: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ In order to make this import process discoverable, we need to change some of our API schemas to reflect the supported upload methods. We also need to add some new schemas/calls. Please, refer to the spec for more info, this is a tracking bug and it likely depends on: https://bugs.launchpad.net/glance/+bug/1523937 ** Affects: glance Importance: Wishlist Status: New ** Tags: mitaka-new-import-process -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1523944 Title: (Import Refactor) Implement discoverability calls Status in Glance: New Bug description: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ In order to make this import process discoverable, we need to change some of our API schemas to reflect the supported upload methods. We also need to add some new schemas/calls. Please, refer to the spec for more info, this is a tracking bug and it likely depends on: https://bugs.launchpad.net/glance/+bug/1523937 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1523944/+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 1523937] [NEW] (Import Refactor) Policy Rules
Public bug reported: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ This spec requires new policy rules to protect the API and enable/disable it when needed. ** Affects: glance Importance: Wishlist Status: New ** Tags: mitaka-new-import-process -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1523937 Title: (Import Refactor) Policy Rules Status in Glance: New Bug description: This is a sub-task for the image import process work: https://review.openstack.org/#/c/232371/ This spec requires new policy rules to protect the API and enable/disable it when needed. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1523937/+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 1522132] Re: Scrubber tests are broken due to deprecated config filesystem_store_datadir under DEFAULT section
** Also affects: glance/liberty Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1522132 Title: Scrubber tests are broken due to deprecated config filesystem_store_datadir under DEFAULT section Status in Glance: Fix Committed Status in Glance liberty series: New Bug description: Store config options under DEFAULT section have been marked deprecated and moved to glance_store section. With glance_store 0.10.0, the deprecated options have been dropped, which causes the scrubber tests to fail as they still have filesystem_store_datadir under DEFAULT section. Here is a link to one of the gate jobs failing: http://logs.openstack.org/48/245948/4/check/gate-glance-python27/b264ae7/console.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1522132/+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 1519402] Re: Add docker container format to defaults
** Also affects: python-glanceclient Importance: Undecided Status: New ** Changed in: python-glanceclient Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1519402 Title: Add docker container format to defaults Status in Glance: In Progress Status in python-glanceclient: New Bug description: An image with the 'docker' container format is a tar archive of the container file system. In order to use the nova-docker compute driver in nova and boot docker instances glance support of the docker container format is required. Rather than having to specifically configure glance to allow the docker container format I would like to add it to the default list of container_formats. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1519402/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1521236] Re: Missing list of stores in glance-api.conf
** Also affects: glance-store/liberty Importance: Medium Status: Confirmed ** Changed in: glance-store/liberty Assignee: (unassigned) => Stuart McLaren (stuart-mclaren) ** Also affects: glance/mitaka Importance: Medium Assignee: Stuart McLaren (stuart-mclaren) Status: In Progress ** No longer affects: glance/mitaka -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1521236 Title: Missing list of stores in glance-api.conf Status in Glance: In Progress Status in glance_store: Confirmed Status in glance_store liberty series: Confirmed Bug description: We used to give some indication of which stores could be configured: [glance_store] # List of which store classes and store class locations are # currently known to glance at startup. # Deprecated group/name - [DEFAULT]/known_stores # Existing but disabled stores: # glance.store.rbd.Store, # glance.store.s3.Store, # glance.store.swift.Store, # glance.store.sheepdog.Store, # glance.store.cinder.Store, # glance.store.gridfs.Store, # glance.store.vmware_datastore.Store, #stores = glance.store.filesystem.Store, # glance.store.http.Store We don't seem to have a full list of stores in etc/glance-api.conf any more: [glance_store] # # From glance.store # # List of stores enabled (list value) #stores = file,http To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1521236/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1495519] Re: import flow doesn't raise error on forbidden location
** Also affects: glance/liberty
Importance: Undecided
Status: New
** Changed in: glance
Importance: High => Medium
** Changed in: glance/liberty
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1495519
Title:
import flow doesn't raise error on forbidden location
Status in Glance:
In Progress
Status in Glance liberty series:
New
Bug description:
The following command correctly raises an exception server side but it
doesn't report the error back to the user. This ends up in the user
"thinking" the task was created correctly:
$ glance --os-image-api-version 2 --os-image-url
http://localhost:9292/v2 --os-tenant-id
a1875f8a27f74708b6fb9281e7430a98 task-create --type import --input
'{"import_from_format": "qcow2", "import_from":
"swift://127.0.0.1:8000/test.qcow2", "image_properties":
{"disk_format": "qcow2", "container_format": "bare"}}'
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1495519/+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 1483353] Re: v1: Updates using x-image-meta-id header provoke E500 or 200
** Summary changed: - v1: incorrect x-image-meta-id header provokes E500 + v1: Updates using x-image-meta-id header provoke E500 or 200 ** Description changed: - (Niall)This bug addresses the problem where the id is incorrect. - $ curl -v -X PUT http://127.0.0.1:9292/v1/images/8aa1f62d-73f2-4ed7-8d4c-b66407abd439 -H 'X-Auth-Token: 7535a1be77e3459e8e4928aae02a8042' -H 'x-image-meta-id: fd6db2fa-9c9d-4105-aa3b-657914593de8' * Hostname was NOT found in DNS cache * Trying 127.0.0.1... * Connected to 127.0.0.1 (127.0.0.1) port 9292 (#0) > PUT /v1/images/8aa1f62d-73f2-4ed7-8d4c-b66407abd439 HTTP/1.1 > User-Agent: curl/7.35.0 > Host: 127.0.0.1:9292 > Accept: */* > X-Auth-Token: 7535a1be77e3459e8e4928aae02a8042 > x-image-meta-id: fd6db2fa-9c9d-4105-aa3b-657914593de8 > < HTTP/1.1 500 Internal Server Error < Content-Type: text/plain < Content-Length: 0 < Date: Mon, 10 Aug 2015 17:00:00 GMT < Connection: close < * Closing connection 0 + + and + + + $ curl -v -X PUT http://127.0.0.1:9292/v1/images/8aa1f62d-73f2-4ed7-8d4c-b66407abd439 -H 'X-Auth-Token: 7535a1be77e3459e8e4928aae02a8042' -H 'x-image-meta-id: fd6db2fa-9c9d-4105-aa3b-657914593de8' + * Hostname was NOT found in DNS cache + * Trying 127.0.0.1... + * Connected to 127.0.0.1 (127.0.0.1) port 9292 (#0) + > PUT /v1/images/8aa1f62d-73f2-4ed7-8d4c-b66407abd439 HTTP/1.1 + > User-Agent: curl/7.35.0 + > Host: 127.0.0.1:9292 + > Accept: */* + > X-Auth-Token: 7535a1be77e3459e8e4928aae02a8042 + > x-image-meta-id: fd6db2fa-9c9d-4105-aa3b-657914593de8 + > + < HTTP/1.1 500 Internal Server Error + < Content-Type: text/plain + < Content-Length: 0 + < Date: Mon, 10 Aug 2015 17:00:00 GMT + < Connection: close + < + * Closing connection 0 + + Should return 403 ** Changed in: glance Milestone: None => mitaka-1 ** Changed in: glance Importance: Undecided => Medium ** Also affects: glance/liberty Importance: Undecided Status: New ** Changed in: glance/liberty Importance: Undecided => Medium ** Changed in: glance/liberty Assignee: (unassigned) => Flavio Percoco (flaper87) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1483353 Title: v1: Updates using x-image-meta-id header provoke E500 or 200 Status in Glance: In Progress Status in Glance liberty series: In Progress Bug description: $ curl -v -X PUT http://127.0.0.1:9292/v1/images/8aa1f62d-73f2-4ed7-8d4c-b66407abd439 -H 'X-Auth-Token: 7535a1be77e3459e8e4928aae02a8042' -H 'x-image-meta-id: fd6db2fa-9c9d-4105-aa3b-657914593de8' * Hostname was NOT found in DNS cache * Trying 127.0.0.1... * Connected to 127.0.0.1 (127.0.0.1) port 9292 (#0) > PUT /v1/images/8aa1f62d-73f2-4ed7-8d4c-b66407abd439 HTTP/1.1 > User-Agent: curl/7.35.0 > Host: 127.0.0.1:9292 > Accept: */* > X-Auth-Token: 7535a1be77e3459e8e4928aae02a8042 > x-image-meta-id: fd6db2fa-9c9d-4105-aa3b-657914593de8 > < HTTP/1.1 500 Internal Server Error < Content-Type: text/plain < Content-Length: 0 < Date: Mon, 10 Aug 2015 17:00:00 GMT < Connection: close < * Closing connection 0 and $ curl -v -X PUT http://127.0.0.1:9292/v1/images/8aa1f62d-73f2-4ed7-8d4c-b66407abd439 -H 'X-Auth-Token: 7535a1be77e3459e8e4928aae02a8042' -H 'x-image-meta-id: fd6db2fa-9c9d-4105-aa3b-657914593de8' * Hostname was NOT found in DNS cache * Trying 127.0.0.1... * Connected to 127.0.0.1 (127.0.0.1) port 9292 (#0) > PUT /v1/images/8aa1f62d-73f2-4ed7-8d4c-b66407abd439 HTTP/1.1 > User-Agent: curl/7.35.0 > Host: 127.0.0.1:9292 > Accept: */* > X-Auth-Token: 7535a1be77e3459e8e4928aae02a8042 > x-image-meta-id: fd6db2fa-9c9d-4105-aa3b-657914593de8 > < HTTP/1.1 500 Internal Server Error < Content-Type: text/plain < Content-Length: 0 < Date: Mon, 10 Aug 2015 17:00:00 GMT < Connection: close < * Closing connection 0 Should return 403 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1483353/+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 1518431] Re: Glance failed to upload image to swift storage
I've debugged this issue a bit further and it's not related to RadosGW.
The swift driver deletes that last 0-byte chunk when the image is being
uploaded and that's causing this conflict.
---
if bytes_read == 0:
# Delete the last chunk, because it's of zero size.
# This will happen if size == 0.
LOG.debug("Deleting final zero-length chunk")
connection.delete_object(location.container,
chunk_name)
break
chunk_id += 1
combined_chunks_size += bytes_read
---
** Summary changed:
- Glance failed to upload image to swift storage via RadosGW
+ Glance failed to upload image to swift storage
** Changed in: glance
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1518431
Title:
Glance failed to upload image to swift storage
Status in Glance:
Confirmed
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 1350892] Re: Nova VMWare provisioning errors
quite old and no feedback ** Changed in: glance-store Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1350892 Title: Nova VMWare provisioning errors Status in glance_store: Invalid Status in OpenStack Compute (nova): Invalid Bug description: I am trying to provision a RHEL VMWare image (custom vmdk created through template) Openstack dashboard shows provisioning status for a long time, however no activity on vCenter. PS- CirrOS VMDK (Conveterted from qemu-img gets deployed with out errors) Request help here 2014-07-31 16:48:44.017 2931 WARNING nova.openstack.common.loopingcall [-] task run outlasted interval by 11.98221 sec 2014-07-31 16:50:27.015 2931 WARNING nova.openstack.common.loopingcall [-] task run outlasted interval by 12.987183 sec 2014-07-31 16:51:57.715 2931 WARNING nova.openstack.common.loopingcall [-] task run outlasted interval by 0.696367 sec 2014-07-31 16:58:32.860 2931 ERROR suds.client [-] http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/;> SessionManager 5216dd75-609c-3c5a-b7e6-9708bd7dc786 Administrator 2014-07-31 16:58:32.863 2931 WARNING nova.virt.vmwareapi.driver [req-e6f5ba33-a37a-476b-a6b6-801ccd80bac6 6b875fcfe8344addb87382298c1a75be dad97a29e60849a2a6ad9d0ffb353161] Unable to validate session 5216dd75-609c-3c5a-b7e6-9708bd7dc786! 2014-07-31 16:58:32.863 2931 WARNING nova.virt.vmwareapi.driver [req-e6f5ba33-a37a-476b-a6b6-801ccd80bac6 6b875fcfe8344addb87382298c1a75be dad97a29e60849a2a6ad9d0ffb353161] Session 5216dd75-609c-3c5a-b7e6-9708bd7dc786 is inactive! 2014-07-31 16:58:48.406 2931 ERROR suds.client [-] http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/;> SessionManager 5216dd75-609c-3c5a-b7e6-9708bd7dc786 To manage notifications about this bug go to: https://bugs.launchpad.net/glance-store/+bug/1350892/+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 1485940] Re: non-admin user get error code "500" if he tries to deactivate the image hosted by admin which have visibility "public"
Kilo: https://review.openstack.org/248856 Liberty: https://review.openstack.org/248855 ** Also affects: glance/kilo Importance: Undecided Status: New ** Also affects: glance/liberty Importance: Undecided Status: New ** Changed in: glance/kilo Importance: Undecided => High ** Changed in: glance/liberty Importance: Undecided => High ** Changed in: glance/kilo Assignee: (unassigned) => Flavio Percoco (flaper87) ** Changed in: glance/liberty Assignee: (unassigned) => Flavio Percoco (flaper87) ** Changed in: glance/kilo Status: New => In Progress ** Changed in: glance/liberty 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/1485940 Title: non-admin user get error code "500" if he tries to deactivate the image hosted by admin which have visibility "public" Status in Glance: Fix Committed Status in Glance kilo series: In Progress Status in Glance liberty series: In Progress Bug description: Description: non-admin user get error code "500" if he tries to deactivate the image hosted by admin which have visibility "public" which is not user friendly it should raise response 403 forbidden. Steps: scenario was tested using tempest. 1. image was uploaded by admin user with visibility "public" using api. 2. deactivate request was generated by non-admin user using api. 3. In response header "500" was received. Expected: 1. even if non-admin user is not allowed to deactivate image uploaded by admin user having visibility "public", response should contain "403 forbidden" to give meaning full information to user that he is not authorized to perform this act. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1485940/+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 1518431] Re: Glance failed to upload image to swift storage via RadosGW
The swift driver is meant to be used to talk to Swift. If there's a problem in RadosGW swift API, we should notify the RadosGW maintainers. ** 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/1518431 Title: Glance failed to upload image to swift storage via RadosGW 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 1517060] Re: User (without admin privileges) can change size your own image with 'deactivated' status.
** Tags removed: liberty-backport-potential ** Also affects: glance/liberty Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1517060 Title: User (without admin privileges) can change size your own image with 'deactivated' status. Status in Glance: In Progress Status in Glance liberty series: New Bug description: Steps to reproduce: 1. Create a new image with 'active' status. 2. Deactivate this image from admin. (image should have a 'deactivated' status) 3. Use this curl request: curl -X PUT http://localhost:9292/v1/images/ -H 'X-Auth-Token: ' -H 'x-image-meta-size: 1234567' 4. Verify that created image have a '1234567' size. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1517060/+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 1507564] Re: os.path.remove doesn't exist. Conver task fails
** Also affects: glance/liberty Importance: Undecided Status: New ** Tags removed: liberty-backport-potential -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1507564 Title: os.path.remove doesn't exist. Conver task fails Status in Glance: In Progress Status in Glance liberty series: New Bug description: File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 96, in run for _state in self.run_iter(): File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 146, in run_iter self._change_state(states.FAILURE) File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 130, in run_iter failure.Failure.reraise_if_any(failures) File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 244, in reraise_if_any failures[0].reraise() File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 251, in reraise six.reraise(*self._exc_info) File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/executor.py", line 86, in _revert_task result = task.revert(**arguments) File "/usr/lib/python2.7/site-packages/glance/async/flows/convert.py", line 99, in revert os.path.remove(fs_path) AttributeError: 'module' object has no attribute 'remove' 2015-07-11 11:40:00.817 6663 INFO eventlet.wsgi.server [req-c4c286ec-2248-4d93-b631-a2270de43ec8 7a6bd2901f0642b18be91d82782ed1ca 3954f0a8635249eba2eda9a489e233a7 - - -] 10.12.27.41 - - [11/Jul/2015 11:40:00] "POST /v2/tasks HTTP/1.1" 500 139 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1507564/+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 1517060] Re: User (without admin privileges) can change size your own image with 'deactivated' status.
** Also affects: glance/kilo Importance: Undecided Status: New ** Changed in: glance/kilo Importance: Undecided => High ** Changed in: glance/liberty Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1517060 Title: User (without admin privileges) can change size your own image with 'deactivated' status. Status in Glance: In Progress Status in Glance kilo series: New Status in Glance liberty series: New Bug description: Steps to reproduce: 1. Create a new image with 'active' status. 2. Deactivate this image from admin. (image should have a 'deactivated' status) 3. Use this curl request: curl -X PUT http://localhost:9292/v1/images/ -H 'X-Auth-Token: ' -H 'x-image-meta-size: 1234567' 4. Verify that created image have a '1234567' size. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1517060/+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 1505474] Re: Glance raise 500 error when delete images with unallowed status change
** Also affects: glance/kilo Importance: Undecided Status: New ** Also affects: glance/liberty Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1505474 Title: Glance raise 500 error when delete images with unallowed status change Status in Glance: Fix Committed Status in Glance kilo series: New Status in Glance liberty series: New Bug description: When user try to change the image's status to unallowed status, such as deactivated --> pending-delete, it will rasie a 500 error. It's not clear to user. So we should catch this error and return to user. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1505474/+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 1412802] Re: copy-from broken for large files and swift
** No longer affects: glance/icehouse ** No longer affects: glance/juno -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1412802 Title: copy-from broken for large files and swift Status in Glance: Fix Released Status in glance_store: In Progress Bug description: Glance may loose some image data while transferring it to the backing store thus corrupting the image when ALL the following conditions are met: - Image is being created by copying data from remote source (--copy-from CLI parameter or appropriate API call) - Backing store is Swift - Image size is larger then configured "swift_store_large_object_size" In such scenarios the last chunk stored in Swift will have the size significantly less then expected. An attempt to download the image will result in a checksum verification error, however the checksum stored in Glance (with image metadata) is correct, and so is the size. This is easily reproducible even on devstack (if the devstack is configured to run Swift as Glance backend). Just decrease 'swift_store_large_object_size' to some reasonably low value (i.e. 200 Mb) and try to copy-from any image which is larger then that value. After the upload is successful, check the object size in swift (by either summing the sizes of all the chunks or by looking to the size of virtual large object) - they will be lower then expected: glance image-create --name tst --disk-format qcow2 --container-format bare --copy-from http://192.168.56.1:8000/F18-x86_64-cfntools.qcow2 ... glance image-list +--+-+-+--+---++ | ID | Name| Disk Format | Container Format | Size | Status | +--+-+-+--+---++ | fc34ec49-4bd3-40dd-918f-44d3254f2ac9 | tst | qcow2 | bare | 536412160 | active | +--+-+-+--+---++ ... swift stat glance fc34ec49-4bd3-40dd-918f-44d3254f2ac9 --os-tenant-name service --os-username admin Account: AUTH_cce6e9c12fa34c63b64ef29e84861554 Container: glance Object: fc34ec49-4bd3-40dd-918f-44d3254f2ac9 Content Type: application/octet-stream Content Length: 509804544 < see, the size is different! Last Modified: Mon, 19 Jan 2015 15:52:18 GMT ETag: "6d0612f82db9a531b34d25823a45073d" Manifest: glance/fc34ec49-4bd3-40dd-918f-44d3254f2ac9- Accept-Ranges: bytes X-Timestamp: 1421682737.01148 X-Trans-Id: tx01a19f7476a541808c9a1-0054bd28e1 glance image-download tst --file out.qcow2 [Errno 32] Corrupt image download. Checksum was 0eeddae1007f01b0029136d28518f538 expected 3ecddfe0787a392960d230c87a421c6a To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1412802/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1507564] Re: os.path.remove doesn't exist. Conver task fails
** Also affects: glance/kilo Importance: Undecided Status: New ** Changed in: glance/kilo Importance: Undecided => Medium ** Changed in: glance/liberty Importance: Undecided => Medium ** Changed in: glance/kilo Assignee: (unassigned) => Flavio Percoco (flaper87) ** Changed in: glance/liberty Assignee: (unassigned) => Flavio Percoco (flaper87) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1507564 Title: os.path.remove doesn't exist. Conver task fails Status in Glance: In Progress Status in Glance kilo series: In Progress Status in Glance liberty series: New Bug description: File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 96, in run for _state in self.run_iter(): File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 146, in run_iter self._change_state(states.FAILURE) File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 130, in run_iter failure.Failure.reraise_if_any(failures) File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 244, in reraise_if_any failures[0].reraise() File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 251, in reraise six.reraise(*self._exc_info) File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/executor.py", line 86, in _revert_task result = task.revert(**arguments) File "/usr/lib/python2.7/site-packages/glance/async/flows/convert.py", line 99, in revert os.path.remove(fs_path) AttributeError: 'module' object has no attribute 'remove' 2015-07-11 11:40:00.817 6663 INFO eventlet.wsgi.server [req-c4c286ec-2248-4d93-b631-a2270de43ec8 7a6bd2901f0642b18be91d82782ed1ca 3954f0a8635249eba2eda9a489e233a7 - - -] 10.12.27.41 - - [11/Jul/2015 11:40:00] "POST /v2/tasks HTTP/1.1" 500 139 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1507564/+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 1513473] Re: Introduce Functionality to Replace "location" and "copy-from" Flags for Glance Image Creation
Hi Gary, This has been proposed other times and the result of those discussions has always been that we won't be adding these flags back explicitly. The reason I mention explicitly is because there's a work-in-progress to change and improve the image import process so that we'd have something consistent, discoverable and interoperable. You can follow that work here: https://review.openstack.org/#/c/232371/ I'm marking this as won't fix. If you have further questions, please don't hesitate to ask. ** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1513473 Title: Introduce Functionality to Replace "location" and "copy-from" Flags for Glance Image Creation Status in Glance: Won't Fix Bug description: Since the "location" and "copy-from" flags are being deprecated / reserved in the newest version of the Glance CLI for creating images, it would be useful to at least replace their functionality with something similar. Suggest adding a flag called "--image-url" that eliminates the need to copy an image to an OpenStack account in order to use it, similar to how "--location" worked. Suggest adding a flag called "--copy-url" that allows the user to provide a URL to an existing image (e.g. on S3), where it can be copied from, similar to how "--copy-from" worked. Since some developers' needs currently depend on these features, they are forced to use the older version of the CLI, exposing them to past bugs and potential security flaws. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1513473/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1505134] Re: Glance should allow to delete de-activated images
** Summary changed:
- error message not clear when image-delete is called on deactivated image
+ Glance should allow to delete de-activated images
** Also affects: glance/liberty
Importance: Undecided
Status: New
** Changed in: glance/liberty
Status: New => Triaged
** Changed in: glance/liberty
Importance: Undecided => High
** Changed in: glance
Importance: Critical => High
** Changed in: glance/liberty
Status: Triaged => Fix Released
** Changed in: glance
Status: Triaged => Fix Released
** Changed in: glance
Status: Fix Released => Fix Committed
** Changed in: glance
Status: Fix Committed => Invalid
** Changed in: glance/liberty
Assignee: (unassigned) => Ramaraja (ramaraja-r)
** Changed in: glance
Assignee: Ramaraja (ramaraja-r) => (unassigned)
** Changed in: glance/liberty
Assignee: Ramaraja (ramaraja-r) => Mike Fedosin (mfedosin)
** Changed in: glance
Importance: High => Undecided
** Changed in: glance
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1505134
Title:
Glance should allow to delete de-activated images
Status in Glance:
Invalid
Status in Glance kilo series:
Triaged
Status in Glance liberty series:
Fix Released
Bug description:
Glance should allow to delete de-activated images
Steps to reproduce:
1. Create image
2. Deactivate image
3. Call image-delete on deactivated image
Actual message:
glance image-delete 5f0f914b-9f04-42c4-9769-07dc09e09056
u'deactivated' is not one of [u'queued', u'saving', u'active', u'killed',
u'deleted', u'pending_delete']
Failed validating u'enum' in schema[u'properties'][u'status']:
{u'description': u'Status of the image (READ-ONLY)',
u'enum': [u'queued',
u'saving',
u'active',
u'killed',
u'deleted',
u'pending_delete'],
u'type': u'string'}
On instance[u'status']:
u'deactivated'
Expected output:
Deactivated image should be deleted successfully.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1505134/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1505710] Re: Wrong logging setup in replicator
Liberty: https://review.openstack.org/#/c/236677/ ** Also affects: glance/liberty Importance: Undecided Status: New ** Changed in: glance/liberty Assignee: (unassigned) => Flavio Percoco (flaper87) ** Changed in: glance/liberty Status: New => In Progress ** Changed in: glance Milestone: None => mitaka-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1505710 Title: Wrong logging setup in replicator Status in Glance: Fix Committed Status in Glance liberty series: In Progress Bug description: The logging.setup accepts two parameters, the first one being the current CONF, the second parameter is the product name. Currently in replicator it's not true. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1505710/+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 1266407] Re: configure_add() method should get called only once during glance server initialization
This bug is now invalid as the glance_store library doesn't do this anymore. ** 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/1266407 Title: configure_add() method should get called only once during glance server initialization Status in Glance: Invalid Bug description: The configure_add() method is called each time during image create, update or delete api calls, which leads to a performance issue. Ideally configuration related activities should be done only once during server initialization. This is applicable to all stores. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1266407/+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 1350713] Re: Store configuration error in sheepdog
This was an expected behavior and it was fixed already (unless I'm reading this bug wrong) ** 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/1350713 Title: Store configuration error in sheepdog Status in Glance: Invalid Bug description: I have found following errors along with the "deprecated" warning 2014-07-30 21:05:14.971 9608 ERROR glance.store.sheepdog [-] Error in store configuration: [Errno 2] No such file or directory 2014-07-30 21:05:14.972 9608 WARNING glance.store [-] Deprecated: glance.store.sheepdog.Store not found in `known_store`. Stores need to be explicitly enabled in the configuration file. in the gate-tempest-dsvm-large-ops tests. Full stacktrace here: http://logs.openstack.org/51/106751/6/check/gate-tempest-dsvm-large- ops/640c35c/logs/screen-g-api.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1350713/+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 1507564] [NEW] os.path.remove doesn't exist. Conver task fails
Public bug reported: File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 96, in run for _state in self.run_iter(): File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 146, in run_iter self._change_state(states.FAILURE) File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 130, in run_iter failure.Failure.reraise_if_any(failures) File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 244, in reraise_if_any failures[0].reraise() File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 251, in reraise six.reraise(*self._exc_info) File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/executor.py", line 86, in _revert_task result = task.revert(**arguments) File "/usr/lib/python2.7/site-packages/glance/async/flows/convert.py", line 99, in revert os.path.remove(fs_path) AttributeError: 'module' object has no attribute 'remove' 2015-07-11 11:40:00.817 6663 INFO eventlet.wsgi.server [req-c4c286ec-2248-4d93-b631-a2270de43ec8 7a6bd2901f0642b18be91d82782ed1ca 3954f0a8635249eba2eda9a489e233a7 - - -] 10.12.27.41 - - [11/Jul/2015 11:40:00] "POST /v2/tasks HTTP/1.1" 500 139 ** Affects: glance Importance: Medium Status: Confirmed ** Changed in: glance Milestone: None => mitaka-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1507564 Title: os.path.remove doesn't exist. Conver task fails Status in Glance: Confirmed Bug description: File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 96, in run for _state in self.run_iter(): File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 146, in run_iter self._change_state(states.FAILURE) File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 119, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py", line 130, in run_iter failure.Failure.reraise_if_any(failures) File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 244, in reraise_if_any failures[0].reraise() File "/usr/lib/python2.7/site-packages/taskflow/types/failure.py", line 251, in reraise six.reraise(*self._exc_info) File "/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/executor.py", line 86, in _revert_task result = task.revert(**arguments) File "/usr/lib/python2.7/site-packages/glance/async/flows/convert.py", line 99, in revert os.path.remove(fs_path) AttributeError: 'module' object has no attribute 'remove' 2015-07-11 11:40:00.817 6663 INFO eventlet.wsgi.server [req-c4c286ec-2248-4d93-b631-a2270de43ec8 7a6bd2901f0642b18be91d82782ed1ca 3954f0a8635249eba2eda9a489e233a7 - - -] 10.12.27.41 - - [11/Jul/2015 11:40:00] "POST /v2/tasks HTTP/1.1" 500 139 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1507564/+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 1504184] Re: Glance does not error gracefully on token validation error
** Also affects: glance/kilo
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1504184
Title:
Glance does not error gracefully on token validation error
Status in Glance:
Fix Committed
Status in Glance kilo series:
New
Status in Glance liberty series:
In Progress
Bug description:
When the registry has an error validating the token that the api has
sent it a 500 is returned, rather than 401. This is with the latest
master.
{code}
2015-10-08 15:03:16.939 ERROR glance.registry.client.v1.client
[req-b561060e-d60c-4085-820d-1e87e64448ed 9f81b40c4b484be99a06754f32500271
51852dcd7e304719939f29fc2c3f3558] Registry client request GET /images/detail
raised NotAuthenticated
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client Traceback
(most recent call last):
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client File
"/opt/stack/glance/glance/registry/client/v1/client.py", line 121, in do_request
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client **kwargs)
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client File
"/opt/stack/glance/glance/common/client.py", line 74, in wrapped
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client return
func(self, *args, **kwargs)
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client File
"/opt/stack/glance/glance/common/client.py", line 375, in do_request
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client
headers=copy.deepcopy(headers))
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client File
"/opt/stack/glance/glance/common/client.py", line 88, in wrapped
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client return
func(self, method, url, body, headers)
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client File
"/opt/stack/glance/glance/common/client.py", line 517, in _do_request
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client raise
exception.NotAuthenticated(res.read())
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client
NotAuthenticated: Authentication required
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client
2015-10-08 15:03:16.940 ERROR glance.common.wsgi
[req-b561060e-d60c-4085-820d-1e87e64448ed 9f81b40c4b484be99a06754f32500271
51852dcd7e304719939f29fc2c3f3558] Caught error: Authentication required
2015-10-08 15:03:16.940 TRACE glance.common.wsgi Traceback (most recent call
last):
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/wsgi.py", line 879, in __call__
2015-10-08 15:03:16.940 TRACE glance.common.wsgi request, **action_args)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/wsgi.py", line 907, in dispatch
2015-10-08 15:03:16.940 TRACE glance.common.wsgi return method(*args,
**kwargs)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/api/v1/images.py", line 366, in detail
2015-10-08 15:03:16.940 TRACE glance.common.wsgi images =
registry.get_images_detail(req.context, **params)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/registry/client/v1/api.py", line 161, in
get_images_detail
2015-10-08 15:03:16.940 TRACE glance.common.wsgi return
c.get_images_detailed(**kwargs)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/registry/client/v1/client.py", line 150, in
get_images_detailed
2015-10-08 15:03:16.940 TRACE glance.common.wsgi res =
self.do_request("GET", "/images/detail", params=params)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/registry/client/v1/client.py", line 136, in do_request
2015-10-08 15:03:16.940 TRACE glance.common.wsgi 'exc_name': exc_name})
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 195, in
__exit__
2015-10-08 15:03:16.940 TRACE glance.common.wsgi six.reraise(self.type_,
self.value, self.tb)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/registry/client/v1/client.py", line 121, in do_request
2015-10-08 15:03:16.940 TRACE glance.common.wsgi **kwargs)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/client.py", line 74, in wrapped
2015-10-08 15:03:16.940 TRACE glance.common.wsgi return func(self, *args,
**kwargs)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/client.py", line 375, in do_request
2015-10-08 15:03:16.940 TRACE glance.common.wsgi
headers=copy.deepcopy(headers))
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
[Yahoo-eng-team] [Bug 1504184] Re: Glance does not error gracefully on token validation error
** Changed in: glance
Milestone: None => mitaka-1
** Also affects: glance/liberty
Importance: Undecided
Status: New
** Changed in: glance/liberty
Importance: Undecided => High
** Changed in: glance/liberty
Assignee: (unassigned) => Flavio Percoco (flaper87)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1504184
Title:
Glance does not error gracefully on token validation error
Status in Glance:
In Progress
Status in Glance liberty series:
In Progress
Bug description:
When the registry has an error validating the token that the api has
sent it a 500 is returned, rather than 401. This is with the latest
master.
{code}
2015-10-08 15:03:16.939 ERROR glance.registry.client.v1.client
[req-b561060e-d60c-4085-820d-1e87e64448ed 9f81b40c4b484be99a06754f32500271
51852dcd7e304719939f29fc2c3f3558] Registry client request GET /images/detail
raised NotAuthenticated
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client Traceback
(most recent call last):
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client File
"/opt/stack/glance/glance/registry/client/v1/client.py", line 121, in do_request
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client **kwargs)
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client File
"/opt/stack/glance/glance/common/client.py", line 74, in wrapped
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client return
func(self, *args, **kwargs)
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client File
"/opt/stack/glance/glance/common/client.py", line 375, in do_request
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client
headers=copy.deepcopy(headers))
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client File
"/opt/stack/glance/glance/common/client.py", line 88, in wrapped
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client return
func(self, method, url, body, headers)
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client File
"/opt/stack/glance/glance/common/client.py", line 517, in _do_request
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client raise
exception.NotAuthenticated(res.read())
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client
NotAuthenticated: Authentication required
2015-10-08 15:03:16.939 TRACE glance.registry.client.v1.client
2015-10-08 15:03:16.940 ERROR glance.common.wsgi
[req-b561060e-d60c-4085-820d-1e87e64448ed 9f81b40c4b484be99a06754f32500271
51852dcd7e304719939f29fc2c3f3558] Caught error: Authentication required
2015-10-08 15:03:16.940 TRACE glance.common.wsgi Traceback (most recent call
last):
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/wsgi.py", line 879, in __call__
2015-10-08 15:03:16.940 TRACE glance.common.wsgi request, **action_args)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/wsgi.py", line 907, in dispatch
2015-10-08 15:03:16.940 TRACE glance.common.wsgi return method(*args,
**kwargs)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/api/v1/images.py", line 366, in detail
2015-10-08 15:03:16.940 TRACE glance.common.wsgi images =
registry.get_images_detail(req.context, **params)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/registry/client/v1/api.py", line 161, in
get_images_detail
2015-10-08 15:03:16.940 TRACE glance.common.wsgi return
c.get_images_detailed(**kwargs)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/registry/client/v1/client.py", line 150, in
get_images_detailed
2015-10-08 15:03:16.940 TRACE glance.common.wsgi res =
self.do_request("GET", "/images/detail", params=params)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/registry/client/v1/client.py", line 136, in do_request
2015-10-08 15:03:16.940 TRACE glance.common.wsgi 'exc_name': exc_name})
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 195, in
__exit__
2015-10-08 15:03:16.940 TRACE glance.common.wsgi six.reraise(self.type_,
self.value, self.tb)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/registry/client/v1/client.py", line 121, in do_request
2015-10-08 15:03:16.940 TRACE glance.common.wsgi **kwargs)
2015-10-08 15:03:16.940 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/client.py", line 74, in wrapped
2015-10-08 15:03:16.940 TRACE glance.common.wsgi retu
[Yahoo-eng-team] [Bug 1483937] Re: version conflict encountered while running with stable/kilo branch
** Also affects: glance/kilo Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1483937 Title: version conflict encountered while running with stable/kilo branch Status in Glance: Invalid Status in Glance kilo series: New Bug description: I hit the following error while running unit test under glance stable/kilo branch. This is the command line I used: ./run_tests.sh -f -V This is the error information: error: python-keystoneclient 1.3.2 is installed but python-keystoneclient>=1.6.0 is required by set(['python-cinderclient']) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1483937/+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 1505675] Re: Flaky tasks test glance.tests.unit.v2.test_tasks_resource.TestTasksController.test_create_with_live_time
** Also affects: glance/liberty Importance: Undecided Status: New ** Changed in: glance Milestone: None => mitaka-1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1505675 Title: Flaky tasks test glance.tests.unit.v2.test_tasks_resource.TestTasksController.test_create_with_live_time Status in Glance: In Progress Status in Glance liberty series: New Bug description: We get constantly failures like: 2015-10-13 06:59:05.343 | == 2015-10-13 06:59:05.343 | FAIL: glance.tests.unit.v2.test_tasks_resource.TestTasksController.test_create_with_live_time 2015-10-13 06:59:05.344 | tags: worker-7 2015-10-13 06:59:05.344 | -- 2015-10-13 06:59:05.344 | Traceback (most recent call last): 2015-10-13 06:59:05.344 | File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/mock/mock.py", line 1305, in patched 2015-10-13 06:59:05.344 | return func(*args, **keywargs) 2015-10-13 06:59:05.344 | File "glance/tests/unit/v2/test_tasks_resource.py", line 365, in test_create_with_live_time 2015-10-13 06:59:05.344 | self.assertEqual(CONF.task.task_time_to_live, task_live_time_hour) 2015-10-13 06:59:05.344 | File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 350, in assertEqual 2015-10-13 06:59:05.344 | self.assertThat(observed, matcher, message) 2015-10-13 06:59:05.344 | File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 435, in assertThat 2015-10-13 06:59:05.345 | raise mismatch_error 2015-10-13 06:59:05.345 | testtools.matchers._impl.MismatchError: 48 != 47 2015-10-13 06:59:05.345 | Ran 2855 tests in 298.484s 2015-10-13 06:59:05.345 | FAILED (id=0, failures=1, skips=2) 2015-10-13 06:59:05.345 | error: testr failed (1) 2015-10-13 06:59:05.394 | ERROR: InvocationError: '/home/jenkins/workspace/gate-glance-python27/.tox/py27/bin/lockutils-wrapper python setup.py testr --slowest --testr-args=' This is caused if the second of timestamp changes between created_at and updated_at gets created. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1505675/+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 1467719] Re: image-create returns wrong error
** Changed in: glance Importance: Undecided => Low ** Also affects: glance/liberty Importance: Low Assignee: takmatsu (takeaki-matsumoto) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1467719 Title: image-create returns wrong error Status in Glance: In Progress Status in Glance liberty series: In Progress Bug description: When set wrong credentials in glance-api.conf and not exist ~/.glanceclient/image_schema.json, image-create returns unrecognized arguments. ex) $vim /etc/glance/glance-api.conf [keystone_authtoken] ... password = wrongpassword #set wrong password ... $ sudo service glance-api restart $ rm ~/.glanceclient/image_schema.json $ export OS_IMAGE_API_VERSION=2 $ wget -P /tmp/images http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img $ glance image-create --name "cirros-0.3.4-x86_64" --file /tmp/images/cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format bare --visibility public --progress usage: glance [--version] [-d] [-v] [--get-schema] [--timeout TIMEOUT] [--no-ssl-compression] [-f] [--os-image-url OS_IMAGE_URL] [--os-image-api-version OS_IMAGE_API_VERSION] [--profile HMAC_KEY] [-k] [--os-cert OS_CERT] [--cert-file OS_CERT] [--os-key OS_KEY] [--key-file OS_KEY] [--os-cacert ] [--ca-file OS_CACERT] [--os-username OS_USERNAME] [--os-user-id OS_USER_ID] [--os-user-domain-id OS_USER_DOMAIN_ID] [--os-user-domain-name OS_USER_DOMAIN_NAME] [--os-project-id OS_PROJECT_ID] [--os-project-name OS_PROJECT_NAME] [--os-project-domain-id OS_PROJECT_DOMAIN_ID] [--os-project-domain-name OS_PROJECT_DOMAIN_NAME] [--os-password OS_PASSWORD] [--os-tenant-id OS_TENANT_ID] [--os-tenant-name OS_TENANT_NAME] [--os-auth-url OS_AUTH_URL] [--os-region-name OS_REGION_NAME] [--os-auth-token OS_AUTH_TOKEN] [--os-service-type OS_SERVICE_TYPE] [--os-endpoint-type OS_ENDPOINT_TYPE] ... glance: error: unrecognized arguments: --name --disk-format qcow2 --container-format bare --visibility public To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1467719/+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] Re: Glance create an image with incorrect location
** Project changed: glance => glance-store ** Also affects: glance-store/liberty Importance: High Assignee: Kairat Kushaev (kkushaev) Status: In Progress ** Also affects: glance-store/kilo Importance: Undecided Status: New ** Changed in: glance-store/kilo Importance: Undecided => High ** Changed in: glance-store/kilo Status: New => Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1485792 Title: Glance create an image with incorrect location Status in glance_store: In Progress Status in glance_store kilo series: Triaged Status in glance_store liberty series: In Progress 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://:~/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://:~/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-store/+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 1496138] Re: logging a warning when someone accesses / seems unnecessary and wasteful
** Also affects: glance/liberty Importance: High Assignee: Erno Kuvaja (jokke) Status: In Progress ** Also affects: glance/kilo Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1496138 Title: logging a warning when someone accesses / seems unnecessary and wasteful Status in Glance: In Progress Status in Glance kilo series: New Status in Glance liberty series: In Progress Bug description: Our load balancer health checks (and other folks too) just load the main glance URL and look for an http status of 300 to determine if glance is okay. Starting I think in Kilo, glance changed and now logs a warning. This is highly unnecessary and ends up generating gigs of useless logs which make diagnosing real issues more difficult. At the least this should be an INFO, but ideally there's no point in logging this at all. 2015-08-04 17:42:43.058 24075 WARNING glance.api.middleware.version_negotiation [-] Unknown version. Returning version choices. 2015-08-04 17:42:43.577 24071 WARNING glance.api.middleware.version_negotiation [-] Unknown version. Returning version choices. 2015-08-04 17:42:45.083 24076 WARNING glance.api.middleware.version_negotiation [-] Unknown version. Returning version choices. 2015-08-04 17:42:45.317 24064 WARNING glance.api.middleware.version_negotiation [-] Unknown version. Returning version choices. 2015-08-04 17:42:47.092 24074 WARNING glance.api.middleware.version_negotiation [-] Unknown version. Returning version choices. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1496138/+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 1495519] [NEW] import flow doesn't raise error on forbidden location
Public bug reported:
The following command correctly raises an exception server side but it
doesn't report the error back to the user. This ends up in the user
"thinking" the task was created correctly:
$ glance --os-image-api-version 2 --os-image-url
http://localhost:9292/v2 --os-tenant-id a1875f8a27f74708b6fb9281e7430a98
task-create --type import --input '{"import_from_format": "qcow2",
"import_from": "swift://127.0.0.1:8000/test.qcow2", "image_properties":
{"disk_format": "qcow2", "container_format": "bare"}}'
** Affects: glance
Importance: High
Status: New
** Changed in: glance
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1495519
Title:
import flow doesn't raise error on forbidden location
Status in Glance:
New
Bug description:
The following command correctly raises an exception server side but it
doesn't report the error back to the user. This ends up in the user
"thinking" the task was created correctly:
$ glance --os-image-api-version 2 --os-image-url
http://localhost:9292/v2 --os-tenant-id
a1875f8a27f74708b6fb9281e7430a98 task-create --type import --input
'{"import_from_format": "qcow2", "import_from":
"swift://127.0.0.1:8000/test.qcow2", "image_properties":
{"disk_format": "qcow2", "container_format": "bare"}}'
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1495519/+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 1480196] Re: Request-id is not getting returned if glance throws 500 error
** Also affects: glance/kilo Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1480196 Title: Request-id is not getting returned if glance throws 500 error Status in Glance: Fix Released Status in Glance kilo series: New Bug description: If glance throws Internal Server Error (500) for some reason, then in that case 'request-id' is not getting returned in response headers. Request-id is required to analyse logs effectively on failure and it should be returned from headers. For ex. - image-create api returns 500 error if property name exceeds 255 characters (fix for this issue is in progress : https://review.openstack.org/#/c/203948/) curl command: $ curl -g -i -X POST -H 'Accept-Encoding: gzip, deflate' -H 'x-image- meta-container_format: ami' -H 'x-image-meta-property- : jskg' -H 'Accept: */*' -H 'X-Auth-Token: b94bd7b3a0fb4fada73fe170fe7d49cb' -H 'Connection: keep-alive' -H 'x -image-meta-is_public: None' -H 'User-Agent: python-glanceclient' -H 'Content-Type: application/octet-stream' -H 'x-image-meta-disk_format: ami' http://10.69.4.173:9292/v1/images HTTP/1.1 500 Internal Server Error Content-Type: text/plain Content-Length: 0 Date: Fri, 31 Jul 2015 08:27:31 GMT Connection: close Here request-id is not part of response header. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1480196/+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 1478690] Re: Request ID has a double req- at the start
** Also affects: glance/kilo
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1478690
Title:
Request ID has a double req- at the start
Status in Glance:
Fix Released
Status in Glance kilo series:
New
Status in OpenStack Search (Searchlight):
Fix Committed
Bug description:
➜ vagrant git:(master) http http://192.168.121.242:9393/v1/search
X-Auth-Token:$token query:='{"match_all" : {}}'
HTTP/1.1 200 OK
Content-Length: 138
Content-Type: application/json; charset=UTF-8
Date: Mon, 27 Jul 2015 20:21:31 GMT
X-Openstack-Request-Id: req-req-0314bf5b-9c04-4bed-bf86-d2e76d297a34
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1478690/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1422699] Re: glance api doesn't abort start up on Store configuration errors
** Also affects: glance/kilo Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1422699 Title: glance api doesn't abort start up on Store configuration errors Status in Glance: Fix Released Status in Glance kilo series: New Status in glance_store: Fix Released Bug description: Glance api service does not abort start up when errors in glance-api.cfg file are encountered. It would make sense to abort service start up when a BadStoreConfiguration exception is encountered, instead of just sending the error to the logs and disabling adding images to that Store. For example if a Filesystem Storage Backend with multiple store is configured with a duplicate directory: filesystem_store_datadirs=/mnt/nfs1/images/:200 filesystem_store_datadirs=/mnt/nfs1/images/:100 Logs will have the error: ERROR glance_store._drivers.filesystem [-] Directory /mnt/nfs1/image specified multiple times in filesystem_store_datadirs option of filesystem configuration TRACE glance_store._drivers.filesystem None TRACE glance_store._drivers.filesystem WARNING glance_store.driver [-] Failed to configure store correctly: None Disabling add method. Service will start and when client tries to add an image he will receive a 410 Gone error saying: Error in store configuration. Adding images to store is disabled. This affects not only the filesystem storage backend but all glance- storage drivers that encounter an error in the configuration and raise a BadStoreConfiguration exception. How reproducible: Every time Steps to Reproduce: 1. Configure Glance to use Filesystem Storage Backend with multiple store and duplicate a filesystem_storage_datadirs. 2. Run glance api Expected behavior: Glance api service should not have started and should have reported that the directory was specified multiple times. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1422699/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1491350] [NEW] /versions endpoint returns 300 everytime
Public bug reported: The /versions endpoint returns a 300 status code even when the user explicitly asks for the version list. This is confusing and not the desired behavior since there's just 1 choice for the `/versions` endpoint. ** Affects: glance Importance: Medium Assignee: Flavio Percoco (flaper87) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Flavio Percoco (flaper87) ** Changed in: glance Milestone: None => liberty-rc1 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1491350 Title: /versions endpoint returns 300 everytime Status in Glance: In Progress Bug description: The /versions endpoint returns a 300 status code even when the user explicitly asks for the version list. This is confusing and not the desired behavior since there's just 1 choice for the `/versions` endpoint. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1491350/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1449639] Re: RBD: On image creation error, image is not deleted
** Also affects: glance-store/kilo Importance: Undecided Status: New ** Changed in: glance-store/kilo Status: New = In Progress ** Changed in: glance-store/kilo Importance: Undecided = Medium ** Changed in: glance-store/kilo Assignee: (unassigned) = Gorka Eguileor (gorka) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1449639 Title: RBD: On image creation error, image is not deleted Status in Glance: Fix Released Status in Glance icehouse series: Fix Released Status in glance_store: Fix Released Status in glance_store kilo series: In Progress Bug description: When an exception rises while adding/creating an image, and the image has been created, this new image is not properly deleted. The fault lies in the `_delete_image` call of the Store.add method that is providing incorrect arguments. This also affects Glance (Icehouse), since back then glance_store functionality was included there. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1449639/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1447215] Re: Schema Missing kernel_id, ramdisk_id causes #1447193
** Also affects: glance/kilo Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1447215 Title: Schema Missing kernel_id, ramdisk_id causes #1447193 Status in Glance: Fix Committed Status in Glance kilo series: New Status in glance package in Ubuntu: Confirmed Bug description: [Description] [Environment] - Ubuntu 14.04.2 - OpenStack Kilo ii glance 1:2015.1~rc1-0ubuntu2~cloud0 all OpenStack Image Registry and Delivery Service - Daemons ii glance-api 1:2015.1~rc1-0ubuntu2~cloud0 all OpenStack Image Registry and Delivery Service - API ii glance-common1:2015.1~rc1-0ubuntu2~cloud0 all OpenStack Image Registry and Delivery Service - Common ii glance-registry 1:2015.1~rc1-0ubuntu2~cloud0 all OpenStack Image Registry and Delivery Service - Registry ii python-glance1:2015.1~rc1-0ubuntu2~cloud0 all OpenStack Image Registry and Delivery Service - Python library ii python-glance-store 0.4.0-0ubuntu1~cloud0all OpenStack Image Service store library - Python 2.x ii python-glanceclient 1:0.15.0-0ubuntu1~cloud0 all Client library for Openstack glance server. [Steps to reproduce] 0) Set /etc/glance/glance-api.conf to enable_v2_api=False 1) nova boot --flavor m1.small --image base-image --key-name keypair --availability-zone nova --security-groups default snapshot-bug 2) nova image-create snapshot-bug snapshot-bug-instance At this point the created image has no kernel_id (None) and image_id (None) 3) Enable_v2_api=True in glance-api.conf and restart. 4) Run a os-image-api=2 client, $ glance --os-image-api-version 2 image-list This will fail with #1447193 [Description] The schema-image.json file needs to be modified to allow null, string values for both attributes. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1447215/+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 1469738] Re: The operation of create image has failed with not enough free quota storage although sufficient space was available
Actually, this is well described in the config option's documentation.
As of today:
cfg.StrOpt('user_storage_quota', default='0',
help=_(Set a system wide quota for every user. This value is
the total capacity that a user can use across
all storage systems. A value of 0 means unlimited.
Optional unit can be specified for the value. Accepted
units are B, KB, MB, GB and TB representing
Bytes, KiloBytes, MegaBytes, GigaBytes and TeraBytes
respectively. If no unit is specified then Bytes is
assumed. Note that there should not be any space
between value and unit and units are case sensitive.)),
** Changed in: glance
Importance: Undecided = Low
** 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/1469738
Title:
The operation of create image has failed with not enough free quota
storage although sufficient space was available
Status in OpenStack Image Registry and Delivery Service (Glance):
Invalid
Bug description:
Description of problem:
Creating an image has failed with error message:Denying attempt to upload
image because it exceeds the quota, although there was enough space for upload
the image
Version-Release number of selected component (if applicable):
python-glanceclient-0.17.0-2.el7ost.noarch
python-glance-2015.1.0-6.el7ost.noarch
python-glance-store-0.4.0-1.el7ost.noarch
openstack-glance-2015.1.0-6.el7ost.noarch
How reproducible:
100%
Steps to Reproduce:
With only cirros image(size=12.6MB) run those steps
1. Edit /etc/glance/glance-api.conf set user_storage_quota =1536000
2. openstack-service restart glance
3. Try to upload an image less than 1536000MB
Actual results:
Failed with 'Denying attempt to upload image because it exceeds the quota'
Expected results:
Creating an image should succeed
Additional info:
It is similar to bug id=1043929
Glance logs
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1469738/+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 1456157] Re: Updating image with invalid operation type raises 500
** Also affects: glance/kilo
Importance: Undecided
Status: New
** Changed in: glance/kilo
Importance: Undecided = High
** Changed in: glance/kilo
Assignee: (unassigned) = Kamil Rykowski (kamil-rykowski)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1456157
Title:
Updating image with invalid operation type raises 500
Status in OpenStack Image Registry and Delivery Service (Glance):
In Progress
Status in Glance kilo series:
New
Bug description:
When trying to update an image using PATCH method I got Internal
Server Error when 'op' (operation) has invalid value. We could
consider changing this behavior to return some kind of 40x message
(400 probably).
Steps to reproduce:
URL: http://localhost:9292/v2/images/image_id
Headers:
X-Auth-Token: XYZ
Content-Type: application/openstack-images-v2.1-json-patch
Data:
[{path: /description, value: , op: axdd}]
Result: 500 Internal Server Error
I'm opening it as `Opinion`, as there can be a reason why are we
returning 500 instead of some 40x code.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1456157/+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 1461776] Re: Error messages are encoded to HTML entity
** No longer affects: python-glanceclient
** Also affects: glance/kilo
Importance: Undecided
Status: New
** Changed in: glance
Importance: Undecided = Medium
** Changed in: glance/kilo
Importance: Undecided = Medium
** Changed in: glance/kilo
Assignee: (unassigned) = Ankit Agrawal (ankitagrawal)
** Changed in: glance/kilo
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/1461776
Title:
Error messages are encoded to HTML entity
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Committed
Status in Glance kilo series:
In Progress
Bug description:
If you pass min_disk or min_ram as -1 to the image create command,
then it shows following error message on the command prompt.
$ glance image-create --name test --container-format bare --disk-format raw
--file filename --min-disk -1
400 Bad Request: Invalid value '-1' for parameter 'min_disk': Image min_disk
must be gt;= 0 ('-1' specified). (HTTP 400)
The above error message will be rendered correctly in the browser but
it is not readable on the command prompt.
This issue belongs to v1 API, in case of v2 api it returns proper error
message:
400 Bad Request: Invalid value '-1' for parameter 'min_disk': Cannot be a
negative value (HTTP 400)
So we can make this error message consistent for both the APIs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1461776/+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 1185851] Re: glance allows delete even if cannot be deleted from ceph backend store
** Project changed: glance = glance-store -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1185851 Title: glance allows delete even if cannot be deleted from ceph backend store Status in OpenStack Glance backend store-drivers library (glance_store): In Progress Bug description: The following steps *should* reproduce the issue. Basically, if I have a copy-on-write cloned vol from image, glance allows me to delet the image from glance itself even if the image cannot be deleted from backend store thus requiring manual deletion from Ceph cluster. Upload an image to Glance. This will create a snapshot of the raw image. glance image-create --name=testimage --is-public=true --disk- format=raw --container-format=ovf precise-server-cloudimg- amd64-disk1.img Create a cinder volume clone of the image nova volume-create --image-id img-id --display-name test-vol 4 When can then see that we have a snaphot image in the glance/images pool and a cloned image in the cinder/volumes pool rbd -p images ls| grep img-id # returns img-id rbd -p volumes ls| grep vol-vol-id # returns vol-vol-id Now if I delete the glance image... glance delete img-id I get a failure as expected since the snapshot is in use Request returned failure status. Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/eventlet/wsgi.py, line 383, in handle_one_response result = self.application(self.environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 130, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 195, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 333, in __call__ response = req.get_response(self.application) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1296, in send application, catch_exc_info=False) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1260, in call_application app_iter = application(self.environ, start_response) File /usr/lib/python2.7/dist-packages/keystoneclient/middleware/auth_token.py, line 450, in __call__ return self.app(env, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 130, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 195, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 333, in __call__ response = req.get_response(self.application) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1296, in send application, catch_exc_info=False) File /usr/lib/python2.7/dist-packages/webob/request.py, line 1260, in call_application app_iter = application(self.environ, start_response) File /usr/lib/python2.7/dist-packages/paste/urlmap.py, line 203, in __call__ return app(environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 144, in __call__ return resp(environ, start_response) File /usr/lib/python2.7/dist-packages/routes/middleware.py, line 131, in __call__ response = self.app(environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 144, in __call__ return resp(environ, start_response) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 130, in __call__ resp = self.call_func(req, *args, **self.kwargs) File /usr/lib/python2.7/dist-packages/webob/dec.py, line 195, in call_func return self.func(req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 540, in __call__ request, **action_args) File /usr/lib/python2.7/dist-packages/glance/common/wsgi.py, line 557, in dispatch return method(*args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/common/utils.py, line 413, in wrapped return func(self, req, *args, **kwargs) File /usr/lib/python2.7/dist-packages/glance/api/v1/images.py, line 861, in delete self._initiate_deletion(req, image['location'], id) File /usr/lib/python2.7/dist-packages/glance/api/v1/images.py, line 813, in _initiate_deletion safe_delete_from_backend(location, req.context, id) File /usr/lib/python2.7/dist-packages/glance/store/__init__.py, line 257, in safe_delete_from_backend return delete_from_backend(context, uri, **kwargs) File /usr/lib/python2.7/dist-packages/glance/store/__init__.py, line 237, in
[Yahoo-eng-team] [Bug 1453068] Re: task: Image's locations empty after importing to store
** Also affects: glance/kilo Importance: Undecided Status: New ** Changed in: glance/kilo Assignee: (unassigned) = Flavio Percoco (flaper87) ** Changed in: glance/kilo Importance: Undecided = High ** Changed in: glance/kilo Status: New = Incomplete ** Changed in: glance/kilo Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1453068 Title: task: Image's locations empty after importing to store Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in Glance kilo series: Confirmed Bug description: The ImportToStore task is setting the image data correctly but not saving it after it's been imported. This causes the image's location to be lost and therefore the image is completely useless because there are no locations associated to it To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1453068/+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 1452750] Re: dest_file in task convert is wrong
** Also affects: glance/kilo Importance: Undecided Status: New ** Changed in: glance/kilo Importance: Undecided = High ** Changed in: glance/kilo Status: New = Confirmed ** Changed in: glance/kilo Assignee: (unassigned) = Flavio Percoco (flaper87) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1452750 Title: dest_file in task convert is wrong Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in Glance kilo series: Confirmed Bug description: https://github.com/openstack/glance/commit/1b144f4c12fd6da58d7c48348bf7bab5873388e9 #diff-f02c20aafcce326b4d31c938376f6c2aR78 - head - desk The dest_path is not formated correctly, which ends up in converting the image to a path that is completely ignored by other tasks. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1452750/+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 1419823] Re: Nullable image description crashes v2 client
** No longer affects: python-glanceclient
** Changed in: glance
Assignee: Kamil Rykowski (kamil-rykowski) = Flavio Percoco (flaper87)
** Changed in: glance
Milestone: None = liberty-1
** Also affects: glance/kilo
Importance: Undecided
Status: New
** Changed in: glance/kilo
Importance: Undecided = Critical
** Changed in: glance/kilo
Status: New = Confirmed
** Changed in: glance/kilo
Assignee: (unassigned) = Flavio Percoco (flaper87)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1419823
Title:
Nullable image description crashes v2 client
Status in OpenStack Image Registry and Delivery Service (Glance):
In Progress
Status in Glance kilo series:
Confirmed
Bug description:
When you somehow set the image description to None the glanceclient v2
image-list crashes (as well as image-show, image-update for this
particular image). The only way to show all images now is to use
client v1, because it's more stable in this case.
Steps to reproduce:
1. Open Horizon and go to the edit page of any image.
2. Set description to anything eg. 123 and save.
3. Open image edit page again, remove description and save it.
4. List all images using glanceclient v2: glance --os-image-api-version 2
image-list
5. Be sad, because of raised exception:
None is not of type u'string'
Failed validating u'type' in schema[u'additionalProperties']:
{u'type': u'string'}
On instance[u'description']:
None
During investigating the issue I've found that the
additionalProperties schema is set to accept only string values, so it
should be expanded to allow for null values as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1419823/+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 1462235] [NEW] File descriptors are left open by the filesystem store
Public bug reported: From this m-l thread: http://lists.openstack.org/pipermail/openstack- dev/2015-June/065889.html I believe what's happening is that the ChunkedFile code opens the file and creates the iterator. Nova then starts iterating through the file. If nova (or any other user of glance) iterates all the way through the file then the ChunkedFile code will hit the finally clause in __iter__() and close the file descriptor. If nova starts iterating through the file and then stops (due to running out of room, for example), the ChunkedFile.__iter__() routine is left with an open file descriptor. At this point deleting the image will not actually free up any space. I'm not a glance guy so I could be wrong about the code. The externally-visible data are: 1) glance-api is holding an open file descriptor to a deleted image file 2) If I kill glance-api the disk space is freed up. 3) If I modify nova to always finish iterating through the file the problem doesn't occur in the first place. Chris ** Affects: glance-store Importance: High Assignee: Flavio Percoco (flaper87) Status: New ** Changed in: glance Importance: Undecided = High ** Changed in: glance Assignee: (unassigned) = Flavio Percoco (flaper87) ** Project changed: glance = glance-store -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1462235 Title: File descriptors are left open by the filesystem store Status in OpenStack Glance backend store-drivers library (glance_store): New Bug description: From this m-l thread: http://lists.openstack.org/pipermail/openstack- dev/2015-June/065889.html I believe what's happening is that the ChunkedFile code opens the file and creates the iterator. Nova then starts iterating through the file. If nova (or any other user of glance) iterates all the way through the file then the ChunkedFile code will hit the finally clause in __iter__() and close the file descriptor. If nova starts iterating through the file and then stops (due to running out of room, for example), the ChunkedFile.__iter__() routine is left with an open file descriptor. At this point deleting the image will not actually free up any space. I'm not a glance guy so I could be wrong about the code. The externally-visible data are: 1) glance-api is holding an open file descriptor to a deleted image file 2) If I kill glance-api the disk space is freed up. 3) If I modify nova to always finish iterating through the file the problem doesn't occur in the first place. Chris To manage notifications about this bug go to: https://bugs.launchpad.net/glance-store/+bug/1462235/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1453047] [NEW] ValueError: Tables artifact_blob_locations, artifact_blobs, artifact_dependencies, artifact_properties, artifact_tags, artifacts, image_locations, image_members,
Public bug reported: A new sanity_check has been enabled in oslo.db, which verifies the table charset. We need to make the switch to utf8 explicit in our models definition. The current error in the gate is: Traceback (most recent call last): File /home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/test_migrations.py, line 572, in test_models_sync self.db_sync(self.get_engine()) File glance/tests/unit/test_migrations.py, line 1686, in db_sync migration.db_sync(engine=engine) File glance/db/migration.py, line 65, in db_sync init_version=init_version) File /home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/migration.py, line 84, in db_sync _db_schema_sanity_check(engine) File /home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/migration.py, line 114, in _db_schema_sanity_check ) % ','.join(table_names)) ValueError: Tables artifact_blob_locations,artifact_blobs,artifact_dependencies,artifact_properties,artifact_tags,artifacts,image_locations,image_members,image_properties,image_tags,images,metadef_namespace_resource_types,metadef_namespaces,metadef_objects,metadef_properties,metadef_resource_types,metadef_tags,task_info,tasks have non utf8 collation, please make sure all tables are CHARSET=utf8 And the fix required should consist in adding `'charset': 'utf-8'` to our GlanceBase model. ** Affects: glance Importance: High Assignee: Flavio Percoco (flaper87) Status: New ** Changed in: glance Importance: Undecided = High ** Changed in: glance Assignee: (unassigned) = Flavio Percoco (flaper87) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1453047 Title: ValueError: Tables artifact_blob_locations,artifact_blobs,artifact_dependencies,artifact_properties,artifact_tags,artifacts,image_locations,image_members,image_properties,image_tags,images,metadef_namespace_resource_types,metadef_namespaces,metadef_objects,metadef_properties,metadef_resource_types,metadef_tags,task_info,tasks have non utf8 collation, please make sure all tables are CHARSET=utf8 Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: A new sanity_check has been enabled in oslo.db, which verifies the table charset. We need to make the switch to utf8 explicit in our models definition. The current error in the gate is: Traceback (most recent call last): File /home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/test_migrations.py, line 572, in test_models_sync self.db_sync(self.get_engine()) File glance/tests/unit/test_migrations.py, line 1686, in db_sync migration.db_sync(engine=engine) File glance/db/migration.py, line 65, in db_sync init_version=init_version) File /home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/migration.py, line 84, in db_sync _db_schema_sanity_check(engine) File /home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_db/sqlalchemy/migration.py, line 114, in _db_schema_sanity_check ) % ','.join(table_names)) ValueError: Tables artifact_blob_locations,artifact_blobs,artifact_dependencies,artifact_properties,artifact_tags,artifacts,image_locations,image_members,image_properties,image_tags,images,metadef_namespace_resource_types,metadef_namespaces,metadef_objects,metadef_properties,metadef_resource_types,metadef_tags,task_info,tasks have non utf8 collation, please make sure all tables are CHARSET=utf8 And the fix required should consist in adding `'charset': 'utf-8'` to our GlanceBase model. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1453047/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1452750] [NEW] dest_file in task convert is wrong
Public bug reported: https://github.com/openstack/glance/commit/1b144f4c12fd6da58d7c48348bf7bab5873388e9 #diff-f02c20aafcce326b4d31c938376f6c2aR78 - head - desk The dest_path is not formated correctly, which ends up in converting the image to a path that is completely ignored by other tasks. ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1452750 Title: dest_file in task convert is wrong Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: https://github.com/openstack/glance/commit/1b144f4c12fd6da58d7c48348bf7bab5873388e9 #diff-f02c20aafcce326b4d31c938376f6c2aR78 - head - desk The dest_path is not formated correctly, which ends up in converting the image to a path that is completely ignored by other tasks. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1452750/+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 1441393] Re: Keystone and Ceilometer unit tests fail with pymongo 3.0
** Also affects: zaqar Importance: Undecided Status: New ** Changed in: zaqar Assignee: (unassigned) = Flavio Percoco (flaper87) ** Changed in: zaqar Importance: Undecided = High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1441393 Title: Keystone and Ceilometer unit tests fail with pymongo 3.0 Status in OpenStack Telemetry (Ceilometer): Fix Committed Status in Ceilometer icehouse series: Fix Committed Status in Ceilometer juno series: Fix Committed Status in OpenStack Identity (Keystone): Fix Committed Status in Keystone icehouse series: In Progress Status in Keystone juno series: In Progress Status in OpenStack Messaging and Notifications Service (Zaqar): New Bug description: pymongo 3.0 was released 2015-04-07. This causes keystone tests to fail: Traceback (most recent call last): File keystone/tests/unit/test_cache_backend_mongo.py, line 357, in test_correct_read_preference region.set(random_key, dummyValue10) ... File keystone/common/cache/backends/mongo.py, line 363, in get_cache_collection self.read_preference = pymongo.read_preferences.mongos_enum( AttributeError: 'module' object has no attribute 'mongos_enum' Traceback (most recent call last): File keystone/tests/unit/test_cache_backend_mongo.py, line 345, in test_incorrect_read_preference random_key, dummyValue10) ... File keystone/common/cache/backends/mongo.py, line 168, in client self.api.get_cache_collection() File keystone/common/cache/backends/mongo.py, line 363, in get_cache_collection self.read_preference = pymongo.read_preferences.mongos_enum( AttributeError: 'module' object has no attribute 'mongos_enum' To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1441393/+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 1374519] Re: Orphaned queues are not auto-deleted for Qpid
** Changed in: oslo.messaging Importance: Undecided = Medium ** Also affects: oslo.messaging/juno Importance: Undecided Status: New ** Changed in: oslo.messaging/juno Importance: Undecided = Medium ** Changed in: oslo.messaging/juno Status: New = In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1374519 Title: Orphaned queues are not auto-deleted for Qpid Status in OpenStack Neutron (virtual network service): Fix Released Status in neutron icehouse series: In Progress Status in Messaging API for OpenStack: Fix Released Status in oslo.messaging juno series: In Progress Bug description: The following patch incorrectly set auto-delete for Qpid to False: https://github.com/openstack/oslo-incubator/commit/5ff534d1#diff- 372094c4bfc6319d22875a970aa6b730R190 While for RabbitMQ, it's True. This results in queues left on the broker if client dies and does not return back. Red Hat bug for reference: https://bugzilla.redhat.com/show_bug.cgi?id=1099657 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1374519/+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 1190559] Re: qcow2 images size should match the virtual image size
@yatin Hey, I think you might be confused with what this bug aimed to do. The bug proposed that the `size` field should match the `virtual_size` instead of the `size`. What we did to fix this was adding a new `virtual_size` field that would represent the `virtual_size` value in some of the images. I don't think nova uses the `virtual_size` field but I should double check. That said, the `virtual_size` value is an independent field that has nothing to do with the `size` of the image. Therefore, I do not believe these 2 fields should match. If anything, the virtual_size should be as big or bigger than the image size. ** 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/1190559 Title: qcow2 images size should match the virtual image size Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: the image size of qcow2 images should match the virtual size reported by qemu-img not the actual data size # glance image-show ff8f8fb3-76a3-47c0-bfc2-79e46950 [...] | size | 699592704 | [...] # qemu-img info /var/lib/glance/images/ff8f8fb3-76a3-47c0-bfc2-79e46950 image: /var/lib/glance/images/ff8f8fb3-76a3-47c0-bfc2-79e46950 file format: qcow2 virtual size: 6.0G (6442450944 bytes) disk size: 667M cluster_size: 65536 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1190559/+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 1398313] [NEW] Nullable fields default values are not part of the schema
Public bug reported: Some fields in the v2 that are nullable - disk_format and container_format, for example - don't have `None` as one of the possible values in their enum. This prevents the API from sending the value back to the client and the client library doesn't consider `None` as a valid value for the field. ** Affects: glance Importance: Undecided Assignee: Flavio Percoco (flaper87) Status: New ** Changed in: glance Assignee: (unassigned) = Flavio Percoco (flaper87) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1398313 Title: Nullable fields default values are not part of the schema Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Some fields in the v2 that are nullable - disk_format and container_format, for example - don't have `None` as one of the possible values in their enum. This prevents the API from sending the value back to the client and the client library doesn't consider `None` as a valid value for the field. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1398313/+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] [NEW] The API doesn't return nullable fields when they're null
Public bug reported: 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. ** Affects: glance Importance: Undecided Assignee: Flavio Percoco (flaper87) Status: In Progress ** Changed in: glance Assignee: (unassigned) = Flavio Percoco (flaper87) -- 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 OpenStack Image Registry and Delivery Service (Glance): In Progress 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 1398314] Re: The API doesn't return nullable fields when they're null
** Also affects: python-glanceclient Importance: Undecided Status: New ** Changed in: python-glanceclient Importance: Undecided = Medium ** Changed in: python-glanceclient Assignee: (unassigned) = Flavio Percoco (flaper87) -- 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 OpenStack Image Registry and Delivery Service (Glance): In Progress Status in Python client library for Glance: New 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 1395368] Re: ExternalNetworksTest[JSON, XML].test_delete_external_networks_with_floating_ip failures
** Also affects: python-glanceclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1395368
Title:
ExternalNetworksTest[JSON,XML].test_delete_external_networks_with_floating_ip
failures
Status in OpenStack Identity (Keystone) Middleware:
New
Status in OpenStack Neutron (virtual network service):
New
Status in Python client library for Glance:
New
Status in Tempest:
Incomplete
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': 'omitted'}
Body: ?xml version=1.0 encoding=UTF-8?
network xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:router=http://docs.openstack.org/ext/neutron/router/api/v1.0;router:external
True/router:external/network
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: ?xml version='1.0' encoding='UTF-8'?
network xmlns=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;statusACTIVE/statussubnets
quantum:type=list /name /provider:physical_network xsi:nil=true
/admin_state_up
quantum:type=boolTrue/admin_state_uptenant_ida3451f42641c4a3ab319253134e5a036/tenant_idprovider:network_typelocal/provider:network_typerouter:external
quantum:type=boolTrue/router:externalshared
quantum:type=boolFalse/sharedid0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc/idprovider:segmentation_id
xsi:nil=true //network
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': 'omitted'}
Body: ?xml version=1.0 encoding=UTF-8?
subnet xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;ip_version
4/ip_versionnetwork_id
0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc/network_idcidr
10.100.0.0/28/cidrgateway_ip 10.100.0.1/gateway_ip/subnet
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: ?xml version='1.0' encoding='UTF-8'?
subnet xmlns=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;name /enable_dhcp
quantum:type=boolTrue/enable_dhcpnetwork_id0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc/network_idtenant_ida3451f42641c4a3ab319253134e5a036/tenant_iddns_nameservers
quantum:type=list
/allocation_poolsallocation_poolstart10.100.0.2/startend10.100.0.14/end/allocation_pool/allocation_poolshost_routes
quantum:type=list /ip_version
quantum:type=int4/ip_versiongateway_ip10.100.0.1/gateway_ipcidr10.100.0.0/28/cidrid49d84272-4d7e-49fd-bf72-0dcf7c923db6/id/subnet
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': 'omitted'}
Body: ?xml version=1.0 encoding=UTF-8?
floatingip
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;floating_network_id
0b8004ad-7e9d-4b8c-9de1-efa8177f6dfc/floating_network_id/floatingip
Response - Headers: {'status': '201', 'content-length': '560',
'connection': 'close', 'date': 'Sat, 22 Nov 2014 18:54:54
[Yahoo-eng-team] [Bug 1385880] Re: RDO - openstack-glance-api.service fails when backend is not configured locally
** 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/1385880 Title: RDO - openstack-glance-api.service fails when backend is not configured locally Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Hi , openstack RDO installed on rhel7 with packstack installer . Whenever glance uses non-default backend , service glance-api in fail state . Attaching to bug glance config file and log Oct 27 02:51:25 rdo-testing glance-api: ERROR: Store for scheme swift not found Oct 27 02:51:26 rdo-testing systemd: openstack-glance-api.service: main process exited, code=exited, status=1/FAILURE Oct 27 02:51:26 rdo-testing systemd: Failed to start OpenStack Image Service (code-named Glance) API server. Oct 27 02:51:26 rdo-testing systemd: Unit openstack-glance-api.service entered failed state. Oct 27 02:51:26 rdo-testing systemd: openstack-glance-api.service holdoff time over, scheduling restart. Oct 27 02:51:26 rdo-testing systemd: Stopping OpenStack Image Service (code-named Glance) API server... Oct 27 02:51:26 rdo-testing systemd: Starting OpenStack Image Service (code-named Glance) API server... I got the same results for storge rbd and swift ERROR: Store for scheme rbd not found Benny To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1385880/+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 1366682] [NEW] ScrubberFileQueue is never called
Public bug reported: It looks like the change I6910b55de8c3b203560d75ff3d1675eda31ae786 might have broken the `test_scrubber_with_metadata_enc` test since now `ScrubberFileQueue` is never called. Adding a FIXME https://github.com/openstack/glance/blob/master/glance/tests/functional/test_scrubber.py#L199 ** Affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1366682 Title: ScrubberFileQueue is never called Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: It looks like the change I6910b55de8c3b203560d75ff3d1675eda31ae786 might have broken the `test_scrubber_with_metadata_enc` test since now `ScrubberFileQueue` is never called. Adding a FIXME https://github.com/openstack/glance/blob/master/glance/tests/functional/test_scrubber.py#L199 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1366682/+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 1316504] Re: glance-manage does not print an error on failed db_sync
The errors where logged in the log file. ** 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/1316504 Title: glance-manage does not print an error on failed db_sync Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: glance-manage db_sync silently fails to prepare the database: # glance-manage db_sync echo ok ok # mysql glance -e show tables +--+ | Tables_in_glance | +--+ | migrate_version | +--+ Steps to Reproduce: $ glance-manage db_sync echo ok Tables migrate_version have non utf8 collation, please make sure all tables are CHARSET=utf8 ok # mysql glance -e show tables +--+ | Tables_in_glance | +--+ | migrate_version | +--+ Expected results: The glance database should be ready to be used or an error should be clearly reported. The quick fix for the issue is to set `db_enforce_mysql_charset=False`. Although this config option will go away in Juno, I think the migration process should report a proper error and exit w/ an error code. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1316504/+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 1315014] Re: when using --size to create a qcow2 image image is creates it as raw but reported as qcow2
We don't have a nice way to support this just yet. This may (or may not) be supported in the future once we figure out what to do with image inspections/operations. I'll mark it as invalid for now. ** Changed in: glance Status: New = Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1315014 Title: when using --size to create a qcow2 image image is creates it as raw but reported as qcow2 Status in OpenStack Image Registry and Delivery Service (Glance): Won't Fix Bug description: I tried creating 20GB qcow2 image using --size and the image Here are the problems: 1. the image is not created with the selected size 2. the image is reported as qcow2 in glance-list but qemu-img shows it as raw (since the source image copied is a raw image we seem to be taking that parameter but reporting qcow2). This is create-image from an remote image which is raw: [root@orange-vdsf images(keystone_admin)]# glance image-create --name dafna_zise1 --disk-format qcow2 --container-format bare --copy-from http://download.eng.tlv.redhat.com/pub/rhel/released/RHEL-6/6.4/Appliance/rhel-client-x86_64-ec2-starter-6.4_20130130.0-1-sda.raw --size 2048 +--+--+ | Property | Value| +--+--+ | checksum | None | | container_format | bare | | created_at | 2014-05-01T09:53:04 | | deleted | False| | deleted_at | None | | disk_format | qcow2| | id | 292c11dd-a16b-46a0-b176-d665293273b3 | | is_public| False| | min_disk | 0| | min_ram | 0| | name | dafna_zise1 | | owner| 5502ab8e099843cfa39df71b3037ccd6 | | protected| False| | size | 2048 | | status | queued | | updated_at | 2014-05-01T09:53:04 | +--+--+ [root@orange-vdsf images(keystone_admin)]# glance image-list --human +--+-+-+--+-++ | ID | Name| Disk Format | Container Format | Size| Status | +--+-+-+--+-++ | | 292c11dd-a16b-46a0-b176-d665293273b3 | dafna_zise1 | qcow2 | bare | 19.5MB | saving | | +--+-+-+--+-++ [root@orange-vdsf images(keystone_admin)]# glance image-list --human +--+-+-+--+-++ | ID | Name| Disk Format | Container Format | Size| Status | +--+-+-+--+-++ | | 292c11dd-a16b-46a0-b176-d665293273b3 | dafna_zise1 | qcow2 | bare | 6GB | active | | +--+-+-+--+-++ [root@orange-vdsf images(keystone_admin)]# qemu-img info 292c11dd-a16b-46a0-b176-d665293273b3 image: 292c11dd-a16b-46a0-b176-d665293273b3 file format: raw virtual size: 6.0G (6442451456 bytes) disk size: 6.0G As you can see, the source image was a raw 6GB image. I created a qcow2 image from this image and tried giving it a 20GB size. the image is created as raw but reported as qcow To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1315014/+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 1316504] [NEW] glance-manage does not print an error on failed db_sync
Public bug reported: glance-manage db_sync silently fails to prepare the database: # glance-manage db_sync echo ok ok # mysql glance -e show tables +--+ | Tables_in_glance | +--+ | migrate_version | +--+ Steps to Reproduce: $ glance-manage db_sync echo ok Tables migrate_version have non utf8 collation, please make sure all tables are CHARSET=utf8 ok # mysql glance -e show tables +--+ | Tables_in_glance | +--+ | migrate_version | +--+ Expected results: The glance database should be ready to be used or an error should be clearly reported. The quick fix for the issue is to set `db_enforce_mysql_charset=False`. Although this config option will go away in Juno, I think the migration process should report a proper error and exit w/ an error code. ** Affects: glance Importance: Medium Status: New ** Changed in: glance Importance: Undecided = Medium -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1316504 Title: glance-manage does not print an error on failed db_sync Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: glance-manage db_sync silently fails to prepare the database: # glance-manage db_sync echo ok ok # mysql glance -e show tables +--+ | Tables_in_glance | +--+ | migrate_version | +--+ Steps to Reproduce: $ glance-manage db_sync echo ok Tables migrate_version have non utf8 collation, please make sure all tables are CHARSET=utf8 ok # mysql glance -e show tables +--+ | Tables_in_glance | +--+ | migrate_version | +--+ Expected results: The glance database should be ready to be used or an error should be clearly reported. The quick fix for the issue is to set `db_enforce_mysql_charset=False`. Although this config option will go away in Juno, I think the migration process should report a proper error and exit w/ an error code. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1316504/+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 1314705] Re: image-download fails causes terminal text to gibberish
This is the expected behavior and it has nothing to do with ssh. `image-
download` default's output is stdout. In order to avoid 'gibberishing'
the terminal, you should redirect the output to a file.
Unfortunately, we can't do anything about the terminal being completely
messed up after the image is dumped to stdout, AFAIK.
I don't think we should change this behavior, it's useful to pipe
image's output.
** 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/1314705
Title:
image-download fails causes terminal text to gibberish
Status in OpenStack Image Registry and Delivery Service (Glance):
Invalid
Bug description:
Description of problem:
Glance image-download fails causing ssh terminal text to gibberish.
Tested using ssh directly to Glance server, as well as ssh to cloud
controller (separate server). Tested from two different remote hosts running
two different terminal clients, not a host/ssh/terminal issue.
Version-Release number of selected component (if applicable):
RHEL 6.5
openstack-glance-2013.2.3-2.el6ost.noarch
python-glanceclient-0.12.0-2.el6ost.noarch
python-glance-2013.2.3-2.el6ost.noarch
How reproducible:
Every time
Steps to Reproduce:
1. Upload an image(Glance backend is Gluster based)
2. # glance image-download image_ID
3. After a short delay a few seconds terminal text turn to gibberish.
Actual results:
After a few seconds of delay the screen fills with:
@2o�xw��4�emuu�s�R���S!Q�P��.
��▒��[b3�p7b�!X;��ԌĎɡ-u�q�%Mao�1E�.1�x▒��=�ؽ��@)�~� ���
�-��t���؏)���w��W�[▒���ߕ�o▒�F��OlR/��1b��x%�#F�|��0�1���U#ң֍�tc��zF
�▒Ȕq��I�J�sP)���ʸJ▒8m�a߰�4��0�*��}$▒J#��\:T2z�J▒�S�cp�3$o2n7i��t.Ob�6q%I�*X��_jl|H4���q[d�e��le��ѿ�,YJ���}˄cM
�/{ˌ���,k��p�_▒���|� IA�z�g��w��:Ȼ
�B�3��d�'�u��▒qj�vP���T�ȄL0�.S�ßU
Expected results:
Image should download successfully without gibberishing ssh session.
Additional info:
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1314705/+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 1307412] Re: The API v2 reserved property error is not raised when there's nothing to update
turns out the client is not sending the owner field update, which IMHO, is wrong. These kind of optimizations belong to the server, not the client. I'll move this bug to the client and update the title. ** Project changed: glance = python-glanceclient ** Summary changed: - The API v2 reserved property error is not raised when there's nothing to update + The client should *always* send the full update request to the server ** Changed in: python-glanceclient Assignee: Flavio Percoco (flaper87) = (unassigned) ** Description changed: - [root@orange-vdse ~(keystone_admin)]# glance --os-image-api-version 2 image-update 9969c805-c5e6-4d4b-b9e3-dd867a06be08 --owner 637ea20d137e4fa3bdbbb89ec513ef05Request returned failure status. + [root@orange-vdse ~(keystone_admin)]# glance --os-image-api-version 2 image-update fc4bfa83-6eea-4090-91a3-92b02668570d --owner 637ea20d137e4fa3bdbbb89ec513ef05Request returned failure status. 403 Forbidden Attribute 'owner' is reserved. - (HTTP 403) + (HTTP 403) - However, if the owner is updated using the API v1, then the same command mentioned above will succeed without error. This may be confusing for the user. Reserved words errors should be raised even for noops + However, if the owner remains unchanged, the client won't send it to the server: + + [fedora@cinder devstack]$ glance --os-image-api-version 2 image-update fc4bfa83-6eea-4090-91a3-92b02668570d --owner cf7d037795cd45919e9d2824c72d0bae + +--+--+ + | Property | Value| + +--+--+ + | checksum | 51bc16b900bf0f814bb6c0c3dd8f0790 | + | container_format | bare | + | created_at | 2014-05-02T10:36:23Z | + | disk_format | qcow2| + | id | fc4bfa83-6eea-4090-91a3-92b02668570d | + | min_disk | 0| + | min_ram | 0| + | name | Fedora-x86_64-20-20131211.1-sda | + | owner| cf7d037795cd45919e9d2824c72d0bae | + | protected| False| + | size | 214106112| + | status | active | + | tags | [] | + | updated_at | 2014-05-02T10:36:24Z | + | visibility | public | + +--+--+ -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1307412 Title: The client should *always* send the full update request to the server Status in Python client library for Glance: New Bug description: [root@orange-vdse ~(keystone_admin)]# glance --os-image-api-version 2 image-update fc4bfa83-6eea-4090-91a3-92b02668570d --owner 637ea20d137e4fa3bdbbb89ec513ef05Request returned failure status. 403 Forbidden Attribute 'owner' is reserved. (HTTP 403) However, if the owner remains unchanged, the client won't send it to the server: [fedora@cinder devstack]$ glance --os-image-api-version 2 image-update fc4bfa83-6eea-4090-91a3-92b02668570d --owner cf7d037795cd45919e9d2824c72d0bae +--+--+ | Property | Value| +--+--+ | checksum | 51bc16b900bf0f814bb6c0c3dd8f0790 | | container_format | bare | | created_at | 2014-05-02T10:36:23Z | | disk_format | qcow2| | id | fc4bfa83-6eea-4090-91a3-92b02668570d | | min_disk | 0| | min_ram | 0| | name | Fedora-x86_64-20-20131211.1-sda | | owner| cf7d037795cd45919e9d2824c72d0bae | | protected| False| | size | 214106112| | status | active | | tags | [] | | updated_at | 2014-05-02T10:36:24Z | | visibility | public | +--+--+ To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1307412/+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 1314928] Re: image-create --progress, missing progress bar
Tzach, the `copy-from` param downloads the image when the request gets to the server. There's no way, without some hacky workaround, to support this right now. I don't think this is worth doing. We can revisit it in the future once async-workers are done. I'll set it as invalid for now. ** Project changed: glance = python-glanceclient ** Also affects: glance Importance: Undecided Status: New ** Changed in: glance Status: New = Invalid ** Changed in: python-glanceclient Status: New = Invalid ** Changed in: glance Importance: Undecided = Wishlist ** Changed in: python-glanceclient Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1314928 Title: image-create --progress, missing progress bar Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Status in Python client library for Glance: Invalid Bug description: Description of problem: Uploading image --progress, upload works but missing progress bar. glance image-create --name tshefi_cli2 --disk-format raw --container- format bare --copy-from http://download.eng.tlv.redhat.com/pub/rhel/released/RHEL-6/6.4/Appliance /rhel-client-x86_64-ec2-starter-6.4_20130130.0-1-sda.raw --progress Semi dist' setup via packstack, Glance uses Gluster as backend. Version-Release number of selected component (if applicable): RHEL6.5 python-glanceclient-0.12.0-2.el6ost.noarch How reproducible: Every time Steps to Reproduce: 1. glance image-create --progressnotice missing progress bar. Actual results: Image is uploaded but no progress bar is shown in the process. Expected results: Image should upload showing progress bar indication To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1314928/+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 1307412] [NEW] The API v2 reserved property error is not raised when there's nothing to update
Public bug reported: [root@orange-vdse ~(keystone_admin)]# glance --os-image-api-version 2 image-update 9969c805-c5e6-4d4b-b9e3-dd867a06be08 --owner 637ea20d137e4fa3bdbbb89ec513ef05Request returned failure status. 403 Forbidden Attribute 'owner' is reserved. (HTTP 403) However, if the owner is updated using the API v1, then the same command mentioned above will succeed without error. This may be confusing for the user. Reserved words errors should be raised even for noops ** Affects: glance Importance: Low Assignee: Flavio Percoco (flaper87) Status: New ** Changed in: glance Importance: Undecided = Low ** Changed in: glance Assignee: (unassigned) = Flavio Percoco (flaper87) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1307412 Title: The API v2 reserved property error is not raised when there's nothing to update Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: [root@orange-vdse ~(keystone_admin)]# glance --os-image-api-version 2 image-update 9969c805-c5e6-4d4b-b9e3-dd867a06be08 --owner 637ea20d137e4fa3bdbbb89ec513ef05Request returned failure status. 403 Forbidden Attribute 'owner' is reserved. (HTTP 403) However, if the owner is updated using the API v1, then the same command mentioned above will succeed without error. This may be confusing for the user. Reserved words errors should be raised even for noops To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1307412/+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 1291848] [NEW] Remove deprecation warning when loading stores
Public bug reported: Tracking the need of removing deprecation warning and the _EXTRA_STORES global from stores/__init__ ** Affects: glance Importance: Medium Status: New ** Tags: low-hanging-fruit ** Changed in: glance Milestone: None = next ** 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/1291848 Title: Remove deprecation warning when loading stores Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Tracking the need of removing deprecation warning and the _EXTRA_STORES global from stores/__init__ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1291848/+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 1276510] Re: MySQL 2013 lost connection is being raised
** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1276510 Title: MySQL 2013 lost connection is being raised Status in Cinder: In Progress Status in OpenStack Compute (Nova): New Status in Oslo - a Library of Common OpenStack Code: Fix Committed Status in oslo havana series: Fix Committed Bug description: MySQL's 2013 code error is not in the list of connection lost issues. This causes the reconnect loop to raise this error and stop retrying. [database] max_retries = -1 retry_interval = 1 mysql down: == scheduler.log == 2014-02-03 16:51:50.956 16184 CRITICAL cinder [-] (OperationalError) (2013, Lost connection to MySQL server at 'reading initial communication packet', system error: 0) None None To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1276510/+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 1249409] Re: IMage v2 api allows reupload of images, but does not update size
Marked as invalid based on @David's comment ** 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/1249409 Title: IMage v2 api allows reupload of images, but does not update size Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: IMage v2 api allows reupload of images, but does not update size To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1249409/+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 1266513] Re: Some Python requirements are not hosted on PyPI
** Also affects: glance Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1266513 Title: Some Python requirements are not hosted on PyPI Status in OpenStack Image Registry and Delivery Service (Glance): New Status in OpenStack Dashboard (Horizon): In Progress Status in OpenStack Identity (Keystone): Fix Released Status in Keystone havana series: In Progress Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Status in OpenStack Core Infrastructure: In Progress Status in Python client library for Keystone: Fix Committed Status in OpenStack Object Storage (Swift): In Progress Status in tripleo - openstack on openstack: In Progress Bug description: Pip 1.5 (released January 2nd, 2014) will by default refuse to download packages which are linked from PyPI but not hosted on pypi.python.org. The workaround is to whitelist these package names individually with both the --allow-external and --allow-insecure options. These options are new in pip 1.4, so encoding them will break for people trying to use pip 1.3.x or earlier. Those earlier versions of pip are not secure anyway since they don't connect via HTTPS with host certificate validation, so we should be encouraging people to use 1.4 and later anyway. The --allow-insecure option is transitioning to a clearer --allow- unverified option name starting with 1.5, but the new form does not work with pip before 1.5 so we should use the old version for now to allow people to transition gracefully. The --allow-insecure form won't be removed until at least pip 1.7 according to comments in the source code. Virtualenv 1.11 (released the same day) bundles pip 1.5 by default, and so requires these workarounds when using requirements external to PyPI. Be aware that 1.11 is broken for projects using sitepackages=True in their tox.ini. The fix is https://github.com/pypa/virtualenv/commit/a6ca6f4 which is slated to appear in 1.11.1 (no ETA available). We've worked around it on our test infrastructure with https://git.openstack.org/cgit/openstack- infra/config/commit/?id=20cd18a for now, but that is hiding the external-packages issue since we're currently running all tests with pip 1.4.1 as a result. This bug will also be invisible in our test infrastructure for projects listed as having the PyPI mirror enforced in openstack/requirements (except for jobs which bypass the mirror, such as those for requirements changes), since our update jobs will pull in and mirror external packages and pip sees the mirror as being PyPI itself in that situation. We'll use this bug to track necessary whitelist updates to tox.ini and test scripts. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1266513/+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 1260717] Re: Notifications are not sent from Glance
Based on the latest updates, I'll close this bug as Invalid. Feel free to file a new one if needed. ** 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/1260717 Title: Notifications are not sent from Glance Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: When we were testing Ceilometer it was found that there is no notifications from Glance. We found out that before moving to oslo.messging everything was fine. Ceilometer was included from the test completely: we just monitored Rabbit queue and no messages appeared. Configs in glance-api.conf: notifier_strategy = rabbit From the code I see that notifier_strategy is deprecated in favor of notification_driver but anyway currently notifier_strategy = rabbit = notification_driver = messaging. One more note: only reply_%UUID% topic appeared in Rabbit when image was created. And no messages at all. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1260717/+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 1263945] [NEW] Backwards compat support breaks transport_url
Public bug reported: Passing a fake url to `get_transport` makes it ignore the configured `transport_url`. This blocks any chance of using the new transport_url configuration. https://github.com/openstack/glance/blob/master/glance/notifier.py#L81 ** Affects: glance Importance: Critical Assignee: Flavio Percoco (flaper87) Status: New ** Changed in: glance Importance: Undecided = Critical ** Changed in: glance Assignee: (unassigned) = Flavio Percoco (flaper87) ** Changed in: glance Milestone: None = icehouse-2 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1263945 Title: Backwards compat support breaks transport_url Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Passing a fake url to `get_transport` makes it ignore the configured `transport_url`. This blocks any chance of using the new transport_url configuration. https://github.com/openstack/glance/blob/master/glance/notifier.py#L81 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1263945/+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 1220610] Re: glance image-create with --owner only work on tenant ID
** 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/1220610 Title: glance image-create with --owner only work on tenant ID Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: running: glance image-create --name tenant --disk-format qcow2 --container-format bare --location http:// --owner dafna +--+--+ | Property | Value| +--+--+ | checksum | None | | container_format | bare | | created_at | 2013-09-04T08:55:45 | | deleted | False| | deleted_at | None | | disk_format | qcow2| | id | 52357c0a-7d9e-4c22-85ab-84a71bb0cfdc | | is_public| False| | min_disk | 0| | min_ram | 0| | name | tenant | | owner| dafna| | protected| False| | size | 1974140928 | | status | active | | updated_at | 2013-09-04T08:55:45 | +--+--+ will give no errors but the image is not created. only if I give the ID of the image, the image is created [root@opens-vdsb ~(keystone_admin)]# glance image-create --name tenant --disk-format qcow2 --container-format bare --location http:// --owner e91123ca35724285a783f33103875dcb +--+--+ | Property | Value| +--+--+ | checksum | None | | container_format | bare | | created_at | 2013-09-04T08:56:26 | | deleted | False| | deleted_at | None | | disk_format | qcow2| | id | 68df9bcc-492e-470d-bbce-bb40f94ec27b | | is_public| False| | min_disk | 0| | min_ram | 0| | name | tenant | | owner| e91123ca35724285a783f33103875dcb | | protected| False| | size | 1974140928 | | status | active | | updated_at | 2013-09-04T08:56:27 | +--+--+ [dron@opens-vdsb /(keystone_admin)]$ glance image-list +--++-+--+++ | ID | Name | Disk Format | Container Format | Size | Status | +--++-+--+++ | cf34a754-5dec-4537-b2d3-0446cd5a3a18 | dron | qcow2 | bare | 699592704 | active | | 68df9bcc-492e-470d-bbce-bb40f94ec27b | tenant | qcow2 | bare | 1974140928 | active | +--++-+--+++ I think we need at least one of the blow fixes to improve glance api: 1. we should be able to create an owned image using tenant name 2. if this will be blocked we should block commnad from running for wrong param supplied. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1220610/+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 1257293] Re: [messaging] QPID broadcast RPC requests to all servers for a given topic
** Also affects: nova Importance: Undecided Status: New ** Also affects: cinder Importance: Undecided Status: New ** Also affects: heat Importance: Undecided Status: New ** Also affects: neutron Importance: Undecided Status: New ** Also affects: ceilometer Importance: Undecided Status: New ** Also affects: keystone 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/1257293 Title: [messaging] QPID broadcast RPC requests to all servers for a given topic Status in OpenStack Telemetry (Ceilometer): New Status in Cinder: In Progress Status in Orchestration API (Heat): New Status in OpenStack Identity (Keystone): New Status in OpenStack Neutron (virtual network service): New Status in OpenStack Compute (Nova): New Status in Oslo - a Library of Common OpenStack Code: Fix Committed Bug description: According to the oslo.messaging documentation, when a RPC request is made to a given topic, and there are multiple servers for that topic, only _one_ server should service that RPC request. See http://docs.openstack.org/developer/oslo.messaging/target.html topic (str) – A name which identifies the set of interfaces exposed by a server. Multiple servers may listen on a topic and messages will be dispatched to one of the servers in a round-robin fashion. In the case of a QPID-based deployment using topology version 2, this is not the case. Instead, each listening server gets a copy of the RPC and will process it. For more detail, see https://bugs.launchpad.net/oslo/+bug/1178375/comments/26 To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1257293/+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 1251757] Re: On restart of QPID broker, fanout no longer works
** Also affects: nova
Importance: Undecided
Status: New
** Also affects: heat
Importance: Undecided
Status: New
** Also affects: cinder
Importance: Undecided
Status: New
** Also affects: ceilometer
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/1251757
Title:
On restart of QPID broker, fanout no longer works
Status in OpenStack Telemetry (Ceilometer):
New
Status in Cinder:
New
Status in Orchestration API (Heat):
New
Status in OpenStack Compute (Nova):
New
Status in Oslo - a Library of Common OpenStack Code:
Fix Released
Status in Messaging API for OpenStack:
Fix Released
Bug description:
When the QPID broker is restarted, RPC servers attempt to re-connect.
This re-connection process is not done correctly for fanout
subscriptions - two subscriptions are established to the same fanout
address.
This problem is compounded by the fix to bug#1178375
https://bugs.launchpad.net/oslo/+bug/1178375
With this bug fix, when topology version 2 is used, the reconnect
attempt uses a malformed subscriber address.
For example, I have a simple RPC server script that attempts to
service my-topic. When it initially connects to the broker using
topology-version 1, these are the subscriptions that are established:
(py27)[kgiusti@t530 work (master)]$ ./my-server.py --topology=1 --auto-delete
server-02
Running server, name=server-02 exchange=my-exchange topic=my-topic
namespace=my-namespace
Using QPID topology version 1
Enable auto-delete
Recevr openstack/my-topic ; {node: {x-declare: {auto-delete: true,
durable: true}, type: topic}, create: always, link: {x-declare:
{auto-delete: true, exclusive: false, durable: false}, durable: true,
name: my-topic}}
Recevr openstack/my-topic.server-02 ; {node: {x-declare: {auto-delete:
true, durable: true}, type: topic}, create: always, link:
{x-declare: {auto-delete: true, exclusive: false, durable: false},
durable: true, name: my-topic.server-02}}
Recevr my-topic_fanout ; {node: {x-declare: {auto-delete: true,
durable: false, type: fanout}, type: topic}, create: always,
link: {x-declare: {auto-delete: true, exclusive: true, durable:
false}, durable: true, name:
my-topic_fanout_489a3178fc704123b0e5e2fbee125247}}
When I restart the qpid broker, the server reconnects using the
following subscriptions
Recevr my-topic_fanout ; {node: {x-declare: {auto-delete: true,
durable: false, type: fanout}, type: topic}, create: always,
link: {x-declare: {auto-delete: true, exclusive: true, durable:
false}, durable: true, name:
my-topic_fanout_b40001afd9d946a582ead3b7b858b588}}
Recevr my-topic_fanout ; {node: {x-declare: {auto-delete: true,
durable: false, type: fanout}, type: topic}, create: always,
link: {x-declare: {auto-delete: true, exclusive: true, durable:
false}, durable: true, name:
my-topic_fanout_b40001afd9d946a582ead3b7b858b588}}
--- Note: subscribing twice to the same exclusive address! (Bad!)
Recevr openstack/my-topic.server-02 ; {node: {x-declare: {auto-delete:
true, durable: true}, type: topic}, create: always, link:
{x-declare: {auto-delete: true, exclusive: false, durable: false},
durable: true, name: my-topic.server-02}}
Recevr openstack/my-topic ; {node: {x-declare: {auto-delete: true,
durable: true}, type: topic}, create: always, link: {x-declare:
{auto-delete: true, exclusive: false, durable: false}, durable: true,
name: my-topic}}
When using topology=2, the failure case is a bit different. On reconnect,
the fanout addresses are lacking proper topic names:
Recevr amq.topic/topic/openstack/my-topic ; {link: {x-declare:
{auto-delete: true, durable: false}}}
Recevr amq.topic/fanout/ ; {link: {x-declare: {auto-delete: true,
exclusive: true}}}
Recevr amq.topic/fanout/ ; {link: {x-declare: {auto-delete: true,
exclusive: true}}}
Recevr amq.topic/topic/openstack/my-topic.server-02 ; {link: {x-declare:
{auto-delete: true, durable: false}}}
Note again - two subscriptions to fanout, and 'my-topic' is missing
(it should be after that trailing /)
FYI - my test RPC server and client can be accessed here:
https://github.com/kgiusti/oslo-messaging-clients
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1251757/+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 1257273] [NEW] Glance download fails when size is 0
Public bug reported:
Glance images are not being fetched by glance's API v1 when the size is
0. There are 2 things wrong with this behaviour:
1) Active images should always be ready to be downloaded, regardless they're
locally or remotely stored.
2) The size shouldn't be the way to verify whether an image has some data or
not.
https://git.openstack.org/cgit/openstack/glance/tree/glance/api/v1/images.py#n455
This is happening in the API v1, but it doesn't seem to be true for v2.
** Affects: glance
Importance: High
Status: New
** Changed in: glance
Importance: Undecided = High
** Description changed:
Glance images are not being fetched by glance's API v1 when the size is
0. There are 2 things wrong with this behaviour:
1) Active images should always be ready to be downloaded, regardless they're
locally or remotely stored.
2) The size shouldn't be the way to verify whether an image has some data or
not.
- 431 if image_meta.get('size') == 0:
- 432 - image_iterator = iter([])
- 433 else:
- 434 image_iterator, size = self._get_from_store(req.context,
- 435
image_meta['location'])
- 436 image_iterator = utils.cooperative_iter(image_iterator)
- 437 image_meta['size'] = size or image_meta['size']
+
https://git.openstack.org/cgit/openstack/glance/tree/glance/api/v1/images.py#n455
This is happening in the API v1, but it doesn't seem to be true for v2.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1257273
Title:
Glance download fails when size is 0
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
Glance images are not being fetched by glance's API v1 when the size
is 0. There are 2 things wrong with this behaviour:
1) Active images should always be ready to be downloaded, regardless they're
locally or remotely stored.
2) The size shouldn't be the way to verify whether an image has some data or
not.
https://git.openstack.org/cgit/openstack/glance/tree/glance/api/v1/images.py#n455
This is happening in the API v1, but it doesn't seem to be true for
v2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1257273/+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 1255154] Re: deny image size updates if image data is already present
*** This bug is a duplicate of bug 1220797 *** https://bugs.launchpad.net/bugs/1220797 ** This bug has been marked a duplicate of bug 1220797 can update image size to smaller number even though cannot create it like that in the first place -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1255154 Title: deny image size updates if image data is already present Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: we should deny updates to an image size if image data is already present valid statuses for size updates are instead (eg.) images queued To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1255154/+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 1080864] Re: glance member-add doesn't validate input
** Changed in: glance Status: Incomplete = 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/1080864 Title: glance member-add doesn't validate input Status in OpenStack Image Registry and Delivery Service (Glance): Won't Fix Bug description: Hi, In ESSEX it is possible to enter invalid data in the glance database when adding members to images. For instance, I can issue the following command and it completes with success: glance member-add foo Even though 'foo' is neither a project nor a registered user in the cloud. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1080864/+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 1092188] Re: Need mechanism too cleanup deleted image rows from the database
** Changed in: glance Importance: Undecided = Wishlist ** Changed in: glance Status: In Progress = Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1092188 Title: Need mechanism too cleanup deleted image rows from the database Status in OpenStack Image Registry and Delivery Service (Glance): Opinion Bug description: When images are deleted and subsequently scrubbed (i.e. the status of the image is deleted)the database records are retained. These records can clutter the database over time leading to performance issues on database migration as well as performance issues querying the database. We need a way of optionally cleaning these records out so that they can be removed or at least archived.I will attach a patch which provides an archiver utility to achieve this. It supplies an archive and archive restore function. I've can include tests when I get feedback on this. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1092188/+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
