Created attachment 1201245 [details] pid_grep Description of problem: When refreshing Azure we are hitting an ERROR that is not clear as to what the root cause is: ================================================================== [----] E, [2016-09-13T16:44:22.284233 #12087:c51994] ERROR -- : MIQ(ManageIQ::Providers::Azure::CloudManager::Refresher#refresh) EMS: [SHAREDINFR (EUS2)], id: [10000000000005] Refresh failed [----] E, [2016-09-13T16:44:23.388626 #12087:c51994] ERROR -- : /opt/rh/cfme-gemset/gems/azure-armrest-0.2.8/lib/azure/armrest/armrest_service.rb:442:in `raise_api_exception' [----] E, [2016-09-13T16:44:23.388749 #12087:c51994] ERROR -- : MIQ(ManageIQ::Providers::Azure::CloudManager::Refresher#refresh) EMS: [SHAREDINFR (EUS2)], id: [10000000000005] Unable to perform refresh for the following targets: [----] E, [2016-09-13T16:44:32.511399 #12087:c51994] ERROR -- : MIQ(ManageIQ::Providers::Azure::CloudManager::Refresher#refresh) --- ManageIQ::Providers::Azure::CloudManager [SHAREDINFR (EUS2)] id [10000000000005] ================================================================== Once error has been hit, refresh continues on and completes. Version-Release number of selected component (if applicable): 5.6.1.2
https://github.com/ManageIQ/azure-armrest/pull/212
PR: https://github.com/ManageIQ/azure-armrest/pull/213
this was prematurely moved to POST, moving back to ON_DEV while I make a PR on upstream /master
https://github.com/ManageIQ/manageiq/pull/11401
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/e17872a7c0867935a2f59e481a0ec5e9b091f591 commit e17872a7c0867935a2f59e481a0ec5e9b091f591 Author: Bronagh Sorota <bsorota> AuthorDate: Tue Sep 20 12:41:47 2016 -0400 Commit: Bronagh Sorota <bsorota> CommitDate: Tue Sep 20 12:41:47 2016 -0400 bump azure-armrest gem from version ~>0.3.5 to =0.3.7 https://bugzilla.redhat.com/show_bug.cgi?id=1376468 gems/pending/Gemfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Like the 5.6 version, it's impossible to purposely create a storage account with no keys except by some internal Azure error. I looked at the code, and the storage accounts are all still working, so I'm moving this to verified and I'll keep an eye on it. Verified armrest version was installed.
There is no specific test case for this, but it's kind of in your face on every other test cases for these types of errors.