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

Post-rebase: conformance test hung getting logs off the node #12458

Closed
smarterclayton opened this issue Jan 12, 2017 · 13 comments
Closed

Post-rebase: conformance test hung getting logs off the node #12458

smarterclayton opened this issue Jan 12, 2017 · 13 comments
Assignees
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. priority/P2

Comments

@smarterclayton
Copy link
Contributor

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/10037/console

This is unusual - I wonder if we ran out of disk space. Opening to have something to track.

@smarterclayton
Copy link
Contributor Author

@ncdc

@ncdc
Copy link
Contributor

ncdc commented Jan 12, 2017 via email

@ncdc
Copy link
Contributor

ncdc commented Jan 12, 2017

@pweil- pweil- added kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1 labels Jan 13, 2017
@smarterclayton
Copy link
Contributor Author

I'm going to disable memcfg notifications until this is fixed.

@smarterclayton
Copy link
Contributor Author

Except we don't have the flag yet until we pick up 1.5.2

@smarterclayton
Copy link
Contributor Author

There is a disable patch, @soltysh on your PR you'll want to ignore that but you may need to default the flag to off in master.

@ncdc
Copy link
Contributor

ncdc commented Jan 15, 2017

Why'd you reopen?

@soltysh
Copy link
Contributor

soltysh commented Jan 15, 2017

@smarterclayton I've added test for ExperimentalKernelMemcgNotification being false in latest push, see here, is that sufficient?

@smarterclayton
Copy link
Contributor Author

Just reopened so we have a place to track turning it to a flag. I think we still want this in 3.5 if we can get the soft lock fixed - I'm hoping to get enough testing that we can turn it back on before thatz

@ncdc
Copy link
Contributor

ncdc commented Mar 27, 2017

AFAIK the lockup is still an issue. The kube 1.6 rebase adds the --experimental-kernel-memcg-notification flag.

@sttts sttts mentioned this issue Mar 27, 2017
2 tasks
@ncdc
Copy link
Contributor

ncdc commented Mar 28, 2017

Lowering priority for now to get this off the blocker list

@sttts sttts mentioned this issue Apr 6, 2017
13 tasks
@ncdc ncdc assigned sjenning and derekwaynecarr and unassigned ncdc May 22, 2017
@ncdc
Copy link
Contributor

ncdc commented May 22, 2017

@derekwaynecarr @sjenning this is the origin issue for the memcg kernel issue. Feel free to close if you just want to manage this in the bz linked above.

@sjenning
Copy link
Contributor

Yeah, this might be drawn out. We can just open a PR to enable it when the kernel BZ is fixed.

Or when we decide to disable THPs on origin 🤞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/test-flake Categorizes issue or PR as related to test flakes. priority/P2
Projects
None yet
Development

No branches or pull requests

6 participants