Skip to content

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

Merged
openshift-merge-bot[bot] merged 1 commit intomainfrom
update-requirements-cachito
Feb 26, 2026
Merged

NO-ISSUE: Update requirements.cachito with latest openshift forks commits#799
openshift-merge-bot[bot] merged 1 commit intomainfrom
update-requirements-cachito

Conversation

@github-actions
Copy link

@github-actions github-actions bot commented Feb 23, 2026

Automated Requirements Update

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

Changes

Ironic (openshift/openstack-ironic)

Sushy (openshift/openstack-sushy)

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 23, 2026
@openshift-ci-robot
Copy link

@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)

Sushy (openshift/openstack-sushy)

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 openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 23, 2026
@openshift-ci
Copy link

openshift-ci bot commented Feb 23, 2026

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
Copy link

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 25, 2026
@elfosardo
Copy link

/approve
/lgtm
/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 25, 2026
@openshift-ci-robot
Copy link

@elfosardo: The verified label has been added.

Details

In response to this:

/approve
/lgtm
/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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2026
@openshift-ci
Copy link

openshift-ci bot commented Feb 25, 2026

[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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 25, 2026
- Ironic: 8812bada70141cbc1dca76b1e3f7f6131feb52f4
- Sushy: 75eef4419e86dce0aba187030773ea47901c157e
@github-actions github-actions bot force-pushed the update-requirements-cachito branch from 9b4efc7 to 4cfd248 Compare February 25, 2026 13:38
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Feb 25, 2026
@openshift-ci-robot
Copy link

@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)

Sushy (openshift/openstack-sushy)

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 openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2026
@elfosardo
Copy link

/verified bypass

@elfosardo
Copy link

/lgtm

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 25, 2026
@openshift-ci-robot
Copy link

@elfosardo: The verified label has been added.

Details

In response to this:

/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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 25, 2026
@elfosardo
Copy link

/retest

I doubt it's related

@openshift-ci
Copy link

openshift-ci bot commented Feb 26, 2026

@github-actions[bot]: all tests passed!

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.

@openshift-merge-bot openshift-merge-bot bot merged commit a918bd2 into main Feb 26, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. automated cachito dependencies jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants