Katello 3.6 yum repo

Support
1

Problem:
Repo data and rpm ownership needs to be updated.

Attempted to reposync rpms for Katello as part of upgrade to Foreman 1.17.1 and ended up with a bunch of rpms not present on https://fedorapeople.org/groups/katello/releases/yum/3.6/katello/el7/x86_64/ This leads me to believe that rpms and repodata wasn’t fully chowned to apache. Ended up copying file links for each rpm listed at above url and performing wget on each rpm. Still ended up missing tfm-rubygem-katello-3.6.0-2.el7.noarch.rpm dependency during upgrade, as its not listed on above url. Luckily, tfm-rubygem-katello_ostree-3.6.0-2.el7.noarch.rpm was listed, so I removed _ostree from filename and was able to wget, as well. Everything in repo still dated for 02 May 2018. Recommend createrepo --update and chown to apache. I was also unable to obtain these rpms from katello “latest” repo.

GREAT JOB on new Foreman interface, very gucci! Hope this helps others.

Expected outcome:
reposync all katello 3.6 rpms

Foreman and Proxy versions:
Now 1.17.1

Foreman and Proxy plugin versions:
Now 1.17.1

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]

2

Howdy @rgold73,

I’m not sure I follow what the issue with the repository is exactly. We generate repositories on our staging server and then rsync them to fedorapeople. There is no createrepo or chown run as part of the process. Could you expand on what process you are attempting?

3

Slide1
Slide1960×720 124 KB

4

From the reposync screenshot, you can see the rpm versions from https://fedorapeople.org/groups/katello/releases/yum/3.6/katello/el7/x86_64 are different from what I obtained when I ran wget on left. Being that rpm filenames are different than what’s visible on webpage, and 0 bytes in size, is why I believe they’re not owned by apache. The files listed on reposync side are what resides in repodata. I didn’t have any issues with reposync from other foreman or katello repos.

Thank you!

5

Nevermind. I’m so sorry. This is apparently an issue with my reposync program. https://github.com/pyther/upstream_sync. Just ran manual reposync and no issues.
Our current production system (centos 6) is still spacewalk, and I use upstream_sync to download
centos and redhat content.

Very Respecfully,

Robert

1 Like