From 79aca264fff6126edd98d480c2233cbddac64432 Mon Sep 17 00:00:00 2001
From: Juan Antonio Osorio Robles <jaosorior@redhat.com>
Date: Fri, 4 Aug 2017 08:36:42 +0300
Subject: [PATCH] Use number for KeystoneCronTokenFlushMaxDelay instead of
 string

Using a string results in an erroneous check in puppet-keystone, which
sets up a zero where it shouldn't. So we change it to number to avoid
that. Note that there will also be a puppet-keystone fix for this.
Changing the value here assures that deployers only give valid values to
this parameter.

Change-Id: I00823e23358df91ce54f421c12636f05d4196e15
Closes-Bug: #1708584
---
 puppet/services/keystone.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/puppet/services/keystone.yaml b/puppet/services/keystone.yaml
index 8796209ba3..218ba740bc 100644
--- a/puppet/services/keystone.yaml
+++ b/puppet/services/keystone.yaml
@@ -178,10 +178,10 @@ parameters:
         Cron to purge expired tokens - Week Day
     default: '*'
   KeystoneCronTokenFlushMaxDelay:
-    type: string
+    type: number
     description: >
         Cron to purge expired tokens - Max Delay
-    default: '0'
+    default: 0
   KeystoneCronTokenFlushDestination:
     type: string
     description: >