Bug 1372436 - Login page should display Version Satellite 6.2.2
Summary: Login page should display Version Satellite 6.2.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Branding
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: jcallaha
URL:
Whiteboard:
: 1373180 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-01 17:30 UTC by jcallaha
Modified: 2019-09-25 21:20 UTC (History)
2 users (show)

Fixed In Version: rubygem-foreman_theme_satellite-0.1.28-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-14 21:02:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1885 0 normal SHIPPED_LIVE Satellite 6.2.2 bug fix update 2016-09-15 00:57:56 UTC

Description jcallaha 2016-09-01 17:30:03 UTC
Description of problem:
The current release for 6.2.2 still has 6.2.1 displayed on the login page.

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

How reproducible:
Always

Steps to Reproduce:
1. View login page

Actual results:
Version Satellite 6.2.1

Expected results:
Version Satellite 6.2.2

Additional info:
Both RHEL 6 and RHEL 7

Comment 2 jcallaha 2016-09-05 12:58:37 UTC
*** Bug 1373180 has been marked as a duplicate of this bug. ***

Comment 3 jcallaha 2016-09-09 12:57:23 UTC
Verified in Satellite 6.2.2 Snap 1.1

Login page now branded correctly.

Comment 5 errata-xmlrpc 2016-09-14 21:02:11 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:1885


Note You need to log in before you can comment on or make changes to this bug.