Connection object `scan_devices` method failure on Global assets about nexpose-client HOT 4 OPEN

A possible explanation is that the asset you were previously able to scan is now a member of another site which is picked by find_device_by_address (it picks the first match when the asset belongs to multiple sites) and the asset is excluded from scans of that site.

from nexpose-client.

I don't think that is it. I just had a successful scan on a Global asset using this method, so now it seems there is some other limitation. Other Global assets are still failing, not sure what the link is yet.

from nexpose-client.

@tmsteen - In version 6.5.7, Nexpose added the ability to create sites without specifying any scan targets. I'm wondering if this might be related. Can you confirm what version of Nexpose you are running and whether or not you have any scan targets in the specified site? It's possible this is an issue with the product and not the gem. Was that site dynamic or static? If dynamic, what type of discovery connection is backing it? What type of asset is this?

Edit: I missed your blurb at the bottom stating you are using 6.5.5.

from nexpose-client.

The sites have assets configured. There is a known 'issue' in that I cannot kick of scans for sites without asset or scans where the assets are defined but have not been scanned yet due to the lack of an asset ID.

I have not explicitly tried on sites configured with dynamic assets. All test cases have been in static sites.

I did just see this for last week's product release (6.5.8): "We fixed an issue where scans launched via API request would fail for sites configured with asset group targets". I had failures for sites without asset groups but perhaps there is some other lingering logic.

Now that I see that the issue is not all but just some global assets I need to see if I can nail down another commonality.

from nexpose-client.