Bug 1620182

Summary:	EOL Banner: 'insure' should be 'ensure'
Product:	Red Hat Satellite 5	Reporter:	Grant Gainey <ggainey>
Component:	WebUI	Assignee:	Grant Gainey <ggainey>
Status:	CLOSED ERRATA	QA Contact:	Radovan Drazny <rdrazny>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	580	CC:	rdrazny, rjerrido, tkasparek, tlestach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-10 12:16:10 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 Grant Gainey 2018-08-22 15:43:00 UTC

Description of problem:

EOL banner has this sentence:

"In order to insure no interruption to your ability to..."

Bad word-choice - should be "In order to ENsure..."

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

5.6
5.7
5.8

Comment 7 Radovan Drazny 2018-09-04 16:16:35 UTC

Tested on:
Sat 5.8: spacewalk-java-2.5.14-122
Sat 5.7: spacewalk-java-2.3.8-168
Sat 5.6: spacewalk-java-2.0.2-120

The word "ensure" is present now, but I have noticed another problem, time related this time. When I set the system date to Jan 30 2019 (on a Sat 5.7 for example), I get a message "Your Red Hat Satellite 5.7.0 has reached its end-of-life date as of 2019-01-31...", although the date 2019-01-31 has not been reached yet. Setting the date to Jan 29 2019 produces a message "1 day to go", etc. It seems the counter is off by one.

Comment 10 Radovan Drazny 2018-09-07 12:43:16 UTC

Verified on:
Sat 5.8 spacewalk-java-2.5.14-124.el6sat
Sat 5.7 spacewalk-java-2.3.8-170.el6sat
Sat 5.6 spacewalk-java-2.0.2-122.el6sat

The EOL banner contains the word "ensure", and the countdown to EOL date is correct. 

VERIFIED

Comment 12 errata-xmlrpc 2018-09-10 12:16:10 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-2018:2662