View Issue Details

IDProjectCategoryView StatusLast Update
0016470CentOS-8-OTHERpublic2019-10-21 00:37
Reporterkallisti5 
PriorityhighSeveritymajorReproducibilityalways
Status newResolutionopen 
Product Version8.0.1905 
Target VersionFixed in Version 
Summary0016470: CentOS 8 BaseOS repository references AppStream repo in a way which is incompatible with Foreman.
DescriptionThe BaseOS repository references AppStream via this:

   /pulp/repos/ORG/Library/custom/CentOS8/base-x86_64/../../../AppStream/x86_64/os/

The issue is this drops out of a "valid" Foreman repo url. (those ..'s go into the "CentOS8 Product")

There's a sister bug @ Foreman here:
https://projects.theforeman.org/issues/27948


This issue doesn't seem to happen with RHEL 8
Steps To ReproduceForeman 1.23.0
TagsNo tags attached.

Activities

kallisti5

kallisti5

2019-09-26 15:23

reporter  

foreman.png (312,440 bytes)
centos8-product.png (128,626 bytes)
centos8-product.png (128,626 bytes)
kallisti5

kallisti5

2019-09-26 15:33

reporter   ~0035232

So, adjusting the repo layout plus adding the relative "sub-repo" has broken foreman deployments of CentOS:

http://yum.tamu.edu/centos/8/BaseOS/x86_64/os

../../../ == http://yum.tamu.edu/centos/8/

foreman/pulp/repos/ORG/Library/custom/CentOS8/base-x86_64

../../../ == foreman/pulp/repos/ORG/Library
jrd

jrd

2019-09-26 15:54

manager   ~0035233

Last edited: 2019-09-26 15:55

View 2 revisions

Sounds like a foreman issue. Has this been reported to the foreman devs?

[edit] I need to learn to read better.

I am not sure what, if anything, we're able to do to accomodate this.

kallisti5

kallisti5

2019-09-26 16:12

reporter   ~0035235

I mean, I assume Redhat doesn't have this issue? Foreman / Satellite server 6 works with RHEL 8. Do they have the same relative ../../../ assumptions in their BaseOS repos?
It seems like a bad idea to make big assumptions a new layout of the repositories (incompatible with any previous release of CentOS) by cross-linking them via relative paths?

Historically these paths are:
centos/7/os/x86_64/

Now:
centos/8/BaseOS/x86_64/os/


Looking at Redhat:
https://cdn.redhat.com/content/dist/rhel8/8/x86_64/baseos/os


So by reorganizing from Redhat's design, CentOS has broken foreman.
kallisti5

kallisti5

2019-09-26 16:22

reporter   ~0035237

as it's relevant, my CentOS 8 installation media in foreman is:
  http://kwforeman.BLAH/pulp/repos/ORG/Library/custom/CentOS8/base-x86_64

A potential work-around is using the external repos vs the Foreman ones for installation, but that kind of defeats the purpose of using foreman and using our "tested" set of software packages.
iballou

iballou

2019-10-16 17:37

reporter   ~0035510

I've updated how to get this to work with Foreman/Katello on the Katello bug linked above. We'll be updating our provisioning docs. Essentially to get CentOS 8 provisioning to work you need to also sync the AppStream repo and Katello will detect that and send it to Anaconda in the kickstart.
iballou

iballou

2019-10-17 18:00

reporter   ~0035525

Another issue seems to occur, however. If in the Kickstart file you have a line like `repo --name my-custom-repo-name --baseurl http://myforeman.example.com/pulp/repos/Demo/Library/custom/CentOS/AppStream/`, it will fail because Anaconda requires the repo name to be AppStream specifically. Would it be possible for this repo name requirement to be more flexible?

Issue History

Date Modified Username Field Change
2019-09-26 15:23 kallisti5 New Issue
2019-09-26 15:23 kallisti5 File Added: foreman.png
2019-09-26 15:23 kallisti5 File Added: centos8-product.png
2019-09-26 15:33 kallisti5 Note Added: 0035232
2019-09-26 15:54 jrd Note Added: 0035233
2019-09-26 15:55 jrd Note Edited: 0035233 View Revisions
2019-09-26 16:12 kallisti5 Note Added: 0035235
2019-09-26 16:22 kallisti5 Note Added: 0035237
2019-10-16 17:37 iballou Note Added: 0035510
2019-10-17 18:00 iballou Note Added: 0035525