Red Hat Bugzilla – Bug 1438092
[Regression] Azure provider refresh fails
Last modified: 2017-05-31 10:45:26 EDT
New commit detected on ManageIQ/manageiq-providers-azure/fine: https://github.com/ManageIQ/manageiq-providers-azure/commit/052a5f6f9b9dd7eb17bac1097a016776f3778e21 commit 052a5f6f9b9dd7eb17bac1097a016776f3778e21 Author: Greg Blomquist <blomquisg@gmail.com> AuthorDate: Fri Mar 31 16:34:09 2017 -0400 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Fri Mar 31 18:06:23 2017 -0400 Merge pull request #42 from djberg96/armrest_version Update armrest version to 0.7.0 (cherry picked from commit c318b5deb87c8f114921bbdd8d84c2abcfb19dd5) https://bugzilla.redhat.com/show_bug.cgi?id=1438092 manageiq-providers-azure.gemspec | 2 +- .../azure/cloud_manager/refresher_spec.rb | 6 +- .../discover/with_all_existing_records.yml | 1906 ++++---- .../discover/with_no_existing_records.yml | 1976 ++++---- .../discover/with_some_existing_records.yml | 1940 ++++---- .../cloud_manager/discover/with_the_same_name.yml | 1976 ++++---- .../with_the_same_name_and_backup_name.yml | 1978 +++++---- ..._name_backup_name_and_secondary_backup_name.yml | 1978 +++++---- .../providers/azure/cloud_manager/refresher.yml | 4696 +++++++++++++------- 9 files changed, 9482 insertions(+), 6976 deletions(-)
New commit detected on ManageIQ/manageiq-gems-pending/fine: https://github.com/ManageIQ/manageiq-gems-pending/commit/aaee67427bce5ae3023827afe0e966bf38c7b2f0 commit aaee67427bce5ae3023827afe0e966bf38c7b2f0 Author: Greg Blomquist <blomquisg@gmail.com> AuthorDate: Fri Mar 31 13:40:44 2017 -0400 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Fri Mar 31 18:03:47 2017 -0400 Merge pull request #100 from djberg96/armrest_version Update the armrest version to 0.7.0. (cherry picked from commit eeb4a3e3ad4283968d3f1f0e70642c488d527a5c) https://bugzilla.redhat.com/show_bug.cgi?id=1438092 manageiq-gems-pending.gemspec | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
Verified in 5.8.0.10
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:1367