From 8c84cf691ea8c9f6100cfcbf7d1942fdf1384f79 Mon Sep 17 00:00:00 2001 From: Robert Collins Date: Fri, 16 May 2014 16:06:36 +1200 Subject: [PATCH] Workaround Heat not handling token expiry Heat cannot handle a token expiring mid-deploy. Until the heat bug is fixed we can workaround it by upping the token expiry time. The value of 4 hours is higher than the time we need to deploy a 30 node cloud of real hardware, and less than the 5 hour upper maximum suggested by Morgan Fainberg, Keystone core. Change-Id: Ib079f8880b3672ac442804557baca954e8af87ff Partial-Bug: #1306294 --- elements/keystone/os-apply-config/etc/keystone/keystone.conf | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/elements/keystone/os-apply-config/etc/keystone/keystone.conf b/elements/keystone/os-apply-config/etc/keystone/keystone.conf index 907e7619f..54532e833 100644 --- a/elements/keystone/os-apply-config/etc/keystone/keystone.conf +++ b/elements/keystone/os-apply-config/etc/keystone/keystone.conf @@ -33,7 +33,8 @@ driver = keystone.catalog.backends.sql.Catalog driver = keystone.token.backends.sql.Token # Amount of time a token should remain valid (in seconds) -# expiration = 86400 +# We set this because of bug https://bugs.launchpad.net/tripleo/+bug/1306294 +expiration = 14400 [policy] # driver = keystone.policy.backends.sql.Policy