Hi,
I have a Katello 3.1 installation running on CentOS 7, and just recently I
added the CentOS 7.3 repositories to our CentOS product.
This completed almost without any oddities, except the main "os" repository
is showing in Katello as having no packages. The underlying Pulp repository
has the expected packages, so these are correctly published to subscribers
to the repository.
Evidence, from the Katello/Foreman side:
$ hammer repository info --id 705
ID: 705
Name: CentOS-7.3-x86_64-os
Label: CentOS-7_3-x86_64-os
Organisation: Example Corp
Red Hat Repository: no
Content Type: yum
Checksum Type: sha256
URL: http://mirror.centos.org/centos/7.3.1611/os/x86_64/
Publish Via HTTP: yes
Published At:
http://katello.example.com/pulp/repos/Example_Corp/Library/custom/CentOS/CentOS-7_3-x86_64-os/
<http://pal212.ad.pvt/pulp/repos/Press_Association/Library/custom/CentOS/CentOS-7_3-x86_64-os/>
Relative Path: Example_Corp/Library/custom/CentOS/CentOS-7_3-x86_64-os
Download Policy: immediate
Product:
ID: 1
Name: CentOS
GPG Key:
Sync:
Status: Success
Last Sync Date: 10 minutes
Created: 2016/12/12 12:18:20
Updated: 2016/12/12 13:24:46
Content Counts:
Packages: 0
Package Groups: 0
Errata: 0
and from the Pulp side:
$ pulp-admin repo list
Id: Example_Corp-Library-CentOS-7-Base-CentOS-CentOS-7_3-x
86_64-os
Display Name: CentOS-7.3-x86_64-os
Description: None
Content Unit Counts:
Distribution: 1
Package Group: 82
Rpm: 9363
Do you have any idea why this might have happened, and if I can do anything
to flush Katello's view of the repositiory?
Cheers,
John
Apologies, just for absolute correctness, this is the correct Pulp repo:
Id: Example_Corp-CentOS-CentOS-7_3-x86_64-os
Display Name: CentOS-7.3-x86_64-os
Description: None
Content Unit Counts:
Distribution: 1
Package Category: 11
Package Environment: 10
Package Group: 82
Rpm: 9363
John
Hi John,
> Sync:
> Status: Success
> Last Sync Date: 10 minutes
> Created: 2016/12/12 12:18:20
> Updated: 2016/12/12 13:24:46
> Content Counts:
> Packages: 0
> Package Groups: 0
> Errata: 0
I see this happen sometimes when packages appear in multiple repos. It appears to only be an interface issue as the packages still "work". In my case it normally clears up in a day or so (when routine cleanup maintenance runs) but you can also force a clean up by setting "force_post_sync_actions" to "yes" under Settings -> Content and then re-running the sync.
Regards,
j
> I see this happen sometimes when packages appear in multiple repos. It
appears to only be an interface issue as the packages
> still "work". In my case it normally clears up in a day or so (when
routine cleanup maintenance runs) but you can also force a
> clean up by setting "force_post_sync_actions" to "yes" under Settings ->
Content and then re-running the sync.
Well, that seems to make sense, as when I added the 7.3 "os" repository
there was also a 7.2 "cr" repository, though I don't quite think that the
existing repositories would have overlapped 100% with the new 7.3 one.
I'll leave it a few days and try your helpful suggestion if it doesn't
clear up by itself.
Thanks,
John
···
On Tuesday, 13 December 2016 14:36:11 UTC, Jason B. Nance wrote:
OK, I got impatient and tried the 'force_post_sync_actions' - it worked a
treat. Thanks.
John
···
On Tuesday, 13 December 2016 15:52:36 UTC, John Beranek - PA wrote:
>
>
> On Tuesday, 13 December 2016 14:36:11 UTC, Jason B. Nance wrote:
> > I see this happen sometimes when packages appear in multiple repos. It
> appears to only be an interface issue as the packages
> > still "work". In my case it normally clears up in a day or so (when
> routine cleanup maintenance runs) but you can also force a
> > clean up by setting "force_post_sync_actions" to "yes" under Settings ->
> Content and then re-running the sync.
>
> Well, that seems to make sense, as when I added the 7.3 "os" repository
> there was also a 7.2 "cr" repository, though I don't quite think that the
> existing repositories would have overlapped 100% with the new 7.3 one.
>
> I'll leave it a few days and try your helpful suggestion if it doesn't
> clear up by itself.
>
