Bug 2087043
| Summary: | Cluster API components should use K8s 1.24 dependencies | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Joel Speed <jspeed> |
| Component: | Cloud Compute | Assignee: | Alberto <agarcial> |
| Cloud Compute sub component: | Other Providers | QA Contact: | Milind Yadav <miyadav> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | high | ||
| Priority: | high | CC: | mimccune |
| Version: | 4.11 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.13.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-05-17 22:46:32 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Joel Speed
2022-05-17 08:07:35 UTC
Currently all other CAPI components (upstream Cluster API operator and all the providers) are blocked as they rely on https://github.com/kubernetes-sigs/cluster-api library, and its 1.24 hasn't been released yet. When upstream components are updated, we will backport those changes to OpenShift repos. Moving to assigned we can move it to ON_QA once upstream dependency is resolved . This will now be worked on for a 4.11.z stream, this isn't a blocker for GA Hi Mike , could you add others PR links as well , I would make sure , we had CI run atleast once successfully after the merge to those repos ? thanks for adding azure , vsphere provider already Please add PR for openstack as well to keep it documented at one Bug . Went through the latest regression results , LGTM will move to verify . Let me know if openstack updates are not needed as of now. AWS - https://reportportal-openshift.apps.ocp-c1.prod.psi.redhat.com/ui/#prow/launches/619/298160 Vsphere - https://reportportal-openshift.apps.ocp-c1.prod.psi.redhat.com/ui/#prow/launches/619/298110 Azure - https://reportportal-openshift.apps.ocp-c1.prod.psi.redhat.com/ui/#prow/launches/619/297969 gcp-https://reportportal-openshift.apps.ocp-c1.prod.psi.redhat.com/ui/#prow/launches/619/297872 techpreview - GCP - https://reportportal-openshift.apps.ocp-c1.prod.psi.redhat.com/ui/#prow/launches/619/297833 AWS-https://reportportal-openshift.apps.ocp-c1.prod.psi.redhat.com/ui/#prow/launches/619/295392 VSPHERE-https://reportportal-openshift.apps.ocp-c1.prod.psi.redhat.com/ui/#prow/launches/619/294105 Azure - https://reportportal-openshift.apps.ocp-c1.prod.psi.redhat.com/ui/#prow/launches/619/293324 Additional info - Checking few failed cases in Azure, looks like automation flake , will move to verified once it is confirmed . No, OpenStack cluster API provider update is not required for now. We don't use it and don't plan to do so in some near future. Wrt Azure, currently it doesn't work with OpenShift, and we have a related epic to enable it https://issues.redhat.com/browse/OCPCLOUD-1577. I updated its dependencies because we ship the image anyway. Based on above comments and regression results moving to VERIFIED Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.13.0 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2023:1326 |