Hide Forgot
Description of problem: Version field of capsule displays version of foreman-proxy RPM instead of that it would display the version of the satellite-capsule RPM. Version-Release number of selected component (if applicable):6.2.12 How reproducible: Steps to Reproduce: 1. In all Version 2. 3. Actual results: The Capsule page in the Satellite GUI (Infrastructure -> Capsules -> capsule.example.com) have a version field. This field displays the current version of the foreman-proxy RPM installed on the Capsule. Expected results: Instead of foreman-proxy RPM it would display the version of the satellite capsule RPM. Additional info: The Capsule page in the Satellite GUI (Infrastructure -> Capsules -> capsule.example.com) have a version field. This field displays the current version of the foreman-proxy RPM installed on the Capsule. It would make much more sense to display the version of the satellite-capsule RPM. This would enable to track which Capsules have been updated.
Moving to branding component. In case this is going to be implemented, it should also change /about#smart_proxies page where the same information is displayed.
Created redmine issue http://projects.theforeman.org/issues/22069 from this bug
Upstream bug assigned to sshtein@redhat.com
Waiting for upstream merge.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22069 has been resolved.
For reproducer steps see: https://github.com/theforeman/foreman/pull/5113#issuecomment-367678696 https://github.com/theforeman/foreman/pull/5113#issuecomment-369237733
Upstream discussion yielded to new issue: https://projects.theforeman.org/issues/24567.
*** Bug 1580142 has been marked as a duplicate of this bug. ***
*** Bug 1625748 has been marked as a duplicate of this bug. ***
*** Bug 1625010 has been marked as a duplicate of this bug. ***
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/RHSA-2018:2927