[release-4.18] OCPBUGS-49361: UPSTREAM: <carry>: Fix Pipefile.lock

[arkadeepsen]

This PR fixes the Pipfile.lock by making it consistent with the current 4.19 branch. The changes to the Pipfile.lock was backported from the main/release-4.19 branch and in the process some of the changes were missed. This PR fixes the issue.

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-48811 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-48811 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
• bug has dependents

Requesting review from QA contact:
/cc @emmajiafan

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

In response to this:

This PR fixes the Pipfile.lock by making it consistent with the current 4.19 branch. The changes to the Pipfile.lock was backported from the main/release-4.19 branch and in the process some of the changes were missed. This PR fixes the issue.

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]

@arkadeepsen: all tests passed!

Full PR test history. Your PR dashboard.

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.

[arkadeepsen]

/cc @chiragkyal

[chiragkyal]

We should add a pre-submit CI job to catch such issues early. openshift/release#60751 should do the work, but it needs some tweaks in the Makefile to have a happy pass.

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arkadeepsen, chiragkyal

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [arkadeepsen,chiragkyal]

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

[chiragkyal]

/retitle [release-4.18] OCPBUGS-49361: UPSTREAM: : Fix Pipefile.lock

[chiragkyal]

The changes to the Pipfile.lock was backported from the main/release-4.19 branch and in the process some of the changes were missed.

• xRef: Backport PR OCPBUGS-48812: V1.36.1 rebase release 4.18 #29

[arkadeepsen]

/cc @TrilokGeer
for the backport-risk-assessed label

[TrilokGeer]

/label backport-risk-assessed

[emmajiafan]

/label cherry-pick-approved

[emmajiafan]

/label qe-approved

[openshift-ci-robot]

@arkadeepsen: This pull request references Jira Issue OCPBUGS-49361, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.0) matches configured target version for branch (4.18.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-48811 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-48811 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
• bug has dependents

Requesting review from QA contact:
/cc @emmajiafan

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

In response to this:

This PR fixes the Pipfile.lock by making it consistent with the current 4.19 branch. The changes to the Pipfile.lock was backported from the main/release-4.19 branch and in the process some of the changes were missed. This PR fixes the issue.

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]

@arkadeepsen: Jira Issue OCPBUGS-49361: All pull requests linked via external trackers have merged:

• openshift/ansible-operator-plugins#30

Jira Issue OCPBUGS-49361 has been moved to the MODIFIED state.

In response to this:

This PR fixes the Pipfile.lock by making it consistent with the current 4.19 branch. The changes to the Pipfile.lock was backported from the main/release-4.19 branch and in the process some of the changes were missed. This PR fixes the issue.

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

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-ansible-operator
This PR has been included in build openshift-enterprise-ansible-operator-container-v4.18.0-202501300501.p0.g39ec678.assembly.stream.el9.
All builds following this will include this PR.