Red Hat Bugzilla – Bug 1186937
Infrastructure > Compute Resources > New Compute Resource: VMware shouldn't have a capital W
Last modified: 2016-07-27 04:46:59 EDT
Description of problem: If you try to create a New Compute Resource, we offer the ability to add a VMware system. In the dropdown for Provider though, we have it shown as "VMWare", when if you go to their website, they don't capitalize the W, it's just "VMware". We should update the string to be "VMware" so that we reflect their name properly. Version-Release number of selected component (if applicable): 6.0.6
Created attachment 985384 [details] Provider = VMWare
Created attachment 985385 [details] "VMware" is how it should be capitalized
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.
Created redmine issue http://projects.theforeman.org/issues/9452 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/9452 has been closed ------------- Anonymous Applied in changeset commit:ba2a9e1b8006af7f68a2c3caf5658ade0165fa1f.
Verified in upstream: foreman-proxy-1.10.0-0.develop.201508250705gitb446e0c.el6.noarch rubygem-smart_proxy_discovery-1.0.2-1.el6.noarch foreman-1.10.0-0.develop.201508241946git8658fa3.el6.noarch foreman-release-1.10.0-0.develop.201508241946git8658fa3.el6.noarch ruby193-rubygem-hammer_cli_import-0.10.21-3.el6.noarch ruby193-rubygem-hammer_cli_foreman_docker-0.0.3-3.el6.noarch ruby193-rubygem-hammer_cli-0.3.0-1.201508241209git174f507.el6.noarch ruby193-rubygem-hammer_cli_foreman_tasks-0.0.7-2.el6.noarch ruby193-rubygem-hammer_cli_foreman_bootdisk-0.1.3-2.el6.noarch ruby193-rubygem-hammer_cli_katello-0.0.17-1.el6.noarch Now VMware is correctly named under New compute-resource -. Providers. Please see the attached screenshot
Created attachment 1069005 [details] Vmware is correctly named under Compute-resource -> Providers
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:1500