Bug 1330673 - Strings do not get branded without changing the PO files
Summary: Strings do not get branded without changing the PO files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Branding
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: jcallaha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-26 17:11 UTC by Shimon Shtein
Modified: 2019-09-25 21:19 UTC (History)
6 users (show)

Fixed In Version: rubygem-foreman_theme_satellite-0.1.15-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:02:01 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Shimon Shtein 2016-04-26 17:11:11 UTC
Description of problem:

Currently the build process gets very complicated. It assumes running a special task each time strings are added to upstream.


Steps to Reproduce:
1. Take a new version from upstream with new branded strings
2. Package foreman
3. Observe new strings don't get branded.

Comment 3 Shimon Shtein 2016-05-29 07:55:38 UTC
I wouldn't call that easy, but there's a way to do it by messing a bit with required gems and documentation:

1. Run 'foreman-rake apipie:cache' it should generate new documentation
2. Go to documentation for V2, look for PUT "/discovered_hosts/:id/" description
3. The description for ip parameter will state "not required if using a subnet with DHCP capsule" as it should

4. Remove dependency on foreman_theme_satellite

5. Run 'foreman-rake apipie:cache' it should generate new documentation
6. Go to documentation for V2, look for PUT "/discovered_hosts/:id/" description
7. The description for ip parameter will state "not required if using a subnet with DHCP proxy" instead of "...DHCP capsule"

Another string that I found that is not branded in PO (and needs on the fly branding) is an error message when refreshing facts:

1. Use discovery to discover a new host (any host)
2. Shut down the proxy (capsule) that is responsible for discovery
3. Refresh the facts for the host
4. Should show an exception that starts with "Could not get facts from capsule..."

5. remove dependency on foreman_theme_satellite

6. Refresh the facts for the host
7. Should show an exception that starts with "Could not get facts from proxy..." instead of "capsule"

Comment 7 jcallaha 2016-06-17 15:50:33 UTC
Dev task, marking as Verified.

Comment 8 Bryan Kearney 2016-07-27 11:02:01 UTC
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


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