Description of problem: After successfully added the Azure provider into CF, it is not detecting any changes to Azure. For example, it discovered 1 instance on Azure, but not the one created afterward. [----] E, [2017-03-09T16:06:45.748870 #12099:a8d130] ERROR -- : MIQ(ManageIQ::Providers::Azure::CloudManager::Refresher#refresh) EMS: [Azure US East], id: [1000000000009] Refresh failed [----] E, [2017-03-09T16:06:45.750917 #12099:a8d130] ERROR -- : [NoMethodError]: undefined method `offer' for #<Azure::Armrest::VirtualMachineModel::Properties::StorageProfile::ImageReference:0x0000000fbaad10> Method:[rescue in block in refresh] [----] E, [2017-03-09T16:06:45.751127 #12099:a8d130] ERROR -- : /var/www/miq/vmdb/app/models/manageiq/providers/azure/cloud_manager/refresh_parser.rb:254:in `guest_os' /var/www/miq/vmdb/app/models/manageiq/providers/azure/cloud_manager/refresh_parser.rb:246:in `process_os' Version-Release number of selected component (if applicable): 5.7.1.3-20170221135006_818f133 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This was addressed in https://github.com/ManageIQ/manageiq-providers-azure/pull/37. I've since added a backport label for Euwe. However, we need to determine how an image without the offer attribute was generated in the first place in order to deal with stuff like this in a more robust manner. Can you tell me more about how this particular image was created?
Ok, I see the issue now. Azure has been encouraging a switch from individual storage accounts to managed accounts, and so the properties we assumed would always be there are not there. I need to update the refresher and also the azure-armrest gem.
https://github.com/ManageIQ/manageiq-providers-azure/pull/41
Refresh is working find with 5.8.0.11 Moving to verified.