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.

Description of problem:
I'm using ubi8/nodejs-14 image
When I run a program that uses the http2 module, I get a TON of sterr output.


Version-Release number of selected component (if applicable):
latest: Pulling from ubi8/nodejs-14
Digest: sha256:c94c7956028e2db96979d461bb9cd82f39c8f962b4cb5b04307a97be36709fd7

nodejs-full-i18n-14.15.4-2.module+el8.3.0+9635+ffdf8381.x86_64
nodejs-14.15.4-2.module+el8.3.0+9635+ffdf8381.x86_64
nodejs-docs-14.15.4-2.module+el8.3.0+9635+ffdf8381.noarch
nodejs-nodemon-2.0.3-1.module+el8.3.0+6519+9f98ed83.noarch

How reproducible: Always

Steps to Reproduce:
Here is a similar bug: https://bugs.centos.org/view.php?id=17047
It contains info on how to reproduce.

Actual results:
Tons of logs dumped to stderr

example:
---
deflatehd: emit indexed index=66, 1 bytes
deflatehd: deflating grpc-accept-encoding: identity,deflate,gzip
deflatehd: name/value match index=65
deflatehd: emit indexed index=65, 1 bytes
---

Expected results:
no additional logging other than what I specify

Additional info:

VERIFIED as TESTED

Test run successfully (jhouska-1MT-RHEL-8.4.0-20210309.1-278949-2021-03-26-14-43)
with (nodejs-14.16.0-2.module+el8.3.0+10180+b92e1eb6.x86_64).

Te same version is now part of nightly compose (http://download.eng.brq.redhat.com/nightly/rhel-8/RHEL-8/latest-RHEL-8.4.0/compose/AppStream/source/tree/Packages/nodejs-14.16.0-2.module+el8.3.0+10180+b92e1eb6.src.rpm).

Hi,

Since the issue described in this bug should be resolved (VERIFIED), could you please close this bug with resolution 'CURRENTRELEASE' if this bug got fixed ?

If the fix for this is not released yet, check if this will ever get fixed. In case of a negative answer then please change it as WONTFIX.

If there's anything else to be done on this BZ, if it's still active, not released yet and we actually intend to release it, then please ignore my message.

Please note: for those bugs which are not included in errata, please add 'TestOnly' keyword, and those bugs with 'TestOnly' keyword will be closed automatically after GA.
TestOnly: Use this when there is no code delivery involved, or for use when code is already upstream and will be incorporated automatically to the next release for testing purposes only.

Thank you.

Shipped in https://errata.devel.redhat.com/advisory/69886 , closing.