Description of problem: Changing the organization in the Satellite WebUI does not change the sync plan page from the previous organization. The customer has four organizations. If He goes to content/sync plans and set up a sync plan under an organization. It will setup the sync plan as expected. However, if he changes the organization to the setup a sync plan in the new organization, he noticed it still keeps the first organization sync plan in place and the changes again will be made to the first organization sync plans. If he wants to make a sync plan to the second organization He needs to change the organization and move off of content/sync plans and then back on to content/sync plans to make the change in the new organization. Version-Release number of selected component (if applicable): Red Hat Satellite 6.3 Actual results: Changing the organization in the Satellite WebUI does not change the sync plan page information from the previous organization Expected results: Changing the organization in the Satellite WebUI does should change the sync plan page information from the previous organization
Created redmine issue https://projects.theforeman.org/issues/29013 from this bug
Upstream bug assigned to walden
This is also a problem with the API as the response for the item is returned rather than the expected 401/403.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Upstream issue is assigned to sajha.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
The fix for this one was in review in the upstream and was just merged. As a result, re-opening the bugzilla and placing in POST for inclusion in a feature release.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Satellite 6.8 release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:4366