it may be that the upstream source has pruned its repo. in that canes try to copy the channel instead. here is an article on RedHat's site that describes a few options https://access.redhat.com/solutions/42232 note the article is based on RHN Satellite 5 so some of the paths may be different but spacewalk is the upstream code base for it so its essentially correct.
On Wed, Jan 18, 2017 at 3:32 PM, Daryl Rose <[email protected]> wrote: > Avi, > > > The steps that you provided work great, with one exception. The original > channel has over 3000 packages, while the new channel has only 752. Why > wouldn't the new channel get all 3000? > > > I didn't know if there was some kind of conflict between the two channels, > so I disconnected the old channel from the repo and ran a new sync. The > sync came back and said there wasn't anything new to sync. > > > Thoughts? > > > Thank you. > > > Daryl > > > ________________________________ > From: [email protected] <[email protected]> > on behalf of Avi Miller <[email protected]> > Sent: Wednesday, January 18, 2017 1:50 PM > To: [email protected] > Subject: Re: [Spacewalk-list] How to fix typo in channel label? > > Hi, > > On 19 Jan 2017, at 2:13 am, Daryl Rose <[email protected]> wrote: > > If I blow away the current channel and recreate it, do I have to blow away > the repository as well? Can I keep the repo and just link them back up? > How about the three systems that I currently have registered to the channel, > do I have to re-register them? > > > You don't have to blow away the repository and you'll find that syncing is > (almost) a no-op on the initial run because the packages already exist > locally. They'll just get added to the new channel. > > You do not need to re-register the systems either. Just switch them to the > new channel (if it is a base channel) or remove the old and add the new > channel (if it is a child). > > So, the simplest option is actually to add a new channel (with the right > name) and assign the repo and run the sync and then switch the clients. > You'll find it's both pretty quick and pretty low risk. > > Note that I would create the new channel and switch all the clients and make > sure it all works before deleting the old channel. You can have multiple > channels pointing to the same repo, so that's fine. > > Cheers, > Avi > > -- > Oracle <http://www.oracle.com> > Avi Miller | Product Management Director | +61 (3) 8616 3496 > Oracle Linux and Virtualization > 417 St Kilda Road, Melbourne, Victoria 3004 Australia > > > _______________________________________________ > 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
