keystone_cron container doesn't need to be deployed if fernet token is used.

Bug #1820784 reported by Keigo Noha
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Incomplete
Medium
Unassigned

Bug Description

Current T-H-T deploys keystone_cron container in containerized environment. The container runs a cron job that runs 'keystone-manage token_flush' periodically. However, the current default token is fernet token. It is not stored in DB and we don't need to do a token_flush with fernet token.

tags: added: tech-debt
Changed in tripleo:
milestone: none → train-1
importance: Undecided → Medium
status: New → Triaged
tags: removed: tech-debt
Changed in tripleo:
milestone: train-1 → train-2
Changed in tripleo:
milestone: train-2 → train-3
Changed in tripleo:
milestone: train-3 → ussuri-1
Changed in tripleo:
milestone: ussuri-1 → ussuri-2
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-2 → ussuri-3
wes hayutin (weshayutin)
Changed in tripleo:
status: Triaged → Incomplete
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-3 → ussuri-rc3
wes hayutin (weshayutin)
Changed in tripleo:
milestone: ussuri-rc3 → victoria-1
Revision history for this message
Keigo Noha (knoha) wrote :
Changed in tripleo:
milestone: victoria-1 → victoria-3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.