Issue Summary
As a possible workaround for JSDSERVER-11098 we tested the following, resulting in the Import removing All the files from the Import Directory, but only importing the Agent's XML file...
Steps to Reproduce
- have a Discovery Agent (Windows) transfer its local Scan Result file to a Discovery\Scans folder of a Discovery tool
- Set up the Discovery Tool to Export to Cloud, with a valid Cloud import token
- Execute the Discovery Tool scan
Expected Results
Both files in the Scans folder will be exported to cloud
Actual Results
Only the Agent xml is exported / imported into cloud, and the Discovery Scan Result is not - both files are removed from the scans directory
Workaround
This was intended to be a workaround for JSDSERVER-11098
Currently there is no workaround.
NOTE:
Tested also:
a. The Discovery Tool is exporting using File Copy to another Directory
b. Using a Collector to File Copy the Discovery Zip and XML to another Directory
In both cases - the result is 1 zip file containing 3 files:
Discovery Settings result xml
Hosts Scan xml
Agent Scan xml
However - attempting to use the Collector to export the Zipped file to cloud - results the same: only the Agent's XML is imported, but the Zip is removed from the import directory.
Bug
Low
Fixed as part of https://jira.atlassian.com/browse/JSDCLOUD-10648. Please let us know if any issues persist