Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

The rhel/tools container (https://access.redhat.com/containers/#/repo/57ea8cf09c624c035f96f3bb) needs a "pod to pod diagnostics infrastructure" (shipped with the rhel/tools container), and a set of defined "plugins" (enabled either based on options for the diagnostics infrastructure, or through auto discovery, based on the pod[s] being diagnosed). 

Execution of this diagnostics infrastructure should takes a given container, or set of containers (on the same host), and validate that the diagnostics infrastructure can reach all of the containers independently. 

The primary reason for using the "rhel/tools" container (as the entry point) for this, is that it provides a mechanism for Red Hat to address shipping and providing a single solution ("pod to pod diagnostics infrastructure") for diagnosing common issues with pods.

Making the pod to pod diagnostics infrastructure "plug-able" keeps every pod[s] diagnostics steps from being a cookie cutter shell when information is collected. In short, Python container issues are likely to be very different from JBoss container issues, and as such what diagnostics are done (or get enabled) need to be treated differently.

You should strace the pid from the outside.  not necessary to enter the container.  But this is generally a problem of debugging across mnt namespaces.

Connected to https://trello.com/c/XVqGqK1T/37-epic-next-generation-diagnostics-tool

Could this RFE ue the same mechanism as atomic scan? http://developers.redhat.com/blog/2016/05/02/introducing-atomic-scan-container-vulnerability-detection/

This might remove the need for a tools container?

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.