-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Updating components to use v1beta3 #6377
Conversation
@bgrant0607 Verified that unit and integration tests pass. |
@@ -558,6 +558,7 @@ func (r *Request) DoRaw() ([]byte, error) { | |||
|
|||
var err error | |||
r.req, err = http.NewRequest(r.verb, r.finalURL(), r.body) | |||
glog.Errorf("REQUEST TO URL: %s", r.finalURL()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this for debugging?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please revert this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverted
What does this affect? Does it change the storage version? |
Yes it affects storage version as well: https://github.com/GoogleCloudPlatform/kubernetes/blob/96a0a0d6189cf89f13f700bb5fa6c8f47aa109e5/pkg/master/master.go#L179 |
@@ -15,6 +15,6 @@ | |||
# limitations under the License. | |||
|
|||
# Provided for backwards compatibility | |||
go run "$(dirname $0)/e2e.go" -v -build -up -test -down | |||
go run "$(dirname $0)/e2e.go" -v -up -test -down |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this change?
Regenerate or revert the kubectl docs. |
9937633
to
dc33f3c
Compare
I think I have fixed all e2e tests now. All but 3 tests are passing. The ones failing seem to be flaky on head as well:
|
Cleaned up the PR and reverted the kubectl docs. Please have another look. |
@nikhiljindal: The monitoring test has not been flaky for the last few days. I would suggest looking into why its failing. |
@@ -165,7 +165,7 @@ function verify-cluster { | |||
local count="0" | |||
until [[ "$count" == "1" ]]; do | |||
local minions | |||
minions=$("${KUBE_ROOT}/cluster/kubectl.sh" get minions -o template -t '{{range.items}}{{.id}}:{{end}}') | |||
minions=$("${KUBE_ROOT}/cluster/kubectl.sh" get minions -o template -t '{{range.items}}{{.id}}:{{end}}' --api-version=v1beta1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why you didn't change this similarly to validate-cluster.sh? The inability to test the change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I decided to change them in a separate PR.
We will have to change these for deleting v1beta1
@vishh The monitoring test failed in the last build on jenkins with the same error: http://kubekins.dls.corp.google.com/job/kubernetes-e2e-gce/lastSuccessfulBuild/ |
LGTM. |
Updating components to use v1beta3
For #5475