Known Issues for Virtual Appliance Version

Known Issues for Virtual Appliance Version

The following are the known issues included in this release.

Issue NumberIssue DescriptionWorkaround
165909Root partition expansion doesn’t work and the related CLI is disabled.There is no workaround.
255912CDPP data wasn’t cleaned up after resetting an appliance.There is no workaround.

Currently, discovery / OPLP can accept log files, system logs, and custom parsers files in UTF-8 encoding only.

If these files are encoded using other encodings, we may fail to parse them properly. This will manifest as UnicodeDecodeError in our logs.

The best practice is to set UTF-8 as the default encoding in all pipelines feeding into OPLP. UTF-8 can handle any character set, so this will not result in any information loss.

For the log files that are already encoded without using UTF-8, convert these files to UTF-8 before uploading them to OPLP.

The following is an example using a file that is encoded in UTF-16.

  1. Unzip if log files are zipped.  In this example, the unzipped text file is logsample.log.
  2. Check current encoding used: file logsample.log > outputs “Little-endian UTF-16 Unicode text,”
  3. Convert it to UTF-8 as  iconv -c -f utf-16 -t utf-8 logsample.log > logsample_utf8.log
  4. Send logsample_utf8.log to OPLP either as a text file or zipped file.
Share this Doc

Known Issues for Virtual Appliance Version

Or copy link

In this topic ...