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

kic test failure: verify_cache_inside_node : different output of crictil and docker images #6445

Closed
medyagh opened this issue Jan 31, 2020 · 0 comments · Fixed by #6487
Closed
Labels
co/docker-driver Issues related to kubernetes in container kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test.

Comments

@medyagh
Copy link
Member

medyagh commented Jan 31, 2020

thanks to this integration test I found out the cache add command doesnt work as expected on "docker driver" with docker run time.

=== RUN   TestFunctional/serial/CacheCmd/cache/verify_cache_inside_node
--- FAIL: TestFunctional/serial/CacheCmd/cache/verify_cache_inside_node (0.27s)
functional_test.go:365: (dbg) Run:  out/minikube-linux-amd64 -p functional-20200130T194619.520931734-14593 ssh sudo crictl images
functional_test.go:370: expected '1.28.4-glibc' to be in the output: -- stdout --
IMAGE                                TAG                 IMAGE ID            SIZE
k8s.gcr.io/coredns                   1.6.2               bf261d1579144       44.2MB
k8s.gcr.io/etcd                      3.3.15-0            b2756210eeabf       248MB
k8s.gcr.io/kube-apiserver            v1.16.2             9c26fe80bbb38       185MB
k8s.gcr.io/kube-controller-manager   v1.16.2             2f6b22cf92d72       128MB
k8s.gcr.io/kube-proxy                v1.16.2             41d59a0b79325       103MB
k8s.gcr.io/kube-scheduler            v1.16.2             fd6c6fdef2251       105MB
k8s.gcr.io/pause                     3.1                 da86e6ba6ca19       746kB
-- /stdout --

I did manual checking:

./out/minikube cache add busybox

in the integration tests we check the output of crictl images inside minikube and expect busybox to be there.

$ ./out/minikube ssh sudo crictl images
IMAGE                                TAG                 IMAGE ID            SIZE
k8s.gcr.io/coredns                   1.6.2               bf261d1579144       44.2MB
k8s.gcr.io/etcd                      3.3.15-0            b2756210eeabf       248MB
k8s.gcr.io/kube-apiserver            v1.16.2             9c26fe80bbb38       185MB
k8s.gcr.io/kube-controller-manager   v1.16.2             2f6b22cf92d72       128MB
k8s.gcr.io/kube-proxy                v1.16.2             41d59a0b79325       103MB
k8s.gcr.io/kube-scheduler            v1.16.2             fd6c6fdef2251       105MB
k8s.gcr.io/pause                     3.1                 da86e6ba6ca19       746kB

the intertesting is the output of "docker images " has what we need !

$ ./out/minikube ssh sudo docker images
REPOSITORY                                TAG                 IMAGE ID            CREATED             SIZE
k8s.gcr.io/kube-proxy                     v1.17.2             cba2a99699bd        12 days ago         116MB
k8s.gcr.io/kube-controller-manager        v1.17.2             da5fd66c4068        12 days ago         161MB
k8s.gcr.io/kube-apiserver                 v1.17.2             41ef50a5f06a        12 days ago         171MB
k8s.gcr.io/kube-scheduler                 v1.17.2             f52d4c527ef2        12 days ago         94.4MB
busybox                                   latest              6d5fcfe5ff17        5 weeks ago         1.22MB
kubernetesui/dashboard                    v2.0.0-beta8        eb51a3597525        7 weeks ago         90.8MB
k8s.gcr.io/coredns                        1.6.5               70f311871ae1        2 months ago        41.6MB
kindest/kindnetd                          0.5.3               aa67fec7d7ef        3 months ago        78.5MB
k8s.gcr.io/etcd                           3.4.3-0             303ce5db0e90        3 months ago        288MB
kubernetesui/metrics-scraper              v1.0.2              3b08661dc379        3 months ago        40.1MB
alpine                                    3.4                 b7c5ffe56db7        12 months ago       4.82MB
busybox                                   1.28.4-glibc        56cc512116c8        20 months ago       4.4MB
k8s.gcr.io/pause                          3.1                 da86e6ba6ca1        2 years ago         742kB
gcr.io/k8s-minikube/storage-provisioner   v1.8.1              4689081edb10        2 years ago         80.8MB
k8s.gcr.io/pause                          latest              350b164e7ae1        5 years ago         240kB
medya@~/workspace/minikube (kic_engine) $ 

interesting is the same test works fine on VM.

@medyagh medyagh added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Jan 31, 2020
@medyagh medyagh changed the title kic test failure: verify_cache_inside_node kic test failure: verify_cache_inside_node : different output of crictil and docker images Jan 31, 2020
@medyagh medyagh added the co/docker-driver Issues related to kubernetes in container label Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/docker-driver Issues related to kubernetes in container kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant