You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
@mdvickst commented on Mon May 21 2018
Specify type:
Priority:
Description:
Systems without RPM command show up as having 1 EAP package. I believe it's counting the error as a package.
Acceptance Criteria:
Bug Report
Version Information:
CLI Server Version or commit information.
Expected behavior:
Describe the expected behavior for the program.
Actual behavior:
Provide the actual behavior for the program.
Steps to reproduce:
List clear steps to reproduce the bug.
Environment information:
Provide detailed information on the scanning and target systems (if applicable); see example below.
@noahl commented on Mon May 21 2018
@mdvickst do you happen to have the input logs from the quipucords machine that did this?
The postprocessing for
jboss.eap.packages
happens at https://github.com/quipucords/quipucords/blob/master/quipucords/scanner/network/processing/eap.py#L137 . I would have expected the processing framework to notice that the command failed with a nonzero return value and automatically discard the result. I want to figure out why that didn't happen.@kholdaway commented on Mon May 21 2018
@mdvickst Can you provide the details report/summary report for that system?
The text was updated successfully, but these errors were encountered: