API Guide

Table 18. HTTP response code (continued)
Code Description
429 Too many requests
500 Internal Server error / timeout
For OMIVV-Specific error codes, see OMIVV-Specific error codes on page 47.
Example Response:
{
"repoProfileID": "{Repository profile ID}",
"bundleID": "{Bundle ID}",
"bundles": [
{
"bundleID": "{Bundle ID}",
"name": "{Bundle name}",
"description": "{Bundle description}",
"model": "{Server model name}",
"targetOS": "{Target host OS name}",
"systemId": "{Server unique ID}"
}
],
"components": [
{
"packageID": "{Component unique package ID}",
"rebootRequired":"{host reboot required (True or False)}",
"releaseDate": "{Component release date and month}",
"name": "{Component name}",
"description": "{Component description}",
"supportedHWComponents": [
{
"componentID": "{Component ID}",
"pcieVariants": [
{
"deviceID": "{Device ID}",
"subDeviceID": "{Sub device ID}",
"subVendorID": "{Sub vendor ID}",
"vendorID": "{Vendor ID}"
}
]
},
]
}],
"revisionHistory": "{Revison history}",
"vendorVersion": "{Vendor Version}",
"criticality": "{importance of component update}"
},
NOTE:
After you upgrade OMIVV to 5.2 (RPM Upgrade or backup and restore), the value of model, revisionHistory, and
description are displayed as null until firmware repository is refreshed. To refresh the repository profile, on the repository
profile page, click Edit and complete the wizard without doing any modification.
For more information, see Response body on page 39.
22
Firmware repository inventory management