NMS-19060: Add Centos 10 installation docs

[mfuhrmann]

Adds CentOS 10 installation documentation based on the existing CentOS 9 guide.

Reviewer Hints

• AWe don't have an EL10 repository file, EL9 one works
• The GPG is violating a security policy in CentOS 10 forward. There is a workaround, and the issue for the key itself is tracked in NMS-19071

External References

• Jira (Issue Tracker): https://opennms.atlassian.net/browse/NMS-19060

[mfuhrmann]

The documentation steps work in general. Right now it is just a duplication of the CentOS 9 guide.

I've noticed two things:

1. There is no repo file for EL10: https://yum.opennms.org/repofiles/
   Luckily, the EL9 works also with CentOS 10. Not sure if this is what we want. But for now it would work.
2. The OpenNMS GPG key seems to be expired. When running this, we get:

[opennms@localhost ~]$ sudo rpm --import https://yum.opennms.org/OPENNMS-GPG-KEY
error: Certificate 57801F6F5B9EFD43:
  Policy rejects 57801F6F5B9EFD43: No binding signature at time 2025-10-30T18:50:59Z
error: https://yum.opennms.org/OPENNMS-GPG-KEY: key 1 import failed.

If I get the output of:
gpg --list-packets OPENNMS-GPG-KEY correct:

1. DSA1024 Key (2012)
Created: 2012-01-22
Expires after: 3 years (from creation)
Expiration date: 2015-01-22
Status: Expired (as of October 30, 2025)
2. DSA1024 Key (2015 Extension)
Extended in 2015: Expires after 8 years (from 2015-01-21)
Expiration date: 2023-01-21
Status: Expired (as of October 30, 2025)
3. RSA4096 Key (2023)
Created: 2023-01-05
Expires: 0 (no expiration date set)
Status: Valid (as of October 30, 2025)

I am not deep in this topic. I can't give qualified solution approach here. But my feeling says, we could maybe remove 1. and 2. from it? For sure, this should be tackled in another issue.

But we are lucky again, because the installation works, even with this error.

I was not taking care about duplicated code here for now, but we could try to improve on that. If we can make the 10 in line https://github.com/OpenNMS/opennms/pull/8086/files#diff-0e036d4e4fe5a65f2c31f2e1fee2336bc578511817c4b8283079299ee301998aR15 dynamic ( 9, 10 ), we could already reduce a bit code. I don't see a big deal here to have the code a bit duplicated for now. I think continuing with the other OS install docs is more important for now. Also, I am still convinced, we should refactor the entire structure of the installation, after the install docs for the other ways are refactored.

[mfuhrmann]

@dino2gnt @indigo423 Please have a look at this. Feedback welcome 🤗

[indigo423]

[opennms@localhost ~]$ sudo rpm --import https://yum.opennms.org/OPENNMS-GPG-KEY
error: Certificate 57801F6F5B9EFD43:
  Policy rejects 57801F6F5B9EFD43: No binding signature at time 2025-10-30T18:50:59Z
error: https://yum.opennms.org/OPENNMS-GPG-KEY: key 1 import failed.

I've captured this in https://opennms.atlassian.net/browse/NMS-19071. Thanks for bringing this up. The issue also has a method to solve this problem. Maybe something you can try out and add to the docs until we have fixed this on our GPG key.

[mfuhrmann]

Thanks. I will give it a try. Am 4. November 2025 17:53:44 MEZ schrieb Ronny Trommer ***@***.***>:

…

indigo423 left a comment (OpenNMS/opennms#8086) > ``` > ***@***.*** ~]$ sudo rpm --import https://yum.opennms.org/OPENNMS-GPG-KEY > error: Certificate 57801F6F5B9EFD43: > Policy rejects 57801F6F5B9EFD43: No binding signature at time 2025-10-30T18:50:59Z > error: https://yum.opennms.org/OPENNMS-GPG-KEY: key 1 import failed. > ``` I've captured this in https://opennms.atlassian.net/browse/NMS-19071. Thanks for bringing this up. The issue also has a method to solve this problem. Maybe something you can try out and add to the docs until we have fixed this on our GPG key. -- Reply to this email directly or view it on GitHub: #8086 (comment) You are receiving this because you authored the thread. Message ID: ***@***.***>

[mfuhrmann]

@indigo423 Your approach didn't work for what ever reason. I was not able to do it like this.
But I found a pretty simple solution now 🙈

The installation on CentOS 10 works like a charm in this state.

[mfuhrmann]

@indigo423 @dino2gnt Anything we want to do differently here?

[dino2gnt]

Can you also add a compatible-rhel10 attribute to antora.yml and update core/system-requirements.adoc to reflect that el10 is an option?

[mfuhrmann]

@dino2gnt I would continue with https://opennms.atlassian.net/browse/NMS-19123 since there are still other other old OS code snippets here and there.

[dino2gnt]

LGTM

[mfuhrmann]

Is the destination branch still valid?
I've seen that we merged the U24 docs into develop. @indigo423 you told me to use release-34.x some weeks ago. But this could be outdated, no?