Skip to content

NO-JIRA: fix: pin http-errors to 2.0.1 for hermetic builds#870

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.18from
mbiarnes:pin-http-errors-to-2.0.1-release-4.18
Apr 9, 2026
Merged

NO-JIRA: fix: pin http-errors to 2.0.1 for hermetic builds#870
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.18from
mbiarnes:pin-http-errors-to-2.0.1-release-4.18

Conversation

@mbiarnes
Copy link
Copy Markdown

@mbiarnes mbiarnes commented Apr 9, 2026

problem:
the build on konflux fails for monitoring-plugin in hermetic mode with

  npm ERR! code ENOTFOUND
  npm ERR! syscall getaddrinfo
  npm ERR! errno ENOTFOUND
  npm ERR! network request to https://registry.npmjs.org/http-errors failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org
  npm ERR! network This is a problem related to network connectivity.
  npm ERR! network In most cases you are behind a proxy or have bad network settings.
  npm ERR! network 
  npm ERR! network If you are behind a proxy, please make sure that the
  npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
  
  npm ERR! A complete log of this run can be found in: /opt/app-root/src/.npm/_logs/2026-04-08T07_50_50_394Z-debug-0.log
  make: *** [Makefile:7: install-frontend-ci] Error 1
  subprocess exited with status 2
  subprocess exited with status 2
  Error: building at STEP "RUN . /cachi2/cachi2.env &&     make install-frontend-ci && make build-frontend": exit status 2 

The test job with these changes:
ocp4-build: SUCCESS
konflux-build: https://konflux-ui.apps.kflux-ocp-p01.7ayg.p1.openshiftapps.com/ns/ocp-art-tenant/applications/openshift-4-18/pipelineruns/ose-4-18-monitoring-plugin-zp9bw
ART-history: https://art-build-history-art-build-history.apps.artc2023.pc3z.p1.openshiftapps.com/build?nvr=monitoring-plugin-container-v4.18.0-202604090818.p2.g0bbcbaf.assembly.test.el9&record_id=7cc27310-0b14-fd5a-7363-139584247887&group=openshift-4.18&outcome=success&type=image

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 9, 2026

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b0c0dc66-d1eb-4e3e-b0f6-6744f0c95235

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci bot requested review from jgbernalp and kyoto April 9, 2026 09:10
@jgbernalp
Copy link
Copy Markdown
Contributor

/lgtm

@jgbernalp jgbernalp changed the title fix: pin http-errors to 2.0.1 for hermetic builds NO-JIRA: fix: pin http-errors to 2.0.1 for hermetic builds Apr 9, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 9, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 9, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@mbiarnes: This pull request explicitly references no jira issue.

Details

In response to this:

problem:
the build on konflux fails for monitoring-plugin in hermetic mode with

 npm ERR! code ENOTFOUND
 npm ERR! syscall getaddrinfo
 npm ERR! errno ENOTFOUND
 npm ERR! network request to https://registry.npmjs.org/http-errors failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org
 npm ERR! network This is a problem related to network connectivity.
 npm ERR! network In most cases you are behind a proxy or have bad network settings.
 npm ERR! network 
 npm ERR! network If you are behind a proxy, please make sure that the
 npm ERR! network 'proxy' config is set properly.  See: 'npm help config'
 
 npm ERR! A complete log of this run can be found in: /opt/app-root/src/.npm/_logs/2026-04-08T07_50_50_394Z-debug-0.log
 make: *** [Makefile:7: install-frontend-ci] Error 1
 subprocess exited with status 2
 subprocess exited with status 2
 Error: building at STEP "RUN . /cachi2/cachi2.env &&     make install-frontend-ci && make build-frontend": exit status 2 

The test job with these changes:
ocp4-build: SUCCESS
konflux-build: https://konflux-ui.apps.kflux-ocp-p01.7ayg.p1.openshiftapps.com/ns/ocp-art-tenant/applications/openshift-4-18/pipelineruns/ose-4-18-monitoring-plugin-zp9bw
ART-history: https://art-build-history-art-build-history.apps.artc2023.pc3z.p1.openshiftapps.com/build?nvr=monitoring-plugin-container-v4.18.0-202604090818.p2.g0bbcbaf.assembly.test.el9&record_id=7cc27310-0b14-fd5a-7363-139584247887&group=openshift-4.18&outcome=success&type=image

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 9, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, mbiarnes

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 9, 2026
@jgbernalp
Copy link
Copy Markdown
Contributor

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Apr 9, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 9, 2026

@mbiarnes: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 0cc64b6 into openshift:release-4.18 Apr 9, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants