Foreman - local repository to workaround manfiests requirement

Problem:
Hi, we’re looking consolidate a number of local repositories from multiple local servers into Foreman, is this possible? would we need to set the upstream URL of a product to the NFS server which the content?

The reason this is needed is due to us not having a satellite license for Redhat and therefore cannot leverage manifests so we need to use different servers running RHEL6, RHEL7 and RHEL8 to download repos in order to patch our estate. if anyone has an alternative solution to this problem, please let me know.

We’re on the latest version of Foreman.

Thanks

Dan

Hey Dan,

Just from your post I’m unsure, but do you know about the Katello plugin for Foreman?

@mcorr - thank you that’s really helpful, i’ll look at investigating this to get the achieved scenario.

1 Like

This content management guide might be helpful also @DanF Content Management Guide

Thanks @mcorr, I’ll take a look at this, I’ve been scouring the web to find out how we work with katello directly to register a local repo.

@mcorr - it seems that i’m not able to locate the package as described in the instructions: python-pulp-manifest. Any help would be greatly appreciated.

Thanks

Dan

Hey @DanF

I will add a note to the docs now as this is a known issue.
There is a workaround here: Missing pulp-python-manifest package - #9 by pjayKHV
Sorry for the inconvenience :frowning:

Thanks for confirming @mcorr but is there an official fix due to be released via the foreman site?

I’m chasing down an answer as to whether it’s a doc fix or a feature that needs to be updated. Looking through the issues confused me. I’ll update once I find out.

1 Like

Hi @mcorr , do you have any updates on this?

Thanks

No, @DanF - I am sorry.
I have one more thing to chase down, but the steps linked above are as close to a workaround as I have for now :frowning:

@DanF we reopened this ticket
https://pulp.plan.io/issues/9289
and have requested that it is published to PyPI, so the Katello team can then package it.

There is a workaround that involves cloning the https://github.com/pulp/pulp_file/ repo and then a few more steps to get things up and running. If you’re willing to implement the workaround, I can get the steps for you?
If not, I’ll watch this ticket and can write to you when there’s an update.

Hi @mcorr sorry for the delay in responding, if you could send over the steps for the pulp workaround that would be much appreciated.

Thanks

Hey @DanF

Here is the workaround:

Until Pulp issue 9289 is resolved:

  1. Clone the https://github.com/pulp/pulp_file Git repo
  2. Change to the /pulp_file/pulp_manifest/ directory.
$ cd /pulp_file/pulp_manifest/
  1. Enter the following command:
$ sudo python ./setup.py install
  1. Run the following command to install the manifest:
$ pulp-manifest ./path/to/dir

Thank you @mcorr, i’ll give this a go now.

appreciate the continued support.

1 Like