I'm assuming you're talking about this bug https://bugzilla.redhat.com/show_bug.cgi?id=1445428 with apache version
2018-02-19 10:10 GMT-06:00 Isaac Hailperin <[email protected]>: > Thank you Alex. It turns out my understanding was incomplete. Disabling > repos is indeed an option, and knowing the spacewalk repos come via the rhn > yum plugin helps to understand how it all works together. > > In the end it was a bug (back from April 2017 ...) that keps me from using > the repos - I had to roll back httpd on the spacewalk server. After that, > all is fine again. > > Isaac > > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:spacewalk-list- > [email protected]] Im Auftrag von Alexandru Raceanu > Gesendet: Donnerstag, 15. Februar 2018 23:26 > An: [email protected] > Betreff: Re: [Spacewalk-list] Fix yum repo definitions on spacewalk clients > > I've been running following in the kickstart %post (non-chroot) to disable > all repos except the ones from Spacewalk without any issues for couple of > years now. > ----snip---- > sed -i -e '/reposdir=.*/d' -e '/cachedir.*/ > s,$,\nreposdir=/etc/yum.repos.d/disabled,' > /mnt/sysimage/etc/yum.conf > ----snip---- > > I hope this helps... > > /Alex > > > From: "Isaac Hailperin" <[email protected]> > To: "[email protected]" <[email protected]> > Sent: Monday, February 12, 2018 10:51:55 AM > Subject: [Spacewalk-list] Fix yum repo definitions on spacewalk clients > > > > Dear list, > > > > I have spacewalk 2.4 installed on a CentOS 7 host, and manage CentOS 7 > servers with it. Now I found that in /etc/yum.repos.d/ all configured > repositories point to Internet repos. Which is not really how it should be, > hosts should use the internal spacewalk repos. I assume this is due to > packages like centos-release* being installed. I am just taking over this > environment, so I am not 100% sure how all this came together. > > > > Nonetheless, I need to fix this. If I just delete the packages to which > the repo definitions belong to, I am left without any repositories (I have > checked - none point to the internal repo, all belong to some installed > package). As the clients are assigned to certain channels, I would like to > add the corresponding repositories again. > > > > So far I have tried re-registering the client with > > > > # rhnreg_ks --serverUrl=https://YourSpacewalk.example.org/XMLRPC > --sslCACert=/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT > --activationkey=<key-with-rhel-custom-channel> --force > > No success. I have also removed all channel subscriptions, and then added > them again, no success. > > > > What would be the easiest, or most reliable way to get the correct repo > definitions back? > > > > Maybe my assumption is wrong, but since the spacewalk client tools have > knowledge of the subscribed channels, I assume that there is also a way to > get the corresponding repository definitions in some automated way. What > would that be? > > > > Any hint or feedback is appreciated. > > > > Regards, > Isaac > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list >
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
