Bug 1197973

Summary:	help text for token_duration confusing
Product:	Red Hat Satellite	Reporter:	Fred van Zwieten <fvzwieten>
Component:	Hosts	Assignee:	Ohad Levy <ohadlevy>
Status:	CLOSED ERRATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.0.7	CC:	bbuckingham, lzap, sthirugn
Target Milestone:	Unspecified	Keywords:	Triaged, UserExperience
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/10194
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 08:49:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Fred van Zwieten 2015-03-03 05:51:17 UTC

Description of problem:
The help text provided for token_duration in the administer -> settings -> provisioning -> token_duration is confusing. It suggests that specifying a value of zero disabled the time-out (meaning the token will never time-out), while it actually means that no token will be generated at all, which will make unattended provisioning across subnets impossible.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
"Time in minutes installation tokens should be valid for, 0 to disable"

Expected results:
"Time in minutes installation tokens should be valid for, 0 to disable token-generation"

Additional info:
Suggestion to remove the possibility to disable token generation. This means check that the value will always be > 0. Then change the help text to "Time in minutes installation tokens should be valid for"

Comment 1 RHEL Program Management 2015-03-03 20:19:23 UTC

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Bryan Kearney 2015-04-17 20:12:42 UTC

Created redmine issue http://projects.theforeman.org/issues/10194 from this bug

Comment 4 Bryan Kearney 2015-05-01 16:05:24 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/10194 has been closed
-------------
Ondrej Prazak
Applied in changeset commit:615728bea09913031537d9b5841284228c983257.

Comment 5 Lukas Zapletal 2015-08-27 14:22:33 UTC

I see this was shipped in 6.1 GA :-)

Comment 8 errata-xmlrpc 2016-07-27 08:49:07 UTC

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/RHBA-2016:1500