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.

Description of problem:

Latest rhel7/rhel-tools container image has no manpages installed


Version-Release number of selected component (if applicable):

registry.access.redhat.com/rhel7/rhel-tools                      latest              37b5171f5352        2 weeks ago         990.4 MB

How reproducible:

100%

Steps to Reproduce:
man <anything>

Actual results:

No manual entry for <anything>

Expected results:

manpage for <anything>

Additional info:

THis is a regression

Hi, 

The article about rhel-tools mentions that it contains man pages: 

https://access.redhat.com/articles/1336853 (in the Overview section)

I am not sure if the respective articles about rsyslog and sadc should mention that they do NOT contain man pages, since this is expected behaviour.

Additionally, there are two other places where a note can go:

1) the Release Notes, under "Other Notes", explaining that no man pages is the expected behaviour, unless there is a workaround as in the case of rhel-tools

2) the "Running Super Privileged Containers..." article: https://access.redhat.com/articles/1342703

I think both should be updated.

Ok, after consulting Eliska, I learned it's about the base images, and in this case the most appropriate places are the Release Notes and the "Recommended Practices for Container Development" article: https://access.redhat.com/articles/1483053.

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, 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://rhn.redhat.com/errata/RHBA-2015-1802.html