Red Hat Bugzilla – Bug 1191584
include Satellite 6 version info in foreman-debug / sosreport
Last modified: 2017-02-23 15:32:58 EST
Description of problem: Quick way to find specific Satellite 6 version through Foreman debug / SoS Report In Satellite 5's Spacewalk-debug you can quickly find out the schema with: ]# cat database-schema-version What is the best practice for quickly getting the Satellite 6 version? (6.* etc.)?
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
(In reply to Ricardo Santamaria from comment #0) > Description of problem: > Quick way to find specific Satellite 6 version through Foreman debug / SoS > Report > Good catch Rikki! Discussed during GSS/Eng Sat6 review to get it into foreman-debug and symlink the file with a more intuitive name. > In Satellite 5's Spacewalk-debug you can quickly find out the schema with: > > ]# cat database-schema-version > Or you could just rpm -q satellite-branding > What is the best practice for quickly getting the Satellite 6 version? (6.* > etc.)? grep -i version /usr/share/foreman/lib/satellite/version.rb Chris (thanks Toledo!) has committed this to git at https://gitlab.sat.lab.tlv.redhat.com/chrobert/foreman/commit/3fb9126ee41df67f0e94e1d7aedaa35a1b9bd39a And https://access.redhat.com/articles/1365633 has been created simlar to RHEL to help find Satellite releases and dates. Xixi
Verified by QE on version Satellite-6.1.0-RHEL-7-20150324.0 foreman-debug satellite_version HOSTNAME: apollo.idmqe.lab.eng.bos.redhat.com OS: redhat RELEASE: Red Hat Enterprise Linux Server release 7.1 (Maipo) FOREMAN: 1.7.2 RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux] PUPPET: 3.6.2 DENIALS: 11 A debug file has been created: /tmp/foreman-debug-S9L98.tar.xz (453136 bytes) You may want to upload the tarball to our public server via rsync. There is a write only directory (readable only by Foreman core developers) for that. Note the rsync transmission is UNENCRYPTED: rsync /tmp/foreman-debug-S9L98.tar.xz rsync://theforeman.org/debug-incoming
I misunderstood the request. I believe the desired output should look like this. HOSTNAME: apollo.idmqe.lab.eng.bos.redhat.com OS: redhat RELEASE: Red Hat Enterprise Linux Server release 7.1 (Maipo) FOREMAN: 1.7.2 SATELLITE: 6.1.0 (Beta) RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux] PUPPET: 3.6.2 DENIALS: 11
Created redmine issue http://projects.theforeman.org/issues/11163 from this bug
waiting on merge https://gitlab.sat.lab.tlv.redhat.com/satellite6/foreman/merge_requests/91
Verified in Sat 6.1.2 z-stream build. I see the satellite version in two places now: 1. At the time of generating the foreman-debug: # foreman-debug Exporting tasks, this may take a few minutes. HOSTNAME: ****** OS: redhat RELEASE: Red Hat Enterprise Linux Server release 7.1 (Maipo) FOREMAN: 1.7.2 SATELLITE: 6.1.1 RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux] PUPPET: 3.6.2 DENIALS: 13 A debug file has been created: /tmp/foreman-debug-R6cjk.tar.xz (848496 bytes) 2. In the generated foreman-debug tar file: foreman-debug.tar/satellite_version: COMMAND> cat /usr/share/foreman/lib/satellite/version.rb module Satellite VERSION = "6.1.1" end
As per Comment 9, the changes are now verified in foreman debug but not in sosreport. @xixi: Can you please review Comment 9 and open an other bug is you need update in sosreport as well.
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-2015:1786
*** Bug 1254557 has been marked as a duplicate of this bug. ***
This patch can be easily missed when rebasing new version. I suggest to refactor this and put this into branding plugin instead. Created a core ticket to allow extension of the summary page: http://projects.theforeman.org/issues/13261