If you removed the repo files, you can run "yum clean all" to ensure everything is in clean state. You can also (simulate) install a package from your repo and check whats listed in the repo column. If there is no repo file with a remote repo, it won't be used. How should the system know about it if it is not configured?
I wonder why my systems don't use these external repos. I set up the system using kickstart (directly via PXE, no pre-configuration). Ever since installation, only my channels are in use. Kind regards, Kevin Olbrich. 2018-06-13 14:31 GMT+02:00 Jérôme Meyer <jerome.me...@lcsystems.ch>: > Hello Waldirio, > > Ok, see to be fine but you know, for checkup I need to be sure that the > client take packages at the spacewalk server and not elsewhere. > That's why I asked how could I check that from my client side? But perhaps > it isn't possible? > > I'll remove too, the repo --name config from my kickstart file. > > Thanks a lot and best regards, J. > > ------------------------------ > *De :* spacewalk-list-boun...@redhat.com [spacewalk-list-bounces@ > redhat.com] de la part de Waldirio Manhães Pinheiro [waldi...@gmail.com] > *Envoyé :* mardi 12 juin 2018 18:20 > > *À :* spacewalk-list@redhat.com > *Objet :* Re: [Spacewalk-list] Client software update (download package > from spacewalk server) > > Hello J > > Good to know everything is ok. > > Sorry, I didn't follow your question *Is there still a way to check it on > the client, like logs or so???* > > Btw to all CentOS machines you can remove the files by default when > registering on the SW, then will be available / visible just the SW repos. > > Best > > ______________ > Atenciosamente > Waldirio > msn: waldi...@gmail.com > Skype: waldirio > Site: www.waldirio.com.br > Blog: blog.waldirio.com.br > LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646 > PGP: www.waldirio.com.br/public.html > > On Tue, Jun 12, 2018 at 8:12 AM, Jérôme Meyer <jerome.me...@lcsystems.ch> > wrote: > >> Hello Waldirio, >> >> Thanks for your quick replay. >> Ok, I've moved all repos from /etc/yum.repos.d. >> Now, it seems to be ok, because the *yum repolist all* showed me the list >> from spacewalk. >> Is there still a way to check it on the client, like logs or so??? >> >> Best regards, >> J. >> >> ------------------------------ >> *De :* spacewalk-list-boun...@redhat.com [spacewalk-list-bounces@redhat >> .com] de la part de Waldirio Manhães Pinheiro [waldi...@gmail.com] >> *Envoyé :* mardi 12 juin 2018 16:54 >> *À :* spacewalk-list@redhat.com >> *Objet :* Re: [Spacewalk-list] Client software update (download package >> from spacewalk server) >> >> Hello Jérome >> >> You can remove *or just move* the standard .repo files from >> /etc/yum.repos.d to another directory, after register on the Spacewalk, the >> client will manage this repos, you can enable/disable via cli or just via >> webUI *Spacewalk* >> >> Let us know if you have any additional question. >> >> ______________ >> Atenciosamente >> Waldirio >> msn: waldi...@gmail.com >> Skype: waldirio >> Site: www.waldirio.com.br >> Blog: blog.waldirio.com.br >> LinkedIn: http://br.linkedin.com/pub/waldirio-pinheiro/22/b21/646 >> PGP: www.waldirio.com.br/public.html >> >> On Tue, Jun 12, 2018 at 7:27 AM, Jérôme Meyer <jerome.me...@lcsystems.ch> >> wrote: >> >>> Dear All, >>> >>> >>> >>> I've created a new system (client) with spacewalk 2.4 (satellite 5.6) >>> using CentOS 7. >>> >>> From Spacewalk server I can now managed this client. The registration >>> was ok. >>> >>> The upgrade is running too but unfortunately the client take not the >>> package from Spacewalk server but directly from internet. (Is it correct >>> that packages must come from the spacewalk server??) >>> >>> Here're the config file from the client: >>> >>> >>> >>> # ls -tlr /etc/yum.repos.d/ >>> >>> total 48 >>> >>> -rw-r--r--. 1 root root 203 May 6 2015 spacewalk-client.repo >>> >>> -rw-r--r--. 1 root root 223 May 6 2015 spacewalk-client-nightly.repo >>> >>> -rw-r--r--. 1 root root 1050 Oct 2 2017 epel-testing.repo >>> >>> -rw-r--r--. 1 root root 951 Oct 2 2017 epel.repo >>> >>> -rw-r--r--. 1 root root 4768 May 17 15:53 CentOS-Vault.repo >>> >>> -rw-r--r--. 1 root root 1331 May 17 15:53 CentOS-Sources.repo >>> >>> -rw-r--r--. 1 root root 630 May 17 15:53 CentOS-Media.repo >>> >>> -rw-r--r--. 1 root root 314 May 17 15:53 CentOS-fasttrack.repo >>> >>> -rw-r--r--. 1 root root 649 May 17 15:53 CentOS-Debuginfo.repo >>> >>> -rw-r--r--. 1 root root 1309 May 17 15:53 CentOS-CR.repo >>> >>> -rw-r--r--. 1 root root 1664 May 17 15:53 CentOS-Base.repo >>> >>> >>> >>> What can I do to change this issue ? >>> >>> Shouldn't these repos be defined by Spacewalk Server? >>> >>> The Client Configuration's Guide spoke only regarding registering client >>> but not about to do update. >>> >>> >>> >>> Thank you and best regards, J. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Spacewalk-list mailing list >>> Spacewalk-list@redhat.com >>> https://www.redhat.com/mailman/listinfo/spacewalk-list >>> >> >> >> _______________________________________________ >> Spacewalk-list mailing list >> Spacewalk-list@redhat.com >> https://www.redhat.com/mailman/listinfo/spacewalk-list >> > > > _______________________________________________ > Spacewalk-list mailing list > Spacewalk-list@redhat.com > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list