Bug 477650 - satellite webui should display right release version instead of spacewalk's 0.4
Summary: satellite webui should display right release version instead of spacewalk's 0.4
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI
Version: 530
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Devan Goodwin
QA Contact: Jeff Browning
URL:
Whiteboard:
Depends On:
Blocks: 463876
TreeView+ depends on / blocked
 
Reported: 2008-12-22 17:51 UTC by Pradeep Kilambi
Modified: 2009-09-10 18:53 UTC (History)
1 user (show)

Fixed In Version: sat530
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-10 18:53:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
satellite Version footer (138.02 KB, image/jpeg)
2008-12-22 17:51 UTC, Pradeep Kilambi 		no flags Details
View All

Description Pradeep Kilambi 2008-12-22 17:51:46 UTC 
Created attachment 327675 [details]
satellite Version footer

The satellite version in the web ui footer displays wrong version as (RHN Satellite 0.4) instead of 5.3. 

see attachment
Comment 1 Devan Goodwin 2009-01-15 20:22:54 UTC 
Suspect this was a bad patching when the package was built from svn. We're now building from git and in test builds the problem appears to be gone, footer now shows 5.3.0.

Moving to modified and will on_qa once the next QA ISO is ready.
Comment 2 Jeff Browning 2009-02-18 21:28:51 UTC 
Verified as fixed in 530
Comment 3 Preethi Thomas 2009-08-07 11:28:39 UTC 
Release Pending
test1182.test.redhat.com
Comment 4 Brandon Perkins 2009-09-10 18:53:42 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1434.html
Note You need to log in before you can comment on or make changes to this bug.