Description of problem: worker memory size selection reverts to 200mb if selecting a value of 1gb in the Workers tab Version-Release number of selected component (if applicable): 5.10.1 How reproducible: all the time Steps to Reproduce: 1.go to configure > configuration 2.go to the zone > an_appliance_here 3.go to the workers tab 4. set the size to 250gb and save 5. set the size to 1gb and save Actual results: on step 5, after saving the value displayed will be 200mb. Expected results: on step 5, the result should be to display the 1gb size. Additional info: was previously happening for all values on CF 4.6
Can you verify the steps again: 4) says 250 GB (I'm assuming 250 MB but it's unclear) 5) says 1 GB (I'm assuming 1 GB) Why is step 4 needed? Is the value saved properly after step 4? Is this for ANY worker or specific worker pulldowns? Finally, where are you "displaying" the result after to see the 200 MB value? What does the pulldown show after saving, leaving the page and coming back? What about advanced settings?
if you set it to 250mb (sorry for any typo) that is properly behaving. if you set it to 1gb it isn't. issue has only been tested against the generic worker. I can't comment on other workers. after the selection is made the page refreshes instantly but you can also load any other tab and then go back to the workers tab for the same effect.
Felix, In the UI, with 5.10.1.2, I was able to do this in the dropdowns in the workers tab: 1) change generic worker to 500 MB, save and see 500 MB in dropdown... leaving the tab and returning still show 500 MB 2) change generic worker to 1 GB, save and see 200 MB in dropdown... leaving the tab and returning still show 200 MB (advanced settings shows 1 GB in bytes) This appears to be a visual problem only, since the data is saved correctly but we fail to show the current setting in the dropdown if the current setting is 1 GB or higher. If so, that's a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1656873 Can you confirm it's a duplicate of this? Note, it's fixed on master and scheduled for 5.10.2.x
*** This bug has been marked as a duplicate of bug 1656873 ***