Skip to content

ART-18521: switch networking-console-plugin pkg_managers from yarn to npm (4.18)#10503

Open
joepvd wants to merge 1 commit into
openshift-eng:openshift-4.18from
joepvd:ART-18521-4.18-networking-console-plugin
Open

ART-18521: switch networking-console-plugin pkg_managers from yarn to npm (4.18)#10503
joepvd wants to merge 1 commit into
openshift-eng:openshift-4.18from
joepvd:ART-18521-4.18-networking-console-plugin

Conversation

@joepvd
Copy link
Copy Markdown
Contributor

@joepvd joepvd commented May 11, 2026

Summary

Switch pkg_managers from yarn to npm for networking-console-plugin on openshift-4.18.

The upstream source uses package-lock.json (npm), not yarn.lock. The hermeto/yarn
prefetch handler fails because it cannot determine the yarn version — there is no
packageManager in package.json and no .yarnrc.yml in the repo.

This aligns with openshift-4.20 which already uses pkg_managers: [npm] and builds
successfully.

Failing build: https://art-build-history-art-build-history.apps.artc2023.pc3z.p1.openshiftapps.com/?name=^networking-console-plugin$&group=openshift-4.18&assembly=stream&engine=konflux&outcome=failure

Analysis

The hermeto prefetch step fails with:

ERROR PackageRejected: Unable to determine the yarn version to use to process the request
Ensure that either yarnPath is defined in .yarnrc.yml or that packageManager is defined in package.json

The upstream repo has package-lock.json (npm) across all branches (4.18, 4.19, 4.20).
The 4.20 ocp-build-data config already uses pkg_managers: [npm] and builds fine.

Changes

  • Changed content.source.pkg_managers from [yarn] to [npm]

Generated with Claude Code

@joepvd joepvd added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 11, 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 May 11, 2026
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 11, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 11, 2026

@joepvd: This pull request references ART-18521 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.18.z" version, but no target version was set.

Details

In response to this:

Summary

Switch pkg_managers from yarn to npm for networking-console-plugin on openshift-4.18.

The upstream source uses package-lock.json (npm), not yarn.lock. The hermeto/yarn
prefetch handler fails because it cannot determine the yarn version — there is no
packageManager in package.json and no .yarnrc.yml in the repo.

This aligns with openshift-4.20 which already uses pkg_managers: [npm] and builds
successfully.

Failing build: https://art-build-history-art-build-history.apps.artc2023.pc3z.p1.openshiftapps.com/?name=^networking-console-plugin$&group=openshift-4.18&assembly=stream&engine=konflux&outcome=failure

Analysis

The hermeto prefetch step fails with:

ERROR PackageRejected: Unable to determine the yarn version to use to process the request
Ensure that either yarnPath is defined in .yarnrc.yml or that packageManager is defined in package.json

The upstream repo has package-lock.json (npm) across all branches (4.18, 4.19, 4.20).
The 4.20 ocp-build-data config already uses pkg_managers: [npm] and builds fine.

Changes

  • Changed content.source.pkg_managers from [yarn] to [npm]

Generated with Claude Code

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 May 11, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign namansharma18899 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@joepvd
Copy link
Copy Markdown
Contributor Author

joepvd commented May 11, 2026

Triggered seed-lockfile test build #393 to verify (ASSEMBLY=test, data from this PR branch).

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 11, 2026

@joepvd: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/art-pre-commit-check 302f371 link false /test art-pre-commit-check

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants