| Summary: | misspelled VM Attributess (was Compute Profiles) | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lukas Pramuk <lpramuk> |
| Component: | Branding | Assignee: | Shimon Shtein <sshtein> |
| Status: | CLOSED ERRATA | QA Contact: | Lukas Pramuk <lpramuk> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | bbuckingham, ehelms |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | foreman-1.11.0.24-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-27 11:10:12 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Lukas Pramuk
2016-04-06 15:36:06 UTC
if last s is generated? then s/VM Attributes/VM Attribute/ in code will fix it. /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_theme_satellite-0.1.4/lib/locale_change.rb:10: "Smart proxy" => "Capsule", "Compute Profile" => "VM Attributes", "Compute profile" => "VM Attributes", "compute profile" => "VM Attributes", "oVirt" => "RHEV", "ovirt" => "RHEV", "Ovirt" => "RHEV", /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_theme_satellite-0.1.4/lib/tasks/satellite_theme.rake:6: "Smart proxy" => "Capsule", "Compute Profile" => "VM Attributes", "Compute profile" => "VM Attributes", "compute profile" => "VM Attributes", "oVirt" => "RHEV", "ovirt" => "RHEV", "Ovirt" => "RHEV", VERIFIED. @Sat6.2.0-Snap11 foreman-1.11.0.17-1.el7sat.noarch Compute Profiles are again "Compute Profiles" VM Attributes is used elsewhere (when editing a Compute Profile) Fixed comment #5: actually verified with foreman-1.11.0.24-1.el7sat.noarch 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 |