Cisco Bug: CSCvu28229 - Prime Infrastructure Compliance Job produces a report but Idle Time Limit setting causes job to fail
Jun 12, 2020
- Cisco Prime Infrastructure
Known Affected Releases
Symptom: When a Compliance Job is run, after a period of time, the job fails, no Violations Report is generated. tail -F /opt/CSCOlumos/logs/ifm_compliance.log shows the job stuck at 99% until Idle Time Out is reached. IFM_COMPLIANCE_INFO: [[com.cisco.ifm.compliance.auditjobmgmt.CreateAuditJob] jobId :: 12256477302 :: Audit job Status :: RUNNING :: percentageCompleted :: 99] IFM_COMPLIANCE_INFO: [[com.cisco.ifm.compliance.auditjobmgmt.CreateAuditJob] Going to Sleep for seconds :-30 jobId :: 12256477302] For 5 minute timeouts, the POLICY_GROUP_VIOLATIONS and POLICY_GROUP_VIOLATIONSDATA database tables get populated, but the ICOMPLIANCE_CHECK table does not. For 15 minute timeouts, all 3 get populated and we can see the results. Conditions: Idle Time Limit accepts a value of 5 to 30 minutes. Compliance jobs continue to run beyond 5 or 30 minutes. Also, no report is seen after the job fails.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases