On Sat, Mar 28, 2020 at 11:09:42AM +0100, Adrian Reber wrote:
On Fri, Mar 27, 2020 at 05:14:48PM -0700, Kevin Fenzi wrote:
> On Fri, Mar 27, 2020 at 12:06:22PM +0100, Pavel Raiskup wrote:
> > On Friday, March 27, 2020 11:34:28 AM CET Adrian Reber wrote:
> > > The global 'exclude' has '--exclude
"*/repodata/*"' and you are using
> > > "${excludes[@]}" everywhere. In all three syncs. This looks
like
> > > 'repodata/*' will never synced.
> >
> > Good catch! Thank you for the review. I am attaching updated patch.
> >
> > Pavel
>
> Looks ok to me from a quick glance... lets give it a try. :)
>
> I think also we should remove the test releases one. It's currently
> failing the invalidate step (because it's repodata is not in the same
> place as the updates repos) and the only reason we would want say
> 32_Beta to be there is so we could point people to download isos from
> it. The repodata will never change.
Just to confirm from the MirrorManager side. MirrorManager is not aware
of any repomd.xml files under releases/test. For 32 MirrorManager points
to development/32 or updates/32 and updates/testing/32.
So MirrorManager will not redirect any clients to releases/test except
for ISOs.
Yeah, so perhaps we should consider just syncing the isos?
And it only needs to run once, so perhaps this could be a manually run
script/playbook.
kevin