Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1140288 - REST API Event Codes Not Described
REST API Event Codes Not Described
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation (Show other bugs)
3.5.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.5.0
Assigned To: Andrew Burden
Julie
:
Depends On:
Blocks: 1193259
  Show dependency treegraph
 
Reported: 2014-09-10 11:53 EDT by Robert McSwain
Modified: 2015-03-12 20:54 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-03-12 20:54:38 EDT
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)

  None (edit)
Description Robert McSwain 2014-09-10 11:53:51 EDT
Description of problem:
The eventcodes (Fault Codes) are described in:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html-single/Developer_Guide/index.html#Event_Codes

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html-single/Technical_Guide/index.html#Event_Codes

From the Rest Interface we received the following codes who are not described in the Online Documentation:
<code>533</code>
<code>1012</code>
<code>1014</code>
<code>1190</code>

Could you provide the description for these codes currently as well as include them in the docs for 3.5?

Version-Release number of selected component (if applicable):
RHEV 3.3 and beyond
Comment 3 Lucy Bopf 2015-03-04 23:31:29 EST
The table of event codes and their corresponding descriptions has been updated to reflect the full list of events for 3.5.

Updated cs23029 to include Event Codes [9076-745779].

Moving to VERIFIED.

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