On 18 September 2017 at 12:51, Jasper Connery <[email protected]> wrote:
> Good afternoon, > > I have created a new Product and Repository on our new Katello server and > subscribed to all our activation keys and content views etc, I can see the > repo showing in the Lifecycle Environments and everywhere except against > each of the hosts, and it looks like I need to manually go through each > host and subscribe this repo in. > > Which seems to me that I am missing something here, is there an easier way > to have all the content hosts pick up the new repo? > Jasper: known working "cluebat" solution - resubscribe each machine to it's activation key using --force developer recommended solution that sometimes doesn't work: subscription-manager refresh I've found that sometimes doing: yum clean all; subscription-manager refresh has better results. I would dearly like for subscription-manager refresh to work as advertised, every time. But that's not been my experience. I would say it works ~70% I have defaulted to trying that solution first, then going to activation keys --force as a final option. Cheers L. ------ "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor should we panic about it. It is a shared consciousness that our institutions have failed and our ecosystem is collapsing, yet we are still here — and we are creative agents who can shape our destinies. Apocalyptic civics is the conviction that the only way out is through, and the only way through is together. " *Greg Bloom* @greggish https://twitter.com/greggish/status/873177525903609857 -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
