keystone puppetry race condition?

[Chris Ricker]

Looks like perhaps a race condition in the keystone puppetry:

debug: Mysql::Db[keystone]: The container Class[Keystone::Db::Mysql] will propagate my refresh event
info: Mysql::Db[keystone]: Scheduling refresh of Exec[keystone-manage db_sync]
debug: Class[Keystone::Db::Mysql]: The container Stage[main] will propagate my refresh event
debug: Exec[keystone-manage db_sync](provider=posix): Executing 'keystone-manage db_sync'
debug: Executing 'keystone-manage db_sync'
notice: /Stage[main]/Keystone/Exec[keystone-manage db_sync]: Triggered 'refresh' from 3 events
info: /Stage[main]/Keystone/Exec[keystone-manage db_sync]: Scheduling refresh of Service[keystone]
debug: /Stage[main]/Keystone/Exec[keystone-manage db_sync]: The container Class[Keystone] will propagate my refresh event
debug: Puppet::Type::Service::ProviderUpstart: Executing '/sbin/status keystone'
debug: Puppet::Type::Service::ProviderUpstart: Executing '/sbin/status keystone'
debug: Service[keystone](provider=upstart): Executing '/sbin/restart keystone'
notice: /Service[keystone]: Triggered 'refresh' from 2 events
debug: /Service[keystone]: The container Class[Keystone] will propagate my refresh event
debug: Class[Keystone]: The container Stage[main] will propagate my refresh event
debug: Prefetching keystone resources for keystone_role
debug: Puppet::Type::Keystone_role::ProviderKeystone: Executing '/usr/bin/keystone --token keystone_admin_token --endpoint http://127.0.0.1:35357/v2.0/ role-list'
err: /Stage[main]/Keystone::Roles::Admin/Keystone_role[Member]: Could not evaluate: Execution of '/usr/bin/keystone --token keystone_admin_token --endpoint http://127.0.0.1:35357/v2.0/ role-list' returned 1: [Errno 111] Connection refused

The keystone role-list fails because the keystone restart hasn't finished?

[Chris Ricker (chris-ricker)]

Not sure if it was caused by this, but at the end of the puppet run I was missing the Member role:

root@conserv:~# keystone role-list
WARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+----------------------------------+-------+
| id | name |
+----------------------------------+-------+
| 5d48dd8924f84f04bcc940f2bac3932f | admin |
+----------------------------------+-------+
root@conserv:~#

After a second puppet run where the role-list failure didn't occur, the Member role was successfully created:

root@conserv:~# keystone role-listWARNING: Bypassing authentication using a token & endpoint (authentication credentials are being ignored).
+----------------------------------+--------+
| id | name |
+----------------------------------+--------+
| d733e7ddcf7d4fd4b4156da8418aedae | Member |
| 5d48dd8924f84f04bcc940f2bac3932f | admin |
+----------------------------------+--------+
root@conserv:~#

So this may tie to Bug #1167483 (where horizon has some functions broken due to lack of the Member role)