Comment 7 for bug 1525214

So i've spent a bunch of time trying to track down this issue and it appears to be somewhere in the nova/glance/keystone world where the token being used by nova to talk to glance is being reported as not a valid token. I can't figure out how to debug this further as it seems to be something within the openstack clients or services and not specific to fuel library. I'm wondering if it might be because of some sort of time skew with the tokens as the time on the keystone server is behind the the glance/nova servers. If a token is generated on a controller that is ahead from the controller that validates it, will the controller that is behind report the token as invalid because it's in the future?

For example here are the logs for one of the ostf glance failures.
Nova:
http://paste.openstack.org/show/482896/

Glance:
http://paste.openstack.org/show/482897/

keystone:
http://paste.openstack.org/show/482898/

The token issue seems to be pretty consistent in the failure related to the filling root tests.