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: e84198f103b6a5eb531baf2560d0f72a77916780
• New: 1a5053a76bde627a4624004f737d1989bf149130
• Compare: https://github.com/openshift/openstack-ironic/compare/e84198f103b6a5eb531baf2560d0f72a77916780..1a5053a76bde627a4624004f737d1989bf149130

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: e84198f103b6a5eb531baf2560d0f72a77916780
• New: 1a5053a76bde627a4624004f737d1989bf149130
• Compare: https://github.com/openshift/openstack-ironic/compare/e84198f103b6a5eb531baf2560d0f72a77916780..1a5053a76bde627a4624004f737d1989bf149130

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]

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]

/approve
/verified bypass

[openshift-ci-robot]

@elfosardo: The verified label has been added.

Details

In response to this:

/approve
/verified bypass

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: elfosardo, github-actions[bot]

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 [elfosardo]

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

[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/images	87062da	link	true	/test images
ci/prow/e2e-metal-ipi-virtualmedia	87062da	link	true	/test e2e-metal-ipi-virtualmedia
ci/prow/prevalidation-images	87062da	link	true	/test prevalidation-images
ci/prow/e2e-metal-ipi-ovn-ipv6	87062da	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-metal-ipi-bm	87062da	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.

[elfosardo]

this needs a new openstacksdk pkg version 4.9.0
working on it