After working with Hong directly, we have determined this was an
environment issue.
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.l
Public bug reported:
Requirements.txt defines the pbr version as
pbr<2.0,>=0.11
but version 0.11 cannot handle the following syntax in the windows
section:
# Windows-only requirements
pywin32;sys_platform=='win32'
wmi;sys_platform=='win32'
This causes the following error when installing neutron
Public bug reported:
When many volumes are attached to instances on the same compute host
(with multipath enabled), volume detach is very slow and get slower as
more volumes are attached.
For example:
1. compute1 is a compute node with instance1 and instance2.
2. instance1 has 10 volumes attache
Public bug reported:
Live migration in nova does not seem to work as it fails with "CPU doesn't have
compatibility" even between hosts with the exact same CPU models. This was
introduced recently by the commit below. If I revert Nova to the offending
commits parent, the live migration succeeds
Public bug reported:
Brick and nova are not synchronized with the same connect_volume lock.
This can cause nova or cinder to logout of an iscsi portal when the
other one is attempting to use it. if nova and cinder are on the same
node.
This may seem like a rare situation but commonly occurs in ou
Public bug reported:
During live migration with attached volume, nova ignores initialize
connection errors and does not roll back.
Steps:
* Create a nova instance
* Attach a cinder volume
* Perform ‘nova live-migration’ to a different backend
-Cause a failure in the ‘initialize_connection
Public bug reported:
Requests for many resources in Glance v2 will return a 404 if the
request is using an unsupported HTTP verb for that resource. For
example, the /v2/images resource does exist but a 404 is returned when
attempting a DELETE on that resource. Instead, this should return an
HTTP 4
Public bug reported:
Attempting a HEAD request on the /images/detail resource results in a
500 response. This should ideally be an HTTP 405 response.
This issue does not occur when doing a HEAD on /images for some reason
curl -i -X HEAD -H "X-Auth-Token: $AUTH_TOKEN" -H 'Content-Type:
applicati
entually try to call ‘append’, resulting in a Forbidden
being raised. Printing the system stack before raising the Forbidden
results in this stack trace: http://paste.openstack.org/show/72301/
** Affects: glance
Importance: High
Assignee: Alex Meade (alex-meade)
Status: In Progress
Public bug reported:
In both glance v1 and v2, if policies forbide an action, when it occurs
there are no logs.
** Affects: glance
Importance: Low
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
Public bug reported:
Glance v2 image property quota enforcement can be unintuitive.
There are a number of reasons an image may have more properties than the
image_propery_quota allows. E.g. if the quota is lowered or when it is
first created. If this happens then any request to modify an image mu
** 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/1041308
Title:
decouple sql debug from debug and implement a verbose
Status in
Public bug reported:
curl -i -X PATCH -H "X-Auth-Token: $AUTH_TOKEN" -H 'Content-Type:
application/openstack-images-v2.1-json-patch' -H 'User-Agent: python-
glanceclient' -d '[{"path": "/locations", "value":
[{"url":"swift+http://service:glance:password@localhost:5000/v2.0/glance
/d0d90e9b-82f2-43
Public bug reported:
When creating an image in glance v1 and specifyig the location with a
bad scheme you receive an HTTP 500. In this case 'http+swift" is a bad
scheme.
glance image-create --name bad-location --disk-format=vhd --container-
format=ovf --location="http+swift://bah"
Request return
Public bug reported:
glance image-create --name bad-location --disk-format=vhd --container-
format=ovf --location="swift+http://bah";
Request returned failure status.
HTTPInternalServerError (HTTP 500)
2013-12-03 21:26:16.684 6312 INFO glance.wsgi.server
[eee7679e-6710-4487-9f55-fae7ba4a7aaa
Actually, yeah i agree with you Fei. The user can see the image anyways
so it's not like we need to hide the fact it exists. I need to stop
listening to other people :P
** Changed in: glance
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
En
I think this is invalid, v1 should not be showing deleted images either
** 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/1197344
Title:
** Changed in: keystone
Assignee: Alex Meade (alex-meade) => (unassigned)
** Changed in: keystone
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchp
Setting this to Fix Committed since it not longer seems to be an issue.
Looking into it, the domain model code fixed the root of this problem.
** Changed in: glance
Status: New => Invalid
** Changed in: glance
Status: Invalid => Fix Committed
--
You received this bug notification
19 matches
Mail list logo
