Skip to content

Conversation

@tnozicka
Copy link
Contributor

@tnozicka tnozicka commented Nov 20, 2020

No description provided.

k8s-ci-robot and others added 30 commits September 10, 2020 21:28
…-pick-of-#93687-upstream-release-1.19

Automated cherry pick of kubernetes#93687: kubectl describe pod: use ReportingController as an event
Fix containerNameToRef func to get init containers and ephemeral containers properly.

Set EphemeralContainers in generatePodCopyWithDebugContainer func to nil which means
dropping ephemeral containers from a copy of pod so that it can be created successfully,
otherwise it is rejected by the API server.
Bug 1854434: UPSTREAM: 94112: Remove canonicalization of endpoints by endpoints controller for better comparison
…ick-of-#94580-origin-release-1.19

Automated cherry pick of kubernetes#94580: Fix index out of range panic for kubectl alpha debug
Bug 1874584: UPSTREAM: <carry>: retry etcd errors
Bug 1875194: UPSTREAM: 94609: Use namespace flag passed to RunKubectl* methods
Bug 1867929: Reduce offline volume expansion flake
…objects

Bug 1877338: UPSTREAM: 94653: Tolerate NotFound errors when deleting snapshots
openshift/origin needs to be able to vendor these definitions so they
need to be committed.

Should be squashed with UPSTREAM: <carry>: Stop ignoring test/e2e/generated/bindata.go
…avoidPod annotation: fail when not all pods are properly deleted

Fail when e2erc.DeleteRCAndWaitForGC returns an error to discover the reason why the pods are not deleted properly
…ied resource

Currently count includes keys from different resource(s) if the keys
are a prefix of the specified resource/key.

Consider the following keys:
A: <storage-prefix>//foo.bar.io/machines
B: <storage-prefix>//foo.bar.io/machinesets
If we ask for the count of key A, the result will also include the
keys from key B since key B shares the same prefix as key A.

Append a separator to mark the end of the key, this will exclude all
other keys from a different resource that is a prefix of the specified
key.
…om source

Remove installation from source of recent bash and protoc 3.0.0 now
that both are available on the ci build root image.

Squash with UPSTREAM: <carry>: Enable build, test and verify
Bug 1877791: Release lock on KCM and KS termination
Bug 1878163: Build with golang 1.15
…lished OpenAPI

kubectl falls over arrays without item schema. Hence, we have to publish a less precise OpenAPI spec (similar to other pruning we already do for the same reason).
…orities-avoidPods

bug 1880279: [e2e] scheduling: Pod should avoid nodes that have avoidPod annotation: fail when not all pods are properly deleted
Add rebase instructions updated to reflect the transition of hyperkube
maintenance from origin to openshift/kubernetes. For releases 4.6 and
above, this document supercedes the instructions in the the [rebase
enhancment](https://github.com/openshift/enhancements/blob/master/enhancements/rebase.md). Putting
this document in the repository to which it applies should simplify
its maintenance as part of the regular rebase workflow and also allow
it to be more easily discovered.

Co-authored-by: Lukasz Szaszkiewicz <lukasz.szaszkiewicz@gmail.com>
…r-scheduler-plugin

bug 1874920: Revert "bug 1874919: UPSTREAM: 94423: debugger scheduler plugin"
@k8s-ci-robot k8s-ci-robot added area/test kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Nov 20, 2020
@tnozicka
Copy link
Contributor Author

/unassign soltysh sttts
(apologies I clicked on the wrong item in the selection menu)

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/windows Categorizes an issue or PR as relevant to SIG Windows. labels Nov 20, 2020
@tnozicka
Copy link
Contributor Author

/uncc soltysh sttts

@k8s-ci-robot
Copy link
Contributor

@tnozicka: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-kubernetes-integration 51999fe link /test pull-kubernetes-integration
pull-kubernetes-typecheck 51999fe link /test pull-kubernetes-typecheck
pull-kubernetes-e2e-kind 51999fe link /test pull-kubernetes-e2e-kind
pull-kubernetes-verify 51999fe link /test pull-kubernetes-verify
pull-kubernetes-dependencies 51999fe link /test pull-kubernetes-dependencies
pull-kubernetes-e2e-gce-100-performance 51999fe link /test pull-kubernetes-e2e-gce-100-performance
pull-kubernetes-e2e-gce-ubuntu-containerd 51999fe link /test pull-kubernetes-e2e-gce-ubuntu-containerd
pull-kubernetes-e2e-gce-alpha-features 51999fe link /test pull-kubernetes-e2e-gce-alpha-features
pull-kubernetes-e2e-gce-iscsi-serial 51999fe link /test pull-kubernetes-e2e-gce-iscsi-serial
pull-kubernetes-e2e-gce-csi-serial 51999fe link /test pull-kubernetes-e2e-gce-csi-serial
pull-kubernetes-e2e-azure-disk-windows 51999fe link /test pull-kubernetes-e2e-azure-disk-windows
pull-kubernetes-e2e-azure-file-windows 51999fe link /test pull-kubernetes-e2e-azure-file-windows
pull-kubernetes-conformance-image-test 51999fe link /test pull-kubernetes-conformance-image-test
pull-kubernetes-e2e-gce-storage-snapshot 51999fe link /test pull-kubernetes-e2e-gce-storage-snapshot
pull-kubernetes-e2e-gce-iscsi 51999fe link /test pull-kubernetes-e2e-gce-iscsi
pull-kubernetes-node-e2e 51999fe link /test pull-kubernetes-node-e2e
pull-kubernetes-conformance-kind-ipv6-parallel 51999fe link /test pull-kubernetes-conformance-kind-ipv6-parallel
pull-kubernetes-e2e-gce-storage-slow 51999fe link /test pull-kubernetes-e2e-gce-storage-slow

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.

@fedebongio
Copy link
Contributor

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/apiserver area/cloudprovider area/code-generation area/conformance Issues or PRs related to kubernetes conformance tests area/dependency Issues or PRs related to dependency changes area/e2e-test-framework Issues or PRs related to refactoring the kubernetes e2e test framework area/ipvs area/kubeadm area/kubectl area/kubelet area/provider/gcp Issues or PRs related to gcp provider area/release-eng Issues or PRs related to the Release Engineering subproject area/test do-not-merge/contains-merge-commits Indicates a PR which contains merge commits. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/apps Categorizes an issue or PR as relevant to SIG Apps. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/autoscaling Categorizes an issue or PR as relevant to SIG Autoscaling. sig/cli Categorizes an issue or PR as relevant to SIG CLI. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/contributor-experience Categorizes an issue or PR as relevant to SIG Contributor Experience. sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. sig/network Categorizes an issue or PR as relevant to SIG Network. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/release Categorizes an issue or PR as relevant to SIG Release. sig/scalability Categorizes an issue or PR as relevant to SIG Scalability. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/testing Categorizes an issue or PR as relevant to SIG Testing. sig/windows Categorizes an issue or PR as relevant to SIG Windows. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Projects

None yet

Development

Successfully merging this pull request may close these issues.