PROGRESS is not properly displayed in 1.29.1 cluster

[axiang99]

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:

• Sonobuoy version: 0.56.17; 0.57.1
• Kubernetes version: (use kubectl version): 1.29.1
• Kubernetes installer & version: kubeadm 1.29.1
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release): Ubuntu in CP and SUSE in node
• Sonobuoy tarball (which contains * below)

[dd-georgiev]

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]

Good day. Is anyone looking into this?

[ystkfujii]

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

[xunleii]

I also faced the same issue, reproductible with a simple kind cluster

kind create cluster
sonobuoy run
sonobuoy status # nothing changes, although we can see the creation of pods/namespaces in the cluster

Environment:

• Sonobuoy version: Sonobuoy Version: v0.57.2
• Kubernetes version:
  • Client Version: v1.30.2
  • Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
  • Server Version: v1.30.0
• Kind version: kind v0.23.0 go1.21.10 linux/amd64