Bug #31522: CentOS Kickstart stopped working after weekly sync. - Katello - Foreman

Actions

Copy link

Bug #31522

closed

CentOS Kickstart stopped working after weekly sync.

Added by Hil Palmer over 4 years ago. Updated almost 4 years ago.

Status:

Rejected

Priority:

Normal

Assignee:

Category:

Content Views

Target version:

Katello Recycle Bin

Difficulty:

Triaged:

Yes

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Foreman - 2.0.1

Red Hat JIRA:

Description

Hello,

We have an issue where we will need to update our ISO to match the latest kickstart from CentOS again. Seems like even though we have our CentOS 8.2 Kickstart Repository locked into a Content View, the backend repository gets updated and the kernel version changes. So when we boot from our 8.2 ISO (or PXE boot) and when it attempts to connect to the CentOS 8.2 Kickstart repo on the foreman server it will not allow anaconda to fully boot.

So for a quick example that I am seeing... I sync'd my kickstart repository from http://mirror.centos.org/centos/8.2.2004/BaseOS/x86_64/kickstart. If you look at the files within http://mirror.centos.org/centos/8.2.2004/BaseOS/x86_64/kickstart/images/pxeboot you will see the dates and sizes of the files that I expect. BUT now when we sync'd the standard repository for CentOS which is now 8.3 from http://mirror.centos.org/centos/8/BaseOS/x86_64/os into a different repo and content view... We are getting the file size and dates within our CentOS 8.2 Kickstart Content View found within http://mirror.centos.org/centos/8/BaseOS/x86_64/os/images/pxeboot.

Thanks,
Hil

Files

Kickstart Repo - CentOS 8.2.png	View Kickstart Repo - CentOS 8.2.png	186 KB		Hil Palmer, 12/17/2020 03:22 PM
Update Repo - CentOS 8.png	View Update Repo - CentOS 8.png	184 KB		Hil Palmer, 12/17/2020 03:22 PM