Hide Forgot
Description of problem: http_proxy settings will never revert back Version-Release number of selected component (if applicable): CFME 5.6.1 How reproducible: 100% Steps to Reproduce: 1. Set http_proxy related settings through UI and Save 2. Delete the settings and leave the parameters blank and then Save Actual results: The settings will revert back to the settings I made in step 1 Expected results: The http_proxy settings should be able to be cleared Additional info:
The problem is you really cannot delete from the advanced settings, you can only change the values. To disable the proxy, try setting the 'host' to false. That should have the desired effect in this case.
Setting it to false works, but it's not obvious this would be a choice. People are going to have to walk though setting it, changing it, wondering why it's not working, do some google searches, and hopefully stumble across this bz like I did. I set the doc type to known issue so that we make sure it's documented as clearly as possible. It's getting pretty late in the release I would think. Anyway, I added a suite of test cases to cover all these possibilities so at least they will be tracked regularly going forward. Whatever we all decide is fine, but I'm assigned the qe contact to myself.
*** Bug 1405482 has been marked as a duplicate of this bug. ***
Chen, looks like this became a known issue for doc. Should this be re-assigned to documentation? (Note that the SF has been closed)
We might be able to document this as I've since found a workaround. You can create a settings.local.yml that basically clears (overrides) the values after you restart the evm services.
Hi Marianne, Jeff, Thank you for your efforts on this bug. Since this is expected behaviour and we have workarounds, yes I agree that we should be clear in the docs to show how to make the options in advanced settings empty. I noticed that this depends on the option itself in comment #4 (sometimes '' sometimes false in this case). Best Regards, Chen
*** This bug has been marked as a duplicate of bug 1358433 ***