Known Issues and Limitations

The known issues addressed in the JSA 7.5.0 Update Package 6 are listed below:

• An issue can occur where the Risks tab does not load as expected after an upgrade from JSA 7.5.0 Update Package 5 to JSA 7.5.0 Update Package 6.

• Upgrades to JSA 7.5.0 Update Package 5 might take an extended amount of time to complete due to glusterfs file cleanup. You must allow the upgrade to continue uninterrupted.

• After upgrading to JSA 7.5.0 Update Package 5, WinCollect 7.X agents can experience management or configuration change errors.

• It is possible for autoupdates to revert to a previous version of autoupdates after upgrading. This will cause autoupdate to not work as intended.

  After you upgrade to JSA 7.5.0 or later, type the following command to check your autoupdate version:

  /opt/qradar/bin/UpdateConfs.pl -v

• Docker services fail to start on JSA appliances that were originally installed at JSA release 2014.8 or earlier, then upgraded to 7.5.0 Update Package 2 Interim Fix 02 or 7.5.0 Update Package 3.

  Before you upgrade to JSA 7.5.0 Update Package 2 Interim Fix 02, run the following command from the JSA Console:

  xfs_info /store | grep ftype

  Review the output to confirm the ftype setting. If the output setting displays "ftype=0", do not proceed with the upgrade to 7.5.0 Update Package 2 Interim Fix 02 or 7.5.0 Update Package 3.

  See KB69793 for additional details.

• After you install JSA 7.5.0, your applications might go down temporarily while they are being upgraded to the latest base image.

• After upgrading some apps remain in "error" state on deployments with more than 30 apps. Restart the apps by using the qappmanager: /opt/qradar/support/qappmanager.

• When adding a Data Node to a cluster, they must either all be encrypted, or all be unencrypted. You cannot add both encrypted and unencrypted Data Nodes to the same cluster.