Bug 1274073

Summary: After running the update instructions from 2.3 to 2.4 spacewalk still showing 2.3 on login page at bottom
Product: [Community] Spacewalk Reporter: David Stratman <david.stratman>
Component: WebUIAssignee: Michael Mráka <mmraka>
Status: CLOSED EOL QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 2.4   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-21 12:27:30 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:
Attachments:
Description Flags
Showing banner on bottom of page after upgrade to 2.4 none

Description David Stratman 2015-10-21 20:19:03 UTC
Created attachment 1085322 [details]
Showing banner on bottom of page after upgrade to 2.4

Document URL: https://fedorahosted.org/spacewalk/wiki/HowToUpgrade

Section Number and Name: How to Upgrade Spacewalk from 2.3 to 2.4

Describe the issue:  After completing the upgrade, the server login page at the bottom is still saying Spacewalk 2.3.  What is the easiest way to validate the 2.4 update, and how can we manually fix the login page issue showing the older version?

Suggestions for improvement: 

Additional information: 

Description of problem:


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


How reproducible: Have not attempted to reproduce it.


Steps to Reproduce:
1. Followed install steps here:  https://fedorahosted.org/spacewalk/wiki/HowToUpgrade  for the internal/default postgres DB (not an exterior DB)
2. Started spacewalk back up -- shows old information on the bottom of the screen.

Actual results:
Spacewalk 2.3 displaying

Expected results:
Spacewalk 2.4 displaying

Additional info:

Comment 1 Michael Mráka 2019-10-21 12:27:30 UTC
Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.