Created attachment 1324536 [details] evm.log during SSA on VM's Description of problem: Perform SSA on Windows VM throws "undefined method `[]' for nil:NilClass" error and not capturing Application list from Windows VM. Version-Release number of selected component (if applicable):5.8.2.0.20170824192913_b09a5f8 How reproducible:100% Steps to Reproduce: 1. Add Azure provider 2. Perform SSA on Windows VM 3. Actual results: Throwing error "undefined method `[]' for nil:NilClass" in evm.log Expected results: There should no error in evm.log also scan should retrieve Application from VM. Additional info:
Jerry, Is this addressed by your managed disk/snapshot work?
I don't think so. I am running SSA on 4 different Windows VMs that are completing but I am seeing filesystem errors in the log on some of them. Also some issues with too much data throughput in a short amount of time - probably because I'm running them all concurrently - which could result in data missing. This will require further investigation.
Brad, please weigh in on how big of a deal this is. We set priority to medium but fear it should be higher.
Satyajit, just to be clear, this only affects Azure? The application lists are successfully pulled from windows VMs on saw VMware or RHEV? I spoke to Brad, he wants us confirm its not a specific OS (Jerry's comment 3 seems to indicate that) and that it is isolated to Azure.
Again just to be clear - this is not an issue that occurs on *all* Windows VMs regardless of provider type. Needs to be investigated certainly. It would be nice to determine what the characteristics are for the Windows systems exhibiting this issue.
*** Bug 1502751 has been marked as a duplicate of this bug. ***
https://github.com/ManageIQ/manageiq-smartstate/pull/45 fixes this issue. This may be showing up in various ways in other open BZs as well - will have to search through my list.
https://github.com/ManageIQ/manageiq-providers-azure/pull/168 allows the most recent GEM version to be used which is now 0.2.4 which has been pushed out.
*** Bug 1524415 has been marked as a duplicate of this bug. ***