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
IBMCloud: Pull in latest openshift/api changes #6056
Conversation
Skipping CI for Draft Pull Request. |
/hold Need to rebase and rework go mod changes |
Having issues rebasing and trying to pull in these changes now. |
/retest |
/retitle Bug 2094891: IBMCloud: Pull in latest openshift/api changes |
@cjschaef: This pull request references Bugzilla bug 2094891, which is invalid:
Comment 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 kubernetes/test-infra repository. |
Some more overwhelmed CI workloads Will look at re-kicking the tests tomorrow hopefully. |
/retest required |
@cjschaef: The
The following commands are available to trigger optional jobs:
Use
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 kubernetes/test-infra repository. |
/retest-required |
1 similar comment
/retest-required |
I've opened a separate PR to update the Kubernetes components first (required for kube-openapi update) Then can rebase and rework this PR to pull in the |
#6165 has merged, will rebase and resolve conflicts to pull in new |
IBMCloud DNS support requires a change to PlatformStatus, which is now available in the openshift/api. Updating go vendor with latest api content.
IBMCloud DNS support requires a change to PlatformStatus, which is now available in the openshift/api. Updating installconfigs CRD for latest api content.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
skip review, will check with feature
/hold cancel |
/retest |
/test e2e-ibmcloud |
/test okd-images |
/lgtm |
/uncc @AnnaZivkovic |
/test e2e-azure |
/test e2e-aws-fips |
I investigated the Otherwise, attempting to retrigger pod timeouts. /retest |
/retest |
/test okd-e2e-aws |
@rvanderp3: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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 kubernetes/test-infra repository. |
I see the main cloud providers passed the tests e2e-(azure, aws, gcp, metal-ipi, vsphere, ovirt). I think that could be enough proof the |
/skip |
@cjschaef: 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/test-infra repository. I understand the commands that are listed here. |
IBMCloud DNS support requires a change to PlatformStatus, which
is now available in the openshift/api.