-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
6.11.4
-
False
-
-
False
-
CLOSED
-
1,550
-
Phoenix - Content
-
-
-
Overflow, Sprint 124, Sprint 125, Sprint 126, Sprint 127
-
Moderate
-
None
Created attachment 1945900 [details]
Before situation, edit situation, after situation.
Description of problem:
In the webGUI for a repository, with sufficient access to edit, you can edit the settings for a repository. If that repository has a restriction in the Sync settings on OS ("Restrict to
OS version" in the GUI) the restriction is set to the default value upon any edit of another property (for example setting a proxy)
This only happens on the FIRST EDIT after (re)loading the repository page, subsequent edits leave the OS restriction alone, untill you refresh the page.
Version-Release number of selected component (if applicable):
6.11.4.1
How reproducible:
Steps to Reproduce:
1. Go to Products, select a product, select a repository.
2. Set an OS restriction on the repo, and refresh the page (if it's already set, skip to 3.)
3. Edit a setting, for example change the name, deactivate SSL checking or set a proxy.
4. Hit Save, and see your OS restriction change to the default (No restriction)
5. Edit the restriction again and save
6. Repeat step 3, and hit save. Now the setting stays (as it should)
7. reload/refresh the page to get the incorrect behaviour again.
Actual results:
OS restriction changes to default (No restriction)
Expected results:
OS restriction was not edited, so should stay as is.
Additional info:
We found it because we were testing proxy settings, but turns out to happen on any of the editable fields. Even the architecture restriction, or the name.
When editing the repository's proxy setting (our example and use-case) through hammer, this does not happen, it really appears to be a GUI issue.
- is duplicated by
-
SAT-23110 Changing the description of custom repository reset the "Restrict the os version" parameter.
- Closed