** Also affects: glance
Importance: Undecided
Status: New
** Changed in: glance
Importance: Undecided => Low
** Changed in: glance
Status: New => In Progress
** Changed in: glance
Milestone: None => pike-1
--
You received this bug notification because you are a member
I think the xen driver needs a code to check the container and disk
formats supported at that glance installation.
A check using the schema call will do the trick
https://github.com/openstack/glance/blob/7c7dd626896d732d75c6b802a33b9462aee885fd/glance/api/v2/images.py#L980
I think the use case is reasonable. I would prefer a spec-lite for this
change, it's a feature more than a bug.
You can file one here:
https://github.com/openstack/glance-specs/blob/master/specs/ocata/approved/glance/lite-specs.rst
** Changed in: glance
Status: New => Opinion
** Changed
I have moved it to Opinion. As per the discussion on the spec
https://review.openstack.org/#/c/242682/ , we've come to an agreement
that such clean up doesn't belong in Glance.
You are welcome to open a new lite-spec with link to this bug to get
wider input.
** Changed in: glance
Status:
Public bug reported:
Recently, more than a few people have asked about different ways a
glance service can be deployed:
* eventlet based
* nginx based
* other ways (like say using repose)
It would be good to document this in our developer docs or specs and
create a FAQ page in our
Have you tried this trick
https://github.com/openstack/glance/blob/11cfe49b8f88f68d83028b5920891bb16792da72/glance/cmd/__init__.py#L23-L49
?
I think that'd work for you and we may have to update the documentation
using this bug as an example to update the docs!
** Changed in: glance
@Lyle: are you using the schemas to validate your request?
I see how a 409 is more convenient.
I'm on the fence for this -- my opinion is that 403 is the right call
from glance's perspective as you are trying to update the reserved
attribute and have some knowledge of the image (using the id).
I doubt if we need doc change for this as the commit itself made the doc
change.
** Changed in: glance
Status: New => Opinion
** Changed in: glance
Importance: Undecided => Wishlist
** Changed in: glance
Importance: Wishlist => Low
--
You received this bug notification because
Public bug reported:
We have removed s3 references in patch
https://review.openstack.org/#/c/348507/
However there are a few incorrect references of s3 in the below
mentioned migration scripts.
We have a project policy to not modify the migration scripts unless a
significant impact exists.
Backports proposed here:
https://review.openstack.org/#/q/I4018af408fa45f3ac0ad6e9c8229428a9f87089f,n,z
** Also affects: glance/liberty
Importance: Undecided
Status: New
** Also affects: glance/mitaka
Importance: Critical
Assignee: Nikhil Komawar (nikhil-komawar)
Status
/glance/api/middleware/version_negotiation.py#L80-L84
** Affects: glance
Importance: Critical
Assignee: Nikhil Komawar (nikhil-komawar)
Status: Triaged
** Changed in: glance
Importance: Undecided => Medium
** Changed in: glance
Status: New => Triaged
** C
** Also affects: glance
Importance: Undecided
Status: New
** Changed in: glance
Importance: Undecided => Low
** Changed in: glance
Status: New => Triaged
** Changed in: glance
Assignee: (unassigned) => Dinesh Bhor (dinesh-bhor)
--
You received this bug notification
Public bug reported:
Matt Riedmann reported on IRC that the developer api reference for a
show call on an image http://developer.openstack.org/api-ref-
image-v2.html#showImage-v2 shows incorrect response.
Specifically, the expected outcome has a flat structure to the response
and the
** Also affects: glance
Importance: Undecided
Status: New
** Changed in: glance
Status: New => In Progress
** Changed in: glance
Importance: Undecided => High
** Changed in: glance
Assignee: (unassigned) => Sven Anderson (ansiwen)
--
You received this bug notification
Public bug reported:
Currently, the oslo config generator takes glance_store configs in
consideration while generating sample configs for the registry. Registry
doesn't really need these configs.
It would be better to get them removed.
** Affects: glance
Importance: Undecided
** Changed in: glance
Status: In Progress => Invalid
** Changed in: glance-store
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1521236
Title:
** Changed in: glance
Importance: Undecided => Medium
** Also affects: glance/liberty
Importance: Undecided
Status: New
** Also affects: glance/kilo
Importance: Undecided
Status: New
** Changed in: glance/kilo
Importance: Undecided => Medium
** Changed in:
** Project changed: glance => glance-store
** Changed in: glance-store
Importance: Undecided => Wishlist
** Tags added: lite-spec
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1297451
1. I agree, the image deletion operation should be atomic.
2. Image data left behind means there is a potential risk of filling up
storage quota and resulting into a DoS; be mindful that it's a denial of
service but NOT a exploit as it is dependent on the operators' failure
scenarios of g-api <->
You can close this bug as it's not related to py34 (99% sure).
The invalid literal and the decoding errors usually happen during
hickups in the connection while trying to upload data.
Here's the conversation I had with Hemanth who sees them a lot in his
cloud.
---
10:44:48 nikhil
rosmaita:
I think we can backport it to Kilo and don;t see any reason why not.
THoughts?
** Also affects: glance/kilo
Importance: Undecided
Status: New
** Tags added: liberty-rc-potential
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Also affects: glance/kilo
Importance: Undecided
Status: New
** Also affects: glance/liberty
Importance: Undecided
Status: New
** No longer affects: glance/liberty
** Tags added: liberty-rc-potential
--
You received this bug notification because you are a member of
** Changed in: python-glanceclient
Status: Fix Released => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1476770
Title:
_translate_from_glance fails with "AttributeError: id"
** Also affects: glance/kilo
Importance: Undecided
Status: New
** Changed in: glance/kilo
Status: New => In Progress
** Changed in: glance/kilo
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
RC2 is yet to be out, so I updated the status to Fix Committed from FIx
Released. This will be released when RC2 is out; that is either tomorrow
(Friday Oct 2) or next week.
** Changed in: glance
Status: Fix Released => Fix Committed
--
You received this bug notification because you are
This has become non-relevant so, lowering priority and removing
milestone target.
The status has been moved to opinion until we get back to it next time.
If no more updates exists it will be won't fix then.
** Changed in: glance
Importance: High => Wishlist
** Changed in: glance
** Also affects: glance/kilo
Importance: Undecided
Status: New
** Also affects: glance/juno
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
** Changed in: glance
Status: New = Fix Committed
** Changed in: glance
Status: Fix Committed = Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1418061
Title:
https://review.openstack.org/#/c/171180/
** Project changed: glance = python-glanceclient
** Changed in: python-glanceclient
Status: Invalid = Fix Committed
** Changed in: python-glanceclient
Importance: Undecided = Low
** Changed in: python-glanceclient
Milestone: None = 0.19.0
** Changed in: glance
Status: Triaged = Confirmed
** Changed in: glance
Status: Confirmed = Won't Fix
** Changed in: glance
Importance: High = Undecided
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
** Also affects: glance/juno
Importance: Undecided
Status: New
** Changed in: glance/juno
Status: New = Fix Committed
** Changed in: glance/juno
Importance: Undecided = Low
** Changed in: glance/juno
Assignee: (unassigned) = Ian Cordasco (icordasc)
--
You received
** Changed in: glance-store
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1422699
Title:
glance api doesn't abort start up on Store
** Changed in: glance-store
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1449639
Title:
RBD: On image creation error, image is not deleted
Public bug reported:
https://review.openstack.org/#/c/154704/ modifies is_public to be non-
reserved.
However, the list --
_reserved_properties = ['owner', 'is_public', 'locations',
does not have it removed.
https://github.com/openstack/glance/blob/master/glance/domain/__init__.py#L56
**
Public bug reported:
As per title
** Affects: glance
Importance: Critical
Assignee: Fei Long Wang (flwang)
Status: In Progress
** Tags: kilo-rc-potential
** Tags added: kilo-rc-potential
** Changed in: glance
Importance: Undecided = Critical
** Changed in: glance
How can this be a bug if export is not even a implemented task yet?
** Changed in: glance
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1446286
Title:
Public bug reported:
Context and information:
--
Currently, 404 is seen by the user when image-delete call is made via the
Glance API or through the Images API of Nova for an Image in deleted status.
However, if an Image is in pending_delete and a user with
Glance change was merge in kilo-3
Glance client change is in tag 0.17.0
** Changed in: glance
Status: In Progress = Fix Committed
** Also affects: python-glanceclient
Importance: Undecided
Status: New
** Changed in: python-glanceclient
Status: New = Fix Released
**
** Changed in: glance
Importance: Undecided = Wishlist
** Also affects: python-glanceclient
Importance: Undecided
Status: New
** Changed in: python-glanceclient
Assignee: (unassigned) = Yamini Sardana (yamini-sardana)
** Changed in: python-glanceclient
Importance: Undecided
** Changed in: python-glanceclient
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1398838
Title:
Errors should not print json
Status in
** Also affects: glance-store
Importance: Undecided
Status: New
** No longer affects: glance
** Changed in: glance-store
Status: New = Triaged
** Changed in: glance-store
Importance: Undecided = Medium
** Changed in: glance-store
Assignee: (unassigned) = Hemanth
** Changed in: glance-store
Status: In Progress = Fix Released
** Changed in: glance
Milestone: None = kilo-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1379798
Title:
** Changed in: glance-store
Importance: Undecided = Medium
** Changed in: glance-store
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1316137
** Also affects: glance-store
Importance: Undecided
Status: New
** Changed in: glance-store
Status: New = In Progress
** Changed in: glance-store
Assignee: (unassigned) = Stuart McLaren (stuart-mclaren)
** Changed in: glance-store
Milestone: None = v0.1.11
** Changed
** Changed in: glance
Importance: Undecided = High
** Changed in: glance-store
Importance: Undecided = High
** Changed in: glance-store
Status: In Progress = Fix Committed
** Changed in: glance
Status: Fix Released = Triaged
** Changed in: glance
Milestone: kilo-2 =
** Also affects: glance-store
Importance: Undecided
Status: New
** Changed in: glance-store
Status: New = In Progress
** Changed in: glance-store
Importance: Undecided = High
** Changed in: glance-store
Assignee: (unassigned) = Sabari Murugesan (smurugesan)
** Changed
** Changed in: glance
Importance: Undecided = Medium
** Also affects: glance-store
Importance: Undecided
Status: New
** Changed in: glance-store
Assignee: (unassigned) = Sabari Murugesan (smurugesan)
** Changed in: glance-store
Status: New = In Progress
** Changed in:
*** This bug is a duplicate of bug 1398830 ***
https://bugs.launchpad.net/bugs/1398830
** This bug is no longer a duplicate of bug 1188532
image download process won't terminate after deleting image from dashboard
** This bug has been marked a duplicate of bug 1398830
Glance image leak
Public bug reported:
The error is seen as
OperationalError: (OperationalError) cannot start a transaction within a
transaction u'/*\n * This is necessary because SQLite does not support\n
* RENAME INDEX or ALTER TABLE CHANGE COLUMN.\n */\nBEGIN TRANSACTION;'
()
More info at:
Unfortunately, we cannot re-delete Image via the API by design.
Another approach for this real issue might be to use the scrubber to
keep track of such leftover data and retry deletes. Please provide your
suggestions here: https://review.openstack.org/#/c/125156/
** Changed in: glance
Public bug reported:
Currently, it's possible to upload data to an image which is not in
queued state; and while attempting to update it status to active the 409
conflict is raised. [1, 2, 3]
We'd prevent this as it could potentially mean bandwidth usage for the
user.
[1]
** Changed in: glance
Status: Confirmed = Invalid
** Changed in: glance
Importance: Medium = Undecided
** Changed in: glance
Assignee: nikhil komawar (nikhil-komawar) = (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
This is by design: http://docs.openstack.org/api/openstack-image-
service/2.0/content/upload-image-file.html
** Changed in: glance
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://review.openstack.org/#/c/110574/9
** Also affects: glance
Importance: Undecided
Status: New
** Also affects: python-glanceclient
Importance: Undecided
Status: New
** No longer affects: glance
** Changed in: python-glanceclient
Status: New = In Progress
**
** Changed in: glance
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1316234
Title:
Image delete calls slow due to synchronous wait on backend
Public bug reported:
Although,
https://github.com/openstack/glance/blob/master/glance/db/registry/api.py#L262
has code for db/registry there are missing tests in
https://github.com/openstack/glance/blob/master/glance/tests/functional/db/test_registry.py
** Affects: glance
Importance:
Public bug reported:
sqlalchemy/sql/default_comparator.py:35: SAWarning: The IN-predicate on
image_locations.id was invoked with an empty sequence. This results in a
contradiction, which nonetheless can be expensive to evaluate. Consider
alternative strategies for improved performance.
Public bug reported:
==
FAIL:
glance.tests.integration.v2.test_tasks_api.TestTasksApi.test_task_schema_api
--
Traceback (most recent call last):
Public bug reported:
A good example of this use case is
https://review.openstack.org/#/c/107594 where the notifications need to
be added to the sample config file provided in Glance so that, the patch
would work with devstack.
However, g-reg does not send any notifications so, we need to either
Public bug reported:
As per the question on this change :-
https://review.openstack.org/#/c/102352/4/requirements.txt
we could potentially have a invalid version installed in the
environment.
The answer to that question lead us to make the change in the global
requirements:-
Thanks Clark, for the feedback. Seems like nova/glance bug, removing it
from infra bug list.
** No longer affects: openstack-ci
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
Following the change the way we store glance location as per
https://review.openstack.org/#/c/98722
we need to modify the example url in SingleTenantStore and
MultiTenantStore to indicate all appropriate urls as per the
situtation..
Public bug reported:
Issue:-
---
Currently, the image delete calls can be very slow if the image being delete is
large (consisting of multiple chunks esp. in case of swift) or if the backend
store has slow response time.
Solution:-
-
Make image delete call asynchronous
Public bug reported:
This is reopen for the bug 1039897 (
https://bugs.launchpad.net/glance/+bug/1039897 ). Description as per the
old bugs description.
Seems the code has been changed since that got merged in and needs a fix
again.
** Affects: glance
Importance: Undecided
Status:
Public bug reported:
Currently, we need to have a Image object (or record) to be able to set
it's data bits.
We need an alternative mechanism for Image creation in cases where
failure in uploading data bits should fail Image creation.
Example use case:
- Say an import task fails while uploading
Public bug reported:
A call to DELETE /v2/tasks/{task_id} for an existing task_id returns a
404 (which is obviously incorrect because a GET on the same URL returns
a task detail response).
The response should be 405 (Method Not Allowed). From the spec:
The method specified in the Request-Line is
Public bug reported:
Proxy on behalf of Sulochan Acharya ( sulochan.acha...@rackspace.co.uk
):-
Taking in to account incomplete dir when the pruner is run will create a case
where if we delete old images taking the new incomplete image in account, and
the new incomplete image fails, then we
Public bug reported:
https://github.com/openstack/glance/blob/master/glance/domain/__init__.py line
376 -- result is referenced however, does not exist in the class definition
and
https://github.com/openstack/glance/blob/master/glance/domain/__init__.py line
382 -- message is referenced
Thanks for pointing that out ttx, however we do not have this issue in
stable/grizzly.
Please find the code for grizzly here:
https://github.com/openstack/glance/blob/stable/grizzly/glance/store/__init__.py#L393
** Changed in: glance/grizzly
Status: New = Invalid
--
You received this
This has been resolved by https://review.openstack.org/#/c/62321/ .
However, that MP did not link to the bug.
** Changed in: glance
Status: Confirmed = Fix Released
** Changed in: glance
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a
Public bug reported:
we should ensure that the imports are in alphabetical order and remove
H306 ignore flag from tox.ini
** Affects: glance
Importance: Undecided
Assignee: nikhil komawar (nikhil-komawar)
Status: New
** Changed in: glance
Assignee: (unassigned) = nikhil
Public bug reported:
We currently, do not allow NULL owner for tasks and models.py lets it be
NULL however, the tasks table ensures that it does not set NULL owner.
So, we do not need migration - just need fix in the code patch for this.
** Affects: glance
Importance: Undecided
72 matches
Mail list logo
