As it stands, migration from Katello/foreman managed server is not supported, but having a patch management system is important. Does Rocky have any plans to support it and furthermore, will katello/foreman work on Rocky server in some near future? At the moment only CentOS/RHEL platforms are supported. Maybe there is some alternative?
Thanks
Vadym
Hi,
Haven’t tried it yet, but I think it’s the same as with satellite and centos.
Satellite does not support centos, so manual configuration of everything needs to be done ( or an ansible playbook )
ie…
create a product
specify the repos
configure installation media (use the BaseOS and Appstream repos as a target)
os
asociate the following with the rocky linux os
then the other stuff as done with rhel/centos
should work I guess.
Rob
Configuration wise it’s understandable. But certain component are missing for installation of the product itself, or maybe I haven’t found them yet.
CentOS Mirror, for example
ok tested the katello install on a rocky8 host.
that works fine.
I did as explained in the foreman docs:
https://docs.theforeman.org/3.0
Now gonna test the product mirror.
doh…
make sure you follow the katello instructions …
starting over…
Right, instruction refers to centos-release-ansible-29 on Centos 8. It doesn’t exist on Rocky
yeah… minor setback
mkdir tmp
cd tmp
curl -O http://mirror.centos.org/centos/7/extras/x86_64/Packages/centos-release-ansible-29-1-1.el7.noarch.rpm
rpm2cpio centos-release-ansible-29-1-1.el7.noarch.rpm | cpio -dvi
cp etc/yum.repos.d/CentOS-SIG-ansible-29.repo /etc/yum.repos.d/
cd
and we’re back to the manual
someday I will learn to remember to also add keys
cd /etc/pki/rpm-gpg
curl -O https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-ConfigManagement
ok so with the small workaround
mkdir tmp
cd tmp
curl -O http://mirror.centos.org/centos/7/extras/x86_64/Packages/centos-release-ansible-29-1-1.el7.noarch.rpm
rpm2cpio centos-release-ansible-29-1-1.el7.noarch.rpm | cpio -dvi
cp etc/yum.repos.d/CentOS-SIG-ansible-29.repo /etc/yum.repos.d/
cd /etc/pki/rpm-gpg
curl -O https://www.centos.org/keys/RPM-GPG-KEY-CentOS-SIG-ConfigManagement
the katello installation works fine
I’ve added a new product
specified the repo
I used the mirror url I found in my local /etc/yum.repos.d/Rocky-BaseOS.repo file
and started a sync
What exactly failed on your site ?
Rob
Ideally, not to rely on CentOS?
yeah the CentOS-SIG-ansible-29 repo hasn’t been added to the rocky linux repos.
Maybe put up a request for it, although I must admit I don’t know where.
For now this works fine though.
Rob
I’m a bit curious as to how the katello dev team is going to deal with the centos8 stream.
They already have quite a challenge keeping it running on centos8
( It took them quite some time before they got that to work )
And centos8-stream isn’t going to make their lives easier when centos8.x is going to be deprecated.
Rob
Which was quickly closed with wont fix
I read the bugzilla
maybe explain that you want it not only for ansible but for other config packages as well.
IE actually mention you want to use it to install theforeman/katello which explicitly states in their documentation that they are not epel compatible.
(been trying to activate my own bugzilla account but I am still waiting for the confirmation email )
Rob
Hmm, I used my forum account to login, work fine
keeps failing for me
@RobVerduijn if you have 2FA/MFA enabled, you need to append it to your password for login to bugzilla to work. Could be a reason why it’s not working.
Hi All
Has there been any movement on this? Interested in starting with Rocky linux but this will be a must have.
Thank You
didn’t check
do you require katello to run on rocky ? or do you require katello to support rocky ?
The latter is working since day 1.
Didn’t check if katello can be installed without the workaround, this is because I really don’t expect those sig repos to be ported and I don’t expect the rocky linux community to port a project as complex like katello.
There is still no official installation for centosstream 8, only the centos8 installation is mentioned in the docs
as I mentioned before, I expect rocky linux to become less compatible as a platform for installing katello in the future.
The provisioning of rocky linux systems using katello has been working starting the day the repositories of rocky came online, and I expect it to remain working untill redhat starts using closed source, burdened with legal ip.
(which i expect from IBM, but not redhat, they are not quite entirely the same company yet…)
cheers