Bug 1414501 - repositories with same url, but different filters can't be defined
Summary: repositories with same url, but different filters can't be defined
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-18 16:35 UTC by Thomas Schweikle
Modified: 2019-10-21 13:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-10-21 13:26:20 UTC

Attachments (Terms of Use)

Description Thomas Schweikle 2017-01-18 16:35:53 UTC
Description of problem:
assume defining some repositories, all with the same url:

but different filters:

Will lead to error "There is already defined a repository with this url! Please use this one!

Version-Release number of selected component (if applicable):
spacewalk 3.6

How reproducible:

Steps to Reproduce:
1. Install spacewalk
2. define repositories with same url, but different filters

Actual results:

Expected results:
shall be possible

Additional info:
If repositories hold x86_64, i386, i686 and other files the whole repository will be ignored if architectures do not match, if the given architecture ist "higher" than the one of the channel:

http://download.bareos.org/bareos/release/15.2/RHEL_5/ holds both: x86_64 and i386 rpm-packages. Adding to a channel with x86_64 will work, while adding to a channel with arch:i386 will lead to an error about package architectur missmatches. Setting a filter to exclude '-*x86_64'-packages all will be fine.
If I am now using this very same channel for x86_64-Systems spacewalk will install only i386 packages for this system! But I'd like to have it install x86_64-packages. But these are excluded because of the set filter to avoid the error message before.
Trying to define a second channel with a different filter (or even without one) leads to an error too.

Comment 1 Michael Mráka 2019-10-21 13:26:20 UTC
Spacewalk 2.8 (and older) has already reached it's End Of Life.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before end of life. If you would still like
to see this bug fixed and are able to reproduce it against current version
of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.

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