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: f8686d33cf45e128c7d58e055c0c0ddf27e3d959
• New: 3104b9cf2c486a140675377d892baca67b8e18eb
• Compare: https://github.com/openshift/openstack-ironic/compare/f8686d33cf45e128c7d58e055c0c0ddf27e3d959..3104b9cf2c486a140675377d892baca67b8e18eb

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: f8686d33cf45e128c7d58e055c0c0ddf27e3d959
• New: 42ee3e263263c8b485e14a80561e8da667b51105
• Compare: https://github.com/openshift/openstack-ironic/compare/f8686d33cf45e128c7d58e055c0c0ddf27e3d959..42ee3e263263c8b485e14a80561e8da667b51105

Sushy (openshift/openstack-sushy)

• Previous: 5a6b97ea02edae6f709a3ced09db7c88c57ae5ef
• New: 7e6b973f3a252929d7f2699a057504758b07b670
• Compare: https://github.com/openshift/openstack-sushy/compare/5a6b97ea02edae6f709a3ced09db7c88c57ae5ef..7e6b973f3a252929d7f2699a057504758b07b670

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.

[MahnoorAsghar]

/ok-to-test

[MahnoorAsghar]

/test okd-scos-images

WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:998)'))': /openstack/requirements/raw/branch/master/upper-constraints.txt
ERROR: Could not install packages due to an OSError: HTTPSConnectionPool(host='opendev.org', port=443): Max retries exceeded with url: /openstack/requirements/raw/branch/master/upper-constraints.txt (Caused by SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:998)')))
error: build error: building at STEP "RUN prepare-image.sh &&     rm -f /bin/prepare-image.sh &&     rm -f /bin/setup.okd &&     /bin/prepare-ipxe.sh &&     rm -f /bin/prepare-ipxe.sh": while running runtime: exit status 1

[MahnoorAsghar]

/test okd-scos-images

[MahnoorAsghar]

/retest

[MahnoorAsghar]

/retest

[MahnoorAsghar]

/test e2e-metal-ipi-bm
e2e-metal-ipi-bm has failed 3 times:

• 7 Apr, 2:27 pm
  level=error msg=ReadyIngressNodesAvailable: Authentication requires functional ingress which requires at least one schedulable and ready node. Got 0 worker nodes, 3 master nodes, 0 custom target nodes (none are schedulable or ready for ingress pods).
• 7 Apr, 5:42 pm and 8 Apr, 11:41 am
  level=error msg=Cluster operator authentication Available is False with WellKnown_NotReady: WellKnownAvailable: The well-known endpoint is not yet available: kube-apiserver oauth endpoint https://10.10.129.61:6443/.well-known/oauth-authorization-server is not yet served and authentication operator keeps waiting (check kube-apiserver operator, and check that instances roll out successfully, which can take several minutes per instance)

[MahnoorAsghar]

/test e2e-metal-ipi-bm

Last e2e-metal-ipi-bm failure analysed using claude:
The failure was a cascading set of delays that collectively pushed worker node readiness past the 1-hour deadline:

1. ManagementCPUsOverride webhook blocked pod creation (~20 min delay at 13:30 UTC)

Error creating: pods "cluster-baremetal-operator-6b68964448-" is forbidden:
autoscaling.openshift.io/ManagementCPUsOverride the cluster does not have any nodes

This prevented the machine-api stack from starting until 13:50 UTC.
2. Ironic API not immediately ready — microversions not supported by endpoint (13:50–14:14)

ironic settings... error caught while checking endpoint, will retry
microversions not supported by endpoint

After the metal3 pod started, the baremetal-operator kept receiving this error when connecting to the ironic API endpoint (metal3-state.openshift-machine-api.svc:6385). Combined with the webhook not being ready, this caused repeated failures to add finalizers to the worker BareMetalHosts (openshift-3, openshift-4):

failed to add finalizer: failed calling webhook "baremetalhost.metal3.io":
no endpoints available for service "baremetal-operator-webhook-service"

With exponential backoff, this stretched to a 24-minute delay before workers were registered.
3. Workers provisioned just 7 minutes before timeout
Ironic provisioning: 14:53–14:55 UTC ✅
Installer timeout: 15:02 UTC ❌ (nodes needed more time to boot and join)

[MahnoorAsghar]

/test e2e-metal-ipi-bm
The ManagementCPUsOverride issue might be coming from the nightly the job was running against. Lets see if a new nightly resolves this.

[MahnoorAsghar]

/test e2e-metal-ipi-virtualmedia e2e-metal-ipi-ovn-ipv6

[MahnoorAsghar]

/test e2e-metal-ipi-ovn-ipv6 e2e-metal-ipi-virtualmedia
These are failing due to non-related failures coming from upstream k8s
Surprisingly, searching for 'FileKeyRef', for example, shows green rows in Sippy

[MahnoorAsghar]

e2e-metal-ipi-bm:
Testing metal3-io/baremetal-operator#3162 here: openshift/baremetal-operator#477
Testing metal3-io/baremetal-operator#3163 here: openshift/baremetal-operator#478
Testing both together here: openshift/baremetal-operator#479

[MahnoorAsghar]

Also, trying to make sure that the failures on these 3 jobs aren't related to the contents of this PR, by running these tests here: #833

[iurygregory]

seems like #833 shows green... I'm wondering if something in our ironic commits broke something, but I couldn't identify things in the logs =(

[elfosardo]

/retest

[elfosardo]

yay for merge conflict, my "fault" actually :)

[elfosardo]

/unhold

[elfosardo]

/retest

[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: f8686d33cf45e128c7d58e055c0c0ddf27e3d959
• New: 3104b9cf2c486a140675377d892baca67b8e18eb
• Compare: https://github.com/openshift/openstack-ironic/compare/f8686d33cf45e128c7d58e055c0c0ddf27e3d959..3104b9cf2c486a140675377d892baca67b8e18eb

Sushy (openshift/openstack-sushy)

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

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.

[elfosardo]

/lgtm
/verified bypass

[openshift-ci-robot]

@elfosardo: The verified label has been added.

Details

In response to this:

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

/retest-required

Remaining retests: 0 against base HEAD 15add7e and 2 for PR HEAD a278a03 in total

[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: f8686d33cf45e128c7d58e055c0c0ddf27e3d959
• New: 3104b9cf2c486a140675377d892baca67b8e18eb
• Compare: https://github.com/openshift/openstack-ironic/compare/f8686d33cf45e128c7d58e055c0c0ddf27e3d959..3104b9cf2c486a140675377d892baca67b8e18eb

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]

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

[elfosardo]

/lgtm
/verified bypass

[openshift-ci-robot]

@elfosardo: The verified label has been added.

Details

In response to this:

/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.