Bug 1553279 – [RFE] Have foreman_theme_satellite read from a file to get Satellite version

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1553279 - [RFE] Have foreman_theme_satellite read from a file to get Satellite version

Summary:	[RFE] Have foreman_theme_satellite read from a file to get Satellite version

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Packaging (Show other bugs)
Sub Component:
Version:	6.3.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified (vote)
Target Milestone:	6.3.1
Target Release:	Unused
Assigned To:	satellite6-bugs
QA Contact:	jcallaha
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-03-08 10:51 EST by Zach Huntington-Meath
Modified:	2018-04-13 09:33 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:	tfm-rubygem-foreman_theme_satellite-1.0.4.17-1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-04-13 09:32:28 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
verification screenshot 1 (4.41 KB, image/png) 2018-03-26 11:25 EDT, jcallaha	no flags	Details
verification screenshot 2 (5.65 KB, image/png) 2018-03-26 11:25 EDT, jcallaha	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:1126	None	None	None	2018-04-13 09:33 EDT

Groups: None (edit)

Description Zach Huntington-Meath 2018-03-08 10:51:58 EST

Description of problem:
Currently we have to update both the Satellite 'meta' rpm and Foreman_theme_satellite everytime we make a new Satellite release. It can be easy to miss updating foreman_theme_satellite which leads to having to rerelease and waste a lot of time.

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

Comment 3 jcallaha 2018-03-26 11:24:50 EDT

Verified in Satellite 6.3.1.

The current Satellite version is stored in /usr/share/satellite/metadata.yml

# cat /usr/share/satellite/metadata.yml
---
version: 6.3.1


Modifying this value will then propagate to the displayed version after restarting katello-services. See attached screenshot for modified version number.

Deleting the file reverts to a displayed version of '0.0.0-development'. See attached screenshot.

Comment 4 jcallaha 2018-03-26 11:25 EDT

Created attachment 1413218 [details]
verification screenshot 1

Comment 5 jcallaha 2018-03-26 11:25 EDT

Created attachment 1413219 [details]
verification screenshot 2

Comment 7 errata-xmlrpc 2018-04-13 09:32:28 EDT

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:1126

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