)]}'
{"validations/undercloud-tokenflush.yaml":[{"author":{"_account_id":4330,"name":"Tomas Sedovic","email":"tsedovic@redhat.com","username":"tomas-8c8"},"change_message_id":"85f7b8683bda27aa8730c1b937fdf446de7fa60b","unresolved":false,"context_lines":[{"line_number":7,"context_line":"        Without a token_flush crontab enabled for the keystone user, the keystone database can grow very large.  This validation checks that the keystone token_flush crontab has been set up."},{"line_number":8,"context_line":"      groups:"},{"line_number":9,"context_line":"      - post-deployment"},{"line_number":10,"context_line":"    cron_check: \"@hourly /bin/keystone-manage token_flush\""},{"line_number":11,"context_line":"  tasks:"},{"line_number":12,"context_line":"  - name: Get keystone crontab"},{"line_number":13,"context_line":"    become: true"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3ac371cc_24414eaa","line":10,"updated":"2016-08-16 14:01:03.000000000","message":"What do you think about dropping the `@hourly` bit and just check that there is a cron entry for flushing the tokens?\n\nI\u0027m thinking people may decide to set up a different time interval but dunno how much is that a real issue.","commit_id":"6467193ad91cf0dabe5a5c335eb78523153229aa"},{"author":{"_account_id":13039,"name":"Martin André","email":"m.andre@redhat.com","username":"mandre"},"change_message_id":"67935e87afa3db07fda10ef108674581d2a82a8e","unresolved":false,"context_lines":[{"line_number":9,"context_line":"        the keystone token_flush crontab has been set up."},{"line_number":10,"context_line":"      groups:"},{"line_number":11,"context_line":"      - post-deployment"},{"line_number":12,"context_line":"    cron_check: \"/bin/keystone-manage token_flush\""},{"line_number":13,"context_line":"  tasks:"},{"line_number":14,"context_line":"  - name: Get keystone crontab"},{"line_number":15,"context_line":"    become: true"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"1ac06dbe_7ce3e633","line":12,"updated":"2016-08-22 08:38:49.000000000","message":"In my environment, the crontab for keystone user is set as following:\n\n    # HEADER: This file was autogenerated at 2016-08-04 11:32:57 +0000 by puppet.\n    # HEADER: While it can still be managed manually, it is definitely not recommended.\n    # HEADER: Note particularly that the comments starting with \u0027Puppet Name\u0027 should\n    # HEADER: not be deleted, as doing so could cause duplicate cron jobs.\n    # Puppet Name: keystone-manage token_flush\n    PATH\u003d/bin:/usr/bin:/usr/sbin SHELL\u003d/bin/sh\n    1 0 * * * keystone-manage token_flush \u003e\u003e/dev/null 2\u003e\u00261\n\nI suggest dropping the path to the keystone-manage command in your check to avoid false positive.","commit_id":"b7ebee5182f92ed75a4647b73d2827cbfbe632e9"}]}