Red Hat Bugzilla – Bug 1166167
Set token_duration to 6 hours instead of one hour
Last modified: 2017-02-23 15:47:18 EST
During OpenStack provisioning on Dell hardware, it was reported that installation took longer than one hour. It was perhaps a remote site with slower connection, I haven't investigated. I think new default value which is still sane could be six hours which "ought to be enough for everybody". Since this is not big deal (tokens are UUID, safe enough) I propose to set this as in Subject. Discuss.
Created from redmine issue http://projects.theforeman.org/issues/7994
I am pulling down important features from the 1.7 release. You can read more abotu this feature at http://theforeman.org/manuals/1.7/index.html#Releasenotesfor1.7 I believe that QE will be done by the community on this feature.
Moving to POST since upstream bug http://projects.theforeman.org/issues/7994 has been closed ------------- Lukas Zapletal Applied in changeset commit:c0262662d355cef3c4bc5371fe224f3f4f7d3dd3.
Verified with: Satellite-6.1.0-RHEL-6-20150210.0 Sat6.1.0 beta snap2 token_duration is set to 360 ( time in minutes) which is equal to 6 hours.
Created attachment 991361 [details] token duration set to 360
This bug is slated to be released with Satellite 6.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592