Bug 1482028 - Azure refresh worker becomes unresponsive during refresh
Summary: Azure refresh worker becomes unresponsive during refresh
Keywords:
Status: CLOSED DUPLICATE of bug 1431912
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.8.3
Assignee: Bronagh Sorota
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks: 1503797
TreeView+ depends on / blocked
 
Reported: 2017-08-16 09:56 UTC by Felix Dewaleyne
Modified: 2020-12-14 09:33 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-28 15:05:48 UTC
Category: ---
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Felix Dewaleyne 2017-08-16 09:56:52 UTC 
Description of problem:
During all refreshes, the Azure worker is becoming unresponsive

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

How reproducible:
all the time

Steps to Reproduce:
1.refresh the worker (manually or automatically)
2.
3.

Actual results:
the worker processes some information then becomes unresponsive and gets killed.

Expected results:
the refresh worker finishes

Additional info:
Comment 7 Dave Johnson 2017-08-21 15:58:02 UTC 
Pretty sure there is a workaround for this that allows the severity to be dropped.  Bronagh, can you confirm and maybe document said workaround?
Comment 10 Dave Johnson 2017-08-21 16:53:16 UTC 
Okay, I was mistaken, no known workaround, bumping back to high severity.
Comment 15 Tina Fitzgerald 2017-08-23 19:44:04 UTC 
Hi Felix,

Can you ask the customer to provide us with a set of logs from an Azure refresh and metrics collection?

Thanks,
Tina
Comment 28 Bronagh Sorota 2017-09-27 13:48:45 UTC 
Yes there is Felix, here you go:
https://bugzilla.redhat.com/show_bug.cgi?id=1431912
Comment 29 Felix Dewaleyne 2017-09-28 15:05:48 UTC 

*** This bug has been marked as a duplicate of bug 1431912 ***
Note You need to log in before you can comment on or make changes to this bug.