Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 905055

Summary:	when logged in from https://<fqdn>/rhn/ in restricted period message about expiration shown twice
Product:	Red Hat Satellite 5	Reporter:	Jan Hutař <jhutar>
Component:	WebUI	Assignee:	Tomas Lestach <tlestach>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Minar <mminar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	550	CC:	cperry, mkoci, mminar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-10-01 21:55:04 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:
Bug Depends On:
Bug Blocks:	924232

Description Jan Hutař 2013-01-28 13:36:03 UTC

Description of problem:
When I log-in from https://<fqdn>/rhn/ page while in restricted period, message about certificate expiration is shown twice.


Version-Release number of selected component (if applicable):
spacewalk-java-1.7.54-110.el5sat
spacewalk-backend-1.7.38-41.el5sat


How reproducible:
always


Steps to Reproduce:
1. Log-in and log-out using "Sign Out" link in upper right corner in webUI
2. You are on https://<fqdn>/rhn/
3. Use that page to log-in again


Actual results:
Message "Your Satellite Certificate has expired. Your Satellite is on day 1 of 24 day restricted period and will soon stop functioning. Please contact Red Hat for a new certificate." shown twice.


Expected results:
That message should be shown once.

Comment 1 Tomas Lestach 2013-01-29 09:17:16 UTC

spacewalk.git: 6600ee362e3316072604265ca95710de1c7f4238

Comment 4 Clifford Perry 2013-10-01 21:55:04 UTC

Satellite 5.6 has been released. This bug was tracked under the release.  

This bug was either VERIFIED or RELEASE_PENDING (re-verified prior shortly
before release). 

Moving to CLOSED CURRENT_RELEASE. 

Text from Upgrade Erratum follows:

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.

http://rhn.redhat.com/errata/RHEA-2013-1395.html