RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2029071 - httpd on CentOS identifies as RHEL
Summary: httpd on CentOS identifies as RHEL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: httpd
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Joe Orton
QA Contact: Branislav Náter
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-04 17:40 UTC by Neal Gompa
Modified: 2022-05-17 12:41 UTC (History)
8 users (show)

Fixed In Version: httpd-2.4.51-4.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 12:29:56 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/centos-stream/rpms httpd merge_requests 37 0 None None None 2021-12-04 17:47:27 UTC
Red Hat Issue Tracker RHELPLAN-104757 0 None None None 2021-12-04 17:41:46 UTC
Red Hat Product Errata RHBA-2022:2324 0 None None None 2022-05-17 12:30:20 UTC

Description Neal Gompa 2021-12-04 17:40:30 UTC 
Description of problem:
Apache HTTPD identifies itself as RHEL 9 instead of CentOS Stream 9 for CentOS Stream builds. It should not say it is RHEL when it is not.

Version-Release number of selected component (if applicable):
2.4.51-3.el9

How reproducible:
Always

Additional info:
Identified on the centos-devel mailing list: https://lists.centos.org/pipermail/centos-devel/2021-November/077482.html
Comment 1 Neal Gompa 2021-12-04 17:46:48 UTC 
Merge request proposed: https://gitlab.com/redhat/centos-stream/rpms/httpd/-/merge_requests/37
Comment 2 Joe Orton 2021-12-06 08:59:52 UTC 
Thanks Neal, this looks fine.
Comment 4 Branislav Náter 2021-12-06 19:15:28 UTC 
Currently I'm getting "Server: Apache/2.4.51 (Red Hat Enterprise Linux)" on rhel-9 machine and "Server: Apache/2.4.51 (Red Hat Enterprise Linux 9)" with '9' at the end of string on c9s machine.

Testing in MR [1], "Server: Apache/2.4.51 (CentOS Stream 9)" is present. It this what we want Neal, Joe? Other variants: "CentOS Stream" (no '9') or just "CentOS" (look like expected here [2]).

1. https://gitlab.com/redhat/centos-stream/rpms/httpd/-/merge_requests/37
2. https://lists.centos.org/pipermail/centos-devel/2021-November/077482.html
Comment 5 Neal Gompa 2021-12-07 00:26:34 UTC 
(In reply to Branislav Náter from comment #4)
> Currently I'm getting "Server: Apache/2.4.51 (Red Hat Enterprise Linux)" on
> rhel-9 machine and "Server: Apache/2.4.51 (Red Hat Enterprise Linux 9)" with
> '9' at the end of string on c9s machine.
> 
> Testing in MR [1], "Server: Apache/2.4.51 (CentOS Stream 9)" is present. It
> this what we want Neal, Joe? Other variants: "CentOS Stream" (no '9') or
> just "CentOS" (look like expected here [2]).
> 
> 1. https://gitlab.com/redhat/centos-stream/rpms/httpd/-/merge_requests/37
> 2. https://lists.centos.org/pipermail/centos-devel/2021-November/077482.html

If we want to always have just the name with no version, I can update it to always use "NAME", which would give us that consistently.
Comment 6 Neal Gompa 2021-12-07 00:27:59 UTC 
I do think we should identify as "CentOS Stream" for CentOS, "Fedora Linux" for Fedora, and "Red Hat Enterprise Linux" for RHEL. I'll update the MR to do that, and also make a corresponding PR for the Fedora httpd package to do the same.
Comment 7 Neal Gompa 2021-12-07 00:37:58 UTC 
I've changed the MR for the CentOS package to use "$NAME" and I've made a PR to the Fedora httpd package for the same change: https://src.fedoraproject.org/rpms/httpd/pull-request/22
Comment 8 Joe Orton 2021-12-07 08:57:57 UTC 
Yes, better to omit the version.  I think in the past we used to use only "(Red Hat)" for RHEL/RHSCL builds as well, but using $NAME seems fine.
Comment 9 Neal Gompa 2021-12-07 10:01:13 UTC 
(In reply to Joe Orton from comment #8)
> Yes, better to omit the version.  I think in the past we used to use only
> "(Red Hat)" for RHEL/RHSCL builds as well, but using $NAME seems fine.

Yeah, I think was before we switched to pulling the value from os-release. We don't have a way to just get "Red Hat"/"CentOS"/"Fedora" anymore, but I think this is fine.
Comment 17 errata-xmlrpc 2022-05-17 12:29:56 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: httpd), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:2324
Note You need to log in before you can comment on or make changes to this bug.