Known Issues for Virtual Appliance Version 121.0.0

Known Issues for Virtual Appliance Version 121.0.0

The following are the known issues included in this release.

Issue Number	Issue Description	Workaround
563349	The virtual IP (VIP) can stop responding in unknown scenarios while the health status of both appliances (master and backup) look correct per the CLI status commands, resulting in data path downtime. This issue is not easily reproduced and can occur right after an appliance software upgrade.	Perform a manual failover by running the failover CLI command on the master appliance. You can also perform the following checks after a successful appliance software upgrade: Ensure that both appliances (master and backup) in the HA deployment show the HA status as expected. Ensure that the VIP responds to the curl and telnet commands on the proxy listener port after the upgrade. If step 2 was not successful, execute the manual failover and wait for the appliances to transition to the correct master and backup states. Then perform step 2 again.

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.