[juno] keystone can't load plugin

Bug #1367684 reported by Denis Egorenko
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Invalid
Critical
MOS Keystone

Bug Description

Deploy custom ISO:
{"build_id": "2014-09-09_18-28-49",
 "ostf_sha": "26bcd619dc12dcdf698e346fcf62ec9feb979ba1",
 "build_number": "226",
 "auth_required": true,
 "api": "1.0",
 "nailgun_sha": "26bb3cdee5e47d5c4f644fa057d34ee7472617d3",
 "production": "docker",
 "fuelmain_sha": "5e350476fd5b0e36cc5a6f570685d188a5030373",
 "astute_sha": "b622d9b36dbdd1e03b282b9ee5b7435ba649e711",
 "feature_groups": ["mirantis"],
 "release": "5.1",
 "release_versions": {"2014.1.1-5.1": {"VERSION": {"build_id": "2014-09-09_18-28-49", "ostf_sha": "26bcd619dc12dcdf698e346fcf62ec9feb979ba1", "build_number": "226", "api": "1.0", "nailgun_sha": "26bb3cdee5e47d5c4f644fa057d34ee7472617d3", "production": "docker", "fuelmain_sha": "5e350476fd5b0e36cc5a6f570685d188a5030373", "astute_sha": "b622d9b36dbdd1e03b282b9ee5b7435ba649e711", "feature_groups": ["mirantis"], "release": "5.1", "fuellib_sha": "4918d1e1fa406b034deec78537a928361077d5da"}}},
 "fuellib_sha": "4918d1e1fa406b034deec78537a928361077d5da"}

During deploy simple mode occurred some errors for all services:
(/Stage[main]/Neutron::Keystone::Auth/Keystone_service[neutron]) Could not evaluate: Execution of '/usr/bin/keystone --os-token 7yATtPtV --os-endpoint http://127.0.0.1:35357/v2.0/ service-list' returned 1: Unable to establish connection to http://127.0.0.1:35357/v2.0/OS-KSADM/services

In keystone log i found traceback:
2014-09-10 09:21:03.103 26753 CRITICAL keystone [-] Exception: Can't load plugin dogpile.cache keystone.cache.memcache_pool
2014-09-10 09:21:03.103 26753 TRACE keystone Traceback (most recent call last):
2014-09-10 09:21:03.103 26753 TRACE keystone File "/usr/bin/keystone-all", line 141, in <module>
2014-09-10 09:21:03.103 26753 TRACE keystone backends.load_backends()
2014-09-10 09:21:03.103 26753 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/backends.py", line 29, in load_backends
2014-09-10 09:21:03.103 26753 TRACE keystone cache.configure_cache_region(cache.REGION)
2014-09-10 09:21:03.103 26753 TRACE keystone File "/usr/lib/python2.7/dist-packages/keystone/common/cache/core.py", line 128, in configure_cache_region
2014-09-10 09:21:03.103 26753 TRACE keystone '%s.' % CONF.cache.config_prefix)
2014-09-10 09:21:03.103 26753 TRACE keystone File "/usr/lib/python2.7/dist-packages/dogpile/cache/region.py", line 369, in configure_from_config
2014-09-10 09:21:03.103 26753 TRACE keystone _config_prefix="%sarguments." % prefix
2014-09-10 09:21:03.103 26753 TRACE keystone File "/usr/lib/python2.7/dist-packages/dogpile/cache/region.py", line 230, in configure
2014-09-10 09:21:03.103 26753 TRACE keystone backend_cls = _backend_loader.load(backend)
2014-09-10 09:21:03.103 26753 TRACE keystone File "/usr/lib/python2.7/dist-packages/dogpile/cache/util.py", line 47, in load
2014-09-10 09:21:03.103 26753 TRACE keystone (self.group, name))
2014-09-10 09:21:03.103 26753 TRACE keystone Exception: Can't load plugin dogpile.cache keystone.cache.memcache_pool
2014-09-10 09:21:03.103 26753 TRACE keystone

Tags: keystone juno
Changed in fuel:
milestone: none → 6.0
Changed in fuel:
assignee: nobody → MOS Keystone (mos-keystone)
Changed in mos:
milestone: none → 6.0
importance: Undecided → High
importance: High → Critical
assignee: nobody → MOS Keystone (mos-keystone)
status: New → Triaged
no longer affects: fuel
Revision history for this message
Yuriy Taraday (yorik-sar) wrote :

Did you use the latest Keystone code? It looks like you got new memcache_pool backend configured but not present in the code. Check that you have this change in code: https://gerrit.mirantis.com/21408 (/usr/lib/python2.7/dist-packages/keystone/common/cache/backends/memcache_pool.py file should be present).

Changed in mos:
status: Triaged → Incomplete
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

Yuriy, this code needs to be patched in our master trees for Juno. Also, is there an upstream code review for this?

Revision history for this message
Yuriy Taraday (yorik-sar) wrote :

Judging by "5.1" in ISO description it looks like this bug is related to 5.1 and Icehouse, not Juno.
Yes, there is open change requests for this in master: https://review.openstack.org/119452 and https://review.openstack.org/119774

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

The CR in upstream is here: https://review.openstack.org/#/c/119452/

Since we will have Fuel master dedicated to 6.0 very soon (as stable/5.1 will be split), I propose to temporarily revert Vladimir's change which enable's Yuri's fix. Once the CR is committed in upstream we can get back Vladimir's change

Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

I found this: https://review.openstack.org/#/c/119452/
It doesn't look merged yet, so we need Yuriy to confirm it should be applied to Keystone master branch for Juno.

Revision history for this message
Denis Egorenko (degorenko) wrote :

No, this file doesn't exist.
This ISO is for Fuel 6.0, so packages are building from master branch in our gerrit. I think this patch should be added to master branch.

Revision history for this message
Yuriy Taraday (yorik-sar) wrote :

This patch will land in Juno in upstream, so there's no need to apply it to our internal branch. Just wait until it's merged into upstream.

Revision history for this message
Denis Egorenko (degorenko) wrote :

Ok, thanks

Revision history for this message
Alexander Makarov (amakarov) wrote :

https://review.openstack.org/#/c/119452/ is merged.
Please update status of the bug.

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Ok, so right now 6.0 iso works. But we need to check if we have to adjust our configuration, since the patch in upstream was changed.

Changed in mos:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.