[Yahoo-eng-team] [Bug 1342811] Re: Bump up the min version of keystonemiddleware
Fixed by: https://github.com/openstack/requirements/commit/df1a6aa7c6fff171ed1ffe25b58273900c18d98d https://github.com/openstack/glance/commit/f41b305899d703f7604f3ae5ceb7cc95d67aa533 ** Changed in: glance Status: Opinion => Fix Committed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1342811 Title: Bump up the min version of keystonemiddleware Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Bug description: As per the question on this change :- https://review.openstack.org/#/c/102352/4/requirements.txt we could potentially have a invalid version installed in the environment. The answer to that question lead us to make the change in the global requirements:- https://review.openstack.org/#/c/102352/5/requirements.txt Keeping this bug open for the further discussion. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1342811/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1350713] Re: Store configuration error in sheepdog
It works as designed. ** Changed in: glance Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1350713 Title: Store configuration error in sheepdog Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: I have found following errors along with the "deprecated" warning 2014-07-30 21:05:14.971 9608 ERROR glance.store.sheepdog [-] Error in store configuration: [Errno 2] No such file or directory 2014-07-30 21:05:14.972 9608 WARNING glance.store [-] Deprecated: glance.store.sheepdog.Store not found in `known_store`. Stores need to be explicitly enabled in the configuration file. in the gate-tempest-dsvm-large-ops tests. Full stacktrace here: http://logs.openstack.org/51/106751/6/check/gate-tempest-dsvm-large- ops/640c35c/logs/screen-g-api.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1350713/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1351413] [NEW] DB migration failure due to 006_mysql_downgrade script handled mysql reserved word as column name wrongly
Public bug reported: Because 006_mysql_downgrade didn't correctly quote 'key' column [0][1] of 'image_properties' table when creating index [2], the index wasn't created as needed, and then operator could not run any upgrade script successfully since 006_mysql_upgrade script could not to handle this unexpected db status [3]. [0] http://dev.mysql.com/doc/mysqld-version-reference/en/mysqld-version-reference-reservedwords-5-5.html [1] http://dev.mysql.com/doc/mysqld-version-reference/en/mysqld-version-reference-reservedwords-5-0.html [2] https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/migrate_repo/versions/006_mysql_downgrade.sql#L11 [3] https://github.com/openstack/glance/blob/master/glance/db/sqlalchemy/migrate_repo/versions/006_mysql_upgrade.sql#L5 Note, this issue doesn't impact one-way upgrade migration operation, since bug existed in downgrade script. But once operator do a reciprocating migration operation, this issue will rise up. When I open "snake walk" mode on migration test, this issue could be triggered as well. == FAIL: glance.tests.unit.test_migrations.TestMigrations.test_walk_versions tags: worker-0 -- Traceback (most recent call last): File "glance/tests/unit/test_migrations.py", line 251, in test_walk_versions self._walk_versions(engine, self.snake_walk) File "glance/tests/unit/test_migrations.py", line 345, in _walk_versions self._migrate_up(engine, version) File "glance/tests/unit/test_migrations.py", line 394, in _migrate_up version) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/migrate/versioning/api.py", line 186, in upgrade return _migrate(url, repository, version, upgrade=True, err=err, **opts) File "", line 2, in _migrate File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/migrate/versioning/util/__init__.py", line 160, in with_engine return f(*a, **kw) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/migrate/versioning/api.py", line 366, in _migrate schema.runchange(ver, change, changeset.step) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/migrate/versioning/schema.py", line 93, in runchange change.run(self.engine, step) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/migrate/versioning/script/sql.py", line 43, in run conn.execute(text) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 721, in execute return self._execute_text(object, multiparams, params) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 870, in _execute_text statement, parameters File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 958, in _execute_context context) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1160, in _handle_dbapi_exception exc_info File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py", line 199, in raise_from_cause reraise(type(exception), exception, tb=exc_tb) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 951, in _execute_context context) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py", line 436, in do_execute cursor.execute(statement, parameters) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/MySQLdb/cursors.py", line 205, in execute self.errorhandler(self, exc, value) File "/home/lzy/workspace/openstack/glance/.tox/py27/local/lib/python2.7/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler raise errorclass, errorvalue OperationalError: (OperationalError) (1091, "Can't DROP 'ix_image_properties_image_id_key'; check that column/key exists") '/*\n * This file is necessary because MySQL does not support\n * renaming indexes.\n */\nDROP INDEX ix_image_properties_image_id_key ON image_properties;\n\n/* Rename the `key` column to `name` */\nALTER TABLE image_properties\nCHANGE COLUMN `key` name VARCHAR(255) NOT NULL;\n\nCREATE UNIQUE INDEX ix_image_properties_image_id_name ON image_properties (image_id, name);\n' () ** Affects: glance Importance: Undecided Status: Triaged ** Tags: db ** Tags added: db -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/13
[Yahoo-eng-team] [Bug 1326955] Re: v1 API GET on image member not implemented
** Changed in: glance Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1326955 Title: v1 API GET on image member not implemented Status in OpenStack Image Registry and Delivery Service (Glance): Won't Fix Bug description: Despite having a client call `glanceclient.image_members.get(image_id, member_id)` [1], the GET call on /v1/image//members/ is not implemented in the v1 API and returns a 405: Method Not Allowed error. I suspect that this was an unintentional omission. The method is listed in the router, but in image_members the comment indicates that a 405 response is intentional. [2,3] It shouldn't be hard for me to implement the fix, but I want to make sure that there wasn't an intentional reason for leaving the API call out? [1] https://github.com/openstack/python-glanceclient/blob/master/glanceclient/v1/image_members.py#L34 [2] https://github.com/openstack/glance/blob/master/glance/api/v1/router.py#L71 [3] https://github.com/openstack/glance/blob/master/glance/api/v1/members.py#L105 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1326955/+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 1343596] Re: utils not imported in store/swift.py
Currently Glance are using glance_store instead of owning backend drivers by own tree. And the issue has already been fixed in glance_store: https://github.com/openstack/glance_store/blob/master/glance_store/_drivers/swift/store.py#L121 . ** 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/1343596 Title: utils not imported in store/swift.py Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: glance/store/swift.py does not import utils from glance.common, yet utils is used here: https://github.com/openstack/glance/blob/master/glance/store/swift.py#L127 This causes the following traceback if swift returns an error (a 408 in my case): 014-07-17 16:45:19.949 22001 TRACE glance.api.v1.upload_utils Traceback (most recent call last): 2014-07-17 16:45:19.949 22001 TRACE glance.api.v1.upload_utils File "/opt/stack/glance/glance/api/v1/upload_utils.py", line 96, in upload_data_to_store 2014-07-17 16:45:19.949 22001 TRACE glance.api.v1.upload_utils store) 2014-07-17 16:45:19.949 22001 TRACE glance.api.v1.upload_utils File "/opt/stack/glance/glance/store/__init__.py", line 338, in store_add_to_backend 2014-07-17 16:45:19.949 22001 TRACE glance.api.v1.upload_utils (location, size, checksum, metadata) = store.add(image_id, data, size) 2014-07-17 16:45:19.949 22001 TRACE glance.api.v1.upload_utils File "/opt/stack/glance/glance/store/swift.py", line 563, in add 2014-07-17 16:45:19.949 22001 TRACE glance.api.v1.upload_utils "Got error from Swift: %s") % utils.exception_to_str(e)) 2014-07-17 16:45:19.949 22001 TRACE glance.api.v1.upload_utils NameError: global name 'utils' is not defined 2014-07-17 16:45:19.949 22001 TRACE glance.api.v1.upload_utils To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1343596/+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 1202963] Re: Unable to run g-api due to sheepdog store
*** This bug is a duplicate of bug 1202098 ***
https://bugs.launchpad.net/bugs/1202098
** This bug has been marked a duplicate of bug 1202098
glance-api failed to startup caused by UnicodeEncodeError in non-English
environment
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1202963
Title:
Unable to run g-api due to sheepdog store
Status in OpenStack Image Registry and Delivery Service (Glance):
New
Bug description:
I am using the latest devstack and openstack code. ./stack.sh will
prompt the following log for g-api:
===g-api===
2013-07-19 03:42:22.387 20198 DEBUG glance.store.location [-] Registering
scheme https with {'store_class': ,
'location_class': }
register_scheme_map /opt/stack/glance/glance/store/location.py:86
2013-07-19 03:42:22.387 20198 DEBUG glance.store [-] Attempting to import
store glance.store.rbd.Store _get_store_class
/opt/stack/glance/glance/store/__init__.py:144
2013-07-19 03:42:22.392 20198 DEBUG glance.store [-] Registering store with schemes ('rbd',) create_stores
/opt/stack/glance/glance/store/__init__.py:174
2013-07-19 03:42:22.393 20198 DEBUG glance.store.base [-] Late loading
location class glance.store.rbd.StoreLocation get_store_location_class
/opt/stack/glance/glance/store/base.py:68
2013-07-19 03:42:22.393 20198 DEBUG glance.store.location [-] Registering
scheme rbd with {'store_class': ,
'location_class': } register_scheme_map
/opt/stack/glance/glance/store/location.py:86
2013-07-19 03:42:22.393 20198 DEBUG glance.store [-] Attempting to import
store glance.store.s3.Store _get_store_class
/opt/stack/glance/glance/store/__init__.py:144
2013-07-19 03:42:22.398 20198 DEBUG glance.store [-] Registering store with schemes ('s3', 's3+http', 's3+https')
create_stores /opt/stack/glance/glance/store/__init__.py:174
2013-07-19 03:42:22.398 20198 DEBUG glance.store.base [-] Late loading
location class glance.store.s3.StoreLocation get_store_location_class
/opt/stack/glance/glance/store/base.py:68
2013-07-19 03:42:22.398 20198 DEBUG glance.store.location [-] Registering
scheme s3 with {'store_class': ,
'location_class': } register_scheme_map
/opt/stack/glance/glance/store/location.py:86
2013-07-19 03:42:22.398 20198 DEBUG glance.store.location [-] Registering
scheme s3+http with {'store_class': ,
'location_class': } register_scheme_map
/opt/stack/glance/glance/store/location.py:86
2013-07-19 03:42:22.399 20198 DEBUG glance.store.location [-] Registering
scheme s3+https with {'store_class': ,
'location_class': } register_scheme_map
/opt/stack/glance/glance/store/location.py:86
2013-07-19 03:42:22.399 20198 DEBUG glance.store [-] Attempting to import
store glance.store.swift.Store _get_store_class
/opt/stack/glance/glance/store/__init__.py:144
2013-07-19 03:42:22.434 20198 DEBUG glance.store [-] Registering store
with schemes ('swift+https', 'swift',
'swift+http') create_stores /opt/stack/glance/glance/store/__init__.py:174
2013-07-19 03:42:22.435 20198 DEBUG glance.store.base [-] Late loading
location class glance.store.swift.StoreLocation get_store_location_class
/opt/stack/glance/glance/store/base.py:68
2013-07-19 03:42:22.435 20198 DEBUG glance.store.location [-] Registering
scheme swift+https with {'store_class': ,
'location_class': }
register_scheme_map /opt/stack/glance/glance/store/location.py:86
2013-07-19 03:42:22.435 20198 DEBUG glance.store.location [-] Registering
scheme swift+http with {'store_class': ,
'location_class': }
register_scheme_map /opt/stack/glance/glance/store/location.py:86
2013-07-19 03:42:22.435 20198 DEBUG glance.store.location [-] Registering
scheme swift with {'store_class': ,
'location_class': }
register_scheme_map /opt/stack/glance/glance/store/location.py:86
2013-07-19 03:42:22.435 20198 DEBUG glance.store [-] Attempting to import
store glance.store.sheepdog.Store _get_store_class
/opt/stack/glance/glance/store/__init__.py:144
2013-07-19 03:42:22.443 20198 DEBUG glance.openstack.common.processutils [-]
Running cmd (subprocess): collie execute
/opt/stack/glance/glance/openstack/common/processutils.py:142
2013-07-19 03:42:22.474 20198 DEBUG glance.openstack.common.processutils [-]
Result was 127 execute
/opt/stack/glance/glance/openstack/common/processutils.py:167
2013-07-19 03:42:22.474 20198 ERROR glance.store.sheepdog [-]
储存配置错误：Unexpected error while running command.
Command: collie
Exit code: 127
Stdout: ''
Stderr: '/bin/sh: 1: collie: not found\n'
2013-07-19 03:42:22.495 20198 CRITICAL glance [-] 'ascii' codec can't encode
characters in position 0-7: ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1202963/+subscriptions
--
Maili
[Yahoo-eng-team] [Bug 1243715] Re: can't configure a location of image manually with a glance CLI command
Currently Glance don't support "copy or move an image to another location". ** 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/1243715 Title: can't configure a location of image manually with a glance CLI command Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Description of problem: the RFE , on glance's multiple location capabilities, resulted with the option to copy or move an image to another location, but this option isn't available in CLI or UI (horizon), and it should be added. Version-Release number of selected component (if applicable): How reproducible: openstack-glance-2013.2-0.12.rc1.el6ost.noarch To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1243715/+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 1214947] Re: chown in postinst fails on netapp storage
** 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/1214947 Title: chown in postinst fails on netapp storage Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: We have /var/lib/glance/images on an nfs share served from a netapp filer. Netapp exports have .snapshot directories that are read only, and the chown calls in glance-common's postinst fails on them. I suggest changing chown -R to find -xdev ... Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1214947/+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 1261738] Re: Openstack Glance: user_total_quota calculated incorrectly
I think we need do this to fix this defect, i verified it in my dev local. http://paste.openstack.org/show/55299/ ** Changed in: glance Status: Invalid => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1261738 Title: Openstack Glance: user_total_quota calculated incorrectly Status in OpenStack Image Registry and Delivery Service (Glance): Confirmed Bug description: Description of problem: Bug in quota calculation, if an image upload fails due to quota limit, the failed image size is still added to total storage sum figure! Thus future images may fail to upload even if it looks as quota hasn’t been reached yet. Version-Release number of selected component (if applicable): RHEL 6.5 python-glanceclient-0.12.0-1.el6ost.noarch openstack-glance-2013.2-5.el6ost.noarch python-glance-2013.2-5.el6ost.noarch How reproducible: Steps to Reproduce: 1. vim /etc/glance/glance-api.conf user_storage_quota = 250mb (in byets) 2. service glance-api restart 3. Upload test small image - would be ok 4. Upload large image say 4Giga, - should fail with "Error unable to create new image" 5. Try to upload another small file say 49MB. Actual results: If the large i,age file or sum of failed uploaded images are more than the quota, any image size will fail to upload. Expected results: I should be able to upload as long as the sum of all my images is less than configured qouta. Additional info: Mysql show databases; connect glance; SELECT * FROM images; Noticed all the images i tired, initial successful uploaded image status=”active”, images that i deleted status=”deleted”, images that failed to upload due to quota status=”killed” I than calculated the sum of all the “killed” images. Set a new quota of the above calculated value + 100MB, restarted glance-api service. Only than i was able to upload another image of 49MB. When i set a lower quota value (below the calculated sum of all the killed images) wasn’t able to upload any image. Images of status killed, which fail upload for any reason, should not be added to total storage sum calcualtion or quota. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1261738/+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 1398656] Re: ceilometer import oslo.concurrency failed issue
** Also affects: glance-store 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/1398656 Title: ceilometer import oslo.concurrency failed issue Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: Fix Committed Status in Designate: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in OpenStack Glance backend store-drivers library (glance_store): In Progress Status in OpenStack Bare Metal Provisioning Service (Ironic): Fix Released Status in OpenStack Identity (Keystone): Fix Committed Status in OpenStack Compute (Nova): Fix Released Bug description: during ceilometer review and find jenkis failed with following message: 2014-12-03 01:28:04.969 | pep8 runtests: PYTHONHASHSEED='0' 2014-12-03 01:28:04.969 | pep8 runtests: commands[0] | flake8 2014-12-03 01:28:04.970 | /home/jenkins/workspace/gate-ceilometer-pep8$ /home/jenkins/workspace/gate-ceilometer-pep8/.tox/pep8/bin/flake8 2014-12-03 01:28:21.508 | ./ceilometer/utils.py:30:1: H302 import only modules.'from oslo.concurrency import processutils' does not import a module 2014-12-03 01:28:21.508 | from oslo.concurrency import processutils 2014-12-03 01:28:21.508 | ^ 2014-12-03 01:28:21.508 | ./ceilometer/ipmi/platform/ipmitool.py:19:1: H302 import only modules.'from oslo.concurrency import processutils' does not import a module 2014-12-03 01:28:21.508 | from oslo.concurrency import processutils 2014-12-03 01:28:21.508 | ^ 2014-12-03 01:28:21.696 | ERROR: InvocationError: '/home/jenkins/workspace/gate-ceilometer-pep8/.tox/pep8/bin/flake8' 2014-12-03 01:28:21.697 | pep8 runtests: commands[1] | flake8 --filename=ceilometer-* bin This seems https://github.com/openstack/oslo.concurrency/blob/master/oslo_concurrency/processutils.py should change to from oslo_concurrency import processutils To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1398656/+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 1372422] Re: Glance exploding on configuration parsing
** No longer affects: 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/1372422 Title: Glance exploding on configuration parsing Status in Python client library for Keystone: In Progress Bug description: From recent various test runs: 2014-09-22 09:10:52.763 21744 INFO glance.notifier.notify_kombu [-] Connected to AMQP server on localhost:5672 2014-09-22 09:10:52.763 21744 INFO glance.api.middleware.cache [-] Initialized image cache middleware 2014-09-22 09:10:52.764 21744 INFO keystoneclient.middleware.auth_token [-] Starting keystone auth_token middleware 2014-09-22 09:10:52.764 21744 WARNING keystoneclient.middleware.auth_token [-] This middleware module is deprecated as of v0.10.0 in favor of keystonemiddleware.auth_token - please update your WSGI pipeline to reference the new middleware package. 2014-09-22 09:10:52.764 21744 CRITICAL glance [-] 'StrOpt' object has no attribute 'type' Then glance-api crashes. The sanity checks in devstack realize that glance isn't running and exit. To manage notifications about this bug go to: https://bugs.launchpad.net/python-keystoneclient/+bug/1372422/+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 1372645] Re: g-api and g-reg fail to start with: 'StrOpt' object has no attribute 'type'
This is not a defect in glance, the root cause is that during the grenade test, the havana level of oslo.config is used (<1.3.0), while the master level of keystoneclient is used, and also in the havana tests the glance services are still using the keystoneclient auth_token middleware. There's a 'fix' at https://review.openstack.org/#/c/123198/ , which gives keystoneclient a defensible logic. ** 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/1372645 Title: g-api and g-reg fail to start with: 'StrOpt' object has no attribute 'type' Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: In https://review.openstack.org/#/c/122215/ candidate fix for cinder failed in gate test gate-grenade-dsvm. grenade.sh.txt contains: 2014-09-22 16:51:30.019 | + screen -S stack -p g-api -X stuff 'cd /opt/stack/old/glance; /usr/local/bin/glance-api --config-file=/etc/glance/glance-api.conf & echo $! >/opt/stack/status/stack/g-api.pid; fg || echo "g-api failed to start" | tee "/opt/stack/status/stack/g-api.failure" ' 2014-09-22 16:51:30.027 | + echo 'Waiting for g-api (127.0.0.1:9292) to start...' 2014-09-22 16:51:30.027 | Waiting for g-api (127.0.0.1:9292) to start... 2014-09-22 16:51:30.027 | + timeout 120 sh -c 'while ! wget --no-proxy -q -O- http://127.0.0.1:9292; do sleep 1; done' 2014-09-22 16:53:30.031 | + die 199 'g-api did not start' 2014-09-22 16:53:30.031 | + local exitcode=0 2014-09-22 16:53:30.032 | [Call Trace] 2014-09-22 16:53:30.032 | ./stack.sh:1055:start_glance 2014-09-22 16:53:30.032 | /opt/stack/old/devstack/lib/glance:199:die 2014-09-22 16:53:30.042 | [ERROR] /opt/stack/old/devstack/lib/glance:199 g-api did not start 2014-09-22 16:53:30.046 | + exit_trap 2014-09-22 16:53:30.046 | + local r=1 screen-g-api ends thusly: 2014-09-22 16:51:30.895 28864 INFO glance.api.middleware.cache [-] Initialized image cache middleware 2014-09-22 16:51:30.896 28864 INFO keystoneclient.middleware.auth_token [-] Starting keystone auth_token middleware 2014-09-22 16:51:30.896 28864 WARNING keystoneclient.middleware.auth_token [-] This middleware module is deprecated as of v0.10.0 in favor of keystonemiddleware.auth_token - please update your WSGI pipeline to reference the new middleware package. 2014-09-22 16:51:30.896 28864 CRITICAL glance [-] 'StrOpt' object has no attribute 'type' g-api failed to start stack@devstack-precise-rax-iad-2340686:/opt/stack/old/glance$ screen-g-reg has the same error: stack@devstack-precise-rax-iad-2340686:/opt/stack/old/devstack$ cd /opt/stack/ol d/glance; /usr/local/bin/glance-registry --config-file=/etc/glance/glance-regist ry.conf & echo $! >/opt/stack/status/stack/g-reg.pid; fg || echo "g-reg failed t o start" | tee "/opt/stack/status/stack/g-reg.failure" [1] 28783 /usr/local/bin/glance-registry --config-file=/etc/glance/glance-registry.conf 2014-09-22 16:51:27.285 28783 DEBUG glance.common.config [-] Loading glance-registry-keystone from /etc/glance/glance-registry-paste.ini load_paste_app /opt/stack/old/glance/glance/common/config.py:223 2014-09-22 16:51:27.547 28783 DEBUG routes.middleware [-] Initialized with method overriding = True, and path info altering = True __init__ /usr/lib/python2.7/dist-packages/routes/middleware.py:41 2014-09-22 16:51:27.547 28783 INFO keystoneclient.middleware.auth_token [-] Starting keystone auth_token middleware 2014-09-22 16:51:27.547 28783 WARNING keystoneclient.middleware.auth_token [-] This middleware module is deprecated as of v0.10.0 in favor of keystonemiddleware.auth_token - please update your WSGI pipeline to reference the new middleware package. 2014-09-22 16:51:27.548 28783 CRITICAL glance [-] 'StrOpt' object has no attribute 'type' g-reg failed to start stack@devstack-precise-rax-iad-2340686:/opt/stack/old/glance$ To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1372645/+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 1379434] Re: Nova unable to download images from glance with rbd backend (juno/rc1)
The store.get() api in glance_store-0.1.8 provided correct signature and
logic [0], and glance has used that version as a requirement [1].
[0]
https://github.com/openstack/glance_store/blob/0.1.8/glance_store/_drivers/rbd.py#L207
[1]
https://github.com/openstack/glance/blob/2014.2.rc1/requirements.txt#L60
** 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/1379434
Title:
Nova unable to download images from glance with rbd backend (juno/rc1)
Status in OpenStack Image Registry and Delivery Service (Glance):
Invalid
Status in “nova” package in Ubuntu:
Invalid
Status in “python-glance-store” package in Ubuntu:
Fix Released
Bug description:
2014-10-09 17:00:41.356 9242 AUDIT nova.compute.manager
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] Starting instance...
2014-10-09 17:00:41.435 9242 WARNING nova.compute.resource_tracker
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] Host field should not be set on the
instance until resources have been claimed.
2014-10-09 17:00:41.435 9242 WARNING nova.compute.resource_tracker
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] Node field should not be set on the
instance until resources have been claimed.
2014-10-09 17:00:41.437 9242 AUDIT nova.compute.claims
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] Attempting claim: memory 512 MB, disk 1 GB
2014-10-09 17:00:41.437 9242 AUDIT nova.compute.claims
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] Total memory: 3952 MB, used: 512.00 MB
2014-10-09 17:00:41.438 9242 AUDIT nova.compute.claims
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] memory limit: 5928.00 MB, free: 5416.00 MB
2014-10-09 17:00:41.438 9242 AUDIT nova.compute.claims
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] Total disk: 9 GB, used: 0.00 GB
2014-10-09 17:00:41.439 9242 AUDIT nova.compute.claims
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] disk limit not specified, defaulting to
unlimited
2014-10-09 17:00:41.449 9242 AUDIT nova.compute.claims
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] Claim successful
2014-10-09 17:00:41.550 9242 INFO nova.scheduler.client.report
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] Compute_service record updated
for ('juju-t-machine-15', 'juju-t-machine-15.openstacklocal')
2014-10-09 17:00:41.871 9242 INFO nova.virt.libvirt.driver
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] Creating image
2014-10-09 17:00:41.929 9242 ERROR glanceclient.common.http
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 ] Request returned failure status 500.
2014-10-09 17:00:41.930 9242 ERROR nova.compute.manager
[req-7b7a713b-087a-46ce-8c6f-1e287abf3c99 None] [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] Instance failed to spawn
2014-10-09 17:00:41.930 9242 TRACE nova.compute.manager [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] Traceback (most recent call last):
2014-10-09 17:00:41.930 9242 TRACE nova.compute.manager [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2231, in
_build_resources
2014-10-09 17:00:41.930 9242 TRACE nova.compute.manager [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] yield resources
2014-10-09 17:00:41.930 9242 TRACE nova.compute.manager [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2101, in
_build_and_run_instance
2014-10-09 17:00:41.930 9242 TRACE nova.compute.manager [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] block_device_info=block_device_info)
2014-10-09 17:00:41.930 9242 TRACE nova.compute.manager [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2613, in
spawn
2014-10-09 17:00:41.930 9242 TRACE nova.compute.manager [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] admin_pass=admin_password)
2014-10-09 17:00:41.930 9242 TRACE nova.compute.manager [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3003, in
_create_image
2014-10-09 17:00:41.930 9242 TRACE nova.compute.manager [instance:
826a1d2d-a341-45c2-b070-c20f30b4d5aa] project_id=instance['project_id'])
2014-10-09 17:00:41.930 9242 TRACE nova.compute.manager [instance:
826a1d2d-a341-45c2-b070-c20f
[Yahoo-eng-team] [Bug 1380547] Re: Image is not added when filesystem_store_datadirs specified in glance configuration
As we designed, glance (even all services) should be able to load options from deprecated place instead of failure. This report involved a backward-compatibility issue of glance or/and glance_store, IMO. Need more investigation. ** Changed in: glance Status: Invalid => 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/1380547 Title: Image is not added when filesystem_store_datadirs specified in glance configuration Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: If user specifies 'filesystem_store_datadirs' option in the glance api configuration, he is not able to add the image to the specified location as following response is returned to the user. 410 Gone 410 Gone Error in store configuration. Adding images to store is disabled. (HTTP N/A) Steps to reproduce: 1. Edit glance-api.conf file to add 'filesystem_store_datadirs' parameter. filesystem_store_datadirs = /opt/stack/data/glance/images/:1 Note: Disable 'filesystem_store_datadir' option 2. restart glance-api service 3. create image glance image-create --file /etc/passwd --name passwd --container-format bare --disk-format raw To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1380547/+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 1380547] Re: Image is not added when filesystem_store_datadirs specified in glance configuration
With abhishekk's clarification, now I see what really happened behind this report. Agreed to mark this as invalid. Thanks for the clarification abhishekk. ** 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/1380547 Title: Image is not added when filesystem_store_datadirs specified in glance configuration Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: If user specifies 'filesystem_store_datadirs' option in the glance api configuration, he is not able to add the image to the specified location as following response is returned to the user. 410 Gone 410 Gone Error in store configuration. Adding images to store is disabled. (HTTP N/A) Steps to reproduce: 1. Edit glance-api.conf file to add 'filesystem_store_datadirs' parameter. filesystem_store_datadirs = /opt/stack/data/glance/images/:1 Note: Disable 'filesystem_store_datadir' option 2. restart glance-api service 3. create image glance image-create --file /etc/passwd --name passwd --container-format bare --disk-format raw To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1380547/+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 1381870] [NEW] Do not use obsolete modules from oslo-incubator
Public bug reported: The follow obsolete oslo-inc modules need to be removed from glance, update project moved to own graduated libraries instead. openstack/glance: gettextutils openstack/glance: test For details, pls ref http://lists.openstack.org/pipermail/openstack- dev/2014-October/048303.html ** Affects: glance Importance: High Assignee: Zhi Yan Liu (lzy-dev) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1381870 Title: Do not use obsolete modules from oslo-incubator Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Bug description: The follow obsolete oslo-inc modules need to be removed from glance, update project moved to own graduated libraries instead. openstack/glance: gettextutils openstack/glance: test For details, pls ref http://lists.openstack.org/pipermail/openstack- dev/2014-October/048303.html To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1381870/+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 1383027] Re: image-create with --copy-from returns failure status 400 in juno with Ceph store
Hello Tom, you just need to add 'http' to the enabled stores list option, at [glance_store]\stores in glance-api.conf _or_ the deprecated place at [DEFAULT]\known_stores. ** 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/1383027 Title: image-create with --copy-from returns failure status 400 in juno with Ceph store Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Can't create an image in Glance using --copy-from on a clean new deployment of Openstack Juno which uses a Ceph backend. As shown from the log below, I can download an image using wget and then upload it to Glance using --file but when I try to do the same thing using --copy-from it fails. The error given is 400 Bad Request, External sourcing not supported for store 'http'. Don't know where store 'http' is coming from because 'rbd' is the only enabled store. The fact that I can create an image using --file also proves that Ceph is working. Store settings in /etc/glance/glance.conf: [DEFAULT] default_store = rbd known_stores=glance.store.rbd.Store [glance_store] stores = glance.store.rbd.Store Log: root@test:~# glance image-create --progress --name=cirros1 --disk-format=qcow2 --container-format=bare --file cirros-0.3.3-x86_64-disk.img [=>] 100% +--+--+ | Property | Value| +--+--+ | checksum | 133eae9fb1c98f45894a4e60d8736619 | | container_format | bare | | created_at | 2014-10-19T19:18:39 | | deleted | False| | deleted_at | None | | disk_format | qcow2| | id | 6fb5afe8-8340-468d-a0ef-9d0b3ce0f13e | | is_public| False| | min_disk | 0| | min_ram | 0| | name | cirros1 | | owner| 3ccce78635eb4cbe96ec2675815fdf8b | | protected| False| | size | 13200896 | | status | active | | updated_at | 2014-10-19T19:18:42 | | virtual_size | None | +--+--+ root@test:~# glance image-create --progress --name=cirros2 --disk-format=qcow2 --container-format=bare --copy-from http://download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img Request returned failure status 400. 400 Bad Request 400 Bad Request External sourcing not supported for store 'http' (HTTP 400) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1383027/+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 1271806] Re: unable to run tests due to missing deps in the virtual env
** Changed in: neutron Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1271806 Title: unable to run tests due to missing deps in the virtual env Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Status in OpenStack Neutron (virtual network service): Invalid Bug description: On both my Ubuntu box and my Mac, I've been unable to run the glance tests since this evening due to a missing dependency, specifically a version of psutil between 0.6 and 1.0. The archive only has 1.1 and up. Here are the logs: Downloading/unpacking psutil>=0.6.1,<1.0 (from -r /Users/mfischer/code/glance/test-requirements.txt (line 19)) http://tarballs.openstack.org/oslo.messaging/oslo.messaging-1.2.0a11.tar.gz#egg=oslo.messaging-1.2.0a11 uses an insecure transport scheme (http). Consider using https if tarballs.openstack.org has it available Could not find a version that satisfies the requirement psutil>=0.6.1,<1.0 (from -r /Users/mfischer/code/glance/test-requirements.txt (line 19)) (from versions: 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.2.0, 1.2.1) Some externally hosted files were ignored (use --allow-external to allow). Cleaning up... No distributions matching the version for psutil>=0.6.1,<1.0 (from -r /Users/mfischer/code/glance/test-requirements.txt (line 19)) Storing debug log for failure in /var/folders/d2/qr0r7fc10j35_lwkz9wwmtxcgp/T/tmpBIMPmg To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1271806/+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 1279753] [NEW] The race condition caused by image created_at break registry v2 api test cases
Public bug reported: For now there are two cases I got: 1. glance.tests.unit.v2.test_registry_api.TestRegistryRPC.test_get_index_sort_status_desc http://logs.openstack.org/79/67079/3/gate/gate-glance- python27/2b0dea1/console.html#_2014-02-13_06_27_19_371 2. glance.tests.unit.v2.test_registry_api.TestRegistryRPC.test_get_index_sort_default_created_at_desc http://logs.openstack.org/79/67079/3/gate/gate-glance- python27/348ad19/console.html#_2014-02-11_18_42_13_276 It is the same reason as https://bugs.launchpad.net/glance/+bug/1272136 fixed. ** Affects: glance Importance: High 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/1279753 Title: The race condition caused by image created_at break registry v2 api test cases Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: For now there are two cases I got: 1. glance.tests.unit.v2.test_registry_api.TestRegistryRPC.test_get_index_sort_status_desc http://logs.openstack.org/79/67079/3/gate/gate-glance- python27/2b0dea1/console.html#_2014-02-13_06_27_19_371 2. glance.tests.unit.v2.test_registry_api.TestRegistryRPC.test_get_index_sort_default_created_at_desc http://logs.openstack.org/79/67079/3/gate/gate-glance- python27/348ad19/console.html#_2014-02-11_18_42_13_276 It is the same reason as https://bugs.launchpad.net/glance/+bug/1272136 fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1279753/+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 1282400] [NEW] The race condition caused by image created_at break DB driver test_image_paginate case
Public bug reported: FAIL: glance.tests.functional.db.test_registry.TestRegistryDriver.test_image_paginate tags: worker-0 -- Traceback (most recent call last): File "glance/tests/functional/db/base.py", line 711, in test_image_paginate self.assertEqual(extra_uuids, [i['id'] for i in page]) File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 321, in assertEqual self.assertThat(observed, matcher, message) File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 406, in assertThat raise mismatch_error MismatchError: !=: reference = ['0be9ce54-f56b-41d5-bef6-9ca75e846b59', 'a75dc71b-df55-41e3-9218-f465b791b7da'] actual= [u'a75dc71b-df55-41e3-9218-f465b791b7da', u'0be9ce54-f56b-41d5-bef6-9ca75e846b59'] http://logs.openstack.org/58/74858/1/check/gate-glance-python27/732468f/console.html#_2014-02-19_23_03_01_798 ** Affects: glance Importance: Medium Assignee: Zhi Yan Liu (lzy-dev) Status: New ** Changed in: glance Importance: Undecided => Medium ** Changed in: glance Assignee: (unassigned) => Zhi Yan Liu (lzy-dev) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1282400 Title: The race condition caused by image created_at break DB driver test_image_paginate case Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: FAIL: glance.tests.functional.db.test_registry.TestRegistryDriver.test_image_paginate tags: worker-0 -- Traceback (most recent call last): File "glance/tests/functional/db/base.py", line 711, in test_image_paginate self.assertEqual(extra_uuids, [i['id'] for i in page]) File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 321, in assertEqual self.assertThat(observed, matcher, message) File "/home/jenkins/workspace/gate-glance-python27/.tox/py27/local/lib/python2.7/site-packages/testtools/testcase.py", line 406, in assertThat raise mismatch_error MismatchError: !=: reference = ['0be9ce54-f56b-41d5-bef6-9ca75e846b59', 'a75dc71b-df55-41e3-9218-f465b791b7da'] actual= [u'a75dc71b-df55-41e3-9218-f465b791b7da', u'0be9ce54-f56b-41d5-bef6-9ca75e846b59'] http://logs.openstack.org/58/74858/1/check/gate-glance-python27/732468f/console.html#_2014-02-19_23_03_01_798 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1282400/+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 1277104] Re: wrong order of assertEquals args
** Also affects: glance Importance: Undecided Status: New ** Changed in: glance Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1277104 Title: wrong order of assertEquals args Status in OpenStack Telemetry (Ceilometer): In Progress Status in OpenStack Image Registry and Delivery Service (Glance): New Status in OpenStack Identity (Keystone): In Progress Status in Python client library for Glance: In Progress Status in Python client library for Ironic: New Status in Python client library for Swift: New Bug description: Args of assertEquals method in ceilometer.tests are arranged in wrong order. In result when test fails it shows incorrect information about observed and actual data. It's found more than 2000 times. Right order of arguments is "expected, actual". To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1277104/+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 1284677] Re: Python 3: do not use 'unicode()'
** Also affects: glance Importance: Undecided Status: New ** Changed in: glance Status: New => Triaged ** Changed in: glance Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1284677 Title: Python 3: do not use 'unicode()' Status in OpenStack Image Registry and Delivery Service (Glance): Triaged Status in Python client library for Glance: Triaged Bug description: The unicode() function is Python2-specific, we should use six.text_type() instead. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1284677/+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 1152218] Re: Fragile Test: glance.tests.functional.test_bin_glance_control.TestGlanceControl.test_reload
** Changed in: glance Status: Triaged => 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/1152218 Title: Fragile Test: glance.tests.functional.test_bin_glance_control.TestGlanceControl.test_reload Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Got next error here http://logs.openstack.org/23805/3/check/gate-glance-python27/3516/ glance.tests.functional.test_bin_glance_control.TestGlanceControl.test_reload Test fails with next trace: ft21.5: glance.tests.functional.test_bin_glance_control.TestGlanceControl.test_reload_StringException: Traceback (most recent call last): File "/home/jenkins/workspace/gate-glance-python27/glance/tests/utils.py", line 121, in wrapped func(*a, **kwargs) File "/home/jenkins/workspace/gate-glance-python27/glance/tests/functional/test_bin_glance_control.py", line 244, in test_reload self.assertTrue(launch_msg is None, launch_msg) AssertionError: Unexpected server launch status To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1152218/+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 1049302] Re: Fragile Test: glance.tests.functional.test_bin_glance:TestBinGlance.test_results_filtering
** Changed in: glance Status: Triaged => 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/1049302 Title: Fragile Test: glance.tests.functional.test_bin_glance:TestBinGlance.test_results_filtering Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Seen at http://logs.openstack.org/12736/5/gate/gate-glance- python26/1809/console.html: 17:54:58 == 17:54:58 ERROR: test_results_filtering (glance.tests.functional.test_bin_glance.TestBinGlance) 17:54:58 -- 17:54:58 Traceback (most recent call last): 17:54:58File "/home/jenkins/workspace/gate-glance-python26/glance/tests/functional/test_bin_glance.py", line 733, in test_results_filtering 17:54:58 exitcode, out, err = execute(cmd) 17:54:58File "/home/jenkins/workspace/gate-glance-python26/glance/tests/utils.py", line 255, in execute 17:54:58 raise RuntimeError(msg) 17:54:58 RuntimeError: Command bin/glance --port=45677 add is_public=True name=Name1 disk_format=vhd container_format=ovf foo=bar did not succeed. Returned an exit code of 1. 17:54:58 17:54:58 STDOUT: Failed to connect to the Glance API server 0.0.0.0:45677. Is the server running? 17:54:58 17:54:58 17:54:58 STDERR: WARNING! This tool is deprecated in favor of python-glanceclient (see http://github.com/openstack/python-glanceclient). To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1049302/+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 1049356] Re: Fragile Test: glance.tests.functional.v1.test_api:TestApi.test_queued_process_flow
** Changed in: glance Status: Triaged => 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/1049356 Title: Fragile Test: glance.tests.functional.v1.test_api:TestApi.test_queued_process_flow Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Seen here http://logs.openstack.org/12760/3/gate/gate-glance- python26/1812/console.html: 18:33:19 == 18:33:19 FAIL: We test the process flow where a user registers an image 18:33:19 -- 18:33:19 Traceback (most recent call last): 18:33:19File "/home/jenkins/workspace/gate-glance-python26/glance/tests/utils.py", line 178, in wrapped 18:33:19 func(*a, **kwargs) 18:33:19File "/home/jenkins/workspace/gate-glance-python26/glance/tests/functional/v1/test_api.py", line 312, in test_queued_process_flow 18:33:19 self.assertEqual(response.status, 200) 18:33:19 AssertionError: 500 != 200 18:33:19 >> raise self.failureException, \ 18:33:19(None or '%r != %r' % (500, 200)) To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1049356/+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 1289309] Re: collie not found error in failed gate test
This situation for Glance is normal. And I know there are two dedicated changes can prevent this error message issue. ** 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/1289309 Title: collie not found error in failed gate test Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Hit this error which is not whitelisted so causes the gate test to fail: 2014-03-07 10:54:32.474 31118 ERROR glance.store.sheepdog [-] Error in store configuration: Unexpected error while running command. Command: None Exit code: - Stdout: "Unexpected error while running command.\nCommand: collie\nExit code: 127\nStdout: ''\nStderr: '/bin/sh: 1: collie: not found\\n'" Stderr: None 2014-03-07 10:54:32.475 31118 WARNING glance.store.base [-] Failed to configure store correctly: Store sheepdog could not be configured correctly. Reason: Error in store configuration: Unexpected error while running command. Command: None Exit code: - Stdout: "Unexpected error while running command.\nCommand: collie\nExit code: 127\nStdout: ''\nStderr: '/bin/sh: 1: collie: not found\\n'" Stderr: None Disabling add method. http://logs.openstack.org/62/72762/14/check/check-grenade- dsvm/fb2420e/logs/new/screen-g-api.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1289309/+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 1302658] [NEW] Sheepdog store accept GET and DELETE request still even failed to configure essential option
Public bug reported: Currently if store raise BadStoreConfiguration exception from configure_add method, the glance will just make this store be readonly instead of fully disable, but for the logic of sheepdog configure_add, it contains all essential initial configurations for the store which are necessary for the store be fully functional, so if any one of they get failed the store should be full block up instead of being readonly accessible. The related test cases need to be handled as well. ** Affects: glance Importance: Low Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1302658 Title: Sheepdog store accept GET and DELETE request still even failed to configure essential option Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Currently if store raise BadStoreConfiguration exception from configure_add method, the glance will just make this store be readonly instead of fully disable, but for the logic of sheepdog configure_add, it contains all essential initial configurations for the store which are necessary for the store be fully functional, so if any one of they get failed the store should be full block up instead of being readonly accessible. The related test cases need to be handled as well. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1302658/+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 1304481] [NEW] Nova operates network failed by "Maximum attempts reached" error when Cloud under heavy workload
executors.base File
"/usr/lib/python2.6/site-packages/neutronclient/v2_0/client.py", line 306, in
list_ports
216555 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
**_params)
216556 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File
"/usr/lib/python2.6/site-packages/neutronclient/v2_0/client.py", line 1250, in
list
216557 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
for r in self._pagination(collection, path, **params):
216558 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File
"/usr/lib/python2.6/site-packages/neutronclient/v2_0/client.py", line 1263, in
_pagination
216559 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
res = self.get(path, params=params)
216560 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File
"/usr/lib/python2.6/site-packages/neutronclient/v2_0/client.py", line 1236, in
get
216561 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
headers=headers, params=params)
216562 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File
"/usr/lib/python2.6/site-packages/neutronclient/v2_0/client.py", line 1228, in
retry_request
216563 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
raise exceptions.ConnectionFailed(reason=_("Maximum attempts reached"))
216564 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
ConnectionFailed: Connection to neutron failed: Maximum attempts reached
216565 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
216566 2014-04-08 02:16:09.847 3777 ERROR oslo.messaging._drivers.common [-]
Returning exception Connection to neutron failed: Maximum attempts reached to
caller
** Affects: nova
Importance: Undecided
Assignee: Zhi Yan Liu (lzy-dev)
Status: New
** Changed in: nova
Assignee: (unassigned) => Zhi Yan Liu (lzy-dev)
--
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/1304481
Title:
Nova operates network failed by "Maximum attempts reached" error when
Cloud under heavy workload
Status in OpenStack Compute (Nova):
New
Bug description:
In my deployment when I provision or terminate numerous VM, e.g. 100+,
I got some "Maximum attempts reached" issues in Nova internal which
happened on Nova operates network/neutron by neutronclient. You might
check follow log snippet for details.
I propose adding a "neutron_http_retries" option to Nova, and to make
each neutron client object leverage this option (in
nova/network/neutronv2/api.py). IMO we could make the fix base on this
change: https://review.openstack.org/#/c/71464/
IFY, in my deployment I verified that when I set http retries of
neutronclient to 5 times (most time 3 is just fine) the problem is
gone.
216492 2014-04-08 02:16:09.844 3777 ERROR oslo.messaging._executors.base [-]
Exception during message handling
216493 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
Traceback (most recent call last):
216494 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
File "/usr/lib/python2.6/site-packages/oslo/messaging/_executors/base.py", line
36, in _dispatch
216495 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
incoming.reply(self.callback(incoming.ctxt, incoming.message))
216496 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line
122, in __call__
216497 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
return self._dispatch(endpoint, method, ctxt, args)
216498 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line
92, in _dispatch
216499 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
result = getattr(endpoint, method)(ctxt, **new_args)
216500 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
File "/usr/lib/python2.6/site-packages/nova/exception.py", line 88, in wrapped
216501 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
payload)
216502 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line
68, in __exit__
216503 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
six.reraise(self.type_, self.value, self.tb)
216504 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base
File "/usr/lib/python2.6/site-packages/nova/exception.py", line 71, in wrapped
216505 2014-04-08 02:16:09.844
[Yahoo-eng-team] [Bug 1314007] [NEW] run_tests.sh failed by "No module named tools" exception
Public bug reported: $ ./run_tests.sh No virtual environment found...create one? (Y/n) y Traceback (most recent call last): File "tools/install_venv.py", line 29, in from tools import install_venv_common as install_venv ImportError: No module named tools Change "Enable H304 check" (I099ed65db9b42223eaa4b66a3a5c6113d1cc56fe) causes it. ** Affects: glance Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1314007 Title: run_tests.sh failed by "No module named tools" exception Status in OpenStack Image Registry and Delivery Service (Glance): Triaged Bug description: $ ./run_tests.sh No virtual environment found...create one? (Y/n) y Traceback (most recent call last): File "tools/install_venv.py", line 29, in from tools import install_venv_common as install_venv ImportError: No module named tools Change "Enable H304 check" (I099ed65db9b42223eaa4b66a3a5c6113d1cc56fe) causes it. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1314007/+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 1304481] Re: Nova operates network failed by "Maximum attempts reached" error when Cloud under heavy workload
** Changed in: nova Status: Invalid => New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1304481 Title: Nova operates network failed by "Maximum attempts reached" error when Cloud under heavy workload Status in OpenStack Neutron (virtual network service): Won't Fix Status in OpenStack Compute (Nova): New Bug description: In my deployment when I provision or terminate numerous VM, e.g. 100+, I got some "Maximum attempts reached" issues in Nova internal which happened on Nova operates network/neutron by neutronclient. You might check follow log snippet for details. I propose adding a "neutron_http_retries" option to Nova, and to make each neutron client object leverage this option (in nova/network/neutronv2/api.py). IMO we could make the fix base on this change: https://review.openstack.org/#/c/71464/ IFY, in my deployment I verified that when I set http retries of neutronclient to 5 times (most time 3 is just fine) the problem is gone. 216492 2014-04-08 02:16:09.844 3777 ERROR oslo.messaging._executors.base [-] Exception during message handling 216493 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base Traceback (most recent call last): 216494 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/oslo/messaging/_executors/base.py", line 36, in _dispatch 216495 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base incoming.reply(self.callback(incoming.ctxt, incoming.message)) 216496 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 122, in __call__ 216497 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base return self._dispatch(endpoint, method, ctxt, args) 216498 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py", line 92, in _dispatch 216499 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base result = getattr(endpoint, method)(ctxt, **new_args) 216500 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/nova/exception.py", line 88, in wrapped 216501 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base payload) 216502 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68, in __exit__ 216503 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base six.reraise(self.type_, self.value, self.tb) 216504 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/nova/exception.py", line 71, in wrapped 216505 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base return f(self, context, *args, **kw) 216506 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 249, in decorated_function 216507 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base pass 216508 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68, in __exit__ 216509 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base six.reraise(self.type_, self.value, self.tb) 216510 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 235, in decorated_function 216511 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base return function(self, context, *args, **kwargs) 216512 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 300, in decorated_function 216513 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base function(self, context, *args, **kwargs) 216514 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 277, in decorated_function 216515 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base e, sys.exc_info()) 216516 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py", line 68, in __exit__ 216517 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base six.reraise(self.type_, self.value, self.tb) 216518 2014-04-08 02:16:09.844 3777 TRACE oslo.messaging._executors.base File "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 264, in decorated_function 21
[Yahoo-eng-team] [Bug 1339039] Re: ERROR: Store for scheme glance.store.rbd.Store not found
According to the error message "Store for scheme glance.store.rbd.Store
not found", your configuration on ''default_store" is wrong, for your
case it should be 'rbd' instead of 'glance.store.rbd.Store', since as
help message of the option mentioned, the value should be schema of
store but the module name of store dirver, pls try it 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/1339039
Title:
ERROR: Store for scheme glance.store.rbd.Store not found
Status in OpenStack Image Registry and Delivery Service (Glance):
Invalid
Bug description:
glance-api is unable to initilize rbd storage backend.
Running glance-api with only rbd backend configured and disabling all
the other backends causes the service to exit with the following
error:
root@control:~# glance-api
2 2014-07-07 17:48:03.950 1874 DEBUG glance.store [-] Attempting to import
store glance.store.rbd.Store _get_store_class
/usr/lib/python2.7/dist-packages/glance/store/__init__.py:168
3 2014-07-07 17:48:03.955 1874 DEBUG glance.store [-] Registering store
with schemes ('rbd',) create_stores
/usr/lib/python2.7/dist-packages/glance/store/__init__.py:210
4 2014-07-07 17:48:03.955 1874 DEBUG glance.store.base [-] Late loading
location class glance.store.rbd.StoreLocation get_store_location_class
/usr/lib/python2.7/dist-packages/glance/store/base.py:80
5 2014-07-07 17:48:03.956 1874 DEBUG glance.store.location [-] Registering
scheme rbd with {'store_class': ,
'location_class': }
register_scheme_map /usr/lib/python2.7/dist-packages/glance/store/location.py:86
6 2014-07-07 17:48:03.958 1874 DEBUG glance.api.policy [-] Loading policy
from /etc/glance/policy.json _read_policy_file
/usr/lib/python2.7/dist-packages/glance/api/policy.py:106
7 2014-07-07 17:48:03.959 1874 DEBUG glance.api.policy [-] Loaded policy
rules: {u'get_task': '@', u'get_image_location': '@', u'add_image': '@',
u'modify_image': '@', u'manage_image_cache': 'role:admin',
u'delete_member': '@', u'get_images': '@', u'delete_image': '@',
u'publicize_image': '@', u'get_member': '@', u'add_member': '@',
u'set_image_location': '@', u'get_image': '@', u'modify_member': '@',
u'context_is_admin': 'role:admin', u'upload_image': '@', u'modify_task':
'@', u'get_members': '@', u'get_tasks': '@', u'add_task': '@', u'default': '@',
u'delete_image_location': '@', u'copy_from': '@', u'download_image': '@'}
load_rules /usr/lib/python2.7/dist-packages/glance/api/policy.py:85
8 ERROR: Store for scheme glance.store.rbd.Store not found
root@control:~# cat /etc/glance/glance-api.conf
[...]
default_store = glance.store.rbd.Store
known_stores = glance.store.rbd.Store
[...]
root@control:~# dpkg -l | grep glance
ii glance 1:2014.1-0ubuntu1
all OpenStack Image Registry and Delivery Service - Daemons
ii glance-api 1:2014.1-0ubuntu1
all OpenStack Image Registry and Delivery Service - API
ii glance-common 1:2014.1-0ubuntu1
all OpenStack Image Registry and Delivery Service - Common
ii glance-registry 1:2014.1-0ubuntu1
all OpenStack Image Registry and Delivery Service - Registry
ii python-glance 1:2014.1-0ubuntu1
all OpenStack Image Registry and Delivery Service - Python library
ii python-glanceclient 1:0.12.0-0ubuntu1
all Client library for Openstack glance server.
After some time of debugging I figured out, that the problem is cased
by the function "get_store_from_scheme(context, scheme, loc=None)".
The argument "context" is evaluated to "glance.store.rbd.Store" not to
"rbd".
Applying the attached quick and dirty fix patch has solved the
problem.
Further investigation needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1339039/+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 1340002] [NEW] Some exceptions raise unicodeError
Public bug reported: Thie bug is a generic case for bug 1339775 [0], there are a lot same cases in codebase which are outside of v2 stuff, but the result is smimilar, UnicodeError exception will be raised. [0] https://bugs.launchpad.net/glance/+bug/1339775 ** 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/1340002 Title: Some exceptions raise unicodeError Status in OpenStack Image Registry and Delivery Service (Glance): New Bug description: Thie bug is a generic case for bug 1339775 [0], there are a lot same cases in codebase which are outside of v2 stuff, but the result is smimilar, UnicodeError exception will be raised. [0] https://bugs.launchpad.net/glance/+bug/1339775 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1340002/+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 1140777] Re: HTTPInternalServerError on TestApi.test_duplicate_image_upload
We did't meet this test failure in jenkins for a long time, so I'm going to close this bug, if you can catch it again pls reopen it as free. ** Changed in: glance Status: Triaged => 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/1140777 Title: HTTPInternalServerError on TestApi.test_duplicate_image_upload Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Got a Jenkins functional test failure that I can't reproduce in my own testing. 2013-03-02 19:44:40.141 | == 2013-03-02 19:44:40.142 | FAIL: glance.tests.functional.v1.test_api.TestApi.test_duplicate_image_upload 2013-03-02 19:44:40.142 | -- 2013-03-02 19:44:40.142 | _StringException: Traceback (most recent call last): 2013-03-02 19:44:40.143 | File "/home/jenkins/workspace/gate-glance-python27/glance/tests/utils.py", line 121, in wrapped 2013-03-02 19:44:40.144 | func(*a, **kwargs) 2013-03-02 19:44:40.145 | File "/home/jenkins/workspace/gate-glance-python27/glance/tests/functional/v1/test_api.py", line 1161, in test_duplicate_image_upload 2013-03-02 19:44:40.145 | self.assertEqual(response.status, 200) 2013-03-02 19:44:40.145 | MismatchError: 500 != 200 The python26 test ran fine and all the tests work fine in a local venv. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1140777/+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 1154458] Re: fragile test: glance.tests.functional.v1.test_ssl.TestSSL.test_ordered_images
We don't meet this test failure in jenkins for a long time, so I'm going to close this bug, if you can catch it again pls reopen it as free. ** Changed in: glance Status: Triaged => 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/1154458 Title: fragile test: glance.tests.functional.v1.test_ssl.TestSSL.test_ordered_images Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: http://logs.openstack.org/24201/2/gate/gate-glance- python27/3622/console.html FAIL: glance.tests.functional.v1.test_ssl.TestSSL.test_ordered_images -- _StringException: Traceback (most recent call last): File "/home/jenkins/workspace/gate-glance-python27/glance/tests/utils.py", line 121, in wrapped func(*a, **kwargs) File "/home/jenkins/workspace/gate-glance-python27/glance/tests/functional/v1/test_ssl.py", line 1067, in test_ordered_images self.assertEqual(response.status, 200) MismatchError: 500 != 200 To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1154458/+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 1193531] Re: Fragile test: glance.tests.unit.v1.test_api.TestGlanceAPI.test_add_copy_from_image_authorized
We don't meet this test failure in jenkins for a long time, so I'm going
to close this bug, if you can catch it again pls reopen it as free,
thanks.
** Changed in: glance
Status: Triaged => 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/1193531
Title:
Fragile test:
glance.tests.unit.v1.test_api.TestGlanceAPI.test_add_copy_from_image_authorized
Status in OpenStack Image Registry and Delivery Service (Glance):
Invalid
Bug description:
From http://logs.openstack.org/34030/2/check/gate-glance-
python26/4449/console.html.gz
2013-06-21 19:27:26.230 | ERROR:
glance.tests.unit.v1.test_api.TestGlanceAPI.test_add_copy_from_image_authorized
2013-06-21 19:27:26.230 |
--
2013-06-21 19:27:26.230 | _StringException: Traceback (most recent call last):
2013-06-21 19:27:26.230 | File
"/home/jenkins/workspace/gate-glance-python26/glance/tests/unit/v1/test_api.py",
line 548, in test_add_copy_from_image_authorized
2013-06-21 19:27:26.230 | res = req.get_response(self.api)
2013-06-21 19:27:26.230 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/webob/request.py",
line 1296, in send
2013-06-21 19:27:26.230 | application, catch_exc_info=False)
2013-06-21 19:27:26.231 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/webob/request.py",
line 1260, in call_application
2013-06-21 19:27:26.231 | app_iter = application(self.environ,
start_response)
2013-06-21 19:27:26.231 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py",
line 130, in __call__
2013-06-21 19:27:26.231 | resp = self.call_func(req, *args, **self.kwargs)
2013-06-21 19:27:26.231 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py",
line 195, in call_func
2013-06-21 19:27:26.231 | return self.func(req, *args, **kwargs)
2013-06-21 19:27:26.231 | File
"/home/jenkins/workspace/gate-glance-python26/glance/common/wsgi.py", line 367,
in __call__
2013-06-21 19:27:26.231 | response = req.get_response(self.application)
2013-06-21 19:27:26.231 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/webob/request.py",
line 1296, in send
2013-06-21 19:27:26.231 | application, catch_exc_info=False)
2013-06-21 19:27:26.231 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/webob/request.py",
line 1260, in call_application
2013-06-21 19:27:26.231 | app_iter = application(self.environ,
start_response)
2013-06-21 19:27:26.232 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py",
line 144, in __call__
2013-06-21 19:27:26.232 | return resp(environ, start_response)
2013-06-21 19:27:26.232 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/routes/middleware.py",
line 131, in __call__
2013-06-21 19:27:26.232 | response = self.app(environ, start_response)
2013-06-21 19:27:26.232 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py",
line 144, in __call__
2013-06-21 19:27:26.232 | return resp(environ, start_response)
2013-06-21 19:27:26.232 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py",
line 130, in __call__
2013-06-21 19:27:26.232 | resp = self.call_func(req, *args, **self.kwargs)
2013-06-21 19:27:26.232 | File
"/home/jenkins/workspace/gate-glance-python26/.tox/py26/lib/python2.6/site-packages/webob/dec.py",
line 195, in call_func
2013-06-21 19:27:26.232 | return self.func(req, *args, **kwargs)
2013-06-21 19:27:26.232 | File
"/home/jenkins/workspace/gate-glance-python26/glance/common/wsgi.py", line 591,
in __call__
2013-06-21 19:27:26.232 | request, **action_args)
2013-06-21 19:27:26.232 | File
"/home/jenkins/workspace/gate-glance-python26/glance/common/wsgi.py", line 608,
in dispatch
2013-06-21 19:27:26.232 | return method(*args, **kwargs)
2013-06-21 19:27:26.233 | File
"/home/jenkins/workspace/gate-glance-python26/glance/common/utils.py", line
407, in wrapped
2013-06-21 19:27:26.233 | return func(self, req, *args, **kwargs)
2013-06-21 19:27:26.233 | File
"/home/jenkins/workspace/gate-glance-python26/glance/api/v1/images.py", line
593, in create
2013-06-21 19:27:26.233 | location_uri = image_meta.get('location')
2013-06-21 19:27:26.233 | AttributeError: 'NoneType' object has no attribute
'get'
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1193531/+subscriptions
--
Mailing list:
[Yahoo-eng-team] [Bug 1251105] Re: test-requirements.txt seems to need correcting
Currently, glance is using psutil>=1.1.1,<2.0.0 and testtools>=0.9.32 , those work for us. ** Changed in: glance Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1251105 Title: test-requirements.txt seems to need correcting Status in OpenStack Image Registry and Delivery Service (Glance): Won't Fix Bug description: from glance-2013.2/test-requirements.txt testtools>=0.9.32 psutil>=0.6.1,<1.0 This is the SECOND time I have found stipulation of testtools version to be wrong (in an openstack package source code). With testtools-0.9.32 installed the testsuite simply goes belly up. It works fine with <=dev-python/testtools-0.9.24-r1 which would translate into <=testtools-0.9.24. It reports missing a module to import. I wonder, is the installed testtools-0.9.32 a different package to the one you use? Second; our versions of psutil from 0.6.1 up all seem to do fine. Hmm. glance-2013.1.4/ has no test-requirements.txt. Tests of TestApi, TestSSL and more yield ERROR & FAIL, however being 2013.1.x I'm guessing this is simply passe, or a memory of the past. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1251105/+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 1049363] Re: Fragile Test: glance.tests.functional.test_bin_glance:TestBinGlance.test_killed_image_not_in_index
This test case is no longer in current glance codebase, feel free to create a new report this if you get the similar issue again, thanks. ** Changed in: glance Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1049363 Title: Fragile Test: glance.tests.functional.test_bin_glance:TestBinGlance.test_killed_image_not_in_index Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: Seen here http://logs.openstack.org/12760/3/gate/gate-glance- python27/1827/console.html: 20:33:51 == 20:33:51 ERROR: We test conditions that produced LP Bug #768969, where an image 20:33:51 -- 20:33:51 Traceback (most recent call last): 20:33:51File "/home/jenkins/workspace/gate-glance-python27/glance/tests/functional/test_bin_glance.py", line 574, in test_killed_image_not_in_index 20:33:51 exitcode, out, err = execute(cmd) 20:33:51File "/home/jenkins/workspace/gate-glance-python27/glance/tests/utils.py", line 255, in execute 20:33:51 raise RuntimeError(msg) 20:33:51 RuntimeError: Command bin/glance --port=39745 index did not succeed. Returned an exit code of 1. 20:33:51 20:33:51 STDOUT: Failed to show index. Got error: 20:33:51 [Errno 111] Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1049363/+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 1250918] Re: No policy for image uploads in v2
Currently we applied the policy enforcement at domain layer instead of api controller in v2, https://github.com/openstack/glance/blob/master/glance/api/policy.py#L237 . ** Changed in: glance Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1250918 Title: No policy for image uploads in v2 Status in OpenStack Image Registry and Delivery Service (Glance): Invalid Bug description: There no policy for the set_data function for image_uploads in glance v2 api To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1250918/+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
