Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 921023 - There is a minor typo on CIM configuration page
There is a minor typo on CIM configuration page
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
6.4
Unspecified Unspecified
high Severity low
: rc
: ---
Assigned To: Fabian Deutsch
Virtualization Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-13 06:32 EDT by Guohua Ouyang
Modified: 2014-01-21 14:28 EST (History)
13 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
On the cim configuration page, there was a minor typing error "CIM Configuation", missing the character "r" in the word "configuration". This was fixed un the UI redesign.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-01-21 14:28:04 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0033 normal SHIPPED_LIVE ovirt-node bug fix and enhancement update 2014-01-21 19:14:30 EST

  None (edit)
Comment 2 Mike Burns 2013-06-10 19:32:55 EDT
Should be fixed with ui re-design
Comment 5 cshao 2013-11-13 00:30:05 EST
Test version:
rhevh-6.5-20131031.1.0
ovirt-node-3.0.1-7.el6.noarch

On cim configuration page, it show as CIM configuration, so the bug is fixed, change bug status to VERIFIED.
Comment 7 errata-xmlrpc 2014-01-21 14:28:04 EST
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.

http://rhn.redhat.com/errata/RHBA-2014-0033.html

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