Description of problem: $rpm -qf /usr/lib/python2.7/site-packages/keystone/middleware/__init__.py python-keystone-auth-token-2012.2-1.fc18.noarch python-keystone-2012.2-1.fc18.noarch Indicates the overlap. The __init__.py is an empty file. Exception part: raise ImportError("%r has no %r attribute" % (entry,attr)) ImportError: <module 'keystone.middleware' from '/usr/lib/python2.7/site-packages/keystone/middleware/__init__.py'> has no 'NormalizingFilter' attribute Steps to Reproduce: 1. yum remove -y python-keystone-auth-token 2. yum install -y openstack-keystone Actual results: /usr/lib/python2.7/site-packages/keystone/middleware/__init__.py is empty Expected results: /usr/lib/python2.7/site-packages/keystone/middleware/__init__.py imports the middleware.core. workaround: yum reinstall -y python-keystone Related issue: #844508
Where do you get Exception i.e. what's step 3. in steps to reproduce?
If the "/usr/lib/python2.7/site-packages/keystone/middleware/__init__.py" empty the issue reproduced. The exception is from the /var/log/messages after a start attempt. $ service openstack-keystone start $ grep -A 2 Import /var/log/messages The issue happens even on the first install, without changing the config file.
I see this too - can reproduce by following the steps in https://fedoraproject.org/wiki/Test_Day:2012-09-18_OpenStack#Fedora_18 on a freshly built F18 server
Could you please provide /var/log/yum.log when this happens? Thanks.
Created attachment 641102 [details] yum.log I'm seeing this too and have attached a yum.log.
Created attachment 641106 [details] yum.log another yum.log from a machine with the issue for comparison
I couldn't reproduce, so it must be randomness in executing post/triggers. But given that auth-token doesn't work standalone in Folsom anyway (bug 844508) I'll drop auth-token subpackage. It will return as a part of Grizzly python-keystoneclient: https://blueprints.launchpad.net/keystone/+spec/authtoken-to-keystoneclient-repo
openstack-keystone-2012.2-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/openstack-keystone-2012.2-3.fc18
Package openstack-keystone-2012.2-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing openstack-keystone-2012.2-3.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17926/openstack-keystone-2012.2-3.fc18 then log in and leave karma (feedback).
Package openstack-keystone-2012.2-4.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing openstack-keystone-2012.2-4.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-17926/openstack-keystone-2012.2-4.fc18 then log in and leave karma (feedback).