search

vmware-tanzu / sonobuoy

Sonobuoy is a diagnostic tool that makes it easier to understand the state of a Kubernetes cluster by running a set of Kubernetes conformance tests and other plugins in an accessible and non-destructive manner.
https://sonobuoy.io
Apache License 2.0
2.89k stars 344 forks source link

PROGRESS is not properly displayed in 1.29.1 cluster #1966

Open axiang99 opened 5 months ago

axiang99 commented 5 months ago

What steps did you take and what happened:

Steps:

$ ~/sonobuoy version
Sonobuoy Version: v0.57.1

~/sonobuoy  run  --e2e-repo-config <omitted>
~/sonobuoy  status

Conformance test has passed 40 mins. Many cases have been executed but the output of ~/sonobuoy status sticks in Passed: 0, Failed: 0. 

         PLUGIN     STATUS   RESULT   COUNT                                PROGRESS
            e2e    running                1   Passed:  0, Failed:  0, Remaining:386
   systemd-logs   complete                4

Sonobuoy is still running. Runs can take 60 minutes or more depending on cluster and plugin configuration.

Finally when the test complets, the status is as below:
 $  ~/sonobuoy   status
         PLUGIN     STATUS   RESULT   COUNT                                PROGRESS
            e2e   complete   passed       1   Passed:  0, Failed:  0, Remaining:386
   systemd-logs   complete   passed       4

What did you expect to happen: Status report show the actual progress.

Anything else you would like to add: Same Sonobuoy and same command lines (steps) works well in 1.28 and 1.27 clusters.

Have searched the open issues and not found similar one. I am not sure it is a Sonobuoy bug, or only happens in my cluster.

Environment:

dd-georgiev commented 5 months ago

I'm observing similar issue.

For me its not reporting progress at all, the output stays like:

./sonobuoy status
         PLUGIN    STATUS   RESULT   COUNT   PROGRESS
            e2e   running                1           
   systemd-logs   running                6           

Sonobuoy is still running. Runs can take 60 minutes or more depending on cluster and plugin configuration.

and I have the following in the e2e pod logs:

Will run 386 of 7407 specs

Also I can see tests are executed (namespaces, pods etc.. are created and deleted)

Environment: Sonobuoy version: v0.57.1 Kubernetes version: 1.29.3 Kubernetes installer & version: Cluster API 1.7.0; kubeadm version v1.29.3 Hardware configuration: Openstack OS: Alpine Linux v3.19

axiang99 commented 4 months ago

Good day. Is anyone looking into this?

ystkfujii commented 2 months ago

I faced the same issue. And, It seems to be working well in v1.28.

Environment: Sonobuoy version: v0.57.1 Kubernetes version: v1.29.5 Kubernetes installer & version: Kubespray v2.25.0; kubeadm version v1.29.5 OS: Ubuntu Server 22.04 LTS