-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Extended.[k8s.io] Kubectl client [k8s.io] Kubectl expose should create services for rc [Conformance] #9444
Comments
The openshift log was truncated at 20MB and doesn't contain anything related to the failing test case. The Jenkins console has this as the last event related to the pod:
I'm guessing this is a gcr.io flake but without logs, I can't say for sure. Please reopen if this happens again, and maybe we'll have more useful logs. |
This is what I suspected - pulling the image is just taking too long.
Upstream has taken to pre-pulling all the images used in tests to avoid situations like this. |
Looks like that is installed via salt. We could modify our test scripts to do something similar. Also see e.g. https://github.com/kubernetes/kubernetes/blob/dd4dae4a57129c40d4496ca6ad37ee3a4fa045fa/test/e2e/e2e.go#L128 |
@derekwaynecarr do you think we should just try to run the upstream image puller manifest in origin's e2e test? |
👍 on pre-pulling e2e images |
Ok, we can't reuse the upstream e2e-image-puller pod as is, at least not on Fedora 24, because our /usr/bin/docker is dynamically linked, and trying to run it bind-mounted into a busybox container results in unresolved shared libraries. I modified the manifest to use fedora:24 and everything is pulling as it should be. We just need to decide how we want to approach this. I assume we don't have the e2e-image-puller.manifest file available by default, so maybe we'll need to download it, run sed to change the image, and then create it. It's also pulling the images serially, which might not be optimal from a timing perspective. It took about 6.5 minutes on my 50Mbps FIOS connection. |
It also looks like it's over 5GB of image data, according to |
We have a wip pr to pre pull On Wednesday, June 29, 2016, Ben Parees notifications@github.com wrote:
|
No need to keep linking 😄 |
@ncdc sorry for the spam, i forgot this one was actually understood/being fixed. :) |
is that wip PR linked to this issue anywhere? or it's still upstream? |
On Saturday, July 2, 2016, Ben Parees notifications@github.com wrote:
|
@ncdc thanks. i took the liberty of updating that PR to indicated it'll fix this issue. |
Test flake: kubectl expose test fails while waiting for redis container
Version
v1.3.0-alpha.1-380-g4965f56
Steps To Reproduce
Current Result
Extended test failure:
Expected Result
Test passes
Additional Information
Times out waiting for redis RC:
https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/2306/
The text was updated successfully, but these errors were encountered: