Red Hat Bugzilla – Bug 1324620
Subnets -> Capsules -> `Discovery Proxy` should be renamed to `Discovery Capsule`
Last modified: 2016-07-27 05:31:03 EDT
Created attachment 1144345 [details] Screenshot Description of problem: Subnets -> Capsules -> `Discovery Proxy` should be renamed to `Discovery Capsule` Version-Release number of selected component (if applicable): Satellite 6.2.0-beta-snap2.1 How reproducible: Steps to Reproduce: N/A Actual results: See screenshot Expected results: `Discovery Proxy` should be renamed to `Discovery Capsule` Additional info:
Also the description needs to be updated: Discovery Proxy to use within this subnet for managing connection to discovered hosts to Discovery Capsule to use within this subnet for managing connection to discovered hosts
Discovery plugin does not have valid locale/en folder. Once it is added, I will be able to run branding script on it.
Do you need it upstream Shimon? Can't you add one only for downstream? Since Foreman core does have it, I will add it.
Upstream bug assigned to lzap@redhat.com
Upstream bug component is Discovery Plugin
Moving to POST since upstream bug http://projects.theforeman.org/issues/14589 has been closed ------------- Anonymous Applied in changeset commit:foreman_discovery|9ba5afb4536e62e15240fb3a8c25317f6b59cc6a.
FAILEDQA the fix didn't seem to land in Snap 8.2 yet. The label still says "DNS Proxy". Perhaps this needs to be taken care of in branding?
Yeah, I only enabled i18n to make the change. Shimon, switching over to you, you know the process I guess.
VERIFIED: on sat6.2.0 Beta (GA11) foreman-discovery-image.noarch 1:3.1.1-7.el7sat rubygem-smart_proxy_discovery.noarch 0:1.0.3-3.el6sat tfm-rubygem-foreman_discovery.noarch 0:5.0.0.5-1.el6sat tfm-rubygem-hammer_cli_foreman_discovery.noarch 0:0.0.2.2-1.el6sat This now displays as 'Discovery Capsule'
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-2016:1501