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

UPSTREAM: google/cadvisor: 1411: Ensure minimum kernel version for thin_ls #10227

Merged
merged 1 commit into from
Aug 5, 2016

Conversation

ncdc
Copy link
Contributor

@ncdc ncdc commented Aug 4, 2016

@ncdc
Copy link
Contributor Author

ncdc commented Aug 4, 2016

[test]

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to 5b055cb

@ncdc
Copy link
Contributor Author

ncdc commented Aug 4, 2016

@timothysc this should fix your thin pool woes

@eparis
Copy link
Member

eparis commented Aug 4, 2016

this will need a re-work once we know the z-stream kernel version... but LGTM for what we know now.

@ncdc ncdc mentioned this pull request Aug 4, 2016
@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7530/)

@ncdc
Copy link
Contributor Author

ncdc commented Aug 5, 2016

[merge]

@openshift-bot
Copy link
Contributor

openshift-bot commented Aug 5, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7549/) (Image: devenv-rhel7_4765)

@ncdc
Copy link
Contributor Author

ncdc commented Aug 5, 2016

@smarterclayton PetSet related?

Running test/cmd/admin.sh:351: executing 'oc create -f test/testdata/app-scenarios' expecting success...
FAILURE after 2.977s: test/cmd/admin.sh:351: executing 'oc create -f test/testdata/app-scenarios' expecting success: the command returned the wrong error code
Standard output from the command:
pod "lonely-pod" created
replicationcontroller "database-app-1" created
replicationcontroller "frontend-app-1" created
service "database-app" created
service "frontend-app" created
service "hello-openshift" created
pod "hello-openshift" created
service "empty-service" created
replicationcontroller "database-rc-1" created
replicationcontroller "frontend-rc-1" created
service "database-rc" created
buildconfig "ruby-sample-build" created
build "ruby-sample-build-1" created
replicationcontroller "database-2" created
replicationcontroller "database-1" created
deploymentconfig "database" created
replicationcontroller "frontend-2" created
replicationcontroller "frontend-1" created
deploymentconfig "frontend" created
service "database" created
service "database-external" created
service "frontend" created
route "frontend" created
route "other" created
buildconfig "sinatra-example-2" created
deploymentconfig "sinatra-example-2" created
imagestream "sinatra-example-2" created
service "sinatra-example-2" created
buildconfig "sinatra-example-1" created
imagestream "sinatra-example-1" created
build "sinatra-example-1-1" created
deploymentconfig "sinatra-example-1" created
service "sinatra-example-1" created
buildconfig "sinatra-app-example" created
imagestream "sinatra-app-example" created
build "sinatra-app-example-1" created
deploymentconfig "sinatra-app-example-a" created
deploymentconfig "sinatra-app-example-b" created
service "sinatra-app-example" created
petset "mysql" created
service "galera" created
pod "mysql-1" created
pod "mysql-2" created

Standard error from the command:
Error from server: The POST operation against Pod could not be completed at this time, please try again.

[merge]

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to 5b055cb

@stevekuznetsov
Copy link
Contributor

issue xref: #10008

@openshift-bot openshift-bot merged commit a593808 into openshift:master Aug 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants