-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OCPBUGS-44231: [release-4.17] capi/aws: bump provider for LB DNS lookup fix #9179
base: release-4.17
Are you sure you want to change the base?
Conversation
We need to bump capa to get a fix for the LB DNS name lookup issue. Notable changes from `git log --oneline 3f3ce5610204..5b4f7c1ac`: ``` 32ebcce58 🐛elbv2: wait for LB active state instead of resolving DNS name 7e0812f59 🌱 Bump CAPI to v1.8.4 (openshift#5061) 8f46a4d34 Allow to specify cidr block for default node nodeport ingress rule ```
This version is needed by the aws provider
/jira cherrypick OCPBUGS-36222 |
@r4f4: Jira Issue OCPBUGS-36222 has been cloned as Jira Issue OCPBUGS-44231. Will retitle bug to link to clone. In response to this:
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. |
@r4f4: This pull request references Jira Issue OCPBUGS-44231, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
/label platform/aws |
@r4f4: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
/approve |
/label backport-risk-assessed |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sadasu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Manual cherry-pick of #8927