Skip to content
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

v1.9.0-beta.2 #39

Closed
enisoc opened this issue Nov 30, 2017 · 7 comments
Closed

v1.9.0-beta.2 #39

enisoc opened this issue Nov 30, 2017 · 7 comments
Assignees
Labels
sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@enisoc
Copy link
Member

enisoc commented Nov 30, 2017

According to the timeline, we should cut v1.9.0-beta.2 on Wed, Dec 6.

However, we might consider cutting on Mon, Dec 4, if the exception requests granted until Dec 1 have merged.

@spiffxp
Copy link
Member

spiffxp commented Dec 6, 2017

@enisoc asked for a status check today at contributor summit

  • good news: all sig-release-master-blocking tests are passing!
  • bad news: sig-release-1.9-blocking#verify is failing, and all sig-release-master-upgrade tests are failing

I'm getting a little worried now. We're moving in the wrong direction with upgrade tests. I am doubtful we will resolve all of these failures in the week we have left before code freeze, let alone any more that crop up.

@enisoc
Copy link
Member Author

enisoc commented Dec 6, 2017

release-1.9 verify is still only broken due to kubernetes/release#470. We could fix it one of two ways: revert the branch to stubs, or disable the check for stubs on the branch. I'm still looking for guidance on which is right.

The consistently failing test cases within the upgrade jobs seem to be:

  • dashboard test for which we just merged a PR into the 1.8 branch that we think might help.
  • network partition test that we already agreed is non-blocking and should be disabled if it can't be fixed.

@enisoc
Copy link
Member Author

enisoc commented Dec 7, 2017

Verify seems to be passing after kubernetes/kubernetes#56910.

https://k8s-testgrid.appspot.com/sig-release-1.9-blocking#verify-1.9

The network partition tests had already been disabled on master, but we are now cherrypicking that to the 1.8 branch (kubernetes/kubernetes#56900).

The dashboard test seems to be getting better since kubernetes/kubernetes#56793 merged, but on some jobs it hasn't run again yet.

https://k8s-testgrid.appspot.com/sig-release-master-upgrade#gce-1.8-master-upgrade-cluster-parallel
https://k8s-testgrid.appspot.com/sig-release-master-upgrade#gce-1.8-master-upgrade-master

@enisoc
Copy link
Member Author

enisoc commented Dec 7, 2017

Verify is green.

The CP to disable the network partition tests on the 1.8 branch is on hold due to the 1.8.5 cut planned today.

The dashboard test is passing on the upgrade job now, but a bunch of others started failing:

https://k8s-testgrid.appspot.com/sig-release-master-upgrade#gce-1.8-master-upgrade-master

@enisoc
Copy link
Member Author

enisoc commented Dec 7, 2017

The official release-blocking list is all green for HEAD of release-1.9:

  Job #                                   Run #   Build # Time/Status
= ======================================= =====   ======= ===========
* build-1.9                               #12     #114    [19:18 12/06]
* (--buildversion=v1.9.0-beta.1.114+3ac6d1f5c03bbc)
- verify-release-1.9                      #667    #114    PASSED
- test-go-release-1.9                     #3284   #114    PASSED
- bazel-build-1-9                         #211    #114    PASSED
- bazel-test-1-9                          #228    #114    PASSED
- periodic-kubernetes-bazel-build-1-9     #166    #114    PASSED
- periodic-kubernetes-bazel-test-1-9      #162    #114    PASSED
- e2e-kubeadm-gce-1-8-on-1-9              #212    #114    PASSED
- periodic-kubernetes-e2e-kubeadm-gce-1-9 #173    #114    PASSED
- e2e-gce-cos-k8sbeta-default             #477    #114    PASSED
- e2e-gce-cos-k8sbeta-reboot              #496    #114    PASSED
- e2e-gce-cos-k8sbeta-serial              #103    #114    PASSED
- e2e-gce-cos-k8sbeta-slow                #481    #114    PASSED
- e2e-gce-cos-k8sbeta-ingress             #488    #114    PASSED
- e2e-gce-cos-k8sbeta-alphafeatures       #478    #114    PASSED
- e2e-gke-cos-k8sbeta-default             #488    #114    PASSED
- e2e-gke-cos-k8sbeta-reboot              #441    #114    PASSED
- e2e-gke-cos-k8sbeta-serial              #105    #114    PASSED
- e2e-gke-cos-k8sbeta-slow                #491    #114    PASSED
- e2e-gke-cos-k8sbeta-ingress             #511    #114    PASSED
- e2e-gce-gpu-beta                        #201    #114    PASSED
- e2e-gce-device-plugin-gpu-beta          #205    #114    PASSED
- e2e-gke-device-plugin-gpu-beta          #203    #114    PASSED
- e2e-gke-device-plugin-gpu-p100-beta     #34     #114    PASSED
- e2e-kops-aws-beta                       #383    #114    PASSED
- node-kubelet-beta                       #369    #114    PASSED
- e2e-gci-gce-scalability-beta            #70     #114    PASSED

I suggest we cut beta.2 to get more mileage on the approved exceptions that have now merged. The upgrade/downgrade problems are unlikely to be worse than they were for beta.1. We just need to keep investigating.

cc @dashpole @spiffxp

@spiffxp
Copy link
Member

spiffxp commented Dec 8, 2017

@enisoc agreed

@dashpole
Copy link

dashpole commented Dec 8, 2017

beta.2 was cut yesterday

@dashpole dashpole closed this as completed Dec 8, 2017
@justaugustus justaugustus added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Dec 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

4 participants