Known Issues for On-Premises Appliance Version 106.0.0.379
Known Issues for On-Premises Appliance Version 106.0.0.379
The following are the known issues included in this release.
Issue Number | Issue Description | Workaround |
---|---|---|
165909 | Root partition expansion doesn’t work and the related CLI is disabled. | There is no workaround. |
255912 | CDPP 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.
- Unzip if log files are zipped. In this example, the unzipped text file is logsample.log.
- Check current encoding used: file logsample.log > outputs “Little-endian UTF-16 Unicode text,”
- Convert it to UTF-8 as iconv -c -f utf-16 -t utf-8 logsample.log > logsample_utf8.log
- Send logsample_utf8.log to OPLP either as a text file or zipped file.