Skip to content

rebase 1.17.0 rc.2#24286

Merged
openshift-merge-robot merged 26 commits intoopenshift:masterfrom
p0lyn0mial:polynomial-rebase-1.17.0-rc.2
Dec 20, 2019
Merged

rebase 1.17.0 rc.2#24286
openshift-merge-robot merged 26 commits intoopenshift:masterfrom
p0lyn0mial:polynomial-rebase-1.17.0-rc.2

Conversation

@p0lyn0mial
Copy link
Copy Markdown
Contributor

@p0lyn0mial p0lyn0mial commented Dec 11, 2019

TODO in this PR

TODO after

This PR disables the following tests which were disabled before as part of sig-cluster-lifecycle suite, see kubernetes/kubernetes@0b3d50b#diff-3b1910d08fb8fd8b32956b5e264f87cb

"[k8s.io] [sig-cloud-provider-gcp] Downgrade [Feature:Downgrade] cluster downgrade should maintain a functioning cluster [Feature:ClusterDowngrade] [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                                             
"[k8s.io] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not be able to proxy to cadvisor port 4194 using proxy subresource [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                                     
"[k8s.io] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not be able to proxy to the readonly kubelet port 10255 using proxy subresource [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                        
"[k8s.io] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not have port 10255 open on its all public IP addresses [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                                                
"[k8s.io] [sig-cloud-provider-gcp] Ports Security Check [Feature:KubeletSecurity] should not have port 4194 open on its all public IP addresses [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                                                 
"[k8s.io] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] cluster upgrade should maintain a functioning cluster [Feature:ClusterUpgrade] [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                                                     
"[k8s.io] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] master upgrade should maintain a functioning cluster [Feature:MasterUpgrade] [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                                                       
"[k8s.io] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] node upgrade should maintain a functioning cluster [Feature:NodeUpgrade] [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                                                           
"[k8s.io] [sig-cloud-provider-gcp] etcd Upgrade [Feature:EtcdUpgrade] etcd upgrade should maintain a functioning cluster [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                                                                        
"[k8s.io] [sig-cloud-provider-gcp] gpu Upgrade [Feature:GPUUpgrade] cluster downgrade should be able to run gpu pod after downgrade [Feature:GPUClusterDowngrade] [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                               
"[k8s.io] [sig-cloud-provider-gcp] gpu Upgrade [Feature:GPUUpgrade] cluster upgrade should be able to run gpu pod after upgrade [Feature:GPUClusterUpgrade] [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                                     
"[k8s.io] [sig-cloud-provider-gcp] gpu Upgrade [Feature:GPUUpgrade] master upgrade should NOT disrupt gpu pod [Feature:GPUMasterUpgrade] [Suite:openshift/conformance/parallel] [Suite:k8s]"                                                                                                                        
"[k8s.io] [sig-cloud-provider-gcp] kube-proxy migration [Feature:KubeProxyDaemonSetMigration] Downgrade kube-proxy from a DaemonSet to static pods should maintain a functioning cluster [Feature:KubeProxyDaemonSetDowngrade] [Suite:openshift/conformance/parallel] [Suite:k8s]"                                  
"[k8s.io] [sig-cloud-provider-gcp] kube-proxy migration [Feature:KubeProxyDaemonSetMigration] Upgrade kube-proxy from static pods to a DaemonSet should maintain a functioning cluster [Feature:KubeProxyDaemonSetUpgrade] [Suite:openshift/conformance/parallel] [Suite:k8s]"

@openshift-ci-robot openshift-ci-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Dec 11, 2019
@p0lyn0mial p0lyn0mial force-pushed the polynomial-rebase-1.17.0-rc.2 branch from 1425aef to 8838cb5 Compare December 11, 2019 19:03
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 11, 2019
@p0lyn0mial p0lyn0mial force-pushed the polynomial-rebase-1.17.0-rc.2 branch from ca455e8 to 89fefb8 Compare December 11, 2019 21:19
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 11, 2019
@p0lyn0mial p0lyn0mial force-pushed the polynomial-rebase-1.17.0-rc.2 branch from 89fefb8 to 32deff9 Compare December 12, 2019 08:56
@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

/test e2e-aws

@p0lyn0mial p0lyn0mial force-pushed the polynomial-rebase-1.17.0-rc.2 branch 4 times, most recently from c978880 to acd2914 Compare December 12, 2019 17:30
@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci-robot openshift-ci-robot added the vendor-update Touching vendor dir or related files label Dec 13, 2019
@p0lyn0mial p0lyn0mial force-pushed the polynomial-rebase-1.17.0-rc.2 branch 2 times, most recently from d1031f3 to 8e9beff Compare December 13, 2019 12:31
@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

/test e2e-gcp-builds

@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

/retest

@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

/test all

@p0lyn0mial p0lyn0mial force-pushed the polynomial-rebase-1.17.0-rc.2 branch from 8556bea to 98f6f7a Compare December 15, 2019 12:26
@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

/test e2e-cmd

@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

requires #24305

This was referenced Dec 16, 2019
@p0lyn0mial p0lyn0mial force-pushed the polynomial-rebase-1.17.0-rc.2 branch from 98f6f7a to d2b6dbd Compare December 16, 2019 17:16
@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

requires #24304

Comment thread glide.yaml Outdated
# etcd v3.3.17 carry until 4.4
- package: github.com/coreos/etcd
version: v3.3.17
version: v3.3.10
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this backleveling isn't correct. Get up with @hexfusion to find the right level, but at the very least don't backlevel it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is exactly what upstream uses https://github.com/kubernetes/kubernetes/blob/v1.17.0-rc.2/go.mod#L231

also github.com/coreos/etcd was replaced by go.etcd.io/etcd

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I remember some issues in that area I can try to delete it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hexfusion is away until 1/2 we need to make a decision.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we decided to revert it back to v3.3.17

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks 100% agree


upgCtx, err := getUpgradeContext(client, lifecycle.GetUpgradeTarget(), lifecycle.GetUpgradeImage())
framework.ExpectNoError(err, "determining what to upgrade to version=%s image=%s", lifecycle.GetUpgradeTarget(), lifecycle.GetUpgradeImage())
upgCtx, err := getUpgradeContext(client, gcp.GetUpgradeTarget(), gcp.GetUpgradeImage())
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm surprised this became cloud specific. You sure?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gvr("settings.k8s.io", "v1alpha1", "podpresets"),
gvr("storage.k8s.io", "v1alpha1", "volumeattachments"),
gvr("discovery.k8s.io", "v1alpha1", "endpointslices"),
gvr("extensions", "v1beta1", "deployments"),
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these look wrong. Are we enabling endpoints that need to be shut off? Can we function with them shut off

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that

// these alphas resources are not enabled in a real cluster but worked fine in the integration test

at runtime extensions/v1beta1 are disabled.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

without it, the test fails

fail [github.com/openshift/origin/test/extended/etcd/etcd_test_runner.go:72]: test failed:
etcd data does not match the types we saw:
in etcd data but not seen:
[
	apps/v1beta1, Resource=controllerrevisions 
	extensions/v1beta1, Resource=podsecuritypolicies 
	extensions/v1beta1, Resource=replicasets 
	extensions/v1beta1, Resource=deployments 
	apps/v1beta1, Resource=deployments 
	apps/v1beta2, Resource=replicasets 
	apps/v1beta2, Resource=statefulsets 
	apps/v1beta2, Resource=deployments 
	extensions/v1beta1, Resource=networkpolicies 
	apps/v1beta2, Resource=daemonsets 
	apps/v1beta2, Resource=controllerrevisions 
	apps/v1beta1, Resource=statefulsets 
	extensions/v1beta1, Resource=daemonsets]
seen but not in etcd data:
[]

for example https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/24286/pull-ci-openshift-origin-master-e2e-aws-serial/11496

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

/test e2e-azure-upgrade

@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

/test e2e-cmd

@p0lyn0mial
Copy link
Copy Markdown
Contributor Author

Did you drop a patch accidentally?

seems like I forgot to add one, I don't know how the other tests can run without it. @smarterclayton could you run e2e-azure-upgrade one more time?

@smarterclayton
Copy link
Copy Markdown
Contributor

/test unit

@smarterclayton
Copy link
Copy Markdown
Contributor

@smarterclayton
Copy link
Copy Markdown
Contributor

/test e2e-cmd

@smarterclayton
Copy link
Copy Markdown
Contributor

The OOMFailure on build is https://bugzilla.redhat.com/show_bug.cgi?id=1785326

@adambkaplan
Copy link
Copy Markdown
Contributor

BZ opened for builds OOMKilled tests failing: https://bugzilla.redhat.com/show_bug.cgi?id=1785326

There is an RHCOS fix which was supposed to have landed already - if this either a) hasn't landed, or b) did land, but didn't fix this issue, I am OK with skipping the test.

@adambkaplan
Copy link
Copy Markdown
Contributor

#24332 disables the build OOM test

@deads2k
Copy link
Copy Markdown
Contributor

deads2k commented Dec 19, 2019

TestUniformDistribution can be straight skipped

@deads2k
Copy link
Copy Markdown
Contributor

deads2k commented Dec 19, 2019

/retest

@deads2k deads2k mentioned this pull request Dec 19, 2019
@smarterclayton
Copy link
Copy Markdown
Contributor

conmon fix is in 44.81.201912191631.0, which is in 4.4 as of 3 hours ago.

@deads2k
Copy link
Copy Markdown
Contributor

deads2k commented Dec 19, 2019

/hold cancel
/lgtm
/override ci/prow/e2e-gcp-builds
for known oom problems

/override ci/prow/e2e-aws-disruptive
for known bastion issues

see if we instamerge

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Dec 19, 2019
@openshift-ci-robot
Copy link
Copy Markdown

@deads2k: Overrode contexts on behalf of deads2k: ci/prow/e2e-aws-disruptive, ci/prow/e2e-gcp-builds

Details

In response to this:

/hold cancel
/lgtm
/override ci/prow/e2e-gcp-builds
for known oom problems

/override ci/prow/e2e-aws-disruptive
for known bastion issues

see if we instamerge

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.

@openshift-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, mfojtik, p0lyn0mial, soltysh

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [deads2k,mfojtik,soltysh]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@deads2k
Copy link
Copy Markdown
Contributor

deads2k commented Dec 19, 2019

/override ci/prow/e2e-gcp-builds

@openshift-ci-robot
Copy link
Copy Markdown

@deads2k: Overrode contexts on behalf of deads2k: ci/prow/e2e-gcp-builds

Details

In response to this:

/override ci/prow/e2e-gcp-builds

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.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

4 similar comments
@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Dec 20, 2019

@p0lyn0mial: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws-disruptive 41dea56 link /test e2e-aws-disruptive

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.

@openshift-bot
Copy link
Copy Markdown
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 41dea56 into openshift:master Dec 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. vendor-update Touching vendor dir or related files

Projects

None yet

Development

Successfully merging this pull request may close these issues.