Bump to kubernetes-v1.18.2#122
Bump to kubernetes-v1.18.2#122sttts merged 76 commits intoopenshift:origin-4.5-kubernetes-1.18.2from
Conversation
|
I'm assuming something trivial is wrong here given that rc.1 passed all of these tests and the changes between 1.18.0-rc.1 and 1.18.2 are minimial. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: marun The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
3 unit tests are failing, all in oom_watcher_linux_test.go: https://gist.github.com/marun/2e5662ab60eb34ca0de12c0f0a337f30 This despite carrying the rc.1 fix. |
|
I think that the following commits are missing. |
beb9586 to
a5f8904
Compare
Good catch, fixed. |
|
@marun: This pull request references Bugzilla bug 1826230, which is invalid:
Comment DetailsIn 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. |
|
@marun: No Bugzilla bug is referenced in the title of this pull request. DetailsIn 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. |
a5f8904 to
0b7be6e
Compare
|
@marun: This pull request references Bugzilla bug 1826230, which is invalid:
Comment DetailsIn 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. |
|
/bugzilla refresh |
|
@marun: This pull request references Bugzilla bug 1826230, which is invalid:
Comment DetailsIn 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. |
|
@marun: This pull request references Bugzilla bug 1826230, which is invalid:
Comment DetailsIn 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. |
|
The unit test failures ended up being due to |
|
@marun: No Bugzilla bug is referenced in the title of this pull request. DetailsIn 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. |
…o function Origin-commit: 0d7fb2d769d631054ec9ac0721aee623c96c1001
Origin-commit: cb0b340d0e68c9524fa7fd6277f571b6aa68bf86
The following packages have tests that exceed the default 120s timeout: k8s.io/kubernetes/pkg/kubelet/volumemanager/reconciler - The tests in this package collectively take longer than 120s. k8s.io/kubernetes/pkg/volume/csi - One of the unit tests has to wait 2 minutes for a timeout to validate its failure condition.
Origin-commit: c0ff1ad9899a1c9db21186e1a02eec35673fb357
Signed-off-by: Ted Yu <zyu@redhat.com> Origin-commit: 1d753cc478134dd84ad9cfdbd166659505da8b6f
… secret This patch brings back the downstream changes that were introduced to allow reading openstack cloud provider config from a secret. They are available in release-4.4, but were reverted in master with openshift/origin#24719 This change includes: - Ability to read metadata values for kubelet. Since the service does not have access to the secret to read the configuration, but it needs data to download (e.g. hostname or flavor), we are trying to get it from the metadata server. - Deprecation of kubeConfig parameter. Now we read the file that was provided with --kubeconfig option. Origin-commit: f95edc26155a29769b3c5b80c03755a01a87b5fc
…alization during Kubelet init
Origin-commit: 648d8f84875920df4a6509ec4c1677859117968a
Origin-commit: f85c00e875ec57e4ff7f45db4b917e94b889e760
Origin-commit: 7ca0dd0a3be3fd2c3bcf51deff76b7e76f95dcd0
The test races with the admission cache and is failing 5-7% of the time in e2e runs. Origin-commit: 3a6baaf17e355b30f37b89400e6e16510c5b32d7
The resource quota priority class preemption tests run in parallel,
and were observed to cause a preemption of another test. The tests
have no need to schedule to a node in order to verify resource quota.
```
Apr 19 16:59:06.749: INFO: At 2020-04-19 16:58:52 +0000 UTC - event for pod-init-b6fbd440-dbc2-454a-b31a-ce44266298d1: {default-scheduler } Scheduled: Successfully assigned e2e-init-container-7691/pod-init-b6fbd440-dbc2-454a-b31a-ce44266298d1 to ip-10-0-148-234.us-west-2.compute.internal
Apr 19 16:59:06.750: INFO: At 2020-04-19 16:58:54 +0000 UTC - event for pod-init-b6fbd440-dbc2-454a-b31a-ce44266298d1: {default-scheduler } Preempted: Preempted by e2e-resourcequota-priorityclass-8850/testpod-pclass9 on node ip-10-0-148-234.us-west-2.compute.internal
```
Origin-commit: a0780b385ca58a02e04ea8498df2fffa6cbc1275
They are useless and only pollute logs with errors. Origin-commit: dc7ec4d52f7a3dea0f1e04ae24856236c2765557
Origin-commit: 61a14d76dcc6578a409385730742d967fd4fe606
1f4f4f9 to
8c8387d
Compare
TODO:
https://docs.google.com/spreadsheets/d/10KYptJkDB1z8_RYCQVBYDjdTlRfyoXILMa0Fg8tnNlY/edit#gid=1388579334
/cc @sttts @p0lyn0mial