You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ ~/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)
The text was updated successfully, but these errors were encountered:
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
What steps did you take and what happened:
Steps:
Conformance test has passed 40 mins. Many cases have been executed but the output of
~/sonobuoy status
sticks inPassed: 0, Failed: 0
.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:
kubectl version
): 1.29.1/etc/os-release
): Ubuntu in CP and SUSE in nodeThe text was updated successfully, but these errors were encountered: