2172872 – Repository GUI changes OS restriction upon any field edit

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2172872 - Repository GUI changes OS restriction upon any field edit

Summary: Repository GUI changes OS restriction upon any field edit

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Satellite
Classification:	Red Hat
Component:	Repositories
Sub Component:
Version:	6.11.4
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	medium
Target Milestone:	Unspecified
Assignee:	satellite6-bugs
QA Contact:	Satellite QE Team
Docs Contact:
URL:
Whiteboard:
Duplicates (1):	2263231 (view as bug list)
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2023-02-23 11:25 UTC by d.o.kip
Modified:	2024-06-06 16:08 UTC (History)
CC List:	5 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2024-06-06 16:08:58 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
Before situation, edit situation, after situation. (95.16 KB, image/jpeg) 2023-02-23 11:25 UTC, d.o.kip	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	SAT-20773	0	None	Migrated	None	2024-06-06 16:08:56 UTC

Description d.o.kip 2023-02-23 11:25:06 UTC

Created attachment 1945900 [details]
Before situation, edit situation, after situation.

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.

Comment 1 Ron Lavi 2024-02-08 15:14:22 UTC

*** Bug 2263231 has been marked as a duplicate of this bug. ***

Comment 2 Eric Helms 2024-06-06 16:08:58 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Note You need to log in before you can comment on or make changes to this bug.