Justin J. Janes

@bruth Did this get put onto a back burner on the Synadia side?

Testing note - stalled currently for December or January releases

@caroline-suse-rancher I'm currently looking at piggybacking off of kubetest2 which takes advantage of this output by default from it's built-in logging. So yes it's still underway, the initial plan was...

$ k3s -v ``` k3s version v1.26.0-rc2+k3s1 (fae88176) go version go1.19.4 ``` =========== k3s config =========== write-kubeconfig-mode: 644 debug: true flannel-backend: ipsec $ k3s server --help | grep flannel-backend ```...

Multi node provisioned using Rancher v2.7.2-rc5 $ rke2 -v ``` rke2 version v1.23.16+rke2r1 (0124f3b3a88575a77ae75778eb82ef87a7302fc7) go version go1.19.5 X:boringcrypto ``` Provisioning Log: ``` 2:58:02 pm | [INFO ] waiting for viable...

$ k3s -v Attention - I did find the error applying plan here (last months release) ``` k3s version v1.23.16+k3s1 (64b0feeb) go version go1.19.5 ``` Provisioning Log: ``` 1:48:24 pm...

I elected to do both k3s/rke2 to get a baseline across both products - k3s is the most recent set of provisioning logs and the latest RCs do not present...

i'm in this same boat right now with the latest cuda-10.2 (from apt install nvidia-jetpack) the files are all present in /usr/local/cuda-10.2/ but getting the same errors. I contemplated just...

Confirming good conformance checks from Sonobuoy against all recent RCs using MySQL 8.4 - (mysqld 8.4.0) MySQL Community Server Will be re-testing this soon to validate.

##Environment Details Reproduced using VERSION=v1.29.4+k3s1 Validated using COMMIT=f9130d537df6862a63120aa4ddb803f1317e0ef9 *Infrastructure* - [X] Cloud *Node(s) CPU architecture, OS, and version:* Linux 5.14.21-150500.53-default x86_64 GNU/Linux PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5" *Cluster Configuration:*...