-
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
Bug 1922292: [release-4.7] data/rhcos.json: Update boot images #4635
Bug 1922292: [release-4.7] data/rhcos.json: Update boot images #4635
Conversation
- amd64: 47.83.202102090044-0 - s390x: 47.83.202102090311-0 - ppc64le: 47.83.202102091015-0 (cherry picked from commit e653cfd)
@ashcrow: This pull request references Bugzilla bug 1922292, 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. |
Overriding bug check since this is a boot image bump and the linked BZ issues were items to make it in to the bump. |
/test e2e-gcp |
@ashcrow: This pull request references Bugzilla bug 1922292, 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. |
1 similar comment
@ashcrow: This pull request references Bugzilla bug 1922292, 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. |
401 problems on registry, flakes or permafail?
/test e2e-openstack |
@ashcrow: This pull request references Bugzilla bug 1922292, 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. |
I've been seeing those since yesterday mid-day |
@ashcrow: 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. |
Based off the checklist everything but openstack passed. |
@ashcrow: This pull request references Bugzilla bug 1922292, 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. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sdodson 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 |
@ashcrow: This pull request references Bugzilla bug 1922292, 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. |
/override ci/prow/e2e-aws-signal-node |
@sdodson: /override requires a failed status context to operate on.
Only the following contexts were expected:
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. |
/override ci/prow/e2e-aws-single-node |
@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-aws-single-node, ci/prow/e2e-aws-upgrade, ci/prow/e2e-kubevirt, ci/prow/e2e-metal-ipi-virtualmedia, ci/prow/e2e-openstack-ipi, ci/prow/e2e-vsphere-upi, ci/prow/openstack-manifests 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. |
@ashcrow: All pull requests linked via external trackers have merged: Bugzilla bug 1922292 has been moved to the MODIFIED state. 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. |
(cherry picked from commit e653cfd)
See: #4633
(sdodson) Attempting to write down testing expectations, need at least installation to complete on all of our major platforms, either ipi or upi for each, doesn't matter: