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.
Current status: The pre-build blobs are still present in the current errata builds.We have statement from legal and waiting for statement/instruction from product security.
Current work: jstanek is working on making a libc available for WASM builds. zsvetlik is working on including llhttp package into RHEL, so we can start using it in place of the bundled dependencies.
Next steps: Depending on the prodsec statement, the source tarball will need to be adjusted to conform. We expect these changes to be manual for this release, and this release to have an "exception" in this regard. The next release should hopefully use blobs created from RH-built sources.
Longer term, we are working on an upstream-compatible process of linking/bundling/utilizing RH-built WASM without resorting to excessive patching of the NodeJS sources.
Since we are still working on remediation of this situation, and customers expect having NodeJS 18 available in the upcoming RHEL batch, I'm requesting an exception from the devel freeze. We will have to do errata respins to comply with the legal and prodsec requirements.
I consider this VERIFIED:
$ tar -xf nodejs-18.10.0-3.module+el9.1.0+16866+0fab0697.src/icu4c-71_1-src.tgz
$ cd nodejs-18.10.0-3.module+el9.1.0+16866+0fab0697.src/
$ tar -xf node-v18.10.0-stripped.tar.gz
$ grep version node-*/deps/undici/src/package.json
"version": "5.10.0",
$ ls | grep undici
undici-5.10.0.tar.gz
$ grep version node-v18.10.0/deps/cjs-module-lexer/package.json
"version": "1.2.2",
$ ls | grep cjs-module-lexer
cjs-module-lexer-1.2.2.tar.gz
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 (nodejs:18 bug fix and enhancement update), 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/RHEA-2022:8233