This is from the keystone custom log:
Populating service catalog with [u'compute_legacy', u'volume', u'alarming', u'identity', u'volumev2', u'metering', u'compute', u'artifact', u'image', u'volumev3', u'network'], types in db: [u'compute_legacy', u'object-store', u'cloudformation', u'volume', u'alarming', u'identity', u'volumev2', u'metering', u'compute', u'artifact', u's3', u'image', u'orchestration', u'volumev3', u'network']
There is no object-store in catalog attached to token, but it is in database. So it's clearly a cache invalidation issue.
This is from the keystone custom log:
Populating service catalog with [u'compute_legacy', u'volume', u'alarming', u'identity', u'volumev2', u'metering', u'compute', u'artifact', u'image', u'volumev3', u'network'], types in db: [u'compute_legacy', u'object-store', u'cloudformation', u'volume', u'alarming', u'identity', u'volumev2', u'metering', u'compute', u'artifact', u's3', u'image', u'orchestration', u'volumev3', u'network']
There is no object-store in catalog attached to token, but it is in database. So it's clearly a cache invalidation issue.