-
Bug
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
True
Description of problem:
Under networking tab for a cluster, while user make changes in cluster-wide proxy i.e. removing an https or http proxy urls without removing the no proxy field and trying to
save with an uploaded additional trust bundle, the edit custer-wide proxy throws a confusing error message as below
Error editing cluster-wide proxyCLUSTERS-MGMT-400: Either 'proxy.http_proxy' or 'proxy.https_proxy' attributes is needed to set 'proxy.no_proxy' 'sad.com'Operation ID: 1e1ed962-4bbe-42ee-8a49-897dfaa4ef27
The information passed in the error message is valid but not valid in the current context. User has already removed https or http proxy fields and no proxy domain has been disabled.
Also note that the user tries to edit proxy settings with additional trust bundles and not related to no proxy domain field values.
The primary reason could be improper handling(clearing of already set values) of values for No proxy domains field.
How reproducible:
Always
Steps to Reproduce:
- Open OCM staging env.
- Install a ROSA cluster with https/ http proxy urls and with valid no proxy domain values
- Open the ROSA cluster > Networking tab > edit cluster-wide proxy settings.
- Remove http/https proxy urls and upload the additional trust bundle.
- Click save and view the behavior.
Actual results:
In Step 5, While saving new cluster-wide proxy settings, below error has been thrown in the dialog.
Error editing cluster-wide proxyCLUSTERS-MGMT-400: Either 'proxy.http_proxy' or 'proxy.https_proxy' attributes is needed to set 'proxy.no_proxy' 'sad.com'Operation ID: 1e1ed962-4bbe-42ee-8a49-897dfaa4ef27
The information passed in the error message is valid but not valid in the current context as the user already removed https or http proxy fields and no proxy domain has been disabled.
Expected results:
In Step 5, there shouldn't be any validation or any other error and additional trust bundle values should be saved successfully for the cluster.
Additional info:
Please find the attached screenshare. ProxyEditError.mp4