OCPBUGS-114789, OCPBUGS-114792, OCPBUGS-114786: fix: upgrade vulnerable fast-uri dependency

[jgbernalp]

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786

Summary by CodeRabbit

• Chores
  • Updated the bundled fast-uri version to improve compatibility and reliability.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Team

Run ID: 96e74dc7-867a-4567-b051-9aee8eb1baf7

📥 Commits

Reviewing files that changed from the base of the PR and between 525bbd1 and f9b1e45.

⛔ Files ignored due to path filters (1)

• web/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• web/package.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Walkthrough

The web package configuration updates the fast-uri override from version 3.1.4 to 3.1.6.

Changes

Dependency override update

Layer / File(s)	Summary
Update fast-uri override web/package.json	The fast-uri override changes from 3.1.4 to 3.1.6.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to f9b1e

This localized dependency update resolves the vulnerable fast-uri version without introducing an actionable merge-blocking risk. The PR is merge-ready after normal checks and review.

Suggested reviewers: peteryurkovich, zhuje

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the vulnerable fast-uri dependency upgrade and references the related issues. It matches the pull request changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PASS: The pull request changes only the fast-uri dependency version in web/package.json and its lockfile entry. It adds no Ginkgo tests or test titles, so it introduces no unstable or overly speci…
Test Structure And Quality	✅ Passed	PASS: The pull request changes only web/package.json and web/package-lock.json, updating fast-uri from 3.1.4 to 3.1.6. The diff contains no Ginkgo tests or cluster operations, so the stated test…
Microshift Test Compatibility	✅ Passed	PASS: The pull request changes only the fast-uri version in web/package.json and the matching lockfile metadata. It adds no Ginkgo tests or other test code, so the MicroShift test compatibility ch…
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PASS: The pull request changes only web/package.json and web/package-lock.json to update the fast-uri override from 3.1.4 to 3.1.6. It adds no Ginkgo e2e tests or other test declarations, so the…
Topology-Aware Scheduling Compatibility	✅ Passed	PASS — The pull request changes only web/package.json and web/package-lock.json to upgrade fast-uri from 3.1.4 to 3.1.6. It does not add or modify deployment manifests, operator code, controller…
Ote Binary Stdout Contract	✅ Passed	PASS. The pull request changes only web/package.json and web/package-lock.json. It updates the fast-uri override and lockfile metadata from 3.1.4 to 3.1.6. It does not change main(), init(),…
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	PASS: The pull request changes only web/package.json and web/package-lock.json to upgrade fast-uri from 3.1.4 to 3.1.6. No Ginkgo e2e tests or other test code were added, so the IPv4 and externa…
No-Weak-Crypto	✅ Passed	PASS: The pull request changes only fast-uri dependency metadata from 3.1.4 to 3.1.6 in web/package.json and web/package-lock.json. It adds no cryptographic code, weak algorithm usage, custom cr…
Container-Privileges	✅ Passed	PASS. The pull request changes only web/package.json and web/package-lock.json to update fast-uri from 3.1.4 to 3.1.6. The diff introduces no privileged, hostPID, hostNetwork, hostIPC, `…
No-Sensitive-Data-In-Logs	✅ Passed	PASS: The pull request changes only the fast-uri version and integrity metadata in web/package.json and web/package-lock.json. The diff adds no logging code or sensitive-data output, and no logg…

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Full details: Stable And Deterministic Test Names

Explanation

PASS: The pull request changes only the fast-uri dependency version in web/package.json and its lockfile entry. It adds no Ginkgo tests or test titles, so it introduces no unstable or overly specific test name.

Full details: Test Structure And Quality

Explanation

PASS: The pull request changes only web/package.json and web/package-lock.json, updating fast-uri from 3.1.4 to 3.1.6. The diff contains no Ginkgo tests or cluster operations, so the stated test-structure requirements do not apply.

Full details: Microshift Test Compatibility

Explanation

PASS: The pull request changes only the fast-uri version in web/package.json and the matching lockfile metadata. It adds no Ginkgo tests or other test code, so the MicroShift test compatibility check does not apply.

Full details: Single Node Openshift (Sno) Test Compatibility

Explanation

PASS: The pull request changes only web/package.json and web/package-lock.json to update the fast-uri override from 3.1.4 to 3.1.6. It adds no Ginkgo e2e tests or other test declarations, so the SNO compatibility check does not apply.

Full details: Topology-Aware Scheduling Compatibility

Explanation

PASS — The pull request changes only web/package.json and web/package-lock.json to upgrade fast-uri from 3.1.4 to 3.1.6. It does not add or modify deployment manifests, operator code, controllers, or scheduling configuration. The topology-aware scheduling check is therefore not applicable.

Full details: Ote Binary Stdout Contract

Explanation

PASS. The pull request changes only web/package.json and web/package-lock.json. It updates the fast-uri override and lockfile metadata from 3.1.4 to 3.1.6. It does not change main(), init(), test suite setup, or any process-level stdout/logging code. Therefore, it introduces no OTE binary stdout contract violation.

Full details: Ipv6 And Disconnected Network Test Compatibility

Explanation

PASS: The pull request changes only web/package.json and web/package-lock.json to upgrade fast-uri from 3.1.4 to 3.1.6. No Ginkgo e2e tests or other test code were added, so the IPv4 and external-connectivity conditions do not apply.

Full details: No-Weak-Crypto

Explanation

PASS: The pull request changes only fast-uri dependency metadata from 3.1.4 to 3.1.6 in web/package.json and web/package-lock.json. It adds no cryptographic code, weak algorithm usage, custom crypto implementation, or secret/token comparison.

Full details: Container-Privileges

Explanation

PASS. The pull request changes only web/package.json and web/package-lock.json to update fast-uri from 3.1.4 to 3.1.6. The diff introduces no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation: true settings. Existing USER 0 directives occur only in unchanged build-stage Dockerfile content, while the application image stages use USER 1001.

Full details: No-Sensitive-Data-In-Logs

Explanation

PASS: The pull request changes only the fast-uri version and integrity metadata in web/package.json and web/package-lock.json. The diff adds no logging code or sensitive-data output, and no logging-related terms appear in the changed lines.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[jgbernalp]

/label qe-approved

[openshift-ci-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114814, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114814, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786
• https://redhat.atlassian.net/browse/OCPBUGS-114814

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114814, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114817, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786
• https://redhat.atlassian.net/browse/OCPBUGS-114814

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114814, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-114817, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786
• https://redhat.atlassian.net/browse/OCPBUGS-114814
• https://redhat.atlassian.net/browse/OCPBUGS-114817

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114814, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114817, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114820, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786
• https://redhat.atlassian.net/browse/OCPBUGS-114814
• https://redhat.atlassian.net/browse/OCPBUGS-114817

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114814, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-114817, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-114820, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786
• https://redhat.atlassian.net/browse/OCPBUGS-114814
• https://redhat.atlassian.net/browse/OCPBUGS-114817
• https://redhat.atlassian.net/browse/OCPBUGS-114820

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114814, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114817, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114820, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114823, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786
• https://redhat.atlassian.net/browse/OCPBUGS-114814
• https://redhat.atlassian.net/browse/OCPBUGS-114817
• https://redhat.atlassian.net/browse/OCPBUGS-114820

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114814, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-114817, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-114820, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-114823, which is invalid:

• expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "4.23.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786
• https://redhat.atlassian.net/browse/OCPBUGS-114814
• https://redhat.atlassian.net/browse/OCPBUGS-114817
• https://redhat.atlassian.net/browse/OCPBUGS-114820
• https://redhat.atlassian.net/browse/OCPBUGS-114823

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786
• https://redhat.atlassian.net/browse/OCPBUGS-114814
• https://redhat.atlassian.net/browse/OCPBUGS-114817
• https://redhat.atlassian.net/browse/OCPBUGS-114820
• https://redhat.atlassian.net/browse/OCPBUGS-114823

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.

[jgbernalp]

/jira-refresh

[openshift-ci-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786

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.

[PeterYurkovich]

/lgtm

[openshift-merge-bot]

Scheduling required tests:
/test e2e-agnostic-cmo
/test e2e-monitoring

[PeterYurkovich]

/retest

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD d05ec90 and 2 for PR HEAD fe13268 in total

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 525bbd1 and 1 for PR HEAD fe13268 in total

[openshift-ci-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789. The bug has been updated to no longer refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114792. The bug has been updated to no longer refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114786. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786

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]

New changes are detected. LGTM label has been removed.

[openshift-ci-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786

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-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-114789, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114792, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

This pull request references Jira Issue OCPBUGS-114786, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.1.0) matches configured target version for branch (5.1.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

Fixes also:

• https://redhat.atlassian.net/browse/OCPBUGS-114792
• https://redhat.atlassian.net/browse/OCPBUGS-114786

Summary by CodeRabbit

• Chores
• Updated the bundled fast-uri version to improve compatibility and reliability.

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]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• OWNERS [PeterYurkovich,jgbernalp]

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• OWNERS [PeterYurkovich,jgbernalp]

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

[jgbernalp]

/retest

[openshift-ci]

@jgbernalp: The following tests 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/e2e-monitoring	fe13268	link	true	/test e2e-monitoring
ci/prow/e2e-agnostic-cmo	fe13268	link	true	/test e2e-agnostic-cmo
ci/prow/translations	f9b1e45	link	true	/test translations

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.