Description of problem: If a TypeError is encountered while reading the importList from the file's PEheader, the exception is currently not handled, and consequently the data collected from *all* files is discarded and no file information is available. Version-Release number of selected component (if applicable): How reproducible: This occurs only for Windows virtual machines. If the file to be collected contains imports, on rare occasion while computing the end of the name in the PEheader.getImports method invalid data is encountered in the file resulting in a TypeError. This is difficult to reproduce on demand. An example of the relevant stack trace is: /usr/local/rvm/gems/ruby-2.6.3/gems/manageiq-smartstate-0.5.0/lib/metadata/util/win32/peheader.rb:152:in `+' /usr/local/rvm/gems/ruby-2.6.3/gems/manageiq-smartstate-0.5.0/lib/metadata/util/win32/peheader.rb:152:in `block in getImports' /usr/local/rvm/gems/ruby-2.6.3/gems/manageiq-smartstate-0.5.0/lib/metadata/util/win32/peheader.rb:140:in `loop' /usr/local/rvm/gems/ruby-2.6.3/gems/manageiq-smartstate-0.5.0/lib/metadata/util/win32/peheader.rb:140:in `getImports' /usr/local/rvm/gems/ruby-2.6.3/gems/manageiq-smartstate-0.5.0/lib/metadata/util/win32/peheader.rb:94:in `imports' /usr/local/rvm/gems/ruby-2.6.3/gems/manageiq-smartstate-0.5.0/lib/metadata/util/md5deep.rb:166:in `processFile' /usr/local/rvm/gems/ruby-2.6.3/gems/manageiq-smartstate-0.5.0/lib/metadata/util/md5deep.rb:81:in `block in scan_glob Steps to Reproduce: 1. Run SmartState Analysis on a Windows VM containing the invalid files as described above. 2. Set up a collection profile that requests file data from the relevant file. 3. Actual results: No data is collected from any files on the virtual Machine. Expected results: Data is collected from all requested files. Additional info:
Fixed by https://github.com/ManageIQ/manageiq-smartstate/pull/111 - still waiting final merge.
Merged. Moving to POST.
https://github.com/ManageIQ/manageiq/pull/20025
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-2020:2020