Bug 1456044 - Azure refresh results in timeout errors
Summary: Azure refresh results in timeout errors
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.6.0
Hardware: All
OS: All
high
medium
Target Milestone: GA
: 5.9.0
Assignee: Daniel Berger
QA Contact: Brandon Squizzato
URL:
Whiteboard: azure:ems_refresh
Depends On:
Blocks: 1459318 1459319
TreeView+ depends on / blocked
 
Reported: 2017-05-26 20:23 UTC by Daniel Berger
Modified: 2018-03-06 15:09 UTC (History)
5 users (show)

Fixed In Version: 5.9.0.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1459318 1459319 (view as bug list)
Environment:
Last Closed: 2018-03-06 15:09:23 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Daniel Berger 2017-05-26 20:23:24 UTC
Description of problem:

In provider regions with large numbers of storage accounts, performing a refresh will sometimes result in a Timeout error or ECONNREFUSED exception as it attempts to collect private image information. When this happens the entire refresh fails.

These errors are coming from Azure and are beyond our control.

Version-Release number of selected component (if applicable):

5.6, 5.7, 5.8

How reproducible:

Sporadic.

Steps to Reproduce:

1. Add Azure cloud provider in region with many storage accounts.
2. Attempt to refresh multiple times.
3. View logs.

Actual results:

Refresh fails with TimeoutException or Errno::ECONNREFUSED.

Expected results:

Refresh skips over such failures and performs the rest of the refresh normally.

Additional info:

This particular issue was addressed by the latest version of the azure-armrest gem which will skip over these errors while collecting private images.

Comment 5 Brandon Squizzato 2018-02-08 16:56:59 UTC
Azure refreshes working fine with CFME 5.9.0.20.20180206200727_d1873b9 using azure-armrest 0.9.5, moving to VERIFIED on the presumption that the newer armrest gem solved the problem as stated.


Note You need to log in before you can comment on or make changes to this bug.