Bug 1810773

Summary: Changes to the refresh worker memory threshold are not saving when changed in the UI
Product: Red Hat CloudForms Management Engine Reporter: Ryan Spagnola <rspagnol>
Component: UI - OPSAssignee: Hilda Stastna <hstastna>
Status: CLOSED ERRATA QA Contact: Parthvi Vala <pvala>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: high    
Version: 5.11.2CC: akarol, bmidwood, dmetzger, hkataria, lavenel, mpovolny, obarenbo, pvala, simaishi
Target Milestone: GAKeywords: Reopened, ZStream
Target Release: 5.11.4Flags: pm-rhel: cfme-5.11.z+
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-17 13:11:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:

Description Ryan Spagnola 2020-03-05 21:16:23 UTC 
Description of problem:
Changes are not persisting when increasing the memory threshold value for the refresh worker in the UI

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

How reproducible:
Always

Steps to Reproduce:
1. navigate to Configuration > Settings > EVM Server > Workers tab
2. Change the value for the Refresh worker and click save
3. refresh the page

Actual results:
value reverts to default 2GB

Expected results:
new value persists

Additional info:
Comment 2 Ryan Spagnola 2020-03-05 21:49:36 UTC 
Seeing the same with C&U Data Collectors
Comment 4 Hilda Stastna 2020-03-06 15:46:31 UTC 
This bug is not reproducible in our dev's master branch, nor in 5.11.4.1.20200228172510_c08508d appliance.
I'm closing the bug.
Comment 5 Aziza Karol 2020-03-09 06:41:08 UTC 
Parthvi, 

Please retest and check if it's reproducible on 5.11.4
Comment 6 Parthvi Vala 2020-03-09 06:50:31 UTC 
FIXED. Verified on 5.11.4.1.20200228172510_c08508d.
Comment 9 errata-xmlrpc 2020-03-17 13:11:39 UTC 
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/RHBA-2020:0867