In the previous version of CloudForms, SmartState collected virtual machine information failed to be stored into VMDB: evm.log stated - "data is not permitted at state finished". This was because there was no finished data event for SmartState Analysis.
This fix adds the state of finished into data event in SmartState Analysis which has now resolved the issue.
DescriptionThomas Hennessy
2016-04-04 14:02:10 UTC
Created attachment 1143359[details]
evm.log lines with 'data is not permitted at state finished' error
Description of problem: CFME 4.0 changed the smartstate collected data criteria such that data collected from a scan is no longer stored into the VMDB when the scan job state is 'finished' . I believe this is an error, and is not the way any prior version of CFME or EVM behaved.
Version-Release number of selected component (if applicable):5.5.2.4
How reproducible: a VM scan job must be in the 'finished' state while the messages associated with the collected data are still pending processing in the message queue.
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: Prior versions of EVM and CFME recognized that the smartstate job status could progress to finished event thought the collected data from these different steps might not yet have been processed into the VMDB, and there was no requirement that the associated job not be in the finished state. This new criteria causes an in-determinant number of scan data elements to fail to be captured into the VMDB even though the resources have been expended to capture and mill the data. Provided log lines shows dozens of error log lines with the "data is not permitted at state finished' error and customer has opened a case complaining that data that is produced by scanning is not consistently represented in CFME standard reports. A review of the 'volumes' table for this case supports this assersion as while there are 400+ vms in inventory there less than 10 VMs in the 'volumes' table for which data exists.
Created attachment 1143360[details]
full output of 'volumes' table showing vm_id with filesystem data from a system with 400+ VMware vms all of which have been scanned
verified this bug in: 5.6.0.4-beta2.3.20160421172650_719e256
evm.log does not have the Error: 'data is not permitted at state finished' error
[root@test log]# grep -i "data is not permitted at state finished" evm.log
[root@test log]#
smart state analysis collected the "used size" data on vmware provider vm's. refer the attached screenshot.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1348
Created attachment 1143359 [details] evm.log lines with 'data is not permitted at state finished' error Description of problem: CFME 4.0 changed the smartstate collected data criteria such that data collected from a scan is no longer stored into the VMDB when the scan job state is 'finished' . I believe this is an error, and is not the way any prior version of CFME or EVM behaved. Version-Release number of selected component (if applicable):5.5.2.4 How reproducible: a VM scan job must be in the 'finished' state while the messages associated with the collected data are still pending processing in the message queue. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Prior versions of EVM and CFME recognized that the smartstate job status could progress to finished event thought the collected data from these different steps might not yet have been processed into the VMDB, and there was no requirement that the associated job not be in the finished state. This new criteria causes an in-determinant number of scan data elements to fail to be captured into the VMDB even though the resources have been expended to capture and mill the data. Provided log lines shows dozens of error log lines with the "data is not permitted at state finished' error and customer has opened a case complaining that data that is produced by scanning is not consistently represented in CFME standard reports. A review of the 'volumes' table for this case supports this assersion as while there are 400+ vms in inventory there less than 10 VMs in the 'volumes' table for which data exists.