NO-ISSUE: Update requirements.cachito with latest openshift forks commits

[github-actions]

Automated Requirements Update

This PR updates requirements.cachito with the latest commit hashes from openshift forks repositories.

Changes

Ironic (openshift/openstack-ironic)

• Previous: 3104b9cf2c486a140675377d892baca67b8e18eb
• New: 7559d3b35773c5a0fae414e701b5075fdb0e8f82
• Compare: https://github.com/openshift/openstack-ironic/compare/3104b9cf2c486a140675377d892baca67b8e18eb..7559d3b35773c5a0fae414e701b5075fdb0e8f82

Sushy (openshift/openstack-sushy)

• Previous: 6094f72fda9c198ce1b3c531cd97c2421dcc4489
• New: 134fc12a1c9e35d86df6178fc6f74db4717fdbe4
• Compare: https://github.com/openshift/openstack-sushy/compare/6094f72fda9c198ce1b3c531cd97c2421dcc4489..134fc12a1c9e35d86df6178fc6f74db4717fdbe4

Verification

Before merging, please ensure:

• The new commits don't introduce breaking changes
• The build completes successfully
• All tests pass

---

This PR was automatically created by the update-requirements workflow.

[openshift-ci-robot]

@github-actions[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Automated Requirements Update

This PR updates requirements.cachito with the latest commit hashes from openshift forks repositories.

Changes

Ironic (openshift/openstack-ironic)

• Previous: 3104b9cf2c486a140675377d892baca67b8e18eb
• New: 8e945731274c116f0caaa815502a9e371470f144
• Compare: https://github.com/openshift/openstack-ironic/compare/3104b9cf2c486a140675377d892baca67b8e18eb..8e945731274c116f0caaa815502a9e371470f144

Verification

Before merging, please ensure:

• The new commits don't introduce breaking changes
• The build completes successfully
• All tests pass

---

This PR was automatically created by the update-requirements workflow.

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 NOT APPROVED

This pull-request has been approved by: github-actions[bot]
Once this PR has been reviewed and has the lgtm label, please assign dtantsur 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:

• OWNERS

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

[openshift-ci]

Hi @github-actions[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[elfosardo]

/ok-to-test

[elfosardo]

/retest

[elfosardo]

latest changes in ironic setup config require a bump in setuptools version

[openshift-ci]

@github-actions[bot]: 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-metal-ipi-ovn-ipv6	5d22589	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/prevalidation-images	5d22589	link	true	/test prevalidation-images
ci/prow/images	5d22589	link	true	/test images
ci/prow/e2e-metal-ipi-bm	5d22589	link	true	/test e2e-metal-ipi-bm

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.

[dtantsur]

/retitle OCPBUGS-44902: Update requirements.cachito with latest openshift forks commits

[openshift-ci-robot]

@github-actions[bot]: This pull request references Jira Issue OCPBUGS-44902, 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.0.0) matches configured target version for branch (5.0.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @jadhaj

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

Details

In response to this:

Automated Requirements Update

This PR updates requirements.cachito with the latest commit hashes from openshift forks repositories.

Changes

Ironic (openshift/openstack-ironic)

• Previous: 3104b9cf2c486a140675377d892baca67b8e18eb
• New: 7559d3b35773c5a0fae414e701b5075fdb0e8f82
• Compare: https://github.com/openshift/openstack-ironic/compare/3104b9cf2c486a140675377d892baca67b8e18eb..7559d3b35773c5a0fae414e701b5075fdb0e8f82

Sushy (openshift/openstack-sushy)

• Previous: 6094f72fda9c198ce1b3c531cd97c2421dcc4489
• New: 134fc12a1c9e35d86df6178fc6f74db4717fdbe4
• Compare: https://github.com/openshift/openstack-sushy/compare/6094f72fda9c198ce1b3c531cd97c2421dcc4489..134fc12a1c9e35d86df6178fc6f74db4717fdbe4

Verification

Before merging, please ensure:

• The new commits don't introduce breaking changes
• The build completes successfully
• All tests pass

---

This PR was automatically created by the update-requirements workflow.

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]

@github-actions[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

Automated Requirements Update

This PR updates requirements.cachito with the latest commit hashes from openshift forks repositories.

Changes

Ironic (openshift/openstack-ironic)

• Previous: 3104b9cf2c486a140675377d892baca67b8e18eb
• New: 7559d3b35773c5a0fae414e701b5075fdb0e8f82
• Compare: https://github.com/openshift/openstack-ironic/compare/3104b9cf2c486a140675377d892baca67b8e18eb..7559d3b35773c5a0fae414e701b5075fdb0e8f82

Sushy (openshift/openstack-sushy)

• Previous: 6094f72fda9c198ce1b3c531cd97c2421dcc4489
• New: 134fc12a1c9e35d86df6178fc6f74db4717fdbe4
• Compare: https://github.com/openshift/openstack-sushy/compare/6094f72fda9c198ce1b3c531cd97c2421dcc4489..134fc12a1c9e35d86df6178fc6f74db4717fdbe4

Verification

Before merging, please ensure:

• The new commits don't introduce breaking changes
• The build completes successfully
• All tests pass

---

This PR was automatically created by the update-requirements workflow.

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.