Ovf_ParseIssue

Ovf_ParseIssue
Ovf_ParseIssue

The ParseIssue structure contains the information about the issue found when parsing an OVF package during deployment or exporting an OVF package including:

  • Parsing and validation error on OVF descriptor (which is an XML document), manifest and certificate files.
  • OVF descriptor generating and device error.
  • Unexpected server error.
JSON Example
{
    "category": "string",
    "file": "string",
    "line_number": 0,
    "column_number": 0,
    "message": {
        "id": "string",
        "default_message": "string",
        "args": [
            "string"
        ],
        "params": {
            "params": {
                "s": "string",
                "dt": "string",
                "i": 0,
                "d": "number",
                "l": {
                    "id": "string",
                    "params": {
                        "params": "Std_LocalizationParam Object"
                    }
                },
                "format": "string",
                "precision": 0
            }
        },
        "localized": "string"
    }
}
category
Required

The ParseIssue.Category enumerated type defines the categories of issues that can be found when parsing files inside an OVF package (see ParseIssue) including OVF descriptor (which is an XML document), manifest and certificate files, or exporting an OVF package.
VALUE_ILLEGAL : Illegal value error. For example, the value is malformed, not a number, or outside of the given range, and so on.
ATTRIBUTE_REQUIRED : Required attribute error. It indicates that a required attribute is missing from an element in the OVF descriptor.
ATTRIBUTE_ILLEGAL : Illegal attribute error. It indicates that an illegal attribute is set for an element in the OVF descriptor. For example, empty disks do not use format, parentRef, and populatedSize attributes, if these attributes are present in an empty disk element then will get this pasrse issue.
ELEMENT_REQUIRED : Required element error. It indicates that a required element is missing from the OVF descriptor.
ELEMENT_ILLEGAL : Illegal element error. It indicates that an element is present in a location which is not allowed, or found multiple elements but only one is allowed at the location in the OVF descriptor.
ELEMENT_UNKNOWN : Unknown element error. It indicates that an element is unsupported when parsing an OVF descriptor.
SECTION_UNKNOWN : Section unknown error. It indicates that a section is unsupported when parsing an OVF descriptor.
SECTION_RESTRICTION : Section restriction error. It indicates that a section appears in place in the OVF descriptor where it is not allowed, a section appears fewer times than is required, or a section appears more times than is allowed.
PARSE_ERROR : OVF package parsing error, including:

  • OVF descriptor parsing errors, for example, syntax errors or schema errors.
  • Manifest file parsing and verification errors.
  • Certificate file parsing and verification errors.
    GENERATE_ERROR : OVF descriptor (which is an XML document) generating error, for example, well-formedness errors as well as unexpected processing conditions.
    VALIDATION_ERROR : An issue with the manifest and signing.
    EXPORT_ERROR : Issue during OVF export, for example, malformed deviceId, controller not found, or file backing for a device not found.
    INTERNAL_ERROR : Server encountered an unexpected error which prevented it from fulfilling the request.
string
file
Required

The name of the file in which the parse issue was found.

integer As int64
line_number
Required

The line number of the line in the file (see ParseIssue.file) where the parse issue was found (or -1 if not applicable).

integer As int64
column_number
Required

The position in the line (see ParseIssue.line-number) (or -1 if not applicable).

message
Required

The LocalizableMessage structure represents localizable string and message template. Services include one or more localizable message templates in the errors they report so that clients can display diagnostic messages in the native language of the user. Services can include localizable strings in the data returned from operations to allow clients to display localized status information in the native language of the user.