Greetings, I have a Satellite 6.2.7 installation and I am adding third party repositories using the Discover Repositories function within a product. For example, I add the EPEL repositories with the url https://dl.fedoraproject.org/pub/epel. The repos get discovered for EL 5,6,7 and various architectures (x86_64, i386, etc.). I select those that I am interested in and this all works fine. However, when I register a content host (subscription-manager register --org "Organization" I noticed that the host sees all of the available repositories from that product and not just those specific to it's RHEL version or architecture. So my RHEL 6 x86_64 system now has access RHEL 5 and RHEL 7 packages. Does any one have a recommendation or best practice for how to deal with external repositories like this. It seems that the Red Hat repositories with their related products seem to do this such that the system registered only sees repositories for its relevant RHEL version and arch. I know that there are a number of ways to do this manually with activation keys or specifying within each host entry in Satellite what repositories within a product are on by default but is there a better or simpler way. I considered creating products specific to arch and version but that seems just as difficult to manage. If all all possible I'd prefer that the content host only be able to subscribe to repositories that are relevant to arch and version. I hope that my question makes sense, if not I can try to clarify. Any advice on this would be much appreciated. thanks
-- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscr...@googlegroups.com. To post to this group, send email to foreman-users@googlegroups.com. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
