Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exclude channels from spacewalk-repo-sync and or mgr-sync-refresh-default #9418

Open
bjin01 opened this issue Oct 29, 2024 · 0 comments
Open
Labels
enhancement New feature or request

Comments

@bjin01
Copy link

bjin01 commented Oct 29, 2024

Short description

Need possibilities to exclude certain channels from repo-sync when using spacewalk-repo-sync

Details

Several customers would like to have the capability to exclude certain channels/repos from daily repo-sync from the internet.
Often cases some channels/repos can't be synced anymore but still exist and needed in Uyuni/SUMA for downstream client systems. The daily repo-sync job fails at those channels and send notifications which are annoying for the admins.

Suggestions - custom solution:

Tested on SUMA 5.0.1

https://github.com/bjin01/salt-sap-patching/blob/master/spacewalk-repo-sync.py
I added this feature into the spacewalk-repo-sync.py and uploaded it into my github repo.

It reads in a hard-coded config file exclude_channels = '/etc/rhn/spacewalk-repo-sync/exclude.list' in yaml.

exclude_channels:
  - channel1
  - channel2
  - xxx

The list in dictionary key "exclude_channels" will be removed from the dictionary d_ch_repo_sync which is used in original spacewalk-repo-sync.py.

@bjin01 bjin01 added the enhancement New feature or request label Oct 29, 2024
@bjin01 bjin01 changed the title xclude channels from spacewalk-repo-sync and or mgr-sync-refresh-default Exclude channels from spacewalk-repo-sync and or mgr-sync-refresh-default Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant