[Yahoo-eng-team] [Bug 1810393] [NEW] shadow user cache is not cleaned when the related idp is deleted.
ttp://38.108.68.96/identity/v3/OS-FEDERATION/identity_providers/samltest/protocols/mapped
0.050s
2019-01-03 02:34:46,210 4283 DEBUG[tempest.lib.common.rest_client] Request
- Headers: {'Accept': 'application/json', 'X-Auth-Token': '',
'Content-Type': 'application/json'}
Body: None
Response - Headers: {'content-location':
'http://38.108.68.96/identity/v3/OS-FEDERATION/identity_providers/samltest/protocols/mapped',
u'x-openstack-request-id': 'req-10dee6dc-dec0-4383-8aea-bbf097c5279b',
u'date': 'Thu, 03 Jan 2019 02:34:46 GMT', u'connection': 'close', u'server':
'Apache/2.4.18 (Ubuntu)', u'vary': 'X-Auth-Token', 'status': '204'}
Body:
2019-01-03 02:34:46,256 4283 INFO [tempest.lib.common.rest_client] Request
(TestSaml2EcpFederatedAuthentication:_run_cleanups): 204 DELETE
http://38.108.68.96/identity/v3/OS-FEDERATION/mappings/8269b21476554bbdb196d7251d8566b9
0.045s
2019-01-03 02:34:46,257 4283 DEBUG[tempest.lib.common.rest_client] Request
- Headers: {'Accept': 'application/json', 'X-Auth-Token': '',
'Content-Type': 'application/json'}
Body: None
Response - Headers: {'content-location':
'http://38.108.68.96/identity/v3/OS-FEDERATION/mappings/8269b21476554bbdb196d7251d8566b9',
u'x-openstack-request-id': 'req-989f407c-9b99-4a05-a92d-34deb01bedc0',
u'date': 'Thu, 03 Jan 2019 02:34:46 GMT', u'connection': 'close', u'server':
'Apache/2.4.18 (Ubuntu)', u'vary': 'X-Auth-Token', 'status': '204'}
Body:
2019-01-03 02:34:46,306 4283 INFO [tempest.lib.common.rest_client] Request
(TestSaml2EcpFederatedAuthentication:_run_cleanups): 204 DELETE
http://38.108.68.96/identity/v3/OS-FEDERATION/identity_providers/samltest 0.048s
2019-01-03 02:34:46,306 4283 DEBUG[tempest.lib.common.rest_client] Request
- Headers: {'Accept': 'application/json', 'X-Auth-Token': '',
'Content-Type': 'application/json'}
Body: None
Response - Headers: {'content-location':
'http://38.108.68.96/identity/v3/OS-FEDERATION/identity_providers/samltest',
u'x-openstack-request-id': 'req-06795a5c-eddd-49e5-85c9-7ce85942b12e', u'date':
'Thu, 03 Jan 2019 02:34:46 GMT', u'connection': 'close', u'server':
'Apache/2.4.18 (Ubuntu)', u'vary': 'X-Auth-Token', 'status': '204'}
Body:
2019-01-03 02:34:46,400 4283 INFO [tempest.lib.common.rest_client] Request
(TestSaml2EcpFederatedAuthentication:_run_cleanups): 200 PATCH
http://38.108.68.96/identity/v3/domains/e14d592e135046f180f94931c2f5f339 0.093s
2019-01-03 02:34:46,400 4283 DEBUG[tempest.lib.common.rest_client] Request
- Headers: {'Accept': 'application/json', 'X-Auth-Token': '',
'Content-Type': 'application/json'}
Body: {"domain": {"enabled": false}}
Response - Headers: {u'content-type': 'application/json', u'date': 'Thu, 03
Jan 2019 02:34:46 GMT', u'connection': 'close', u'server': 'Apache/2.4.18
(Ubuntu)', u'x-openstack-request-id':
'req-ebfc5cdc-af5e-45fd-bca3-f500012489a1', u'content-length': '306',
'content-location':
'http://38.108.68.96/identity/v3/domains/e14d592e135046f180f94931c2f5f339',
u'vary': 'X-Auth-Token', 'status': '200'}
Body: {"domain": {"description": "Auto generated federated domain for
Identity Provider: samltest", "links": {"self":
"http://38.108.68.96/identity/v3/domains/e14d592e135046f180f94931c2f5f339"},
"tags": [], "enabled": false, "id": "e14d592e135046f180f94931c2f5f339", "name":
"e14d592e135046f180f94931c2f5f339"}}
2019-01-03 02:34:46,656 4283 INFO [tempest.lib.common.rest_client] Request
(TestSaml2EcpFederatedAuthentication:_run_cleanups): 204 DELETE
http://38.108.68.96/identity/v3/domains/e14d592e135046f180f94931c2f5f339 0.255s
2019-01-03 02:34:46,657 4283 DEBUG[tempest.lib.common.rest_client] Request
- Headers: {'Accept': 'application/json', 'X-Auth-Token': '',
'Content-Type': 'application/json'}
Body: None
Response - Headers: {'content-location':
'http://38.108.68.96/identity/v3/domains/e14d592e135046f180f94931c2f5f339',
u'x-openstack-request-id': 'req-41df84a1-40f5-4105-9034-1ed63d91dc43', u'date':
'Thu, 03 Jan 2019 02:34:46 GMT', u'connection': 'close', u'server':
'Apache/2.4.18 (Ubuntu)', u'vary': 'X-Auth-Token', 'status': '204'}
Body:
}}}
Traceback (most recent call last):
File
"/opt/stack/tempest/.tox/tempest/local/lib/python2.7/site-packages/keystone_tempest_plugin/tests/scenario/test_federated_authentication.py",
line 168, in test_request_unscoped_token
self._request_unscoped_token()
File
"/opt/stack/tempest/.tox/tempest/local/lib/python2.7/site-packages/keystone_tempest_plugin/tests/scenario/test_federated_authentication.py",
line 159, in _request_unscoped_token
self.assertEqual(http_client.CREATED, resp.status_code)
File
"/opt/stack/tempest/.tox/tempest/local/lib/python2.7/site-packages/testtools/testcase.py",
l
[Yahoo-eng-team] [Bug 1801309] [NEW] Support configurable saml assertion property
Public bug reported: Keystone as Identity Provider supports to generator saml assertion for SP. The content in the saml assertion is hard code. The attribute contains: openstack_user,openstack_roles,openstack_project,openstack_project_domain,openstack_user_domain. But in case the SP need more information from IdP Keystone,(or IdP want to provide more information to SP) there is no way to extend the saml information. Such as user's extra info, like email address, the description of a role and so on. Or a case like: IdP Keystone mapping to two SP-SP1 and SP2, SP1 need additional key1:value1, but SP2 need.key2:value2. For those cases, Keystone as IdP should support configurable saml assertion property ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1801309 Title: Support configurable saml assertion property Status in OpenStack Identity (keystone): New Bug description: Keystone as Identity Provider supports to generator saml assertion for SP. The content in the saml assertion is hard code. The attribute contains: openstack_user,openstack_roles,openstack_project,openstack_project_domain,openstack_user_domain. But in case the SP need more information from IdP Keystone,(or IdP want to provide more information to SP) there is no way to extend the saml information. Such as user's extra info, like email address, the description of a role and so on. Or a case like: IdP Keystone mapping to two SP-SP1 and SP2, SP1 need additional key1:value1, but SP2 need.key2:value2. For those cases, Keystone as IdP should support configurable saml assertion property To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1801309/+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 1710329] Re: support for chinese name to show
Can't reproduce on master branch. Feel free to add more information and reopen
the bug.
http://paste.openstack.org/show/733754/
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1710329
Title:
support for chinese name to show
Status in OpenStack Identity (keystone):
Invalid
Status in python-keystoneclient:
Incomplete
Bug description:
I create a project with a chinese name, then get the project with the
name.
openstack --debug project show 中文
REQ: curl -g -i -X GET http://10.43.166.109:35357/v2.0/tenants -H
"User-Agent: python-keystoneclient" -H "Accept: application/json" -H
"X-Auth-Token: {SHA1}fe395e6a71aed0df6b06ef64cde70a93e3338f7b"
"GET /v2.0/tenants HTTP/1.1" 200 584
RESP: [200] Content-Length: 584 Vary: X-Auth-Token Connection: keep-alive
Date: Sat, 23 Jun 2001 02:24:46 GMT Content-Type: application/json
X-Openstack-Request-Id: req-5e4c498e-a474-4fa1-9614-b350d60d036a
/usr/lib/python2.7/site-packages/keystoneclient/base.py:283: UnicodeWarning:
Unicode equal comparison failed to convert both arguments to Unicode -
interpreting them as being unequal
for (attr, value) in searches):
No tenant with a name or ID of '中文' exists.
my env variable is as:
export OS_USERNAME=admin
export OS_PASSWORD=keystone
export OS_AUTH_URL=http://10.43.166.109:5000/v2.0
export OS_TENANT_NAME=admin
export OS_REGION_NAME=RegionOne
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1710329/+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 1799384] [NEW] cache guide is out of date
Public bug reported: The contributor doc for keystone caching layer is totally out of date now[1]. It should be updated to follow current caching usage in Keystone. [1]: http://git.openstack.org/cgit/openstack/keystone/tree/doc/source/contributor /caching-layer.rst ** Affects: keystone Importance: Undecided Status: New ** Tags: documentation ** Tags added: documentation -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1799384 Title: cache guide is out of date Status in OpenStack Identity (keystone): New Bug description: The contributor doc for keystone caching layer is totally out of date now[1]. It should be updated to follow current caching usage in Keystone. [1]: http://git.openstack.org/cgit/openstack/keystone/tree/doc/source/contributor /caching-layer.rst To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1799384/+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 1799153] Re: Inappropriate behaviour of limits when passing --region None in create and list.
https://review.openstack.org/#/c/612283 ** Project changed: keystone => python-openstackclient -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1799153 Title: Inappropriate behaviour of limits when passing --region None in create and list. Status in python-openstackclient: New Bug description: When creating registered limit by passing --region None in registered limit create cli, it is giving error message "More than one resource exist for region" which is definitely a wrong message as regions with same name cannot be created neither same exist. The correct behaviour should be - 1. In the case if --region None it should create a registered limit. 2. "No region exist with name xyz" if passed a invalid 'xyz' region while creating. Same in case of registerd limit list 1. In the case if --region None it should list all limits ignoring None. 2. "No region exist with name xyz" if passed a invalid 'xyz' region while listing. Sane behaviors for limit create and list To manage notifications about this bug go to: https://bugs.launchpad.net/python-openstackclient/+bug/1799153/+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 1798744] Re: Openstack limit list --project giving error
you can add this cli filter support in openstackclient ** Project changed: keystone => python-openstackclient -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1798744 Title: Openstack limit list --project giving error Status in python-openstackclient: New Bug description: when doing openstack limit list --project xyz_id, CLI raising error unrecognized arguments, whereas in api-ref document [1], user can pass project_id as query param. [1] https://developer.openstack.org/api-ref/identity/v3/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/python-openstackclient/+bug/1798744/+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 1798716] [NEW] can't update registered limit's region_id to None
Public bug reported: The region_id for registered limit is optional, we should allow update registered limit's region_id to None. But it's now blocked by input schema check and the 400 BadRequest raises. ** Affects: keystone Importance: Low Assignee: wangxiyuan (wangxiyuan) Status: In Progress ** Changed in: keystone Assignee: (unassigned) => wangxiyuan (wangxiyuan) ** Changed in: keystone Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1798716 Title: can't update registered limit's region_id to None Status in OpenStack Identity (keystone): In Progress Bug description: The region_id for registered limit is optional, we should allow update registered limit's region_id to None. But it's now blocked by input schema check and the 400 BadRequest raises. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1798716/+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 1791579] [NEW] Keystone, the OpenStack Identity Service in keystone
Public bug reported: test for doc tag. This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: __ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2018-09-10 03:19 SHA: ac2b2160d61754547ffa6baea6b3f76a70995499 Source: https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/index.rst URL: http://logs.openstack.org/51/601151/1/check/build-openstack-sphinx-docs/0474220/html/ ** Affects: keystone Importance: Undecided Status: Invalid ** Tags: documentation ** Changed in: keystone Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1791579 Title: Keystone, the OpenStack Identity Service in keystone Status in OpenStack Identity (keystone): Invalid Bug description: test for doc tag. This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: __ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2018-09-10 03:19 SHA: ac2b2160d61754547ffa6baea6b3f76a70995499 Source: https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/index.rst URL: http://logs.openstack.org/51/601151/1/check/build-openstack-sphinx-docs/0474220/html/ To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1791579/+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 1791580] [NEW] Keystone, the OpenStack Identity Service in keystone
Public bug reported: test This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: __ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2018-09-10 02:02 SHA: 08390d4befd01919f24f8eaae6bf9ddde5424da3 Source: https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/index.rst URL: https://docs.openstack.org/keystone/latest/ ** Affects: keystone Importance: Undecided Status: Invalid ** Tags: doc ** Changed in: keystone Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1791580 Title: Keystone, the OpenStack Identity Service in keystone Status in OpenStack Identity (keystone): Invalid Bug description: test This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: __ - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: on 2018-09-10 02:02 SHA: 08390d4befd01919f24f8eaae6bf9ddde5424da3 Source: https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/index.rst URL: https://docs.openstack.org/keystone/latest/ To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1791580/+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 1787874] [NEW] There is no way to forbid users changing password to itself
Public bug reported:
When users changing their password, we hope that they should use a new
password instead. But actually now even users provide the same password
as it is, the request will still be success.
There is an option "unique_last_password_count" that can limit users
password. But the value is 2 at least. It means that it can only forbid
users changing password like: pw1 -> pw2 -> pw1. But the case pw1 -> pw1
is not covered.
There are two way to solve the problem IMO:
1. forbid users changing password like pw1 -> pw1 by default in Keystone.
2. Or make "unique_last_password_count"'s minimum to 0. Set to 1 means users
can't change password like pw1 -> pw1
The first Option may be better, since in actual use case, changing pw1
to pw1 is stupid and useless. What's more, the ClI has already forbade
this action.
** Affects: keystone
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: keystone
Assignee: (unassigned) => wangxiyuan (wangxiyuan)
** Description changed:
When users changing their password, we hope that they should use a new
password instead. But actually now even users provide the same password
as it is, the request will still be success.
- There is a option "unique_last_password_count" that can limit users
+ There is an option "unique_last_password_count" that can limit users
password. But the value is 2 at least. It means that it can only forbid
users changing password like: pw1 -> pw2 -> pw1. But the case pw1 -> pw1
is not covered.
There are two way to solve the problem IMO:
1. forbid users changing password like pw1 -> pw1 by default in Keystone.
2. Or make "unique_last_password_count"'s minimum to 0. Set to 1 means users
can't change password like pw1 -> pw1
The first Option may be better, since in actual use case, changing pw1
to pw1 is stupid and useless. What's more, the ClI has already forbade
this action.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1787874
Title:
There is no way to forbid users changing password to itself
Status in OpenStack Identity (keystone):
New
Bug description:
When users changing their password, we hope that they should use a new
password instead. But actually now even users provide the same
password as it is, the request will still be success.
There is an option "unique_last_password_count" that can limit users
password. But the value is 2 at least. It means that it can only
forbid users changing password like: pw1 -> pw2 -> pw1. But the case
pw1 -> pw1 is not covered.
There are two way to solve the problem IMO:
1. forbid users changing password like pw1 -> pw1 by default in Keystone.
2. Or make "unique_last_password_count"'s minimum to 0. Set to 1 means users
can't change password like pw1 -> pw1
The first Option may be better, since in actual use case, changing pw1
to pw1 is stupid and useless. What's more, the ClI has already forbade
this action.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1787874/+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 1783049] [NEW] image-upload will log unexpected info if using "glance.db.registry.api"
Public bug reported: Env: - Glance master branch - keystoneauth>=3.7.0 - set "data_api" to "glance.db.registry.api" in config file. Reproduce: 1. create a queue image 2. upload data to this image. The log: Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token. ** Affects: glance Importance: Undecided Status: New ** Summary changed: - image-upload will fail if use "glance.db.registry.api" + image-upload will log unexpected info if using "glance.db.registry.api" -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1783049 Title: image-upload will log unexpected info if using "glance.db.registry.api" Status in Glance: New Bug description: Env: - Glance master branch - keystoneauth>=3.7.0 - set "data_api" to "glance.db.registry.api" in config file. Reproduce: 1. create a queue image 2. upload data to this image. The log: Unable to create trust: no such option collect_timing in group [keystone_authtoken] Use the existing user token. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1783049/+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 1779903] [NEW] the project limits should be cleaned up when the related project is deleted
Public bug reported: when a project is deleted, its limits should be purged as well. ** Affects: keystone Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: keystone Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1779903 Title: the project limits should be cleaned up when the related project is deleted Status in OpenStack Identity (keystone): New Bug description: when a project is deleted, its limits should be purged as well. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1779903/+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 1776219] [NEW] document should be updated for Flask
Public bug reported: Now Keystone use Flask for WSGI and the usage for paste.deploy is removed. The document should be updated as well. ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1776219 Title: document should be updated for Flask Status in OpenStack Identity (keystone): New Bug description: Now Keystone use Flask for WSGI and the usage for paste.deploy is removed. The document should be updated as well. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1776219/+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 1775140] Re: Keystoneauth does not consistently add the collect-timing parameter
** Changed in: keystone
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1775140
Title:
Keystoneauth does not consistently add the collect-timing parameter
Status in OpenStack Identity (keystone):
Invalid
Status in Mistral:
Confirmed
Bug description:
Mistral devstack tests started to fail due to the following error [1]
2018-06-04 19:23:37.223185 Server-side error: "no such option collect_timing
in group [keystone_authtoken]". Detail:
2018-06-04 19:23:37.223221 Traceback (most recent call last):
2018-06-04 19:23:37.223226
2018-06-04 19:23:37.223231 File
"/usr/local/lib/python2.7/dist-packages/wsmeext/pecan.py", line 85, in
callfunction
2018-06-04 19:23:37.223235 result = f(self, *args, **kwargs)
2018-06-04 19:23:37.223239
2018-06-04 19:23:37.223243 File
"/opt/stack/mistral/mistral/api/controllers/v2/event_trigger.py", line 81, in
post
2018-06-04 19:23:37.223247 workflow_params=values.get('workflow_params'),
2018-06-04 19:23:37.223251
2018-06-04 19:23:37.223255 File "/opt/stack/mistral/mistral/db/utils.py",
line 88, in decorate
2018-06-04 19:23:37.223259 return retry.call(_with_auth_context,
auth_ctx, func, *args, **kw)
2018-06-04 19:23:37.223263
2018-06-04 19:23:37.223267 File
"/opt/stack/mistral/mistral/utils/rest_utils.py", line 247, in call
2018-06-04 19:23:37.223271 return super(MistralRetrying, self).call(fn,
*args, **kwargs)
2018-06-04 19:23:37.223275
2018-06-04 19:23:37.223279 File
"/usr/local/lib/python2.7/dist-packages/tenacity/__init__.py", line 330, in call
2018-06-04 19:23:37.223283 start_time=start_time)
2018-06-04 19:23:37.223287
2018-06-04 19:23:37.223291 File
"/usr/local/lib/python2.7/dist-packages/tenacity/__init__.py", line 279, in iter
2018-06-04 19:23:37.223295 return fut.result()
2018-06-04 19:23:37.223299
2018-06-04 19:23:37.223303 File
"/usr/local/lib/python2.7/dist-packages/concurrent/futures/_base.py", line 455,
in result
2018-06-04 19:23:37.223307 return self.__get_result()
2018-06-04 19:23:37.223311
2018-06-04 19:23:37.223315 File
"/usr/local/lib/python2.7/dist-packages/tenacity/__init__.py", line 333, in call
2018-06-04 19:23:37.223319 result = fn(*args, **kwargs)
2018-06-04 19:23:37.223322
2018-06-04 19:23:37.223326 File "/opt/stack/mistral/mistral/db/utils.py",
line 45, in _with_auth_context
2018-06-04 19:23:37.223330 return func(*args, **kw)
2018-06-04 19:23:37.223334
2018-06-04 19:23:37.223338 File
"/opt/stack/mistral/mistral/services/triggers.py", line 186, in
create_event_trigger
2018-06-04 19:23:37.223342 security.add_trust_id(values)
2018-06-04 19:23:37.223355
2018-06-04 19:23:37.223360 File
"/opt/stack/mistral/mistral/services/security.py", line 110, in add_trust_id
2018-06-04 19:23:37.223364 trust = create_trust()
2018-06-04 19:23:37.223368
2018-06-04 19:23:37.223372 File
"/opt/stack/mistral/mistral/services/security.py", line 45, in create_trust
2018-06-04 19:23:37.223376 trustee_id =
keystone.client_for_admin().session.get_user_id()
2018-06-04 19:23:37.223380
2018-06-04 19:23:37.223384 File
"/opt/stack/mistral/mistral/utils/openstack/keystone.py", line 143, in
client_for_admin
2018-06-04 19:23:37.223388 return _admin_client()
2018-06-04 19:23:37.223392
2018-06-04 19:23:37.223396 File
"/opt/stack/mistral/mistral/utils/openstack/keystone.py", line 136, in
_admin_client
2018-06-04 19:23:37.223400 auth=auth
2018-06-04 19:23:37.223403
2018-06-04 19:23:37.223408 File
"/usr/local/lib/python2.7/dist-packages/keystoneauth1/loading/session.py", line
270, in load_from_conf_options
2018-06-04 19:23:37.223412 return Session().load_from_conf_options(*args,
**kwargs)
2018-06-04 19:23:37.223416
2018-06-04 19:23:37.223420 File
"/usr/local/lib/python2.7/dist-packages/keystoneauth1/loading/session.py", line
251, in load_from_conf_options
2018-06-04 19:23:37.223424 kwargs.setdefault('collect_timing',
c.collect_timing)
2018-06-04 19:23:37.223428
2018-06-04 19:23:37.223432 File
"/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py", line 3409, in
__getattr__
2018-06-04 19:23:37.223436 return self._conf._get(name, self._group)
2018-06-04 19:23:37.223440
2018-06-04 19:23:37.223444 File
"/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2950, in _get
2018-06-04 19:23:37.223448 value, loc = self._do_get(name, group,
namespace)
2018-06-04 19:23:37.223452
2018-06-04 19:23:37.223456 File
"/usr/local/lib/python2.7/dist-packages/oslo_config/cfg.py", line 2968, in
_do_get
2018-06-04 19:23:37.223460 info = self._get_opt_info(name, group)
2018-06-04 19:23:37.223464
2018-06-04 19:23:37.223468 File
[Yahoo-eng-team] [Bug 1772252] Re: Typo in the page - "Keystone Installation Tutorial for Ubuntu in keystone"
*** This bug is a duplicate of bug 1762633 *** https://bugs.launchpad.net/bugs/1762633 ** This bug has been marked a duplicate of bug 1762633 Keystone Installation Tutorial for Ubuntu in keystone -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1772252 Title: Typo in the page - "Keystone Installation Tutorial for Ubuntu in keystone" Status in OpenStack Identity (keystone): New Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [ ] This doc is inaccurate in this way: __ - [ ] This is a doc addition request. - [x] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode --- Release: 13.0.1.dev9 on 2018-05-08 06:44 SHA: 4ca0172fcdb1ce28a1f00d5a0e1bb3d646141803 Source: https://git.openstack.org/cgit/openstack/keystone/tree/doc/source/install/index-ubuntu.rst URL: https://docs.openstack.org/keystone/queens/install/index-ubuntu.html In the first note, it says MaOS instead of MacOS: "The Training Labs scripts provide an automated way of deploying the cluster described in this Installation Guide into VirtualBox or KVM VMs. You will need a desktop computer or a laptop with at least 8 GB memory and 20 GB free storage running Linux, MaOS, or Windows. Please see the OpenStack Training Labs." Please fix it to: "The Training Labs scripts provide an automated way of deploying the cluster described in this Installation Guide into VirtualBox or KVM VMs. You will need a desktop computer or a laptop with at least 8 GB memory and 20 GB free storage running Linux, MacOS, or Windows. Please see the OpenStack Training Labs." ~~~ Long live GNU/Linux! To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1772252/+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 1760843] [NEW] Idp's domain is not unique
Public bug reported: Backing to the patch https://review.openstack.org/#/c/399684/ when the domain_id is added for Idp, I assume that the domain_id is designed for unique? The domain_id in Idp model is unique: https://github.com/openstack/keystone/blob/master/keystone/federation/backends/sql.py#L58 But the db migration is not: https://github.com/openstack/keystone/blob/master/keystone/common/sql/expand_repo/versions/012_expand_add_domain_id_to_idp.py#L55-L56 They are not in consistence. Since I don't know the origin purpose for the change, I'm not very sure which is correct but I prefer the first one. What's more, our unit test use resource models to init db so that it's unique in our unit test sqlite db. It's not in consistence as well with the real usage. ** Affects: keystone Importance: Undecided Status: New ** Description changed: Backing to the patch https://review.openstack.org/#/c/399684/ when the - domain_id is added for Idp, I assume that the domain_id is designed - unique. + domain_id is added for Idp, I assume that the domain_id is designed for + unique? The domain_id in Idp model is unique: https://github.com/openstack/keystone/blob/master/keystone/federation/backends/sql.py#L58 But the db migration is not: https://github.com/openstack/keystone/blob/master/keystone/common/sql/expand_repo/versions/012_expand_add_domain_id_to_idp.py#L55-L56 They are not in consistence. Since I don't know the origin purpose for the change, I'm not very sure which is correct but I prefer the first one. What's more, our unit test use resource models to init db so that it's unique in our unit test sqlite db. It's not in consistence as well with the real usage. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1760843 Title: Idp's domain is not unique Status in OpenStack Identity (keystone): New Bug description: Backing to the patch https://review.openstack.org/#/c/399684/ when the domain_id is added for Idp, I assume that the domain_id is designed for unique? The domain_id in Idp model is unique: https://github.com/openstack/keystone/blob/master/keystone/federation/backends/sql.py#L58 But the db migration is not: https://github.com/openstack/keystone/blob/master/keystone/common/sql/expand_repo/versions/012_expand_add_domain_id_to_idp.py#L55-L56 They are not in consistence. Since I don't know the origin purpose for the change, I'm not very sure which is correct but I prefer the first one. What's more, our unit test use resource models to init db so that it's unique in our unit test sqlite db. It's not in consistence as well with the real usage. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1760843/+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 1760809] [NEW] delete domain raise 500 error if the domain contains idp
Public bug reported: How to reproduce: 1. create domain openstack domain create domainA 2. create a idp to the domainA openstack identity provider create idpA --domain domainA 3. disable the domainA and then try to delete it. openstack domain set domainA --disable openstack domain delete domainA Expect result: The domainA and its related resource will be deleted Actual result: Keystone raise 500 internal error reproduce example: http://paste.openstack.org/show/718241/ ** Affects: keystone Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: keystone Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1760809 Title: delete domain raise 500 error if the domain contains idp Status in OpenStack Identity (keystone): New Bug description: How to reproduce: 1. create domain openstack domain create domainA 2. create a idp to the domainA openstack identity provider create idpA --domain domainA 3. disable the domainA and then try to delete it. openstack domain set domainA --disable openstack domain delete domainA Expect result: The domainA and its related resource will be deleted Actual result: Keystone raise 500 internal error reproduce example: http://paste.openstack.org/show/718241/ To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1760809/+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 1755411] [NEW] image can't be deleted in some case
Public bug reported: We meet this problem in our production environment. When users is deleting an image but the glance-api process is down or restarted suddenly, the image's status will be 'deleted', but the 'deleted' column in the image table is False. This lead an error that the image still can be shown, but its status is 'deleted', and then it can't be deleted anymore either by DELETE API call or db purge. I found that the bug related to the code: https://github.com/openstack/glance/blob/master/glance/db/__init__.py#L205 what glance does; 1. mark the image's status as 'deleted' 2. then delete the image's property and mark the image as deleted=True, deleted_at=xxx. If the glance-api process or the DELETE API call is down between step 1 and 2. The case I mentioned above will occur. I have two idea to solve the problem: 1. add a check mechanism to service initialization. When glance-api process start, it should check the db data, purge the remain ones. 2. combine step 1 and step 2 into one sql transaction to avoid data inconsistency. ** Affects: glance Importance: Undecided Status: New ** Description changed: We meet this problem in our production environment. - When users is deleting a image but the glance-api process is down or + When users is deleting an image but the glance-api process is down or restarted suddenly, the image's status will be 'deleted', but the 'deleted' column in the image table is False. This lead an error that the image still can be shown, but its status is 'deleted', and then it can't be deleted anymore either by DELETE API call or db purge. I found that the bug related to the code: https://github.com/openstack/glance/blob/master/glance/db/__init__.py#L205 what glance does; 1. mark the image's status as 'deleted' 2. then delete the image's property and mark the image as deleted=True, deleted_at=xxx. If the glance-api process or the DELETE API call is down between step 1 and 2. The case I mentioned above will occur. I have two idea to solve the problem: 1. add a check mechanism to service initialization. When glance-api process start, it should check the db data, purge the remain ones. 2. combine step 1 and step 2 into one sql transaction to avoid data inconsistency. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1755411 Title: image can't be deleted in some case Status in Glance: New Bug description: We meet this problem in our production environment. When users is deleting an image but the glance-api process is down or restarted suddenly, the image's status will be 'deleted', but the 'deleted' column in the image table is False. This lead an error that the image still can be shown, but its status is 'deleted', and then it can't be deleted anymore either by DELETE API call or db purge. I found that the bug related to the code: https://github.com/openstack/glance/blob/master/glance/db/__init__.py#L205 what glance does; 1. mark the image's status as 'deleted' 2. then delete the image's property and mark the image as deleted=True, deleted_at=xxx. If the glance-api process or the DELETE API call is down between step 1 and 2. The case I mentioned above will occur. I have two idea to solve the problem: 1. add a check mechanism to service initialization. When glance-api process start, it should check the db data, purge the remain ones. 2. combine step 1 and step 2 into one sql transaction to avoid data inconsistency. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1755411/+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 1748062] Re: idp_id, protocol_id, unique_id and name filter doesn't work for list_users API when domain_specific_drivers_enabled is set
** Changed in: keystone Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1748062 Title: idp_id, protocol_id, unique_id and name filter doesn't work for list_users API when domain_specific_drivers_enabled is set Status in OpenStack Identity (keystone): Invalid Bug description: When domain_specific_drivers_enabled is set to True, the idp_id, protocol_id, unique_id and name filter will not work for listing federated users. Reproduce: 1. set the domain_specific_drivers_enabled = true, then restart Keystone. 2. try to list the federated users by "idp_id" filter, for example, if you have a federated user whose idp_id is "deamoidp" already, try this: GET /v3/users?idp_id=demoidp please ensure the user driver is domian aware, that is, should not be ldap. Expect: the federated user whose idp_id=demoidp should return. Actual: Nothing returned. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1748062/+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 1748062] [NEW] idp_id, protocol_id, unique_id and name filter doesn't work for list_users API when domain_specific_drivers_enabled is set
Public bug reported: When domain_specific_drivers_enabled is set to True, the idp_id, protocol_id, unique_id and name filter will not work for listing federated users. Reproduce: 1. set the domain_specific_drivers_enabled = true, then restart Keystone. 2. try to list the federated users by "idp_id" filter, for example, if you have a federated user whose idp_id is "deamoidp" already, try this: GET /v3/users?idp_id=demoidp please ensure the user driver is domian aware, that is, should not be ldap. Expect: the federated user whose idp_id=demoidp should return. Actual: Nothing returned. ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1748062 Title: idp_id, protocol_id, unique_id and name filter doesn't work for list_users API when domain_specific_drivers_enabled is set Status in OpenStack Identity (keystone): New Bug description: When domain_specific_drivers_enabled is set to True, the idp_id, protocol_id, unique_id and name filter will not work for listing federated users. Reproduce: 1. set the domain_specific_drivers_enabled = true, then restart Keystone. 2. try to list the federated users by "idp_id" filter, for example, if you have a federated user whose idp_id is "deamoidp" already, try this: GET /v3/users?idp_id=demoidp please ensure the user driver is domian aware, that is, should not be ldap. Expect: the federated user whose idp_id=demoidp should return. Actual: Nothing returned. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1748062/+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 1747332] [NEW] application credential cache is not invalidated
Public bug reported: application credential cache is not invalidated when the related user is disabled/deleted or the related assignment is removed. reproduce: 1. create an application credential. 2. get it for caching. 3. delete the related user (or disable it, or remove an assigned role) 4. get it again. Expect: return 404 in step 4. Actual: still return the deleted application credential. ** Affects: keystone Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: keystone Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1747332 Title: application credential cache is not invalidated Status in OpenStack Identity (keystone): New Bug description: application credential cache is not invalidated when the related user is disabled/deleted or the related assignment is removed. reproduce: 1. create an application credential. 2. get it for caching. 3. delete the related user (or disable it, or remove an assigned role) 4. get it again. Expect: return 404 in step 4. Actual: still return the deleted application credential. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1747332/+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 1746868] [NEW] cache invalidate doesn't work for application credential
Public bug reported: when cache is enabled and an application credential is deleted, it still can be get from cache during the caching time. The cache invalidate doesn't work for application credential now. ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1746868 Title: cache invalidate doesn't work for application credential Status in OpenStack Identity (keystone): New Bug description: when cache is enabled and an application credential is deleted, it still can be get from cache during the caching time. The cache invalidate doesn't work for application credential now. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1746868/+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 1745905] [NEW] system scope doesn't work for the service which use project specified endpoint
Public bug reported:
For some project, such as Cinder, the endpoint is project specified, the format
is like:
http://ip/volume/v3/{project_id}/volumes
There are two problem:
1. For this kind of endpoint, system-scoped token doesn't work because that
there is no project_id in the token.
2. When issue a system-scoped token, the Cinder's endpoint in the token
catalog is empty. It means the Cinder service will not be discoverable
when use system-scoped token.
** Affects: cinder
Importance: Undecided
Status: New
** Affects: keystone
Importance: Undecided
Status: New
** Also affects: cinder
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1745905
Title:
system scope doesn't work for the service which use project specified
endpoint
Status in Cinder:
New
Status in OpenStack Identity (keystone):
New
Bug description:
For some project, such as Cinder, the endpoint is project specified, the
format is like:
http://ip/volume/v3/{project_id}/volumes
There are two problem:
1. For this kind of endpoint, system-scoped token doesn't work because that
there is no project_id in the token.
2. When issue a system-scoped token, the Cinder's endpoint in the
token catalog is empty. It means the Cinder service will not be
discoverable when use system-scoped token.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1745905/+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 1744195] [NEW] unit tests don't enable Foreign Key for Sqlite
Public bug reported: Now Keystone runs unit test with sqlite backend by default. But sqlite doesn't enable Foreign Key function by default. It means that we lost the case for all FK related test. Even after enabled FK for the test. There still some problems: 1. We lost root domain (<>) when setup tests. So that a lot of tests will fail. 2. Some tests, such as test_sql_upgrade and identity.backens.test_sql, use global db engine. It means that the test will meet conflict if the FK is enabled for the global db engine. So we should refactor our test code to satisfy sqilte FK function. There are some steps: 1. Add FK support for the tests. Disable it by default 2. Enable FK for the test one by one. 3. Make sure the Fk is disabled for test_sql_upgrade and identity.backens.test_sql ** Affects: keystone Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1744195 Title: unit tests don't enable Foreign Key for Sqlite Status in OpenStack Identity (keystone): New Bug description: Now Keystone runs unit test with sqlite backend by default. But sqlite doesn't enable Foreign Key function by default. It means that we lost the case for all FK related test. Even after enabled FK for the test. There still some problems: 1. We lost root domain (<>) when setup tests. So that a lot of tests will fail. 2. Some tests, such as test_sql_upgrade and identity.backens.test_sql, use global db engine. It means that the test will meet conflict if the FK is enabled for the global db engine. So we should refactor our test code to satisfy sqilte FK function. There are some steps: 1. Add FK support for the tests. Disable it by default 2. Enable FK for the test one by one. 3. Make sure the Fk is disabled for test_sql_upgrade and identity.backens.test_sql To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1744195/+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 1736875] [NEW] Keystone raise 500 error when authorize request token with invalid body
Public bug reported:
Keystone raise 500 error when authorize request token with invalid body.
reproduce:
1. create a request token first, suppose the token key is
f13b2c6755634131b59cf5fa08d49331
2. PUT
http://keystone-server/v3/OS-OAUTH1/authorize/f13b2c6755634131b59cf5fa08d49331
with body:
{
"roles": [
{
"id": "711aa6371a6343a9a43e8a310fbe4a6f"
},
{
"name": "admin"
}
]
}
Keystone will raise 500 error. error log:
Traceback (most recent call last):
File "/opt/stack/keystone/keystone/common/wsgi.py", line 226, in __call__
result = method(req, **params)
File "/opt/stack/keystone/keystone/common/controller.py", line 82, in inner
return f(self, request, *args, **kwargs)
File "/opt/stack/keystone/keystone/oauth1/controllers.py", line 404, in
authorize_request_token
authed_roles.add(role['id'])
KeyError: 'id'
here are two things we can improve:
1. Add the schema check for request token authorize API
2. Support role name.
To fix the 500 error, step 1 is enough.
** Affects: keystone
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: keystone
Assignee: (unassigned) => wangxiyuan (wangxiyuan)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1736875
Title:
Keystone raise 500 error when authorize request token with invalid
body
Status in OpenStack Identity (keystone):
New
Bug description:
Keystone raise 500 error when authorize request token with invalid body.
reproduce:
1. create a request token first, suppose the token key is
f13b2c6755634131b59cf5fa08d49331
2. PUT
http://keystone-server/v3/OS-OAUTH1/authorize/f13b2c6755634131b59cf5fa08d49331
with body:
{
"roles": [
{
"id": "711aa6371a6343a9a43e8a310fbe4a6f"
},
{
"name": "admin"
}
]
}
Keystone will raise 500 error. error log:
Traceback (most recent call last):
File "/opt/stack/keystone/keystone/common/wsgi.py", line 226, in __call__
result = method(req, **params)
File "/opt/stack/keystone/keystone/common/controller.py", line 82, in inner
return f(self, request, *args, **kwargs)
File "/opt/stack/keystone/keystone/oauth1/controllers.py", line 404, in
authorize_request_token
authed_roles.add(role['id'])
KeyError: 'id'
here are two things we can improve:
1. Add the schema check for request token authorize API
2. Support role name.
To fix the 500 error, step 1 is enough.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1736875/+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 1734244] [NEW] keystone raise 500 error when create trust with invalid role key
Public bug reported:
When a user try to create a trust, if the "roles" in the request body
contains some invalid keys(except "id" and "name"), Keystone will raise
500 error.
an example:
curl -g -i -X POST http://10.3.150.25/identity/v3/OS-TRUST/trusts -H
"User-Agent: python-keystoneclient" -H "Content-Type: application/json"
-H "Accept: application/json" -H "X-Auth-Token:
gABaF5Odiawpf1t9BAAhyS3_FBZCKDPycpOnSndiC0TEmqemZvnINxcTPHLGR0J3mnjf60TdqIpct7SgO5movr5uWY-
hmTT4R2Sr_5rYOPC_-w0y6XWbNn265U5IKVz0qMRr-
1VagtuA3iPmyZkjCbFweZsP8yFkwWSxkY4_I0U6JTPzllM" -d '{"trust":
{"impersonation": false, "project_id":
"d88a1e3ce2504a10a5340225b85a844c", "trustor_user_id":
"f98b4cc01a554453a84fa4b9ccf5a1f0", "roles": [{"fake_key": "123"}],
"trustee_user_id": "c8b34ea0d6d6406aae5993061de92e77"}}'
** Affects: keystone
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: keystone
Assignee: (unassigned) => wangxiyuan (wangxiyuan)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1734244
Title:
keystone raise 500 error when create trust with invalid role key
Status in OpenStack Identity (keystone):
New
Bug description:
When a user try to create a trust, if the "roles" in the request body
contains some invalid keys(except "id" and "name"), Keystone will
raise 500 error.
an example:
curl -g -i -X POST http://10.3.150.25/identity/v3/OS-TRUST/trusts -H
"User-Agent: python-keystoneclient" -H "Content-Type:
application/json" -H "Accept: application/json" -H "X-Auth-Token:
gABaF5Odiawpf1t9BAAhyS3_FBZCKDPycpOnSndiC0TEmqemZvnINxcTPHLGR0J3mnjf60TdqIpct7SgO5movr5uWY-
hmTT4R2Sr_5rYOPC_-w0y6XWbNn265U5IKVz0qMRr-
1VagtuA3iPmyZkjCbFweZsP8yFkwWSxkY4_I0U6JTPzllM" -d '{"trust":
{"impersonation": false, "project_id":
"d88a1e3ce2504a10a5340225b85a844c", "trustor_user_id":
"f98b4cc01a554453a84fa4b9ccf5a1f0", "roles": [{"fake_key": "123"}],
"trustee_user_id": "c8b34ea0d6d6406aae5993061de92e77"}}'
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1734244/+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 1733754] [NEW] 500 error if OS-TRUST:trust is not a dict when authenticate
Public bug reported:
env: master branch
when user try to issue a token with OS-TRUST:trust if OS-TRUST:trust is not a
dict, keystone will raise 500 error:
SZX1000339032 devstack@keystone.service[12272]: ERROR keystone.common.wsgi
Traceback (most recent call last):
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/common/wsgi.py", line
228, in __call__
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi LOG.warning(
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/auth/controllers.py",
line 114, in authenticate_for_token
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi auth_info = core.AuthInfo.create(auth=auth)
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/auth/core.py", line
142, in create
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi auth_info._validate_and_normalize_auth_data(scope_only)
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/auth/core.py", line
295, in _validate_and_normalize_auth_data
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi self._validate_and_normalize_scope_data()
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/auth/core.py", line
255, in _validate_and_normalize_scope_dat
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi self.auth['scope']['OS-TRUST:trust'])
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/auth/core.py", line
224, in _lookup_trust
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi trust_id = trust_info.get('id')
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi AttributeError: 'str' object has no attribute 'get'
Keystone should add OS-TRUST:trust into the schema check as well.
** Affects: keystone
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: keystone
Assignee: (unassigned) => wangxiyuan (wangxiyuan)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1733754
Title:
500 error if OS-TRUST:trust is not a dict when authenticate
Status in OpenStack Identity (keystone):
New
Bug description:
env: master branch
when user try to issue a token with OS-TRUST:trust if OS-TRUST:trust is not a
dict, keystone will raise 500 error:
SZX1000339032 devstack@keystone.service[12272]: ERROR keystone.common.wsgi
Traceback (most recent call last):
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/common/wsgi.py", line
228, in __call__
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi LOG.warning(
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/auth/controllers.py",
line 114, in authenticate_for_token
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi auth_info = core.AuthInfo.create(auth=auth)
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/auth/core.py", line
142, in create
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi auth_info._validate_and_normalize_auth_data(scope_only)
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/auth/core.py", line
295, in _validate_and_normalize_auth_data
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi self._validate_and_normalize_scope_data()
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/auth/core.py", line
255, in _validate_and_normalize_scope_dat
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi self.auth['scope']['OS-TRUST:trust'])
Nov 07 16:46:18 SZX1000339032 devstack@keystone.service[12272]: ERROR
keystone.common.wsgi File "/opt/stack/keystone/keystone/auth/core.py"
[Yahoo-eng-team] [Bug 1730270] [NEW] keystone raise 500 error when authenticate with "mapped"
Public bug reported: When authenticate with "mapped" method, if users forget to add "identity_provider" or "protocol" keypair, keystone will raise 500 error. In this case, keystone should raise 400 Bad Request. ** Affects: keystone Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: In Progress ** Changed in: keystone Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1730270 Title: keystone raise 500 error when authenticate with "mapped" Status in OpenStack Identity (keystone): In Progress Bug description: When authenticate with "mapped" method, if users forget to add "identity_provider" or "protocol" keypair, keystone will raise 500 error. In this case, keystone should raise 400 Bad Request. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1730270/+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 1368661] Re: Unit tests sometimes fail because of stale pyc files
** Changed in: python-zaqarclient Status: Fix Committed => Fix Released -- 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/1368661 Title: Unit tests sometimes fail because of stale pyc files Status in congress: Fix Released Status in Gnocchi: Invalid Status in Ironic: Fix Released Status in Magnum: Fix Released Status in Mistral: Fix Released Status in Monasca: Fix Committed Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) icehouse series: Fix Released Status in oslo.cache: Invalid Status in oslo.concurrency: Invalid Status in oslo.service: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in Glance Client: In Progress Status in python-heatclient: Fix Committed Status in python-keystoneclient: Fix Released Status in python-magnumclient: Fix Released Status in python-mistralclient: Fix Released Status in python-neutronclient: Fix Released Status in Python client library for Sahara: Fix Released Status in python-solumclient: Fix Released Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Committed Status in Python client library for Zaqar: Fix Released Status in Solum: Fix Released Status in OpenStack Object Storage (swift): Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in zaqar: Fix Released Bug description: Because python creates pyc files during tox runs, certain changes in the tree, like deletes of files, or switching branches, can create spurious errors. This can be suppressed by PYTHONDONTWRITEBYTECODE=1 in the tox.ini. To manage notifications about this bug go to: https://bugs.launchpad.net/congress/+bug/1368661/+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 1683730] Re: [NOVA] There is no method to delete non-empty cells.
** Project changed: cinder => nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1683730 Title: [NOVA] There is no method to delete non-empty cells or "cell mappings". Status in OpenStack Compute (nova): New Bug description: We have several method to create cells and mapping cell with hosts, database and message queue but there's no method to delete the non-empty cells in nova. We can delete the empty cells through "nova-manage cell_v2 delete_cell --cell_uuid ". But if cell is mapped to hosts, we don't have any CLI or method to delete that cell because to delete any cell we first need to remove its mapping with hosts. For it to be resolved first we need a method to delete cell mappings. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1683730/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1495519] Re: import flow doesn't raise error on forbidden location
** Changed in: glance
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1495519
Title:
import flow doesn't raise error on forbidden location
Status in Glance:
Fix Released
Status in Glance liberty series:
New
Bug description:
The following command correctly raises an exception server side but it
doesn't report the error back to the user. This ends up in the user
"thinking" the task was created correctly:
$ glance --os-image-api-version 2 --os-image-url
http://localhost:9292/v2 --os-tenant-id
a1875f8a27f74708b6fb9281e7430a98 task-create --type import --input
'{"import_from_format": "qcow2", "import_from":
"swift://127.0.0.1:8000/test.qcow2", "image_properties":
{"disk_format": "qcow2", "container_format": "bare"}}'
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1495519/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1512369] Re: glance should declare a test-requirements.txt on swiftclient
** No longer affects: glance ** Changed in: glance/liberty 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/1512369 Title: glance should declare a test-requirements.txt on swiftclient Status in Glance liberty series: Fix Released Bug description: As glance is building its config, it needs swiftclient. And it isn't defined in test-requirements.txt, meaning that some options may be missing for swift. I've added python-swiftclient in the Build-Depends- Indep: of the Debian package, though it should IMO also go into the test-requirements.txt of the upstream project. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/liberty/+bug/1512369/+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 1658137] Re: volume backups fail if no container name provided
** Changed in: cinder Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1658137 Title: volume backups fail if no container name provided Status in Cinder: Invalid Status in OpenStack Dashboard (Horizon): Fix Released Bug description: if no container name is provided, horizon ends up passing "" to the cinder client api call. This is an invalid container name - None is the correct value to pass for this to work as desired. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1658137/+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 1574991] Re: member-id should contian only numbers and letters
** Project changed: glance => python-glanceclient -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1574991 Title: member-id should contian only numbers and letters Status in python-glanceclient: In Progress Bug description: Now, there is no limit for member-id's format. It means that all characters are allowed. But member_id means a project's(tenant's) id. It shoud contian only numbers and letters. If not, it will lead some error: reprodue: env: glance master 1.create a member for an image: $glance member-create b9125ded-d2d0-4d4e-9eee-5623344c9cbf fdsae#$%^^da 2.delete the member from the image: $glance member-delete b9125ded-d2d0-4d4e-9eee-5623344c9cbf fdsae#$%^^da the error accoured: 404 Not Found fdsae not found in the member list of the image b9125ded-d2d0-4d4e-9eee-5623344c9cbf. (HTTP 404) To manage notifications about this bug go to: https://bugs.launchpad.net/python-glanceclient/+bug/1574991/+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 1607317] Re: metadata def namespace update CLI is not working as expected for parameter "protected"
not only this command but also others has this problem, you can take a try with "glance image-update --protectd". The reason is that glance client analyze this kind of parameter to "False" when it's not boolean. ** Project changed: glance => python-glanceclient -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1607317 Title: metadata def namespace update CLI is not working as expected for parameter "protected" Status in python-glanceclient: New Bug description: In v2 glance metadata def namespace update API, it is observed that when we are updating protected parameter with different invalid values, it updates this parameter inappropriately. Following CLI update output shows this behavior - # Create a v2 metadata def namespace using admin credentials - stack@ubuntu-VirtualBox:/opt/stack/tempest$ glance --os-image-api-version 2 md-namespace-create test-ns ++--+ | Property | Value| ++--+ | created_at | 2016-07-28T10:51:25Z | | namespace | test-ns | | owner | 93efcc2b00164c61aafaa6f234b99bc3 | | protected | False| | schema | /v2/schemas/metadefs/namespace | | updated_at | 2016-07-28T10:51:25Z | | visibility | private | ++--+ stack@ubuntu-VirtualBox:/opt/stack/tempest$ Now look at below different invalid protected parameters and behavior - stack@ubuntu-VirtualBox:/opt/stack/tempest$ glance --debug --os-image-api-version 2 md-namespace-update test-ns --protected True ++--+ | Property | Value| ++--+ | created_at | 2016-07-28T10:51:25Z | | namespace | test-ns | | owner | 93efcc2b00164c61aafaa6f234b99bc3 | | protected | True | | schema | /v2/schemas/metadefs/namespace | | updated_at | 2016-07-28T10:51:32Z | | visibility | private | ++--+ stack@ubuntu-VirtualBox:/opt/stack/tempest$ ++--+ | Property | Value| ++--+ | created_at | 2016-07-28T10:51:25Z | | namespace | test-ns | | owner | 93efcc2b00164c61aafaa6f234b99bc3 | | protected | True | | schema | /v2/schemas/metadefs/namespace | | updated_at | 2016-07-28T10:51:32Z | | visibility | private | ++--+ stack@ubuntu-VirtualBox:/opt/stack/tempest$ glance --os-image-api-version 2 md-namespace-update test-ns --protected True ++--+ | Property | Value| ++--+ | created_at | 2016-07-28T10:51:25Z | | namespace | test-ns | | owner | 93efcc2b00164c61aafaa6f234b99bc3 | | protected | True | | schema | /v2/schemas/metadefs/namespace | | updated_at | 2016-07-28T10:51:32Z | | visibility | private | ++--+ stack@ubuntu-VirtualBox:/opt/stack/tempest$ glance --os-image-api-version 2 md-namespace-update test-ns --protected False ++--+ | Property | Value| ++--+ | created_at | 2016-07-28T10:51:25Z | | namespace | test-ns | | owner | 93efcc2b00164c61aafaa6f234b99bc3 | | protected | False| | schema | /v2/schemas/metadefs/namespace | | updated_at | 2016-07-28T10:53:04Z | | visibility | private | ++--+ stack@ubuntu-VirtualBox:/opt/stack/tempest$ glance --os-image-api-version 2 md-namespace-update test-ns --protected "True" ++--+ | Property | Value| ++--+ | created_at | 2016-07-28T10:51:25Z | | namespace | test-ns | | owner | 93efcc2b00164c61aafaa6f234b99bc3 | | protected | True | | schema | /v2/schemas/metadefs/namespace
[Yahoo-eng-team] [Bug 1574991] [NEW] member-id should contian only numbers and letters
Public bug reported: Now, there is no limit for member-id's format. It means that all characters are allowed. But member_id means a project's(tenant's) id. It shoud contian only numbers and letters. If not, it will lead some error: reprodue: env: glance master 1.create a member for an image: $glance member-create b9125ded-d2d0-4d4e-9eee-5623344c9cbf fdsae#$%^^da 2.delete the member from the image: $glance member-delete b9125ded-d2d0-4d4e-9eee-5623344c9cbf fdsae#$%^^da the error accoured: 404 Not Found fdsae not found in the member list of the image b9125ded-d2d0-4d4e-9eee-5623344c9cbf. (HTTP 404) ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: glance Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1574991 Title: member-id should contian only numbers and letters Status in Glance: New Bug description: Now, there is no limit for member-id's format. It means that all characters are allowed. But member_id means a project's(tenant's) id. It shoud contian only numbers and letters. If not, it will lead some error: reprodue: env: glance master 1.create a member for an image: $glance member-create b9125ded-d2d0-4d4e-9eee-5623344c9cbf fdsae#$%^^da 2.delete the member from the image: $glance member-delete b9125ded-d2d0-4d4e-9eee-5623344c9cbf fdsae#$%^^da the error accoured: 404 Not Found fdsae not found in the member list of the image b9125ded-d2d0-4d4e-9eee-5623344c9cbf. (HTTP 404) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1574991/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1537626] Re: `glance location-update` deletes locations and backend images
https://review.openstack.org/#/c/35134/14
here is the original patch
** Project changed: python-glanceclient => glance
** Also affects: python-glanceclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1537626
Title:
`glance location-update` deletes locations and backend images
Status in Glance:
New
Status in python-glanceclient:
New
Bug description:
Hi all,
I am having trouble using `glance location-update --url
--metadata ` to update the metadata of a location. When
I try run the command, the locations become a blank list and the image
is deleted from my backend (swift+https). I have traced it down to the
following:
When doing a location-update, glanceclient actually sends two patch
commands:
[{'op': 'replace', 'path': '/locations', 'value': []},
{'op': 'replace',
'path': '/locations',
'value': [{u'metadata': {u'key': 'value'},
{u'url': u'swift+https://image1'}]}]
This is due to a note in python-
glanceclient/glanceclient/v2/images.py, update_location():
# NOTE: The server (as of now) doesn't support modifying individual
# location entries. So we must:
# 1. Empty existing list of locations.
# 2. Send another request to set 'locations' to the new list
# of locations.
However, at the server end, the _do_replace_locations() function which
handles this call, actually deletes the locations and images when it
gets the first call with the empty values
(glance/glance/api/v2/images.py) ???
def _do_replace_locations(self, image, value):
if len(image.locations) > 0 and len(value) > 0:
msg = _("Cannot replace locations from a non-empty "
"list to a non-empty list.")
raise webob.exc.HTTPBadRequest(explanation=msg)
if len(value) == 0:
# NOTE(zhiyan): this actually deletes the location
# from the backend store.
del image.locations[:]
if image.status == 'active':
image.status = 'queued'
This seems to result in the first call deleting all the locations from
the backend store, and the second call throwing an error because there
is no location any more.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1537626/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1534083] Re: Glance api config file lost the configuration item "filesystem_store_datadir" default value
/var/lib/glance/images seems good. It's what in the official guideline. ** 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/1534083 Title: Glance api config file lost the configuration item "filesystem_store_datadir" default value Status in glance_store: New Bug description: The config item "filesystem_store_datadir "default value lost, so after install glance, users have to manually configure it. To manage notifications about this bug go to: https://bugs.launchpad.net/glance-store/+bug/1534083/+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 1533927] [NEW] the help command of glance-replicator and glance-cache-manage is broken
Public bug reported: reproduce: 1.glance-replicator Unknown command: None 2.glance-replicator help 2016-01-14 10:08:17.045 96623 ERROR glance.cmd.replicator [-] Print help specific to a command. options: the parsed command line options args: the command line ERROR: object of type 'NoneType' has no len() 3.glance-cache-manage help Please specify a command ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: In Progress ** Changed in: glance Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1533927 Title: the help command of glance-replicator and glance-cache-manage is broken Status in Glance: In Progress Bug description: reproduce: 1.glance-replicator Unknown command: None 2.glance-replicator help 2016-01-14 10:08:17.045 96623 ERROR glance.cmd.replicator [-] Print help specific to a command. options: the parsed command line options args: the command line ERROR: object of type 'NoneType' has no len() 3.glance-cache-manage help Please specify a command To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1533927/+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 1529572] [NEW] Replace locations with multi-requests returns wrong result
Public bug reported:
Env: glance-master,
Reproduce:
1. Suppose there is an image with its location in Glance already.
2. send a location-update request with two bodies, like:
[
{
"op":"replace",
"path":"/locations",
"value":[
]
},
{
"op":"replace",
"path":"/locations",
"value":[
{
"url":
"swift+http://admin:admin:root@10.229.45.145:35357/v3/glance/wrong-test.img;,
#note: this is a wrong location url.
"metadata": {}
}
]
}
]
The first body is to set the location to empty. The second body is to
set the location to a new one, but the url is wrong.
3. the Glance raise an error: Invalid locations. Because that I send a
wrong url to Glance.
4. Show the image.
Expect result:
the image's status is 'queued' and the location is empty.
Actual result:
the image's status is 'active', but the location is empty.
The reason is that Glance save the image' information to db when the
hole request is over. But i give the wrong url, so that the the location
has been removed and image didn't be saved to db.
So IMO, we should take db saving each time we change the location.
** Affects: glance
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: glance
Assignee: (unassigned) => wangxiyuan (wangxiyuan)
** Description changed:
Env: glance-master,
Reproduce:
- 1. Suppose there is an image with its location in Glance already.
+ 1. Suppose there is an image with its location in Glance already.
+
2. send a location-update request with two bodies, like:
[
- {
- "op":"replace",
- "path":"/locations",
- "value":[
- ]
-},
-
-{
- "op":"replace",
- "path":"/locations",
- "value":[
- {
- "url":
"swift+http://admin:admin:root@10.229.45.145:35357/v3/glance/wrong-test.img;,
- #note: this is a wrong location url.
- "metadata": {}
- }
- ]
-}
+ {
+ "op":"replace",
+ "path":"/locations",
+ "value":[
+ ]
+ },
+
+ {
+ "op":"replace",
+ "path":"/locations",
+ "value":[
+ {
+ "url":
"swift+http://admin:admin:root@10.229.45.145:35357/v3/glance/wrong-test.img;,
+ #note: this is a wrong location url.
+ "metadata": {}
+ }
+ ]
+ }
]
- 3. the Glance raise an error: Invalid locations. Because that I send a wrong
url to Glance.
+
+ The first body is to set the location to empty. The second body is to
+ set the location to a new one, but the url is wrong.
+
+ 3. the Glance raise an error: Invalid locations. Because that I send a
+ wrong url to Glance.
+
4. Show the image.
Expect result:
the image's status is 'queued' and the location is empty.
Actual result:
the image's status is 'active', but the location is empty.
The reason is that Glance save the image' information to db when the
hole request is over. But i give the wrong url, so that the the location
has been removed and image didn't be saved to db.
So IMO, we should take db saving each time we change the location.
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1529572
Title:
Replace locations with multi-requests returns wrong result
Status in Glance:
New
Bug description:
Env: glance-master,
Reproduce:
1. Suppose there is an image with its location in Glance already.
2. send a location-update request with two bodies, like:
[
{
"op":"replace",
"path":"/locations",
"value":[
]
},
{
"op":"replace",
"path":"/locations",
"value":[
{
"url":
"swift+http://admin:admin:root@10.229.45.145:35357/v3/glance/wrong-test.img;,
#note: this is a wrong location url.
"metadata": {}
}
]
}
]
The first body is to set the location to empty. The second body is to
set the location to a new one, but the url is wrong.
3. the Glance raise an error: Invalid locations. Because that I send a
wrong url to Glance.
4. Show the image.
Expect result:
the image's status is 'queued' and the location is empty.
Actual result:
the image's status is 'active', but the location is empty.
[Yahoo-eng-team] [Bug 1529198] [NEW] Glance raise 500 when upload image data
Public bug reported: Now, when the storage back-end doesn't has enough space fro image store, the back-end(Such as Swift) will sometimes raise a BackendException error and Glance will not catch it. Reproduce: 1.suppose use Swift back-end, and there is 1G could be use. 2.create an image with 2G. 3.Glance will return 500 error. So IMO, Glance should catch BackendException error to show the error message to users. ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: glance Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1529198 Title: Glance raise 500 when upload image data Status in Glance: New Bug description: Now, when the storage back-end doesn't has enough space fro image store, the back-end(Such as Swift) will sometimes raise a BackendException error and Glance will not catch it. Reproduce: 1.suppose use Swift back-end, and there is 1G could be use. 2.create an image with 2G. 3.Glance will return 500 error. So IMO, Glance should catch BackendException error to show the error message to users. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1529198/+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 1521423] Re: is-public = true should be removed from manual seems
In v1 , we use "--is-public True(or False)". In v2, we use "--visibility public(or private)". The client's default api version is 2 now. So you should use --visibility. The doc is ok. You can find "glance image-create (v1)" and "glance image-create (v2)" in it. Please check again. ** 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/1521423 Title: is-public = true should be removed from manual seems Status in Glance: Invalid Bug description: when i tried creating image using --is-public True I gave me following message unrecognized arguments: --is-public True ubuntu-14.04-server-cloudimg- amd64-disk1.img It should be removed from manuals http://docs.openstack.org/cli- reference/content/glanceclient_commands.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1521423/+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 1521467] Re: Snapshot of volume base instance shows type as image not snapshot and size as 0
** Changed in: glance Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1521467 Title: Snapshot of volume base instance shows type as image not snapshot and size as 0 Status in Glance: Invalid Status in OpenStack Compute (nova): New Bug description: Reproduce Step: 1. Create an instance holly-vm1 base on storage volume(xiv use here). 2. Create a snapshot from the instance in step1. 3. List the images and found 2 problems: a, the type of holly-vm1-snapshot is "Image", which should be "Snapshot"! b, the size of holly-vm1-snapshot is "0". 4. I created a snapshot from an instance based on local disk holly-vm4-snapshot to compare and put the screenshot in attachment. You could see the different value showed in table. Using Kilo version OpenStack, not sure if the same on the latest code. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1521467/+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 1521466] Re: volume snapshot which is created by create snapshot from storage base instance don't be deleted automatic
** Changed in: glance Status: New => Opinion -- 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/1521466 Title: volume snapshot which is created by create snapshot from storage base instance don't be deleted automatic Status in Glance: Opinion Status in OpenStack Compute (nova): New Bug description: Reproduce Step: 1. Create an instance holly-vm1 base on storage volume(xiv use here with 2 volumes). 2. Create a snapshot from the instance in step1. 3. Found snapshot holly-vm1-snapshot under image list. 4. Found 2 volume snapshots under volume snapshot page.(snapshot for holly-vm1-snapshot) 5. Delete snapshot holly-vm1-snapshot 6. Found the 2 volume snapshot .(snapshot for holly-vm1-snapshot) still there which should be deleted with snapshot image. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1521466/+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 1521466] Re: volume snapshot which is created by create snapshot from storage base instance don't be deleted automatic
Now if a user want to delete the snapshot which is created by back-end instance, he should delete both the image in Glance and the snapshot in Cinder. So do you think that when delete the image, Glance should delete the snapshot in Cinder? ** No longer affects: nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1521466 Title: volume snapshot which is created by create snapshot from storage base instance don't be deleted automatic Status in Glance: Opinion Bug description: Reproduce Step: 1. Create an instance holly-vm1 base on storage volume(xiv use here with 2 volumes). 2. Create a snapshot from the instance in step1. 3. Found snapshot holly-vm1-snapshot under image list. 4. Found 2 volume snapshots under volume snapshot page.(snapshot for holly-vm1-snapshot) 5. Delete snapshot holly-vm1-snapshot 6. Found the 2 volume snapshot .(snapshot for holly-vm1-snapshot) still there which should be deleted with snapshot image. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1521466/+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 1521467] Re: Snapshot of volume base instance shows type as image not snapshot and size as 0
When create images for volume back-end instances, the image's size is 0. It's not a bug as I know, because in this action, cinder create d a backup volume and then glance create a image of which properties contained the backup volume's information. I'm not sure the behavior "the type is Image, not Snapshot" is a bug or not. At last, this is a Nova problem, not Glance. :) ** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1521467 Title: Snapshot of volume base instance shows type as image not snapshot and size as 0 Status in Glance: New Status in OpenStack Compute (nova): New Bug description: Reproduce Step: 1. Create an instance holly-vm1 base on storage volume(xiv use here). 2. Create a snapshot from the instance in step1. 3. List the images and found 2 problems: a, the type of holly-vm1-snapshot is "Image", which should be "Snapshot"! b, the size of holly-vm1-snapshot is "0". 4. I created a snapshot from an instance based on local disk holly-vm4-snapshot to compare and put the screenshot in attachment. You could see the different value showed in table. Using Kilo version OpenStack, not sure if the same on the latest code. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1521467/+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 1521466] Re: volume snapshot which is created by create snapshot from storage base instance don't be deleted automatic
** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1521466 Title: volume snapshot which is created by create snapshot from storage base instance don't be deleted automatic Status in Glance: New Status in OpenStack Compute (nova): New Bug description: Reproduce Step: 1. Create an instance holly-vm1 base on storage volume(xiv use here with 2 volumes). 2. Create a snapshot from the instance in step1. 3. Found snapshot holly-vm1-snapshot under image list. 4. Found 2 volume snapshots under volume snapshot page.(snapshot for holly-vm1-snapshot) 5. Delete snapshot holly-vm1-snapshot 6. Found the 2 volume snapshot .(snapshot for holly-vm1-snapshot) still there which should be deleted with snapshot image. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1521466/+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 1520398] [NEW] glance doesn't have image number quota
Public bug reported: Acccording to the bluerpint : https://blueprints.launchpad.net/glance/+spec/glance-basic-quotas It would be very helpful if we were able to limit the usage of some basic image-related resources, like the number of images stored. So I think we should add it to Glance now. ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Tags: spce-lite ** Summary changed: - glance doesn't image number quota + glance doesn't have image number quota -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1520398 Title: glance doesn't have image number quota Status in Glance: New Bug description: Acccording to the bluerpint : https://blueprints.launchpad.net/glance/+spec/glance-basic-quotas It would be very helpful if we were able to limit the usage of some basic image-related resources, like the number of images stored. So I think we should add it to Glance now. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1520398/+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 1520053] [NEW] Duplicate location error should raise HTTPConflict
Public bug reported: When add or replace a duplicate location to an image, Glance should raise 409 HTTPConflict, not 400 HTTPBadRequest. The glance client raise 409, we should keep the same with the client. ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: In Progress ** Changed in: glance Assignee: (unassigned) => wangxiyuan (wangxiyuan) ** Description changed: When add or replace a duplicate location to an image, Glance should raise 409 HTTPConflict, not 400 HTTPBadRequest. + + The glance client raise 409, we should keep the same with the client. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1520053 Title: Duplicate location error should raise HTTPConflict Status in Glance: In Progress Bug description: When add or replace a duplicate location to an image, Glance should raise 409 HTTPConflict, not 400 HTTPBadRequest. The glance client raise 409, we should keep the same with the client. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1520053/+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 1369854] Re: min_disk and size information wrong when creating an instance image
** Changed in: glance Assignee: wangxiyuan (wangxiyuan) => (unassigned) ** Changed in: glance Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1369854 Title: min_disk and size information wrong when creating an instance image Status in Glance: Invalid Status in OpenStack Compute (nova): Fix Released Bug description: If I launch an instance from an image that has min_disk set to 2GB, then create an image from the instance, the min_disk attribute is not set correctly on the image (it's set to 0). Instead of being set as an attribute, it exists as a property instead. This can cause issues when other services rely on min_disk to make decisions about size (e.g. bug 1368600 for Horizon, not sure if Cinder is affected too). This doesn't seem to happen when creating a basic instance from an instance, only when there is also a volume involved. I'm not sure if this is a nova or glance issue so I'm opening a task on both for now. Steps to reproduce (done on a recent devstack) 1. Create a new image with e.g. min_disk 2GB $ glance image-create --name mindisk2gb --disk-format qcow2 --container-format bare --location https://launchpad.net/cirros/trunk/0.3.0/+download/cirros-0.3.0-i386-disk.img --min-disk 2 +--+--+ | Property | Value| +--+--+ | checksum | None | | container_format | bare | | created_at | 2014-09-16T12:35:33 | | deleted | False| | deleted_at | None | | disk_format | qcow2| | id | 9bbed3a5-00bf-4901-855e-556ca02e7fb7 | | is_public| False| | min_disk | 2| <-- min_disk set as expected | min_ram | 0| | name | mindisk2gb | | owner| eb6acc49df4b4390a99c722ded526284 | | protected| False| | size | 9159168 | <-- size looks ok | status | active | | updated_at | 2014-09-16T12:35:37 | | virtual_size | None | +--+--+ 2. Boot an instance from this image, backed by a volume (I believe this matches what happens when launching with "Image (creates a new volume)" in Horizon) $ nova boot --flavor 4115a835-04f0-4457-b93c-1817bc44812c --block-device device='/dev/vda',source='image',dest='volume',id='9bbed3a5-00bf-4901-855e-556ca02e7fb7',size=2,bootindex=0 my_instance +--+--+ | Property | Value | +--+--+ | OS-DCF:diskConfig| MANUAL | | OS-EXT-AZ:availability_zone | nova | | OS-EXT-STS:power_state | 0 | | OS-EXT-STS:task_state| - | | OS-EXT-STS:vm_state | building | | OS-SRV-USG:launched_at | - | | OS-SRV-USG:terminated_at | - | | accessIPv4 | | | accessIPv6 | | | adminPass| Uo2DL64GaY74 | | config_drive | | | created | 2014-09-16T12:55:30Z | | flavor | m1.lowmem (4115a835-04f0-4457-b93c-1817bc44812c) | | hostId | | | id | 3e70fd2e-1dc6-4001-941e-9496a9514882 | | image| Attempt to boot from volume - no image su
[Yahoo-eng-team] [Bug 1513230] Re: Users have cross-tenant visibility on images
** 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/1513230 Title: Users have cross-tenant visibility on images Status in Glance: Invalid Bug description: Using Kilo 2015.1.2 and Glance Client 0.17.0: Using two users (demo in the demo tenant, alt_demo in the alt_demo tenant, neither have the admin role), I am able to create an image with is_public set to False as the demo user/tenant, and then show data/use that image to create an instance as the alt_demo: > env | grep OS_ OS_PASSWORD=secret OS_AUTH_URL=http://localhost:5000/v2.0 OS_USERNAME=demo OS_TENANT_NAME=demo > glance image-create --container-format bare --disk-format raw --is-public false --name demo_image +--+--+ | Property | Value| +--+--+ | checksum | None | | container_format | bare | | created_at | 2015-11-04T21:33:14.00 | | deleted | False| | deleted_at | None | | disk_format | raw | | id | 51215efe-3533-4128-a36f-a44e507df5d7 | | is_public| False| | min_disk | 0| | min_ram | 0| | name | demo_image | | owner| None | | protected| False| | size | 0| | status | queued | | updated_at | 2015-11-04T21:33:14.00 | | virtual_size | None | +--+--+ The image then does not appear in image-list: > glance image-list +--++-+--+---++ | ID | Name | Disk Format | Container Format | Size | Status | +--++-+--+---++ | 7eb66946-70c1-4d35-93d8-93a315710be9 | tempest_alt_image | raw | bare | 947466240 | active | | 50eccbfd-baf3-4f0e-a10d-c20292b01d9d | tempest_main_image | raw | bare | 947466240 | active | +--++-+--+---++ With --all-tenants, it appears > glance image-list --all-tenants +--++-+--+---++ | ID | Name | Disk Format | Container Format | Size | Status | +--++-+--+---++ | 51215efe-3533-4128-a36f-a44e507df5d7 | demo_image | raw | bare | | queued | | 7eb66946-70c1-4d35-93d8-93a315710be9 | tempest_alt_image | raw | bare | 947466240 | active | | 50eccbfd-baf3-4f0e-a10d-c20292b01d9d | tempest_main_image | raw | bare | 947466240 | active | | 8f1430dc-8fc0-467b-b006-acf6b481714e | test_snapshot | raw | bare | | active | +--++-+--+---++ With image-show and the name, error message: > glance image-show demo_image No image with a name or ID of 'demo_image' exists. With image-show and the uuid, data: > glance image-show 51215efe-3533-4128-a36f-a44e507df5d7 +--+--+ | Property | Value| +--+--+ | container_format | bare | | created_at | 2015-11-04T21:33:14.00 | | deleted | False| | disk_format | raw | | id | 51215efe-3533-4128-a36f-a44e507df5d7 | | is_public| False| | min_disk | 0| | min_ram | 0| | name | demo_image | | protected| False
[Yahoo-eng-team] [Bug 1512231] [NEW] Glance doesn't return direct_url if location is None.
Public bug reported: When turn on the show_image_direct_url option, the image-show should return the image's direct_url. If the image has no locations, it should return []. But now Glance return nothing when show a queued image. We should make the behavior same as the show_multiple_locations option does. ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: glance Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1512231 Title: Glance doesn't return direct_url if location is None. Status in Glance: New Bug description: When turn on the show_image_direct_url option, the image-show should return the image's direct_url. If the image has no locations, it should return []. But now Glance return nothing when show a queued image. We should make the behavior same as the show_multiple_locations option does. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1512231/+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 1493026] Re: location-add return error when add new location to 'queued' image
** Description changed: Reproduce: 1. create a new image: glance image-create --disk-format qcow2 --container-format bare --name test suppose the image'id is 1 2.add location to the image: glance location-add 1 --url Result : the client raise an error:'The administrator has disabled API access to image locations'. - But when use REST API to reproduce the step 2, it runs well and the image's status will be changed into 'active'. - According to the code: https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L735-L750 - I think we should add check in glance like client does. + 3.set show_multiple_locations = True in glance-api.conf. Then take step + 1,2. It works now. + + But when use REST API to reproduce it, No matter show_multiple_locations + is False or True, it runs both well and the image's status will be + changed into 'active'. + + So there are one thing to discuess: Is it need to check the location in + glance-client(show_multiple_locations)? Or Is it need to add the check + like glance-client does in Glance server on the contrary? ** Also affects: python-glanceclient Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1493026 Title: location-add return error when add new location to 'queued' image Status in Glance: Opinion Status in python-glanceclient: New Bug description: Reproduce: 1. create a new image: glance image-create --disk-format qcow2 --container-format bare --name test suppose the image'id is 1 2.add location to the image: glance location-add 1 --url Result : the client raise an error:'The administrator has disabled API access to image locations'. 3.set show_multiple_locations = True in glance-api.conf. Then take step 1,2. It works now. But when use REST API to reproduce it, No matter show_multiple_locations is False or True, it runs both well and the image's status will be changed into 'active'. So there are one thing to discuess: Is it need to check the location in glance-client(show_multiple_locations)? Or Is it need to add the check like glance-client does in Glance server on the contrary? To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1493026/+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 1508359] Re: Can't create images with specified owner in v2
** This bug is no longer a duplicate of bug 1499368 Image Create does not allow admins to set owner ** Changed in: glance Status: In Progress => Invalid ** Changed in: glance Assignee: wangxiyuan (wangxiyuan) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1508359 Title: Can't create images with specified owner in v2 Status in Glance: Invalid Bug description: Reproduce: env: devstack-glance(master), ubuntu 14.04, tenant:admin,demo 1.use admin tenant. 2.create an image with command: glance image-create --owner (demo tenant id) result: 403 Forbidden: Attribute 'owner' is reserved. (HTTP 403) except: the image could be created and its owner should be demo tenant. when use the "glance help image-create" command with glance-client, it shows that the owner could be sent as a parameter.and we can also update the image's owner with image-update api. So I think we should support to create an image with onwer. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1508359/+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 1508359] [NEW] Can't create images with specified owner in v2
Public bug reported: Reproduce: env: devstack-glance(master), ubuntu 14.04, tenant:admin,demo 1.use admin tenant. 2.create an image with command: glance image-create --owner (demo tenant id) result: 403 Forbidden: Attribute 'owner' is reserved. (HTTP 403) except: the image could be created and its owner should be demo tenant. when use the "glance help image-create" command with glance-client, it shows that the owner could be sent as a parameter.and we can also update the image's owner with image-update api. So I think we should support to create an image with onwer. ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: glance Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1508359 Title: Can't create images with specified owner in v2 Status in Glance: New Bug description: Reproduce: env: devstack-glance(master), ubuntu 14.04, tenant:admin,demo 1.use admin tenant. 2.create an image with command: glance image-create --owner (demo tenant id) result: 403 Forbidden: Attribute 'owner' is reserved. (HTTP 403) except: the image could be created and its owner should be demo tenant. when use the "glance help image-create" command with glance-client, it shows that the owner could be sent as a parameter.and we can also update the image's owner with image-update api. So I think we should support to create an image with onwer. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1508359/+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 1492702] Re: import task doesn't check image properties
** Changed in: glance
Status: In Progress => Invalid
** Changed in: glance
Assignee: wangxiyuan (wangxiyuan) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1492702
Title:
import task doesn't check image properties
Status in Glance:
Invalid
Bug description:
Reproduce:
Create a import task like:
{
"type":"import",
"input":{
"import_from":"http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img;,
"import_from_format":"",
"image_properties":{
"disk_format":"wrong-format",
"container_format":"wrong-format",
"name":"test-task"
}
}
}
Expect : raise an error, image_properties is invalid.
Actual : the task is done successful. but the image's disk_format or
container_format is "wrong-format".
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1492702/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1505474] [NEW] Glance raise 500 error when change image's status to unallowed stauts
Public bug reported: When user try to change the image's status to unallowed status, such as deactivated --> pending-delete, it will rasie a 500 error. It's not clear to user. So we should catch this error and return to user. ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: glance Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1505474 Title: Glance raise 500 error when change image's status to unallowed stauts Status in Glance: New Bug description: When user try to change the image's status to unallowed status, such as deactivated --> pending-delete, it will rasie a 500 error. It's not clear to user. So we should catch this error and return to user. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1505474/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1501233] [NEW] DB downgrade doesn't be supported in OpenStack Now
Public bug reported: As downgrade are not supported after Kilo with OpenStack, we should remove them now. Roll backs can be performed as mentioned in the below link: http://docs.openstack.org/openstack-ops/content/ops_upgrades-roll- back.html ** 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/1501233 Title: DB downgrade doesn't be supported in OpenStack Now Status in Glance: New Bug description: As downgrade are not supported after Kilo with OpenStack, we should remove them now. Roll backs can be performed as mentioned in the below link: http://docs.openstack.org/openstack-ops/content/ops_upgrades-roll- back.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1501233/+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 1493026] Re: location-add return error when add new location to 'queued' image
don't have any good way to solve it now. need discussion. ** Changed in: glance Status: In Progress => Opinion ** Changed in: glance Assignee: wangxiyuan (wangxiyuan) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1493026 Title: location-add return error when add new location to 'queued' image Status in Glance: Opinion Bug description: Reproduce: 1. create a new image: glance image-create --disk-format qcow2 --container-format bare --name test suppose the image'id is 1 2.add location to the image: glance location-add 1 --url Result : the client raise an error:'The administrator has disabled API access to image locations'. But when use REST API to reproduce the step 2, it runs well and the image's status will be changed into 'active'. According to the code: https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L735-L750 I think we should add check in glance like client does. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1493026/+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 1495884] Re: image's backend file was deleted while it was still being use.
https://blueprints.launchpad.net/glance/+spec/add-location-manage- mechanism ** Changed in: glance Status: New => Invalid ** Changed in: glance Assignee: wangxiyuan (wangxiyuan) => (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1495884 Title: image's backend file was deleted while it was still being use. Status in Glance: Invalid Bug description: Reproduce: 1.create an image A, add backend 'X' to it's location . 2.create another image B, add the same backend 'X' to it's location. 3.show the two image, their status are both 'active'. 4.delete image A. After this setep, the backend X will be deleted as well. 5. show the image B. Its status is still 'active'. Obviously, image B's backend file 'X' has been deleted, So B can't be use anymore. So IMHO, before we delete the backend file, we should check that whether the file is being use. If yes, we should not delete it directly. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1495884/+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 1488311] Re: import task still in progress although there occured an error
the same bug : https://bugs.launchpad.net/glance/+bug/1495519
** Changed in: glance
Status: In Progress => Invalid
** Changed in: glance
Assignee: wangxiyuan (wangxiyuan) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1488311
Title:
import task still in progress although there occured an error
Status in Glance:
Invalid
Bug description:
Reproduce:
Create a import task like:
{
"type":"import",
"input":{
"import_from":"file://wrong_address", #1. wrong image address
# 2.lack of "import_from_format" , or even "import_from",
"image_properties"
"image_properties":{
"disk_format":"qcow2",
"container_format":"bare",
"name":"test-task1"
}
}
}
It will return an error :
1. URLError:
2. Invalid: Input does not contain 'import_from_format' field
But command 'glance task-show task_id' : return that the task
status still in progress and will never be chaned.
Expect result : Task status is changed into failure.
The reason is that glance only checked the parameters before taskflow
start, but didn't do any dispose about task status.
As in taskflow, it has checked the parameters already, we could remove
the checking before the taskflow.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1488311/+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 1495884] [NEW] image's backend file was deleted while it was still being use.
Public bug reported: Reproduce: 1.create an image A, add backend 'X' to it's location . 2.create another image B, add the same backend 'X' to it's location. 3.show the two image, their status are both 'active'. 4.delete image A. After this setep, the backend X will be deleted as well. 5. show the image B. Its status is still 'active'. Obviously, image B's backend file 'X' has been deleted, So B can't be use anymore. So IMHO, before we delete the backend file, we should check that whether the file is being use. If yes, we should not delete it directly. ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: glance Assignee: (unassigned) => wangxiyuan (wangxiyuan) ** Summary changed: - image's location was deleted while it was still being use. + image's backend file was deleted while it was still being use. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1495884 Title: image's backend file was deleted while it was still being use. Status in Glance: New Bug description: Reproduce: 1.create an image A, add backend 'X' to it's location . 2.create another image B, add the same backend 'X' to it's location. 3.show the two image, their status are both 'active'. 4.delete image A. After this setep, the backend X will be deleted as well. 5. show the image B. Its status is still 'active'. Obviously, image B's backend file 'X' has been deleted, So B can't be use anymore. So IMHO, before we delete the backend file, we should check that whether the file is being use. If yes, we should not delete it directly. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1495884/+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 1493026] Re: location-add return error when add new location to 'queued' image
** Description changed: Reproduce: 1. create a new image: glance image-create --disk-format qcow2 --container-format bare --name test suppose the image'id is 1 2.add location to the image: glance location-add 1 --url - - Result : the client raise an error:'The administrator has disabled API access to image locations'. - + Result : the client raise an error:'The administrator has disabled API + access to image locations'. But when use REST API to reproduce the step 2, it runs well and the image's status will be changed into 'active'. + According to the code: https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L735-L750 + I think we should add check in glance like client does. ** Project changed: python-glanceclient => glance -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1493026 Title: location-add return error when add new location to 'queued' image Status in Glance: In Progress Bug description: Reproduce: 1. create a new image: glance image-create --disk-format qcow2 --container-format bare --name test suppose the image'id is 1 2.add location to the image: glance location-add 1 --url Result : the client raise an error:'The administrator has disabled API access to image locations'. But when use REST API to reproduce the step 2, it runs well and the image's status will be changed into 'active'. According to the code: https://github.com/openstack/glance/blob/master/glance/api/v2/images.py#L735-L750 I think we should add check in glance like client does. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1493026/+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 1495346] [NEW] metadata_object missed _validate_limit function
Public bug reported: in api/v2/metadef_objects.py, The Class RequestDeserializer lost _validate_limit function. It's will lead an error that index can't get the limit parameter. ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: glance Assignee: (unassigned) => wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1495346 Title: metadata_object missed _validate_limit function Status in Glance: New Bug description: in api/v2/metadef_objects.py, The Class RequestDeserializer lost _validate_limit function. It's will lead an error that index can't get the limit parameter. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1495346/+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 1492702] [NEW] import task doesn't check image properties
Public bug reported:
Reproduce:
Create a import task like:
{
"type":"import",
"input":{
"import_from":"http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img;,
"import_from_format":"",
"image_properties":{
"disk_format":"wrong-format",
"container_format":"wrong-format",
"name":"test-task"
}
}
}
Expect : raise an error, image_properties is invalid.
Actual : the task is done successful. but the image's disk_format or
container_format is "wrong-format".
** Affects: glance
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: glance
Assignee: (unassigned) => wangxiyuan (wangxiyuan)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1492702
Title:
import task doesn't check image properties
Status in Glance:
New
Bug description:
Reproduce:
Create a import task like:
{
"type":"import",
"input":{
"import_from":"http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img;,
"import_from_format":"",
"image_properties":{
"disk_format":"wrong-format",
"container_format":"wrong-format",
"name":"test-task"
}
}
}
Expect : raise an error, image_properties is invalid.
Actual : the task is done successful. but the image's disk_format or
container_format is "wrong-format".
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1492702/+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 1489212] [NEW] 'Public' and 'Protect' cant' be set to True in metadata
Public bug reported: Reproduce: 1.Click System - Metadata Definitions 2.Set 'Public' or 'Protected' to False in any section. 3.Set them to True. But it can't work and still be False. ** Affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1489212 Title: 'Public' and 'Protect' cant' be set to True in metadata Status in OpenStack Dashboard (Horizon): New Bug description: Reproduce: 1.Click System - Metadata Definitions 2.Set 'Public' or 'Protected' to False in any section. 3.Set them to True. But it can't work and still be False. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1489212/+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 1488360] [NEW] CONF.task.task_time_to_live doesn't work
Public bug reported:
Reproduce:
1.set task_time_to_live to 1 in glance-api.conf:
task_time_to_live = 1
2. restart glance-api
3. create a import task
{
type:import,
input:{
import_from:http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img;,
import_from_format:,
image_properties:{
disk_format:qcow2,
container_format:bare,
name:test-task
}
}
}
4. wait for task success
5. show the task:
glance task-show
Expect : updated_at and expires_at should have the difference of 1 hours.
Actual : they have the difference of 48 hours, which is the default value of
task_time_to_live.
The reason is that taskflow created a different task object from the one
created by the glance api. And the task_time_to_live was set to default
48 when taskflow get it.
** Affects: glance
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: glance
Assignee: (unassigned) = wangxiyuan (wangxiyuan)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1488360
Title:
CONF.task.task_time_to_live doesn't work
Status in Glance:
New
Bug description:
Reproduce:
1.set task_time_to_live to 1 in glance-api.conf:
task_time_to_live = 1
2. restart glance-api
3. create a import task
{
type:import,
input:{
import_from:http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img;,
import_from_format:,
image_properties:{
disk_format:qcow2,
container_format:bare,
name:test-task
}
}
}
4. wait for task success
5. show the task:
glance task-show
Expect : updated_at and expires_at should have the difference of 1 hours.
Actual : they have the difference of 48 hours, which is the default value
of task_time_to_live.
The reason is that taskflow created a different task object from the
one created by the glance api. And the task_time_to_live was set to
default 48 when taskflow get it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1488360/+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 1488311] [NEW] import task still in progress although there occured an error
Public bug reported:
Reproduce:
Create a import task like:
{
type:import,
input:{
import_from:file://wrong_address, #1. wrong image address
# 2.lack of import_from_format , or even import_from,
image_properties
image_properties:{
disk_format:qcow2,
container_format:bare,
name:test-task1
}
}
}
It will return an error :
1. URLError: urlopen error The given uri is not valid. Please specify a valid
uri from the following list of supported uri ['http']
2. Invalid: Input does not contain 'import_from_format' field
But command 'glance task-show task_id' : return that the task status
still in progress and will never be chaned.
Expect result : Task status is changed into failure.
The reason is that glance only checked the parameters before taskflow
start, but didn't do any dispose about task status.
As in taskflow, it has checked the parameters already, we could remove
the checking before the taskflow.
** Affects: glance
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: glance
Assignee: (unassigned) = wangxiyuan (wangxiyuan)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1488311
Title:
import task still in progress although there occured an error
Status in Glance:
New
Bug description:
Reproduce:
Create a import task like:
{
type:import,
input:{
import_from:file://wrong_address, #1. wrong image address
# 2.lack of import_from_format , or even import_from,
image_properties
image_properties:{
disk_format:qcow2,
container_format:bare,
name:test-task1
}
}
}
It will return an error :
1. URLError: urlopen error The given uri is not valid. Please specify a
valid uri from the following list of supported uri ['http']
2. Invalid: Input does not contain 'import_from_format' field
But command 'glance task-show task_id' : return that the task
status still in progress and will never be chaned.
Expect result : Task status is changed into failure.
The reason is that glance only checked the parameters before taskflow
start, but didn't do any dispose about task status.
As in taskflow, it has checked the parameters already, we could remove
the checking before the taskflow.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1488311/+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 1488303] [NEW] ‘result’ and 'message' are in wrong order
Public bug reported: According to Task class in glance.domain.__init__ .py: https://github.com/openstack/glance/blob/master/glance/domain/__init__.py#L352 'message' should after 'result' in TaskFactory.new_task: https://github.com/openstack/glance/blob/master/glance/domain/__init__.py#L479 ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: In Progress ** Changed in: glance Assignee: (unassigned) = wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1488303 Title: ‘result’ and 'message' are in wrong order Status in Glance: In Progress Bug description: According to Task class in glance.domain.__init__ .py: https://github.com/openstack/glance/blob/master/glance/domain/__init__.py#L352 'message' should after 'result' in TaskFactory.new_task: https://github.com/openstack/glance/blob/master/glance/domain/__init__.py#L479 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1488303/+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 1484860] [NEW] http doesn't pass auth_token to backend
Public bug reported: In some use cases, The http backend should get and pass the auth-token information in the context. And it should ensure that the auth-token is safe encode. For example, if user try to get images from other glance instances, they will need the auth-token. So we should pass context if needed. This is not a bug, but it's worth to do it I think. ** Affects: glance Importance: Undecided Status: Invalid ** Changed in: glance Status: New = Incomplete ** Changed in: glance Status: Incomplete = New ** 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/1484860 Title: http doesn't pass auth_token to backend Status in Glance: Invalid Bug description: In some use cases, The http backend should get and pass the auth-token information in the context. And it should ensure that the auth-token is safe encode. For example, if user try to get images from other glance instances, they will need the auth-token. So we should pass context if needed. This is not a bug, but it's worth to do it I think. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1484860/+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 1481154] [NEW] Glace return HTTPInternalServerError when use postgresql
Public bug reported: version: master db: postgreSQL reproduce: 1.create one or more images without data, like: glance image-create --name xxx or glance image-create then we will get image information though 'glance image-list', like: +--+--+-+--+-++ | ID | Name | Disk Format | Container Format | Size| Status | +--+--+-+--+-++ | 67b47035-3e70-4dd0-a5a7-3fc3350a26ee | cirros-0.3.0-x86_64-disk | qcow2 | bare | 9761280 | active | | bf8022ef-3e3a-4bef-8d13-ccea9000828f | test | | | | queued | | 0180e9f2-6506-46c7-be07-e67ee6d5dab8 | test2| | | | queued | | 505bbc97-f470-44b7-bb59-315a5d92d8e0 | test3| | | | queued | | 03ef4387-f276-40dc-9aa6-ad811eb3c466 | test5| | | | queued | | 5af5d95d-8c2f-4bec-9fdd-74ce9ce3a4ca | | | | | queued | +--+--+-+--+-++ 2.list image like : glance image-list --sort-key=size --page-size=3 (sort-key must be 'size', and page-size must be less than or equal to image amount ) then, glance will return an error: HTTPInternalServerError (HTTP 500) P.S.:When use mysql db, I didn't encounter this problem. ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: glance Assignee: (unassigned) = wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1481154 Title: Glace return HTTPInternalServerError when use postgresql Status in Glance: New Bug description: version: master db: postgreSQL reproduce: 1.create one or more images without data, like: glance image-create --name xxx or glance image-create then we will get image information though 'glance image-list', like: +--+--+-+--+-++ | ID | Name | Disk Format | Container Format | Size| Status | +--+--+-+--+-++ | 67b47035-3e70-4dd0-a5a7-3fc3350a26ee | cirros-0.3.0-x86_64-disk | qcow2 | bare | 9761280 | active | | bf8022ef-3e3a-4bef-8d13-ccea9000828f | test | | | | queued | | 0180e9f2-6506-46c7-be07-e67ee6d5dab8 | test2| | | | queued | | 505bbc97-f470-44b7-bb59-315a5d92d8e0 | test3| | | | queued | | 03ef4387-f276-40dc-9aa6-ad811eb3c466 | test5| | | | queued | | 5af5d95d-8c2f-4bec-9fdd-74ce9ce3a4ca | | | | | queued | +--+--+-+--+-++ 2.list image like : glance image-list --sort-key=size --page-size=3 (sort-key must be 'size', and page-size must be less than or equal to image amount ) then, glance will return an error: HTTPInternalServerError (HTTP 500) P.S.:When use mysql db, I didn't encounter this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1481154/+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 1479257] [NEW] error message 's format in image_member.py is not correct
Public bug reported:
When users try to get member list with a public image in api v2. It will
return an error:
glance --os-image-api-version 2 member-list --image-id
403 Forbidden: (u'Error fetching members of image %(image_id)s: %(inner_msg)s',
{'image_id': u'', 'inner_msg': u'Public images do not have members.'})
(HTTP 403)
The error information's format is not correct. It should be:
403 Forbidden: Error fetching members of image : Public images do
not have members. (HTTP 403)
** Affects: glance
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: glance
Assignee: (unassigned) = wangxiyuan (wangxiyuan)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1479257
Title:
error message 's format in image_member.py is not correct
Status in Glance:
New
Bug description:
When users try to get member list with a public image in api v2. It
will return an error:
glance --os-image-api-version 2 member-list --image-id
403 Forbidden: (u'Error fetching members of image %(image_id)s:
%(inner_msg)s', {'image_id': u'', 'inner_msg': u'Public images do not have
members.'}) (HTTP 403)
The error information's format is not correct. It should be:
403 Forbidden: Error fetching members of image : Public images do
not have members. (HTTP 403)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1479257/+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 1477912] Re: size still exist when create image with incomplete parameter in api v1
** Changed in: glance Status: New = Invalid ** Changed in: glance Assignee: wangxiyuan (wangxiyuan) = (unassigned) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1477912 Title: size still exist when create image with incomplete parameter in api v1 Status in Glance: Invalid Bug description: version:Glance master Reproduce: 1. glance image-create --file --name test(in my env, image file's size is 642580480B) Then An error raised: 400 Bad Request: Disk format is not specified. (HTTP 400) 2. glance image-list list information: ID | Name | Disk Format | Container Format | Size | Status xxx | test | | |642580480 | queued except: There should not leave 'size' in the list. ID | Name | Disk Format | Container Format | Size | Status xxx | test | | | | queued There is no bug in api v2. Only occured in api v1 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1477912/+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 1477912] [NEW] size still exist when create image with incomplete parameter in api v1
Public bug reported: version:Glance master Reproduce: 1. glance image-create --file --name test(in my env, image file's size is 642580480B) Then An error raised: 400 Bad Request: Disk format is not specified. (HTTP 400) 2. glance image-list list information: ID | Name | Disk Format | Container Format | Size | Status xxx | test | | |642580480 | queued except: There should not leave 'size' in the list. ID | Name | Disk Format | Container Format | Size | Status xxx | test | | | | queued There is no bug in api v2. Only occured in api v1 ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: glance Assignee: (unassigned) = wangxiyuan (wangxiyuan) ** Description changed: version:Glance master Reproduce: 1. glance image-create --file --name test(in my env, image file's size is 642580480B) -Then An error raised: 400 Bad Request: Disk format is not specified. (HTTP 400) + Then An error raised: 400 Bad Request: Disk format is not specified. (HTTP 400) 2. glance image-list - list information: - +--+-+---+---+-++ - | ID | Name | Disk Format | Container Format | Size | Status | - +--+-+---+---+-++ - | b2e8b309-d40f-4399-b34f-44bfdf6791e0 | test | | | 642580480 | queued | - +--+-+---+---+-++ + list information: + +--+-+---+ + | ID| Name | Disk Format | Container Format | Size | Status |+--+-+---+--- + | b2e8b309-d40f-4399-b34f-44bfdf6791e0 | test || | 642580480 | queued | + +--+-+---+ except: without 'size' - +--+-+---+---+-++ - | ID | Name | Disk Format | Container Format | Size | Status | - +--+-+---+---+-++ - | b2e8b309-d40f-4399-b34f-44bfdf6791e0 | test | | | | queued | - +--+-+---+---+-++ - + +--+-+---+ + | ID| Name | Disk Format | Container Format | Size | Status |+--+-+---+--- + | b2e8b309-d40f-4399-b34f-44bfdf6791e0 | test || | | queued | + +--+-+---+ There is no bug in api v2. Only occured in api v1 ** Description changed: version:Glance master Reproduce: 1. glance image-create --file --name test(in my env, image file's size is 642580480B) Then An error raised: 400 Bad Request: Disk format is not specified. (HTTP 400) 2. glance image-list list information: - +--+-+---+ - | ID| Name | Disk Format | Container Format | Size | Status |+--+-+---+--- - | b2e8b309-d40f-4399-b34f-44bfdf6791e0 | test || | 642580480 | queued | - +--+-+---+ + + ID | Name | Disk Format | Container Format | Size | Status + + xxx | test ||642580480 | queued except: without 'size' - +--+-+---+ - | ID| Name | Disk Format | Container Format | Size | Status |+--+-+---+--- - | b2e8b309-d40f-4399
[Yahoo-eng-team] [Bug 1460887] Re: when backup a vm booted from volume , the error information is not detailed
** Changed in: nova Status: In Progress = Invalid ** Changed in: nova Assignee: wangxiyuan (wangxiyuan) = (unassigned) -- 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/1460887 Title: when backup a vm booted from volume ,the error information is not detailed Status in OpenStack Compute (nova): Invalid Bug description: Now,when backup a vm booted from volume ,the error information is:The request is invalid. Users don't know why. So we can support more information like: It's not supported to backup volume backed instance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1460887/+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 1474236] [NEW] unexpect response when create an image with owner or locations in api v2
Public bug reported:
When create an image with the parameter 'owner' or 'locations' in api
v2, it will raise an error like:
403 Forbidden
Attribute 'owner' is reserved.
403 Forbidden
Attribute 'locations' is reserved.
Reproduce:
Create an image like:
POSThttp://hostip:v2/images
body:
{
name: v2_test,
tags: [
ubuntu,
quantal
],
disk_format: qcow2,
container_format: bare,
owner: x,
locations: [
{
url: xx,
metadata:{}
}
]
}
** Affects: glance
Importance: Undecided
Assignee: wangxiyuan (wangxiyuan)
Status: New
** Changed in: glance
Assignee: (unassigned) = wangxiyuan (wangxiyuan)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1474236
Title:
unexpect response when create an image with owner or locations in api
v2
Status in Glance:
New
Bug description:
When create an image with the parameter 'owner' or 'locations' in api
v2, it will raise an error like:
403 Forbidden
Attribute 'owner' is reserved.
403 Forbidden
Attribute 'locations' is reserved.
Reproduce:
Create an image like:
POSThttp://hostip:v2/images
body:
{
name: v2_test,
tags: [
ubuntu,
quantal
],
disk_format: qcow2,
container_format: bare,
owner: x,
locations: [
{
url: xx,
metadata:{}
}
]
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1474236/+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 1470047] Re: CLI fails to report an error after creating a snapshot from instance
The reason why image been deleted is that Nova didn't pass 'size' parameter to Glance,So it didn't go quota check in Glance. So I think it can be fixed in Nova. ** Project changed: glance = nova ** Changed in: nova Assignee: (unassigned) = wangxiyuan (wangxiyuan) -- 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/1470047 Title: CLI fails to report an error after creating a snapshot from instance Status in OpenStack Compute (Nova): New Status in Python client library for Nova: In Progress Bug description: Description of problem: The CLI fails to declare an error and stuck with Server snapshotting... 0 when a user tries to save a snapshot of an instance while his quota is too small. Version-Release number of selected component (if applicable): python-glanceclient-0.17.0-2.el7ost.noarch python-glance-2015.1.0-6.el7ost.noarch python-glance-store-0.4.0-1.el7ost.noarch openstack-glance-2015.1.0-6.el7ost.noarch openstack-nova-api-2015.1.0-13.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Edit /etc/glance/glance-api.conf set user_storage_quota with low space for creating snapshot from instance 2. openstack-service restart glance 3. Create a snapshot from instance via command line: 'nova image-create instanceName snapName --poll' Actual results: The CLI fails to declare an error and stuck with Server snapshotting... 0 Expected results: ERROR should be appeared indicating that quota is too small Additional info: log To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1470047/+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 1459491] Re: Unexpected result when create server booted from volume
** Changed in: nova Status: In Progress = Invalid ** Changed in: nova Assignee: wangxiyuan (wangxiyuan) = (unassigned) -- 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/1459491 Title: Unexpected result when create server booted from volume Status in OpenStack Compute (Nova): Invalid Bug description: Enviroment: flalvor :1 --- 1G disk. volume :aaa ,---2G,bootable,image:bbb, image:bbb 13M when boot from volume like this: nova boot --flavor 1 --nic net-id=xxx --boot-volume aaa it will rasie an error: FlavorDiskTooSmall when boot from volum like this: nova boot --flavor 1 --nic net-id=xxx --block-device id=bbb,source=image,dest=volume,size=2,bootindex=0 test2 it goes well. But,the second one is same with the first one.So,either the first or the second is unexcepted. I think the second one should raise 'FlavorDiskTooSmall' error. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1459491/+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 1471080] [NEW] Unexpected warning when create image without data
Public bug reported: When create a image without data via api v2.0. It will raise a warning like: 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. from the code: https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/api.py#L798 The reason is that 'location_data' 's value is [], not None. So the function '_image_locations_set' will be always executed. ** Affects: glance Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: glance Assignee: (unassigned) = wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1471080 Title: Unexpected warning when create image without data Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: When create a image without data via api v2.0. It will raise a warning like: 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. from the code: https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/api.py#L798 The reason is that 'location_data' 's value is [], not None. So the function '_image_locations_set' will be always executed. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1471080/+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 1470047] Re: CLI fails to report an error after creating a snapshot from instance
** Also affects: python-novaclient Importance: Undecided Status: New ** Changed in: glance Assignee: wangxiyuan (wangxiyuan) = (unassigned) ** Changed in: python-novaclient Assignee: (unassigned) = wangxiyuan (wangxiyuan) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1470047 Title: CLI fails to report an error after creating a snapshot from instance Status in OpenStack Image Registry and Delivery Service (Glance): New Status in Python client library for Nova: New Bug description: Description of problem: The CLI fails to declare an error and stuck with Server snapshotting... 0 when a user tries to save a snapshot of an instance while his quota is too small. Version-Release number of selected component (if applicable): python-glanceclient-0.17.0-2.el7ost.noarch python-glance-2015.1.0-6.el7ost.noarch python-glance-store-0.4.0-1.el7ost.noarch openstack-glance-2015.1.0-6.el7ost.noarch openstack-nova-api-2015.1.0-13.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Edit /etc/glance/glance-api.conf set user_storage_quota with low space for creating snapshot from instance 2. openstack-service restart glance 3. Create a snapshot from instance via command line: 'nova image-create instanceName snapName --poll' Actual results: The CLI fails to declare an error and stuck with Server snapshotting... 0 Expected results: ERROR should be appeared indicating that quota is too small Additional info: log To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1470047/+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 1461891] Re: Can't boot with bdm of which the source type is blank and destination is volume
** 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.launchpad.net/bugs/1461891 Title: Can't boot with bdm of which the source type is blank and destination is volume Status in OpenStack Compute (Nova): Invalid Bug description: Now,boot a vm like this: nova boot --flavor 1 --nic net-id=xxx--block-device source=blank,dest=volume,bootindex=0 without size in bdm. the vm state will be error .And error information is :No valid host was found. So,I think we can't boot a vm that there is no size in bdm when source=blank and dest=volume. We should checkt it in api side. and return code 400. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1461891/+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 1462393] Re: security group is Invalid when boot with port
** 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.launchpad.net/bugs/1462393 Title: security group is Invalid when boot with port Status in OpenStack Compute (Nova): Invalid Bug description: When create a vm with specified security group and ports,the security group is invalid.Because ports have their own security group. Perhaps users will be confused with this situation.They input security group parameter，but it doesn't work. So I think we should print a warning information in log files at least to point out that the security group is invalid with ports. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1462393/+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 1462393] [NEW] security group is Invalid when boot with port
Public bug reported: When create a vm with specified security group and ports,the security group is invalid.Because ports have their own security group. Perhaps users will be confused with this situation.They input security group parameter，but it doesn't work. So,IMO,there are two situations here: 1.boot only with ports. in this situation ,we shouldn't allow users boot and return code 400 to show that security group is invalid and unnecessary. 2.not only with ports but also with networks. in this situation,we should print a worning information in log files at least to point out that the security group is invalid with ports. ** Affects: nova Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: nova Assignee: (unassigned) = wangxiyuan (wangxiyuan) -- 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/1462393 Title: security group is Invalid when boot with port Status in OpenStack Compute (Nova): New Bug description: When create a vm with specified security group and ports,the security group is invalid.Because ports have their own security group. Perhaps users will be confused with this situation.They input security group parameter，but it doesn't work. So,IMO,there are two situations here: 1.boot only with ports. in this situation ,we shouldn't allow users boot and return code 400 to show that security group is invalid and unnecessary. 2.not only with ports but also with networks. in this situation,we should print a worning information in log files at least to point out that the security group is invalid with ports. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1462393/+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 1461891] [NEW] Can't boot with bdm of which the source type is blank and destination is volume
Public bug reported: Now,boot a vm like this: nova boot --flavor 1 --nic net-id=xxx--block-device source=blank,dest=volume,bootindex=0 without size in bdm. the vm state will be error .And error information is :No valid host was found. So,I think we can't boot a vm that there is no size in bdm when source=blank and dest=volume. We should checkt it in api side. and return code 400. ** Affects: nova Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: Confirmed ** Changed in: nova Assignee: (unassigned) = wangxiyuan (wangxiyuan) -- 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/1461891 Title: Can't boot with bdm of which the source type is blank and destination is volume Status in OpenStack Compute (Nova): Confirmed Bug description: Now,boot a vm like this: nova boot --flavor 1 --nic net-id=xxx--block-device source=blank,dest=volume,bootindex=0 without size in bdm. the vm state will be error .And error information is :No valid host was found. So,I think we can't boot a vm that there is no size in bdm when source=blank and dest=volume. We should checkt it in api side. and return code 400. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1461891/+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 1460528] [NEW] Some useless variables and parameters
Public bug reported: There are some uesless variables and parameters in nova.api.openstack.compute.server.py and nova.compute.api.py. nova.api.openstack.compute.server.py lines 650 except Exception as error -- except Exception nova.compute.api.py. lines 563 remove the context parameter. lines 1097 considertaion -- consideration ** Affects: nova Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: nova Assignee: (unassigned) = wangxiyuan (wangxiyuan) ** Description changed: - There are some uesless variables and parametesr in + There are some uesless variables and parameters in nova.api.openstack.compute.server.py and nova.compute.api.py. - nova.api.openstack.compute.server.py lines 650 except Exception as error -- except Exception nova.compute.api.py. lines 563 remove the context parameter. -lines 1097 considertaion -- consideration + lines 1097 considertaion -- consideration -- 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/1460528 Title: Some useless variables and parameters Status in OpenStack Compute (Nova): New Bug description: There are some uesless variables and parameters in nova.api.openstack.compute.server.py and nova.compute.api.py. nova.api.openstack.compute.server.py lines 650 except Exception as error -- except Exception nova.compute.api.py. lines 563 remove the context parameter. lines 1097 considertaion -- consideration To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1460528/+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 1460887] [NEW] when backup a vm booted from volume , the error information is not detailed
Public bug reported: Now,when backup a vm booted from volume ,the error information is:The request is invalid. Users don't know why. So we can support more information like: It's not supported to backup volume backed instance. ** Affects: nova Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Description changed: Now,when backup a vm booted from volume ,the error information is:The request is invalid. - User don't know why. + Users don't know why. So we can support more information like: It's not supported to backup volume backed instance. ** Changed in: nova Assignee: (unassigned) = wangxiyuan (wangxiyuan) -- 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/1460887 Title: when backup a vm booted from volume ,the error information is not detailed Status in OpenStack Compute (Nova): New Bug description: Now,when backup a vm booted from volume ,the error information is:The request is invalid. Users don't know why. So we can support more information like: It's not supported to backup volume backed instance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1460887/+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 1356737] Re: nova backup vm should not backup those vm boot from cinder volume
** Changed in: nova Status: In Progress = Fix Released -- 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/1356737 Title: nova backup vm should not backup those vm boot from cinder volume Status in OpenStack Compute (Nova): Fix Released Bug description: When doing backup on a vm which boot from cinder volume, it firstly shutdown vm and then do backup work. But it fails and the detail exception log could be seen in the last part. When we need nova to backup a vm booted from cinder volume, we could do this by using cinder's functioncopy volume to image. I think we could raise an exception when nova backup a vm from cinder volume. ==Nova-compute exception log=== Traceback (most recent call last): File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 134, in _dispatch_and_reply incoming.message)) File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 177, in _dispatch return self._do_dispatch(endpoint, method, ctxt, args) File /usr/local/lib/python2.7/dist-packages/oslo/messaging/rpc/dispatcher.py, line 123, in _do_dispatch result = getattr(endpoint, method)(ctxt, **new_args) File /opt/stack/nova/nova/exception.py, line 88, in wrapped payload) File /opt/stack/nova/nova/openstack/common/excutils.py, line 82, in __exit__ six.reraise(self.type_, self.value, self.tb) File /opt/stack/nova/nova/exception.py, line 71, in wrapped return f(self, context, *args, **kw) File /opt/stack/nova/nova/compute/manager.py, line 285, in decorated_function pass File /opt/stack/nova/nova/openstack/common/excutils.py, line 82, in __exit__ six.reraise(self.type_, self.value, self.tb) File /opt/stack/nova/nova/compute/manager.py, line 271, in decorated_function return function(self, context, *args, **kwargs) File /opt/stack/nova/nova/compute/manager.py, line 313, in decorated_function kwargs['instance'], e, sys.exc_info()) File /opt/stack/nova/nova/openstack/common/excutils.py, line 82, in __exit__ six.reraise(self.type_, self.value, self.tb) File /opt/stack/nova/nova/compute/manager.py, line 301, in decorated_function return function(self, context, *args, **kwargs) File /opt/stack/nova/nova/compute/manager.py, line 2741, in backup_instance self._do_snapshot_instance(context, image_id, instance, rotation) File /opt/stack/nova/nova/compute/manager.py, line 360, in decorated_function % image_id, instance=instance) File /opt/stack/nova/nova/openstack/common/excutils.py, line 82, in __exit__ six.reraise(self.type_, self.value, self.tb) File /opt/stack/nova/nova/compute/manager.py, line 351, in decorated_function *args, **kwargs) File /opt/stack/nova/nova/compute/manager.py, line 2729, in _do_snapshot_instance task_states.IMAGE_BACKUP) File /opt/stack/nova/nova/compute/manager.py, line 2807, in _snapshot_instance update_task_state) File /opt/stack/nova/nova/virt/libvirt/driver.py, line 1501, in snapshot image_type=source_format) File /opt/stack/nova/nova/virt/libvirt/imagebackend.py, line 716, in snapshot return backend(path=disk_path) File /opt/stack/nova/nova/virt/libvirt/imagebackend.py, line 421, in __init__ info = libvirt_utils.logical_volume_info(path) File /opt/stack/nova/nova/virt/libvirt/utils.py, line 336, in logical_volume_info '--separator', '|', path, run_as_root=True) File /opt/stack/nova/nova/virt/libvirt/utils.py, line 54, in execute return utils.execute(*args, **kwargs) File /opt/stack/nova/nova/utils.py, line 164, in execute return processutils.execute(*cmd, **kwargs) File /opt/stack/nova/nova/openstack/common/processutils.py, line 194, in execute cmd=' '.join(cmd)) ProcessExecutionError: Unexpected error while running command. Command: lvs -o vg_all,lv_all --separator | /dev/disk/by-path/ip-10.250.10.193:3260-iscsi-iqn.2010-10.org.openstack:volume-9ba91e05-050b-4dda-ac3c-9f3630c704c0-lun-1 Exit code: 5 Stdout: '' Stderr: ' disk/by-path/ip-10.250.10.193:3260-iscsi-iqn.2010-10.org.openstack:volume-9ba91e05-050b-4dda-ac3c-9f3630c704c0-lun-1: Invalid path for Logical Volume\n' To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1356737/+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 1459917] [NEW] Can't boot with bdm when use image in local
Public bug reported: when boot vm with bdm like this: nova boot --flavor 1 --nic net-id=2746e15a-b35a-4316-9b9a-792224f84499 --image 774b174a-a15a-492d-978d-74c3292a116e --block-device source=image,dest=local,id=774b174a-a15a-492d-978d-74c3292a116e,size=2,bootindex=0 test it rasie a error:Mapping image to local is not supported. But in nova it said : # if this bdm is generated from --image ,then # source_type = image and destination_type = local is allowed ** Affects: nova Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: nova Assignee: (unassigned) = wangxiyuan (wangxiyuan) -- 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/1459917 Title: Can't boot with bdm when use image in local Status in OpenStack Compute (Nova): New Bug description: when boot vm with bdm like this: nova boot --flavor 1 --nic net-id=2746e15a-b35a-4316-9b9a-792224f84499 --image 774b174a-a15a-492d-978d-74c3292a116e --block-device source=image,dest=local,id=774b174a-a15a-492d-978d-74c3292a116e,size=2,bootindex=0 test it rasie a error:Mapping image to local is not supported. But in nova it said : # if this bdm is generated from --image ,then # source_type = image and destination_type = local is allowed To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1459917/+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 1459491] [NEW] Unexpected result when create server booted from volume
Public bug reported: Enviroment: flalvor :1 --- 1G disk. volume :128c8c78-ff3d-4636-8c5a-e27660741ec0 ,---2G,bootable,image:774b174a-a15a-492d-978d-74c3292a116e, image:774b174a-a15a-492d-978d-74c3292a116e 13M when boot from volume like this: nova boot --flavor 1 --nic net-id=2746e15a-b35a-4316-9b9a-792224f84499 --boot-volume 128c8c78-ff3d-4636-8c5a-e27660741ec0 test1 it will rasie an error: FlavorDiskTooSmall when boot from volum like this: nova boot --flavor 2 --nic net-id=2746e15a-b35a-4316-9b9a-792224f84499 --block-device id=774b174a-a15a-492d-978d-74c3292a116e,source=image,dest=volume,size=2,bootindex=0 test2 it goes well. But,the second one is same with the first one.So,either the first or the second is unexcepted. I think the second one should raise 'FlavorDiskTooSmall' error. ** Affects: nova Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: nova Assignee: (unassigned) = wangxiyuan (wangxiyuan) ** Summary changed: - unexpect result when boot from volume + Unexpected result when create server booted from volume -- 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/1459491 Title: Unexpected result when create server booted from volume Status in OpenStack Compute (Nova): New Bug description: Enviroment: flalvor :1 --- 1G disk. volume :128c8c78-ff3d-4636-8c5a-e27660741ec0 ,---2G,bootable,image:774b174a-a15a-492d-978d-74c3292a116e, image:774b174a-a15a-492d-978d-74c3292a116e 13M when boot from volume like this: nova boot --flavor 1 --nic net-id=2746e15a-b35a-4316-9b9a-792224f84499 --boot-volume 128c8c78-ff3d-4636-8c5a-e27660741ec0 test1 it will rasie an error: FlavorDiskTooSmall when boot from volum like this: nova boot --flavor 2 --nic net-id=2746e15a-b35a-4316-9b9a-792224f84499 --block-device id=774b174a-a15a-492d-978d-74c3292a116e,source=image,dest=volume,size=2,bootindex=0 test2 it goes well. But,the second one is same with the first one.So,either the first or the second is unexcepted. I think the second one should raise 'FlavorDiskTooSmall' error. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1459491/+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 1443324] [NEW] spell mistake
Public bug reported: In nova.compute.api.py _check_and_transform_bdm method There are two words spelt error in comment wrote by gibi . outher - other unnecessasry - unnecessary ** Affects: nova Importance: Undecided Assignee: wangxiyuan (wangxiyuan) Status: New ** Changed in: neutron Assignee: (unassigned) = wangxiyuan (wangxiyuan) ** Summary changed: - nova spell mistake + spell mistake ** Project changed: neutron = nova -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1443324 Title: spell mistake Status in OpenStack Compute (Nova): New Bug description: In nova.compute.api.py _check_and_transform_bdm method There are two words spelt error in comment wrote by gibi . outher - other unnecessasry - unnecessary To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1443324/+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
