[Yahoo-eng-team] [Bug 1602715] Re: If barbicanclient does not exist causes 500
** 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/1602715 Title: If barbicanclient does not exist causes 500 Status in Glance: Invalid Bug description: 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data Traceback (most recent call last): 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/api/v2/image_data.py", line 114, in upload 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data image.set_data(data, size) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/domain/proxy.py", line 195, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data self.base.set_data(data, size) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/notifier.py", line 449, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data _send_notification(notify_error, 'image.upload', msg) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data self.force_reraise() 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data six.reraise(self.type_, self.value, self.tb) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/notifier.py", line 396, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data self.repo.set_data(data, size) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/api/policy.py", line 192, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data return self.image.set_data(*args, **kwargs) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/quota/__init__.py", line 298, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data self.image.set_data(data, size=size) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/location.py", line 415, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data self.context, self.image.extra_properties) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/common/signature_utils.py", line 271, in get_verifier 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data signature_key_type) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/common/signature_utils.py", line 427, in get_public_key 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data certificate = get_certificate(context, signature_certificate_uuid) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/common/signature_utils.py", line 453, in get_certificate 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data keymgr_api = key_manager.API() 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/castellan/key_manager/__init__.py", line 30, in API 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data cls = importutils.import_class(conf.key_manager.api_class) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/oslo_utils/importutils.py", line 30, in import_class 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data __import__(mod_str) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/castellan/key_manager/barbican_key_manager.py", line 42, in 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data from barbicanclient import client as barbican_client 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data ImportError: No module named
[Yahoo-eng-team] [Bug 1602715] [NEW] If barbicanclient does not exist causes 500
Public bug reported: 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data Traceback (most recent call last): 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/api/v2/image_data.py", line 114, in upload 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data image.set_data(data, size) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/domain/proxy.py", line 195, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data self.base.set_data(data, size) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/notifier.py", line 449, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data _send_notification(notify_error, 'image.upload', msg) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data self.force_reraise() 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data six.reraise(self.type_, self.value, self.tb) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/notifier.py", line 396, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data self.repo.set_data(data, size) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/api/policy.py", line 192, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data return self.image.set_data(*args, **kwargs) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/quota/__init__.py", line 298, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data self.image.set_data(data, size=size) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/location.py", line 415, in set_data 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data self.context, self.image.extra_properties) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/common/signature_utils.py", line 271, in get_verifier 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data signature_key_type) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/common/signature_utils.py", line 427, in get_public_key 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data certificate = get_certificate(context, signature_certificate_uuid) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/glance/common/signature_utils.py", line 453, in get_certificate 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data keymgr_api = key_manager.API() 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/castellan/key_manager/__init__.py", line 30, in API 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data cls = importutils.import_class(conf.key_manager.api_class) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/oslo_utils/importutils.py", line 30, in import_class 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data __import__(mod_str) 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data File "/opt/stack/venv/glance-20160712T142933Z/lib/python2.7/site-packages/castellan/key_manager/barbican_key_manager.py", line 42, in 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data from barbicanclient import client as barbican_client 2016-07-13 09:26:03.602 28677 ERROR glance.api.v2.image_data ImportError: No module named barbicanclient This should be caught rather than throwing a 500 error. ** Affects: glance Importance: Undecided Assignee: Niall Bunting (niall-bunting) Status: New -- You r
[Yahoo-eng-team] [Bug 1595467] Re: Signature verification failure leads to saving image
** 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/1595467
Title:
Signature verification failure leads to saving image
Status in Glance:
Invalid
Bug description:
Overview:
When signature verification fails it can cause a 500 error. This causes the
image to become stuck in the saving state.
What should happen is that it returns a 40? and the image is put into
the deleted state.
Reproducing:
glance image-create --name mySignedImage --container-format bare
--disk-format qcow2 --property img_signature="WRONG SIGNATURE" --property
img_signature_certificate_uuid="$cert_uuid" --property
img_signature_hash_method='SHA-256' --property img_signature_key_type='RSA-PSS'
< myimage
++--+
| Property | Value|
++--+
| checksum | None |
| container_format | bare |
| created_at | 2016-06-23T09:46:34Z |
| disk_format| qcow2|
| id | f0839709-4ff6-4291-9997-a4d387e20582 |
| img_signature | |
| img_signature_certificate_uuid | cd7cc675-e573-419c-8fff-33a72734a243 |
| img_signature_hash_method | SHA-256 |
| img_signature_key_type | RSA-PSS |
| min_disk | 0|
| min_ram| 0|
| name | mySignedImage|
| owner | 7f065427534f49ab97a0b68ecc73fd07 |
| protected | False|
| size | None |
| status | queued |
| tags | [] |
| updated_at | 2016-06-23T09:46:34Z |
| virtual_size | None |
| visibility | private |
++--+
500 Internal Server Error
The server has either erred or is incapable of performing the requested
operation.
(HTTP 500)
nib@work-devstack:/tmp/testtmp/nest$ glance image-show
f0839709-4ff6-4291-9997-a4d387e20582
++--+
| Property | Value|
++--+
| checksum | None |
| container_format | bare |
| created_at | 2016-06-23T09:46:34Z |
| disk_format| qcow2|
| id | f0839709-4ff6-4291-9997-a4d387e20582 |
| img_signature | |
| img_signature_certificate_uuid | cd7cc675-e573-419c-8fff-33a72734a243 |
| img_signature_hash_method | SHA-256 |
| img_signature_key_type | RSA-PSS |
| min_disk | 0|
| min_ram| 0|
| name | mySignedImage|
| owner | 7f065427534f49ab97a0b68ecc73fd07 |
| protected | False|
| size | None |
| status | saving |
| tags | [] |
| updated_at | 2016-06-23T09:46:34Z |
| virtual_size | None |
| visibility | private |
++--+
Console:
2016-06-23 09:46:35.619 TRACE glance.common.wsgi _('Signature
verification failed')
2016-06-23 09:46:35.619 TRACE glance.common.wsgi SignatureVerificationError:
Signature verification failed
2016-06-23 09:46:35.619 TRACE glance.common.w
[Yahoo-eng-team] [Bug 1595467] [NEW] Signature verification failure leads to saving image
Public bug reported:
Overview:
When signature verification fails it can cause a 500 error. This causes the
image to become stuck in the saving state.
What should happen is that it returns a 40? and the image is put into
the deleted state.
Reproducing:
glance image-create --name mySignedImage --container-format bare --disk-format
qcow2 --property img_signature="WRONG SIGNATURE" --property
img_signature_certificate_uuid="$cert_uuid" --property
img_signature_hash_method='SHA-256' --property img_signature_key_type='RSA-PSS'
< myimage
++--+
| Property | Value|
++--+
| checksum | None |
| container_format | bare |
| created_at | 2016-06-23T09:46:34Z |
| disk_format| qcow2|
| id | f0839709-4ff6-4291-9997-a4d387e20582 |
| img_signature | |
| img_signature_certificate_uuid | cd7cc675-e573-419c-8fff-33a72734a243 |
| img_signature_hash_method | SHA-256 |
| img_signature_key_type | RSA-PSS |
| min_disk | 0|
| min_ram| 0|
| name | mySignedImage|
| owner | 7f065427534f49ab97a0b68ecc73fd07 |
| protected | False|
| size | None |
| status | queued |
| tags | [] |
| updated_at | 2016-06-23T09:46:34Z |
| virtual_size | None |
| visibility | private |
++--+
500 Internal Server Error
The server has either erred or is incapable of performing the requested
operation.
(HTTP 500)
nib@work-devstack:/tmp/testtmp/nest$ glance image-show
f0839709-4ff6-4291-9997-a4d387e20582
++--+
| Property | Value|
++--+
| checksum | None |
| container_format | bare |
| created_at | 2016-06-23T09:46:34Z |
| disk_format| qcow2|
| id | f0839709-4ff6-4291-9997-a4d387e20582 |
| img_signature | |
| img_signature_certificate_uuid | cd7cc675-e573-419c-8fff-33a72734a243 |
| img_signature_hash_method | SHA-256 |
| img_signature_key_type | RSA-PSS |
| min_disk | 0|
| min_ram| 0|
| name | mySignedImage|
| owner | 7f065427534f49ab97a0b68ecc73fd07 |
| protected | False|
| size | None |
| status | saving |
| tags | [] |
| updated_at | 2016-06-23T09:46:34Z |
| virtual_size | None |
| visibility | private |
++--+
Console:
2016-06-23 09:46:35.619 TRACE glance.common.wsgi _('Signature verification
failed')
2016-06-23 09:46:35.619 TRACE glance.common.wsgi SignatureVerificationError:
Signature verification failed
2016-06-23 09:46:35.619 TRACE glance.common.wsgi
** Affects: glance
Importance: Undecided
Assignee: Niall Bunting (niall-bunting)
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/1595467
Title:
Signature verification failure leads to saving image
Status in Glance:
New
Bug d
[Yahoo-eng-team] [Bug 1593177] [NEW] The default policy should be admin
Public bug reported: From: https://review.openstack.org/#/c/309346/ " I investigated the behaviour of the policy file when various policies are removed. A completely empty policy file will return a 403 Forbidden. As the user will not match with any of the policies. However, because glance has the policy ``default: ""``. It means that any policy that is not explicitly stated in the the policy.json, is by default usable by any member. I think that the ``default`` option is a potentially bad thing to have in the policy.json file, due to the ability to give permissions without explicitly stating it. " Therefore we should change ``"default": "",`` to ``"default": "role:admin",``. To make sure that members don't inherit policies that they shouldn't in the future. From a operators perspective it should be more secure to have an opt-in rather than opt-out. ** Affects: glance Importance: Undecided Assignee: Niall Bunting (niall-bunting) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Niall Bunting (niall-bunting) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1593177 Title: The default policy should be admin Status in Glance: In Progress Bug description: From: https://review.openstack.org/#/c/309346/ " I investigated the behaviour of the policy file when various policies are removed. A completely empty policy file will return a 403 Forbidden. As the user will not match with any of the policies. However, because glance has the policy ``default: ""``. It means that any policy that is not explicitly stated in the the policy.json, is by default usable by any member. I think that the ``default`` option is a potentially bad thing to have in the policy.json file, due to the ability to give permissions without explicitly stating it. " Therefore we should change ``"default": "",`` to ``"default": "role:admin",``. To make sure that members don't inherit policies that they shouldn't in the future. From a operators perspective it should be more secure to have an opt-in rather than opt-out. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1593177/+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 1581583] [NEW] test_update_disallowed_attributes tests incorrectly
Public bug reported: test_update_disallowed_attributes in glance/tests/unit/v2/test_images_resource.py Does not work as intended. It does not test if the attributes are disallowed but actually falls back to a validation that happens later on in the code. ** Affects: glance Importance: Undecided Assignee: Niall Bunting (niall-bunting) Status: New ** Summary changed: - check_allowed does not work + test_update_disallowed_attributes does not work ** Summary changed: - test_update_disallowed_attributes does not work + test_update_disallowed_attributes tests incorrectly -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1581583 Title: test_update_disallowed_attributes tests incorrectly Status in Glance: New Bug description: test_update_disallowed_attributes in glance/tests/unit/v2/test_images_resource.py Does not work as intended. It does not test if the attributes are disallowed but actually falls back to a validation that happens later on in the code. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1581583/+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 1568018] Re: Stable liberty seems to fail tests
** Project changed: glance => magnum -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1568018 Title: Stable liberty seems to fail tests Status in Magnum: New Bug description: Overview: When running tox -epy27 this seems to occur. Output: 016-04-05 09:32:46.225 | FAIL: magnum.tests.unit.api.test_hooks.TestContextHook.test_context_hook_before_method 2016-04-05 09:32:46.225 | tags: worker-3 2016-04-05 09:32:46.225 | -- 2016-04-05 09:32:46.225 | Empty attachments: 2016-04-05 09:32:46.225 | stderr 2016-04-05 09:32:46.225 | stdout 2016-04-05 09:32:46.225 | 2016-04-05 09:32:46.225 | Traceback (most recent call last): 2016-04-05 09:32:46.226 | File "magnum/tests/unit/api/test_hooks.py", line 51, in test_context_hook_before_method 2016-04-05 09:32:46.226 | ','.join(ctx.roles)) 2016-04-05 09:32:46.226 | File "/home/jenkins/workspace/gate-magnum-python27/.tox/py27/local/lib/python2. 7/site-packages/testtools/testcase.py", line 362, in assertEqual 2016-04-05 09:32:46.226 | self.assertThat(observed, matcher, message) 2016-04-05 09:32:46.226 | File "/home/jenkins/workspace/gate-magnum-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 447, in assertThat 2016-04-05 09:32:46.227 | raise mismatch_error 2016-04-05 09:32:46.227 | testtools.matchers._impl.MismatchError: 'role1,role2' != '' To manage notifications about this bug go to: https://bugs.launchpad.net/magnum/+bug/1568018/+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 1568018] [NEW] Stable liberty seems to fail tests
Public bug reported:
Overview:
When running tox -epy27 this seems to occur.
Output:
016-04-05 09:32:46.225 | FAIL:
magnum.tests.unit.api.test_hooks.TestContextHook.test_context_hook_before_method
2016-04-05 09:32:46.225 | tags: worker-3
2016-04-05 09:32:46.225 |
--
2016-04-05 09:32:46.225 | Empty attachments:
2016-04-05 09:32:46.225 | stderr
2016-04-05 09:32:46.225 | stdout
2016-04-05 09:32:46.225 |
2016-04-05 09:32:46.225 | Traceback (most recent call last):
2016-04-05 09:32:46.226 | File "magnum/tests/unit/api/test_hooks.py", line
51, in test_context_hook_before_method
2016-04-05 09:32:46.226 | ','.join(ctx.roles))
2016-04-05 09:32:46.226 | File
"/home/jenkins/workspace/gate-magnum-python27/.tox/py27/local/lib/python2.
7/site-packages/testtools/testcase.py", line 362, in assertEqual
2016-04-05 09:32:46.226 | self.assertThat(observed, matcher, message)
2016-04-05 09:32:46.226 | File
"/home/jenkins/workspace/gate-magnum-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 447, in assertThat
2016-04-05 09:32:46.227 | raise mismatch_error
2016-04-05 09:32:46.227 | testtools.matchers._impl.MismatchError: 'role1,role2'
!= ''
** Affects: glance
Importance: Undecided
Assignee: Niall Bunting (niall-bunting)
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/1568018
Title:
Stable liberty seems to fail tests
Status in Glance:
New
Bug description:
Overview:
When running tox -epy27 this seems to occur.
Output:
016-04-05 09:32:46.225 | FAIL:
magnum.tests.unit.api.test_hooks.TestContextHook.test_context_hook_before_method
2016-04-05 09:32:46.225 | tags: worker-3
2016-04-05 09:32:46.225 |
--
2016-04-05 09:32:46.225 | Empty attachments:
2016-04-05 09:32:46.225 | stderr
2016-04-05 09:32:46.225 | stdout
2016-04-05 09:32:46.225 |
2016-04-05 09:32:46.225 | Traceback (most recent call last):
2016-04-05 09:32:46.226 | File "magnum/tests/unit/api/test_hooks.py", line
51, in test_context_hook_before_method
2016-04-05 09:32:46.226 | ','.join(ctx.roles))
2016-04-05 09:32:46.226 | File
"/home/jenkins/workspace/gate-magnum-python27/.tox/py27/local/lib/python2.
7/site-packages/testtools/testcase.py", line 362, in assertEqual
2016-04-05 09:32:46.226 | self.assertThat(observed, matcher, message)
2016-04-05 09:32:46.226 | File
"/home/jenkins/workspace/gate-magnum-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py",
line 447, in assertThat
2016-04-05 09:32:46.227 | raise mismatch_error
2016-04-05 09:32:46.227 | testtools.matchers._impl.MismatchError:
'role1,role2' != ''
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1568018/+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 1560005] [NEW] Read only or reserved properties could contain better error messages
Public bug reported:
Overview:
The task output makes do difference just contains a message about an internal
error. However the logs this difference is specified so we should pass this
onto the user, to make it easier to debug problems.
How to reproduce:
curl -X POST http://127.0.0.1:9292/v2/tasks -H "X-Auth-Token: $token" -d
'{"type": "import","input": {"import_from":
"http://google.com","import_from_format": "qcow2","image_properties":
{"disk_format": "vhd","id": "ovf","created_at": "1"}}}'
glance task-show *id returned*
** Affects: glance
Importance: Low
Assignee: Niall Bunting (niall-bunting)
Status: New
** Changed in: glance
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1560005
Title:
Read only or reserved properties could contain better error messages
Status in Glance:
New
Bug description:
Overview:
The task output makes do difference just contains a message about an internal
error. However the logs this difference is specified so we should pass this
onto the user, to make it easier to debug problems.
How to reproduce:
curl -X POST http://127.0.0.1:9292/v2/tasks -H "X-Auth-Token: $token" -d
'{"type": "import","input": {"import_from":
"http://google.com","import_from_format": "qcow2","image_properties":
{"disk_format": "vhd","id": "ovf","created_at": "1"}}}'
glance task-show *id returned*
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1560005/+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 1555275] [NEW] Tags set changes on delete
Public bug reported: When working on a new test I ran into this, the set should not fail due the tags being deleted. == FAIL: glance.tests.unit.v2.test_images_resource.TestImagesController.test_delete_deactivated_images_anyone tags: worker-0 -- Traceback (most recent call last): File "glance/tests/unit/v2/test_images_resource.py", line 2034, in test_delete_deactivated_images_anyone self.controller.delete(request, UUID1) File "glance/common/utils.py", line 362, in wrapped return func(self, req, *args, **kwargs) File "glance/api/v2/images.py", line 236, in delete image_repo.remove(image) File "glance/domain/proxy.py", line 104, in remove result = self.base.remove(base_item) File "glance/notifier.py", line 487, in remove super(ImageRepoProxy, self).remove(image) File "glance/domain/proxy.py", line 104, in remove result = self.base.remove(base_item) File "glance/domain/proxy.py", line 104, in remove result = self.base.remove(base_item) File "glance/domain/proxy.py", line 104, in remove result = self.base.remove(base_item) File "glance/domain/proxy.py", line 104, in remove result = self.base.remove(base_item) File "glance/db/__init__.py", line 294, in remove new_values = self.db_api.image_destroy(self.context, image.image_id) File "glance/db/simple/api.py", line 64, in wrapped output = func(*args, **kwargs) File "glance/db/simple/api.py", line 761, in image_destroy for tag in tags: RuntimeError: Set changed size during iteration ** Affects: glance Importance: Undecided Assignee: Niall Bunting (niall-bunting) 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/1555275 Title: Tags set changes on delete Status in Glance: In Progress Bug description: When working on a new test I ran into this, the set should not fail due the tags being deleted. == FAIL: glance.tests.unit.v2.test_images_resource.TestImagesController.test_delete_deactivated_images_anyone tags: worker-0 -- Traceback (most recent call last): File "glance/tests/unit/v2/test_images_resource.py", line 2034, in test_delete_deactivated_images_anyone self.controller.delete(request, UUID1) File "glance/common/utils.py", line 362, in wrapped return func(self, req, *args, **kwargs) File "glance/api/v2/images.py", line 236, in delete image_repo.remove(image) File "glance/domain/proxy.py", line 104, in remove result = self.base.remove(base_item) File "glance/notifier.py", line 487, in remove super(ImageRepoProxy, self).remove(image) File "glance/domain/proxy.py", line 104, in remove result = self.base.remove(base_item) File "glance/domain/proxy.py", line 104, in remove result = self.base.remove(base_item) File "glance/domain/proxy.py", line 104, in remove result = self.base.remove(base_item) File "glance/domain/proxy.py", line 104, in remove result = self.base.remove(base_item) File "glance/db/__init__.py", line 294, in remove new_values = self.db_api.image_destroy(self.context, image.image_id) File "glance/db/simple/api.py", line 64, in wrapped output = func(*args, **kwargs) File "glance/db/simple/api.py", line 761, in image_destroy for tag in tags: RuntimeError: Set changed size during iteration To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1555275/+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 1551728] Re: Glance image-upload fails
It was a matter of releasing the glance-store which has now happened. ** 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/1551728 Title: Glance image-upload fails Status in Glance: Invalid Bug description: Overview: It seems uploading an image fails due to: TypeError: add_to_backend() got an unexpected keyword argument 'verifier' How to reproduce: nib@VM:~/devstack/devstack$ glance image-upload 9138919d-efac-4048-9922-a07c74294233 --file /etc/fstab 500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500) Traceback: http://paste.openstack.org/show/488747/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1551728/+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 1551728] [NEW] Glance image-upload fails
Public bug reported: Overview: It seems uploading an image fails due to: TypeError: add_to_backend() got an unexpected keyword argument 'verifier' How to reproduce: nib@VM:~/devstack/devstack$ glance image-upload 9138919d-efac-4048-9922-a07c74294233 --file /etc/fstab 500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500) Traceback: http://paste.openstack.org/show/488747/ ** 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/1551728 Title: Glance image-upload fails Status in Glance: New Bug description: Overview: It seems uploading an image fails due to: TypeError: add_to_backend() got an unexpected keyword argument 'verifier' How to reproduce: nib@VM:~/devstack/devstack$ glance image-upload 9138919d-efac-4048-9922-a07c74294233 --file /etc/fstab 500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500) Traceback: http://paste.openstack.org/show/488747/ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1551728/+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 1551689] [NEW] Adding member in a list causes 500
Public bug reported:
Overview:
One of the responses that wsgi returns reports: "Unexpected body type. Expected
list/dict." I then tried supplying the new member as a list for it to fail.
How to reproduce:
The command:
nib@VM:~/devstack/devstack$ curl -H "X-Auth-Token: $token" -X POST
http://127.0.0.1:9292/v2/images/a394fe2a-bc8b-4485-9819-e264d278e45f/members -d
'["f9544674f852450faf5b595a38f4e98f"]'
500 Internal Server Error
500 Internal Server Error
The server has either erred or is incapable of performing the requested
operation.
Partial stack trace:
2016-03-01 11:35:07.189 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/api/v2/image_members.py", line 249, in create
2016-03-01 11:35:07.189 TRACE glance.common.wsgi member_id = body['member']
2016-03-01 11:35:07.189 TRACE glance.common.wsgi TypeError: list indices must
be integers, not str
Output:
500
Expected:
400
** Affects: glance
Importance: Undecided
Assignee: Niall Bunting (niall-bunting)
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/1551689
Title:
Adding member in a list causes 500
Status in Glance:
New
Bug description:
Overview:
One of the responses that wsgi returns reports: "Unexpected body type.
Expected list/dict." I then tried supplying the new member as a list for it to
fail.
How to reproduce:
The command:
nib@VM:~/devstack/devstack$ curl -H "X-Auth-Token: $token" -X POST
http://127.0.0.1:9292/v2/images/a394fe2a-bc8b-4485-9819-e264d278e45f/members -d
'["f9544674f852450faf5b595a38f4e98f"]'
500 Internal Server Error
500 Internal Server Error
The server has either erred or is incapable of performing the requested
operation.
Partial stack trace:
2016-03-01 11:35:07.189 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/api/v2/image_members.py", line 249, in create
2016-03-01 11:35:07.189 TRACE glance.common.wsgi member_id =
body['member']
2016-03-01 11:35:07.189 TRACE glance.common.wsgi TypeError: list indices must
be integers, not str
Output:
500
Expected:
400
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1551689/+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 1540934] [NEW] glance-cache-prefetcher is broken
Public bug reported: Glance prefetcher is still configured to use keystone v1. As it still does not use the right uri or pass the values as json but rather uses headers. ** Affects: glance Importance: Undecided Assignee: Niall Bunting (niall-bunting) 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/1540934 Title: glance-cache-prefetcher is broken Status in Glance: New Bug description: Glance prefetcher is still configured to use keystone v1. As it still does not use the right uri or pass the values as json but rather uses headers. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1540934/+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 1531906] [NEW] Add details about all the cache config to the documents
Public bug reported: The documents currently does not cover all the options. ** Affects: glance Importance: Low Assignee: Niall Bunting (niall-bunting) 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/1531906 Title: Add details about all the cache config to the documents Status in Glance: New Bug description: The documents currently does not cover all the options. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1531906/+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 1530328] Re: Failed to create image due to exception NotAuthenticated
As posted on your review (https://review.openstack.org/#/c/262770/) this is being solved by trusts. ** 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/1530328 Title: Failed to create image due to exception NotAuthenticated Status in Glance: Won't Fix Bug description: Failed to create image due to exception NotAuthenticated. If we take a long time to upload a large image to store, it may trigger an exception "NotAuthenticated: Authentication required" and the image has been stuck in SAVING state, this due to the token expires after a period of time(default is expiration=3600s -- 1 hour, this can be modified in the keystone conf file). PS: Image Size: 80G Take Time: 2 hours Icehouse Ceph backend The error log below: 2015-12-12 18:45:00.416 6370 INFO glance.registry.client.v1.client [b7ee5de9-addf-457c-88a8-552476044f0d 44edf16aa49f4469a76c90c984fe7ce7 b10adc7c9afd4506b26d42779c77b2f4 - - -] Registry client request PUT /images/9366c0a1-40a9-4f4a-a821-2acac905ecd5 raised NotAuthenticated 2015-12-12 18:45:00.417 6370 ERROR glance.api.v1.upload_utils [b7ee5de9-addf-457c-88a8-552476044f0d 44edf16aa49f4469a76c90c984fe7ce7 b10adc7c9afd4506b26d42779c77b2f4 - - -] Failed to upload image 9366c0a1-40a9-4f4a-a821-2acac905ecd5 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils Traceback (most recent call last): 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils File "/usr/lib/python2.6/site-packages/glance/api/v1/upload_utils.py", line 152, in upload_data_to_store 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils from_state='saving') 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils File "/usr/lib/python2.6/site-packages/glance/registry/client/v1/api.py", line 169, in update_image_metadata 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils from_state=from_state) 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils File "/usr/lib/python2.6/site-packages/glance/registry/client/v1/client.py", line 190, in update_image 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils headers=headers) 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils File "/usr/lib/python2.6/site-packages/glance/registry/client/v1/client.py", line 107, in do_request 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils **kwargs) 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils File "/usr/lib/python2.6/site-packages/glance/common/client.py", line 69, in wrapped 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils return func(self, *args, **kwargs) 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils File "/usr/lib/python2.6/site-packages/glance/common/client.py", line 386, in do_request 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils headers=copy.deepcopy(headers)) 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils File "/usr/lib/python2.6/site-packages/glance/common/client.py", line 83, in wrapped 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils return func(self, method, url, body, headers) 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils File "/usr/lib/python2.6/site-packages/glance/common/client.py", line 527, in _do_request 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils raise exception.NotAuthenticated(res.read()) 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils NotAuthenticated: Authentication required 2015-12-12 18:45:00.417 6370 TRACE glance.api.v1.upload_utils 2015-12-12 18:45:00.447 6370 INFO glance.registry.client.v1.client [b7ee5de9-addf-457c-88a8-552476044f0d 44edf16aa49f4469a76c90c984fe7ce7 b10adc7c9afd4506b26d42779c77b2f4 - - -] Registry client request PUT /images/9366c0a1-40a9-4f4a-a821-2acac905ecd5 raised NotAuthenticated 2015-12-12 18:45:00.448 6370 ERROR glance.api.v1.upload_utils [b7ee5de9-addf-457c-88a8-552476044f0d 44edf16aa49f4469a76c90c984fe7ce7 b10adc7c9afd4506b26d42779c77b2f4 - - -] Unable to kill image 9366c0a1-40a9-4f4a-a821-2acac905ecd5: 2015-12-12 18:45:00.448 6370 TRACE glance.api.v1.upload_utils Traceback (most recent call last): 2015-12-12 18:45:00.448 6370 TRACE glance.api.v1.upload_utils File "/usr/lib/python2.6/site-packages/glance/api/v1/upload_utils.py", line 76, in safe_kill 2015-12-12 18:45:00.448 6370 TRACE glance.api.v1.upload_utils _kill(req, image_id, from_state) 2015-12-12 18:45:00.448 6370 TRACE glance.api.v1.upload_utils File "/usr/lib/python2.6/site-packages/glance/api/v1/upload_utils.py", line 61, in _kill 2015-12-12 18:45:00.448 6370 TRACE glance.api.v1.upload_utils from_state=from_state) 2015-12-12 18:45:00.448 6370 TRACE glance.api.v1.upload_utils File
[Yahoo-eng-team] [Bug 1521422] Re: glance image-create should not work without parameters
** 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/1521422 Title: glance image-create should not work without parameters Status in Glance: Invalid Bug description: when i do glance image-create it creates the empty image and shows a image without name on image- list It should not be created without specifying parameters like container and image path or is it like you can create empty one and later update it ? To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1521422/+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 1515619] [NEW] Nova uses some deprecated glanceclient exceptions
Public bug reported: Some of the glanceclient exceptions in Nova are now deprecated and should be updated to the current exceptions. Nova: 12.0.0? ** Affects: nova Importance: Undecided Assignee: Niall Bunting (niall-bunting) Status: New ** Changed in: nova Assignee: (unassigned) => Niall Bunting (niall-bunting) -- 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/1515619 Title: Nova uses some deprecated glanceclient exceptions Status in OpenStack Compute (nova): New Bug description: Some of the glanceclient exceptions in Nova are now deprecated and should be updated to the current exceptions. Nova: 12.0.0? To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1515619/+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 1515305] [NEW] Reactivating a admins image returns a 500
Public bug reported:
When trying to reactivate an admins image it gets a 500 returned.
Console:
2015-11-11 15:25:23.210 ERROR glance.common.wsgi
[req-14abeda8-f037-4ca2-bbd7-2b02ec25d5df 84405b7957be46d7bd1b59f77c0fbe60
ee7437c495d9491093d40c73ac54be3f] Caught error: 'ImmutableImageProxy' object
has no attribute 'reactivate'
2015-11-11 15:25:23.210 TRACE glance.common.wsgi Traceback (most recent call
last):
2015-11-11 15:25:23.210 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/wsgi.py", line 886, in __call__
2015-11-11 15:25:23.210 TRACE glance.common.wsgi request, **action_args)
2015-11-11 15:25:23.210 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/wsgi.py", line 915, in dispatch
2015-11-11 15:25:23.210 TRACE glance.common.wsgi return method(*args,
**kwargs)
2015-11-11 15:25:23.210 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/utils.py", line 425, in wrapped
2015-11-11 15:25:23.210 TRACE glance.common.wsgi return func(self, req,
*args, **kwargs)
2015-11-11 15:25:23.210 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/api/v2/image_actions.py", line 65, in reactivate
2015-11-11 15:25:23.210 TRACE glance.common.wsgi image.reactivate()
2015-11-11 15:25:23.210 TRACE glance.common.wsgi AttributeError:
'ImmutableImageProxy' object has no attribute 'reactivate'
How to reproduce:
glance image-reactivate 709d022f-7ff3-438b-b672-cd21a2a7d467
Whats expected:
A forbidden.
** Affects: glance
Importance: Undecided
Assignee: Niall Bunting (niall-bunting)
Status: New
** Changed in: glance
Assignee: (unassigned) => Niall Bunting (niall-bunting)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1515305
Title:
Reactivating a admins image returns a 500
Status in Glance:
New
Bug description:
When trying to reactivate an admins image it gets a 500 returned.
Console:
2015-11-11 15:25:23.210 ERROR glance.common.wsgi
[req-14abeda8-f037-4ca2-bbd7-2b02ec25d5df 84405b7957be46d7bd1b59f77c0fbe60
ee7437c495d9491093d40c73ac54be3f] Caught error: 'ImmutableImageProxy' object
has no attribute 'reactivate'
2015-11-11 15:25:23.210 TRACE glance.common.wsgi Traceback (most recent call
last):
2015-11-11 15:25:23.210 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/wsgi.py", line 886, in __call__
2015-11-11 15:25:23.210 TRACE glance.common.wsgi request, **action_args)
2015-11-11 15:25:23.210 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/wsgi.py", line 915, in dispatch
2015-11-11 15:25:23.210 TRACE glance.common.wsgi return method(*args,
**kwargs)
2015-11-11 15:25:23.210 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/common/utils.py", line 425, in wrapped
2015-11-11 15:25:23.210 TRACE glance.common.wsgi return func(self, req,
*args, **kwargs)
2015-11-11 15:25:23.210 TRACE glance.common.wsgi File
"/opt/stack/glance/glance/api/v2/image_actions.py", line 65, in reactivate
2015-11-11 15:25:23.210 TRACE glance.common.wsgi image.reactivate()
2015-11-11 15:25:23.210 TRACE glance.common.wsgi AttributeError:
'ImmutableImageProxy' object has no attribute 'reactivate'
How to reproduce:
glance image-reactivate 709d022f-7ff3-438b-b672-cd21a2a7d467
Whats expected:
A forbidden.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1515305/+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 1512239] Re: Typo in doc about "git co {branch_name}"
Are you sure this is in the right place?
** 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/1512239
Title:
Typo in doc about "git co {branch_name}"
Status in Glance:
Invalid
Bug description:
Typo in doc about "git co {branch_name}" in
http://docs.openstack.org/infra/publications/ci-automation/#%2814%29
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1512239/+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 1511025] [NEW] Image download with multi tenant true fails
Public bug reported: Overview: Trying to download an image while using multi tenant fails. How to reproduce: In the glance-api.conf set swift_store_multi_tenant = True. Then upload an image glance --os-image-api-version 1 image-create --name test --copy-from http://127.0.0.1:5321 --container-format bare --disk-format raw Download image glance image-download 965afb71-61f7-4834-b62b-6fc6e3a1d381 --file /tmp/file Output: 'NoneType' object has no attribute 'close' The server: http://paste.openstack.org/show/477571/ Expected: Image to be downloaded. ** 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/1511025 Title: Image download with multi tenant true fails Status in Glance: New Bug description: Overview: Trying to download an image while using multi tenant fails. How to reproduce: In the glance-api.conf set swift_store_multi_tenant = True. Then upload an image glance --os-image-api-version 1 image-create --name test --copy-from http://127.0.0.1:5321 --container-format bare --disk-format raw Download image glance image-download 965afb71-61f7-4834-b62b-6fc6e3a1d381 --file /tmp/file Output: 'NoneType' object has no attribute 'close' The server: http://paste.openstack.org/show/477571/ Expected: Image to be downloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1511025/+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 1507610] Re: Keystone v3 incompatable with keystone v2
** 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/1507610
Title:
Keystone v3 incompatable with keystone v2
Status in glance_store:
New
Bug description:
Overview:
After an upgrade to using keystone v3 the old style of location ceases to
work. This happens because it raises a 404 which in turn raises a 401. As it
tries to go to the location /v2.0/auth/tokens which did not exist in v2, but
rather the link is /v2.0/tokens.
How to reproduce:
Create an image with the 'old style' location. Something like this:
| locations| [{"url": "swift+http://service%3Aglance-
|
| |
swift:redacted@10.0.0.8:5000/v2.0/glance/2f174860-efe3-4d5a-8f73-83e7298523b8",
|
| | "metadata": {}}]
Then upgrade to keystone v3. And try to run a copy-from or image-download.
Such as:
glance image-download 2f174860-efe3-4d5a-8f73-83e7298523b8 --file /opt/out
Output:
Keystone v3:
sudo ngrep -W byline port 5000 -d lo
interface: lo (127.0.0.0/255.0.0.0)
filter: (ip or ip6) and ( port 5000 )
T 10.0.0.8:45256 -> 10.0.0.8:5000 [AP]
POST /v2.0/auth/tokens HTTP/1.1.
Host: 10.0.0.8:5000.
Content-Length: 222.
Accept-Encoding: gzip, deflate.
Accept: application/json.
User-Agent: python-keystoneclient.
Connection: keep-alive.
Content-Type: application/json.
.
{"auth": {"scope": {"project": {"domain": {"id": "default"}, "name":
"service"}}, "identity": {"password": {"user": {"domain": {"id": "default"},
"password": "redacted", "name": "glance-swift"}}, "methods": ["password"]}}}
##
T 10.0.0.8:5000 -> 10.0.0.8:45256 [AP]
HTTP/1.1 404 Not Found.
Date: Mon, 19 Oct 2015 13:54:27 GMT.
Server: Apache/2.4.7 (Ubuntu).
Vary: X-Auth-Token.
x-openstack-request-id: req-c8c78196-1b77-4b4f-b0dc-8baa5144c30f.
Content-Length: 93.
Keep-Alive: timeout=5, max=100.
Connection: Keep-Alive.
Content-Type: application/json.
.
{"error": {"message": "The resource could not be found.", "code": 404,
"title": "Not Found"}}
V2:
sudo ngrep -W byline port 5000 -d lo
interface: lo (127.0.0.0/255.0.0.0)
filter: (ip or ip6) and ( port 5000 )
T 10.0.0.8:45247 -> 10.0.0.8:5000 [AP]
POST /v2.0/tokens HTTP/1.1.
Host: 10.0.0.8:5000.
Content-Length: 112.
Accept-Encoding: gzip, deflate.
Accept: application/json.
User-Agent: python-keystoneclient.
Connection: keep-alive.
Content-Type: application/json.
.
{"auth": {"tenantName": "service", "passwordCredentials": {"username":
"glance-swift", "password": "redacted"}}}
##
T 10.0.0.8:5000 -> 10.0.0.8:45247 [AP]
HTTP/1.1 200 OK.
Date: Mon, 19 Oct 2015 13:53:42 GMT.
Server: Apache/2.4.7 (Ubuntu).
Vary: X-Auth-Token.
x-openstack-request-id: req-cb538a90-5134-476d-b789-27fcf0576ad8.
Content-Length: 3407.
Keep-Alive: timeout=5, max=100.
Connection: Keep-Alive.
Content-Type: application/json.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance-store/+bug/1507610/+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 1507610] [NEW] Keystone v3 incompatable with keystone v2
Public bug reported:
Overview:
After an upgrade to using keystone v3 the old style of location ceases to work.
This happens because it raises a 404 which in turn raises a 401. As it tries to
go to the location /v2.0/auth/tokens which did not exist in v2, but rather the
link is /v2.0/tokens.
How to reproduce:
Create an image with the 'old style' location. Something like this:
| locations| [{"url": "swift+http://service%3Aglance-
|
| |
swift:redacted@10.0.0.8:5000/v2.0/glance/2f174860-efe3-4d5a-8f73-83e7298523b8",
|
| | "metadata": {}}]
Then upgrade to keystone v3. And try to run a copy-from or image-download. Such
as:
glance image-download 2f174860-efe3-4d5a-8f73-83e7298523b8 --file /opt/out
Output:
Keystone v3:
sudo ngrep -W byline port 5000 -d lo
interface: lo (127.0.0.0/255.0.0.0)
filter: (ip or ip6) and ( port 5000 )
T 10.0.0.8:45256 -> 10.0.0.8:5000 [AP]
POST /v2.0/auth/tokens HTTP/1.1.
Host: 10.0.0.8:5000.
Content-Length: 222.
Accept-Encoding: gzip, deflate.
Accept: application/json.
User-Agent: python-keystoneclient.
Connection: keep-alive.
Content-Type: application/json.
.
{"auth": {"scope": {"project": {"domain": {"id": "default"}, "name":
"service"}}, "identity": {"password": {"user": {"domain": {"id": "default"},
"password": "redacted", "name": "glance-swift"}}, "methods": ["password"]}}}
##
T 10.0.0.8:5000 -> 10.0.0.8:45256 [AP]
HTTP/1.1 404 Not Found.
Date: Mon, 19 Oct 2015 13:54:27 GMT.
Server: Apache/2.4.7 (Ubuntu).
Vary: X-Auth-Token.
x-openstack-request-id: req-c8c78196-1b77-4b4f-b0dc-8baa5144c30f.
Content-Length: 93.
Keep-Alive: timeout=5, max=100.
Connection: Keep-Alive.
Content-Type: application/json.
.
{"error": {"message": "The resource could not be found.", "code": 404, "title":
"Not Found"}}
V2:
sudo ngrep -W byline port 5000 -d lo
interface: lo (127.0.0.0/255.0.0.0)
filter: (ip or ip6) and ( port 5000 )
T 10.0.0.8:45247 -> 10.0.0.8:5000 [AP]
POST /v2.0/tokens HTTP/1.1.
Host: 10.0.0.8:5000.
Content-Length: 112.
Accept-Encoding: gzip, deflate.
Accept: application/json.
User-Agent: python-keystoneclient.
Connection: keep-alive.
Content-Type: application/json.
.
{"auth": {"tenantName": "service", "passwordCredentials": {"username":
"glance-swift", "password": "redacted"}}}
##
T 10.0.0.8:5000 -> 10.0.0.8:45247 [AP]
HTTP/1.1 200 OK.
Date: Mon, 19 Oct 2015 13:53:42 GMT.
Server: Apache/2.4.7 (Ubuntu).
Vary: X-Auth-Token.
x-openstack-request-id: req-cb538a90-5134-476d-b789-27fcf0576ad8.
Content-Length: 3407.
Keep-Alive: timeout=5, max=100.
Connection: Keep-Alive.
Content-Type: application/json.
** Affects: glance
Importance: Undecided
Assignee: Niall Bunting (niall-bunting)
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/1507610
Title:
Keystone v3 incompatable with keystone v2
Status in Glance:
New
Bug description:
Overview:
After an upgrade to using keystone v3 the old style of location ceases to
work. This happens because it raises a 404 which in turn raises a 401. As it
tries to go to the location /v2.0/auth/tokens which did not exist in v2, but
rather the link is /v2.0/tokens.
How to reproduce:
Create an image with the 'old style' location. Something like this:
| locations| [{"url": "swift+http://service%3Aglance-
|
| |
swift:redacted@10.0.0.8:5000/v2.0/glance/2f174860-efe3-4d5a-8f73-83e7298523b8",
|
| | "metadata": {}}]
Then upgrade to keystone v3. And try to run a copy-from or image-download.
Such as:
glance image-download 2f174860-efe3-4d5a-8f73-83e7298523b8 --file /opt/out
Output:
Keystone v3:
sudo ngrep -W byline port 5000 -d lo
interface: lo (127.0.0.0/255.0.0.0)
filter: (ip or ip6) and ( port 5000 )
T 10.0.0.8:45256 -> 10.0.0.8:5000 [AP]
POST /v2.0/auth/tokens HTTP/1.1.
Host: 10.0.0.8:5000.
Content-Length: 222.
Accept-Encoding: gzip, deflate.
Accept: application/json.
User-Agent: python-keystoneclient.
Connection: keep-alive.
Content-Type: application/json.
.
{"auth": {"scope": {"project": {"domain": {"id": "default"}, "name":
"service"}}, "identity": {"password": {"user": {"domain": {"id": "default"},
[Yahoo-eng-team] [Bug 1502850] [NEW] Location add does not catch BadStoreUri
Public bug reported: Overview: If you create an image and then use location-add to add a bad uri, the server returns a 500. As the BadStoreUri is not caught. How to produce: glance image-create glance location-add de6d8022-6954-4039-b53a-042e2fc909de --url file:// 500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500) 2015-10-05 10:31:54.015 TRACE glance.common.wsgi raise exceptions.BadStoreUri(uri=uri) 2015-10-05 10:31:54.015 TRACE glance.common.wsgi BadStoreUri: The Store URI was malformed: http:// Output: 500 Expected: 400 ** Affects: glance Importance: Undecided Assignee: Niall Bunting (niall-bunting) Status: New ** Changed in: glance Assignee: (unassigned) => Niall Bunting (niall-bunting) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1502850 Title: Location add does not catch BadStoreUri Status in Glance: New Bug description: Overview: If you create an image and then use location-add to add a bad uri, the server returns a 500. As the BadStoreUri is not caught. How to produce: glance image-create glance location-add de6d8022-6954-4039-b53a-042e2fc909de --url file:// 500 Internal Server Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500) 2015-10-05 10:31:54.015 TRACE glance.common.wsgi raise exceptions.BadStoreUri(uri=uri) 2015-10-05 10:31:54.015 TRACE glance.common.wsgi BadStoreUri: The Store URI was malformed: http:// Output: 500 Expected: 400 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1502850/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1499368] [NEW] Image Create does not allow admins to set owner
Public bug reported: If you try to create an image a image with the owner property currently you are restricted as you get the following error: 403 Forbidden: Attribute 'owner' is reserved. (HTTP 403) What is expected: For non-admin: 403 For admin: 200 This allows admins to create images with different owners. ** Affects: glance Importance: Undecided Assignee: Niall Bunting (niall-bunting) Status: In Progress ** Changed in: glance Assignee: (unassigned) => Niall Bunting (niall-bunting) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1499368 Title: Image Create does not allow admins to set owner Status in Glance: In Progress Bug description: If you try to create an image a image with the owner property currently you are restricted as you get the following error: 403 Forbidden: Attribute 'owner' is reserved. (HTTP 403) What is expected: For non-admin: 403 For admin: 200 This allows admins to create images with different owners. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1499368/+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 1499367] [NEW] Image Create does not allow admins to set owner
Public bug reported: If you try to create an image a image with the owner property currently you are restricted as you get the following error: 403 Forbidden: Attribute 'owner' is reserved. (HTTP 403) What is expected: For non-admin: 403 For admin: 200 This allows admins to create images with diffrent owners. ** 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/1499367 Title: Image Create does not allow admins to set owner Status in Glance: New Bug description: If you try to create an image a image with the owner property currently you are restricted as you get the following error: 403 Forbidden: Attribute 'owner' is reserved. (HTTP 403) What is expected: For non-admin: 403 For admin: 200 This allows admins to create images with diffrent owners. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1499367/+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 1490979] Re: Glance returned 404 status code when we specify bad headers or we do not specify headers when updated artifact
You need to add -X in front of POST as curl thinks that POST is the host
name.
curl -H "X-Auth-Token: 3b4e028c1e6f457595497afc1df37ffb" -X POST -d
'{"data":"la-la"}'
http://172.18.76.44:9292/v3/artifacts/myartifact/v2.0/91671992-c84e-4723-9024-3c9b6dddf079/description
-i
** 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/1490979
Title:
Glance returned 404 status code when we specify bad headers or we do
not specify headers when updated artifact
Status in Glance:
Invalid
Bug description:
ENVIRONMENT: devstack, Glance (master, 31.08.2015)
STEPS TO REPRODUCE:
We are trying to upgrade artifact
1) curl -H "X-Auth-Token: 3b4e028c1e6f457595497afc1df37ffb" -H "ddd"
POST -d '{"data":"la-la"}'
http://172.18.76.44:9292/v3/artifacts/myartifact/v2.0/91671992-c84e-4723-9024-3c9b6dddf079/description
-i
2)curl -H "X-Auth-Token: 3b4e028c1e6f457595497afc1df37ffb" POST -d
'{"data":"la-la"}'
http://172.18.76.44:9292/v3/artifacts/myartifact/v2.0/91671992-c84e-4723-9024-3c9b6dddf079/description
-i
EXPECTED RESULT:
status code 400 and message error
ACTUAL RESULT:
curl: (6) Could not resolve host: POST
HTTP/1.1 404 Not Found
Content-Length: 154
Content-Type: text/html; charset=UTF-8
X-Openstack-Request-Id: req-40cae297-ccbe-4507-945f-e6ebfd29ab23
Date: Tue, 01 Sep 2015 13:08:38 GMT
404 Not Found
404 Not Found
The resource could not be found.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1490979/+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 1488174] [NEW] A tag with a long length will return a 500
Public bug reported:
Overview:
The tag length is not checked, it tries to insert the tag into the database and
can't. This then causes a database exception.
How to produce:
curl -v -X PUT
http://10.0.0.8:9292/v2/images/4e1cd2f0-8704-4e19-953f-62ff14d1b22a/tags/0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789
-H "X-Auth-Token: eb51438851c64ffab72163092924e1cf"
> PUT
> /v2/images/4e1cd2f0-8704-4e19-953f-62ff14d1b22a/tags/0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789
> HTTP/1.1
> User-Agent: curl/7.35.0
> Host: 10.0.0.8:9292
> Accept: */*
> X-Auth-Token: eb51438851c64ffab72163092924e1cf
>
Actual result:
< HTTP/1.1 500 Internal Server Error
< Content-Length: 228
< Content-Type: text/html; charset=UTF-8
< X-Openstack-Request-Id: req-8df454b9-32e4-4356-a23c-5de4a60b49fa
< Date: Mon, 24 Aug 2015 16:41:42 GMT
<
500 Internal Server Error
500 Internal Server Error
The server has either erred or is incapable of performing the requested
operation.
Expected:
400
** Affects: glance
Importance: Undecided
Assignee: Niall Bunting (niall-bunting)
Status: New
** Changed in: glance
Assignee: (unassigned) => Niall Bunting (niall-bunting)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1488174
Title:
A tag with a long length will return a 500
Status in Glance:
New
Bug description:
Overview:
The tag length is not checked, it tries to insert the tag into the database
and can't. This then causes a database exception.
How to produce:
curl -v -X PUT
http://10.0.0.8:9292/v2/images/4e1cd2f0-8704-4e19-953f-62ff14d1b22a/tags/0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789
-H "X-Auth-Token: eb51438851c64ffab72163092924e1cf"
> PUT
/v2/images/4e1cd2f0-8704-4e19-953f-62ff14d1b22a/tags/0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789
HTTP/1.1
> User-Agent: curl/7.35.0
> Host: 10.0.0.8:9292
> Accept: */*
> X-Auth-Token: eb51438851c64ffab72163092924e1cf
>
Actual result:
< HTTP/1.1 500 Internal Server Error
< Content-Length: 228
< Content-Type: text/html; charset=UTF-8
< X-Openstack-Request-Id: req-8df454b9-32e4-4356-a23c-5de4a60b49fa
< Date: Mon, 24 Aug 2015 16:41:42 GMT
<
500 Internal Server Error
500 Internal Server Error
The server has either erred or is incapable of performing the requested
operation.
Expected:
400
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1488174/+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 1487026] [NEW] When tasks fail importing with an error
Public bug reported: If tasks fail importing an image for whatever reason, such as a 404. It leaves the task in a 500 internal error state and the image in a saving state. This should be changed so the image is killed and a reasonable message is replied to the task failure screen. ** Affects: glance Importance: Undecided Assignee: Niall Bunting (niall-bunting) Status: New ** Changed in: glance Assignee: (unassigned) => Niall Bunting (niall-bunting) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1487026 Title: When tasks fail importing with an error Status in Glance: New Bug description: If tasks fail importing an image for whatever reason, such as a 404. It leaves the task in a 500 internal error state and the image in a saving state. This should be changed so the image is killed and a reasonable message is replied to the task failure screen. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1487026/+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 1481741] Re: sql file should NOT be ignored by .gitignore
** 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/1481741 Title: sql file should NOT be ignored by .gitignore Status in Glance: Invalid Bug description: in .gitignore file , the rules defined as below # Swap files range from .saa to .swp *.s[a-w][a-p] which will cause the *.sql file for db migration ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1481741/+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 1483688] [NEW] v1: correct x-image-meta-id header provokes E500
Public bug reported: This bug addresses the problem where the id is correct. $ 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 ** Affects: glance Importance: Undecided Status: New ** Description changed: This bug addresses the problem where the id is correct. $ 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 -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1483688 Title: v1: correct x-image-meta-id header provokes E500 Status in Glance: New Bug description: This bug addresses the problem where the id is correct. $ 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/1483688/+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 1480400] Re: Documentation error for properties
** Also affects: openstack-api-site
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/1480400
Title:
Documentation error for properties
Status in Glance:
New
Status in openstack-api-site:
New
Bug description:
Document: http://developer.openstack.org/api-ref-image-v2.html
Under the image create drop down there is the following line:
properties (Optional) plain | xsd:dict | Properties, if any, that are
associated with the image.
This suggests that the properties are a dict and would look like this:
-d '{"name": "thename", "properties": {"myprop", "mydata"}}'
this is not the case, as if you want
to define custom properties in a curl command you do it by defining it like
any other property eg.
-d '{"name": "thename", "myprop": "mydata"}'
The documentation is not clear about this distinction.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1480400/+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 1480400] [NEW] Documentation error for properties
Public bug reported:
Document: http://developer.openstack.org/api-ref-image-v2.html
Under the image create drop down there is the following line:
properties (Optional) plain | xsd:dict | Properties, if any, that are
associated with the image.
This suggests that the properties are a dict and would look like this:
-d '{"name": "thename", "properties": {"myprop", "mydata"}}'
this is not the case, as if you want
to define custom properties in a curl command you do it by defining it like any
other property eg.
-d '{"name": "thename", "myprop": "mydata"}'
The documentation is not clear about this distinction.
** Affects: glance
Importance: Undecided
Status: New
** Tags: documentation
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1480400
Title:
Documentation error for properties
Status in Glance:
New
Bug description:
Document: http://developer.openstack.org/api-ref-image-v2.html
Under the image create drop down there is the following line:
properties (Optional) plain | xsd:dict | Properties, if any, that are
associated with the image.
This suggests that the properties are a dict and would look like this:
-d '{"name": "thename", "properties": {"myprop", "mydata"}}'
this is not the case, as if you want
to define custom properties in a curl command you do it by defining it like
any other property eg.
-d '{"name": "thename", "myprop": "mydata"}'
The documentation is not clear about this distinction.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1480400/+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 1476695] [NEW] Invalid body in image creation causes 500
Public bug reported:
Overview:
When creating an image the user either puts a number as the body or sends some
type of string will cause the server to fall over due to a type error.
How to produce:
curl -X POST http://your-ip:9292/v2/images/ -H "X-Auth-Token: your-auth-token"
-d 123
Rather than a number lots of inputs can cause the type error to be
thrown such as '[]' or '["some text"]'.
Actual:
500
Expected:
400 with body invalid message.
** Affects: glance
Importance: Undecided
Assignee: Niall Bunting (niall-bunting)
Status: New
** Changed in: glance
Assignee: (unassigned) => Niall Bunting (niall-bunting)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1476695
Title:
Invalid body in image creation causes 500
Status in Glance:
New
Bug description:
Overview:
When creating an image the user either puts a number as the body or sends
some type of string will cause the server to fall over due to a type error.
How to produce:
curl -X POST http://your-ip:9292/v2/images/ -H "X-Auth-Token:
your-auth-token" -d 123
Rather than a number lots of inputs can cause the type error to be
thrown such as '[]' or '["some text"]'.
Actual:
500
Expected:
400 with body invalid message.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1476695/+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 1476253] [NEW] Create a member with unexpected body returns 500
Public bug reported:
Overview:
If when creating a member the user either puts a number as the body or sends
some type of string will cause the server to fall over due to a type error.
How to produce:
curl -X POST http://your-ip:9292/v2/images/your-image-id/members -H
"X-Auth-Token: your-auth-token" -d 123
Rather than a number lots of inputs can cause the type error to be
thrown such as '[]' or '["some text"]'.
Actual:
500
Expected:
400 with body invalid message.
** Affects: glance
Importance: Undecided
Assignee: Niall Bunting (niall-bunting)
Status: New
** Changed in: glance
Assignee: (unassigned) => Niall Bunting (niall-bunting)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1476253
Title:
Create a member with unexpected body returns 500
Status in Glance:
New
Bug description:
Overview:
If when creating a member the user either puts a number as the body or sends
some type of string will cause the server to fall over due to a type error.
How to produce:
curl -X POST http://your-ip:9292/v2/images/your-image-id/members -H
"X-Auth-Token: your-auth-token" -d 123
Rather than a number lots of inputs can cause the type error to be
thrown such as '[]' or '["some text"]'.
Actual:
500
Expected:
400 with body invalid message.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1476253/+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 1475647] [NEW] Get image API returns 500 if a body is included
Public bug reported: Overview: If a user attaches a body to a http get to get the image data a 500 response is returned as the API did not expect a body. Steps to reproduce: (1) The curl command, which includes a body: curl -v -X GET http://16.49.137.85:9292/v2/images/5619cf1f-5c43-4a1d-a90b-aa7354e453e7 -H "X-Auth-Token: 3ee83196ecbb4a559b945ac849c1520e" -d '[]' (2) Sends the following: GET http://16.49.137.85:9292/v2/images/5619cf1f-5c43-4a1d-a90b-aa7354e453e7 HTTP/1.1. User-Agent: curl/7.35.0. Host: 16.49.137.85:9292. Accept: */*. Proxy-Connection: Keep-Alive. X-Auth-Token: 3ee83196ecbb4a559b945ac849c1520e. Content-Length: 2. Content-Type: application/x-www-form-urlencoded. . [] Actual: The response in a 500 error. Expected: It may be nice if it caught the fact that a body was not expected and returned a error early, to stop the whole body being uploaded. I would like some input into what people think the expected behavior should be? ** Affects: glance Importance: Undecided Assignee: Niall Bunting (niall-bunting) Status: New ** Changed in: glance Assignee: (unassigned) => Niall Bunting (niall-bunting) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1475647 Title: Get image API returns 500 if a body is included Status in Glance: New Bug description: Overview: If a user attaches a body to a http get to get the image data a 500 response is returned as the API did not expect a body. Steps to reproduce: (1) The curl command, which includes a body: curl -v -X GET http://16.49.137.85:9292/v2/images/5619cf1f-5c43-4a1d-a90b-aa7354e453e7 -H "X-Auth-Token: 3ee83196ecbb4a559b945ac849c1520e" -d '[]' (2) Sends the following: GET http://16.49.137.85:9292/v2/images/5619cf1f-5c43-4a1d-a90b-aa7354e453e7 HTTP/1.1. User-Agent: curl/7.35.0. Host: 16.49.137.85:9292. Accept: */*. Proxy-Connection: Keep-Alive. X-Auth-Token: 3ee83196ecbb4a559b945ac849c1520e. Content-Length: 2. Content-Type: application/x-www-form-urlencoded. . [] Actual: The response in a 500 error. Expected: It may be nice if it caught the fact that a body was not expected and returned a error early, to stop the whole body being uploaded. I would like some input into what people think the expected behavior should be? To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1475647/+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
