[test failure] verify.openapi-spec

[krzyzacy]

@calebamiles looks like you've merged c007efc into master branch? That seems have broken http://k8s-testgrid.appspot.com/google-unit#verify-master and http://k8s-testgrid.appspot.com/presubmits-kubernetes-blocking#pull-kubernetes-verify

can you take a look?

/priority failing-test
/assign @calebamiles

[krzyzacy]

/sig release
cc @jiayingz

[cblecker]

This looks to have been resolved, but root cause unknown:
failed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-verify-master/18553
passed: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-verify-master/18554
same repo commit, different infra commit

[krzyzacy]

I'll leave @calebamiles to close this? I'm not sure the root cause yet, but if that manual merged commit is related, we should probably avoid it in the future.

[calebamiles]

@krzyzacy, I believe that commit was made "automagically" by anago while I was attempting to cut the 1.10 branch. @david-mcmahon noticed other problems and has magically cleaned up after the tool. Will follow up with him and you tomorrow.

[david-mcmahon]

Root cause was two tags landing on the same commit due to this recent change. Solution was to temporarily remove the -beta tag from that commit so it doesn't interfere with the -alpha tag. master branch is now fine. Still need to tag the branch, but the question is, how given we don't make a change to the branch at branch time. When it gets worked out will update this issue. cc @ixdy @enisoc

[jberkus]

adding priority, move to critical if it is

/priority important-soon

[jberkus]

adding kind as well, sorry I missed that.

/kind bug

[jberkus]

now critical, since we're in Code Freeze.

/priority critical-urgent
/remove-priority important-soon

[krzyzacy]

the test is fixed, we can move discussion to kubernetes/sig-release#85