Bug 1810773 - Changes to the refresh worker memory threshold are not saving when changed in the UI
Summary: Changes to the refresh worker memory threshold are not saving when changed in...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.11.2
Hardware: All
OS: All
high
high
Target Milestone: GA
: 5.11.4
Assignee: Hilda Stastna
QA Contact: Parthvi Vala
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-05 21:16 UTC by Ryan Spagnola
Modified: 2023-09-07 22:13 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-17 13:11:39 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:
pm-rhel: cfme-5.11.z+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0867 0 None None None 2020-03-17 13:11:49 UTC

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
Note You need to log in before you can comment on or make changes to this bug.