Hello BigFix Community,
We have identified an issue in SCA 2.0 Patch 16 that may cause data import failures after upgrading. This post provides details to help you determine if you are affected and what steps to take.
Who is impacted?
Customers who have upgraded to SCA 2.0 Patch 16. Not all environments are affected, but the issue is not limited to a specific configuration, any customer on Patch 16 could potentially encounter it. We are actively working on identifying the root cause of the issue, a hotfix is available and a fix for GA is currently in progress.
How do I know if I'm affected?
You may be affected if you notice any of the following after upgrading to Patch 16:
- SCA compliance reports are showing outdated or incomplete data that is not refreshing after import
- Data import completes with errors or fails to complete
- Your SCA import log contains any of these error messages:
- Unique constraint violation
- Custom site names as ActionSite
- Unable to find subscribed site analysis
To check your import log, navigate to your SCA server and review the most recent import log entries. If your imports are completed successfully and your reports are showing current data, you are not affected.
How to avoid it?
If you have not yet upgraded to SCA 2.0 Patch 16, we recommend holding off until the fix is available.
What to do if you are impacted?
A hotfix is available for impacted customers. Please contact BigFix Support to request the hotfix and receive guidance on applying it to your environment.
What is the remediation plan?
We are preparing an updated release that permanently resolves this issue. We are targeting a fix in the next few weeks and will update this post once the release is available.
We apologize for the inconvenience and appreciate your patience. If you have any questions, please reach out to BigFix Support or reply to this thread.
Thank you,
– The BigFix Compliance team