k8s tests false positive #6

New issue

Open

opened 2023-11-10 18:27:11 +00:00 by earl-warren · 1 comment

earl-warren commented

2023-11-10 18:27:11 +00:00

Owner

[/test]   | [INFO]  systemd: Starting k3s                                                                                                                                                                  
[/test]   | Job for k3s.service failed because the control process exited with error code.                                                                                                                 
[/test]   | See "systemctl status k3s.service" and "journalctl -xeu k3s.service" for details.

The test script looks for Starting k3s and always succeeds. In reality kmsg fails to mount and k3s does not start.

``` [/test] | [INFO] systemd: Starting k3s [/test] | Job for k3s.service failed because the control process exited with error code. [/test] | See "systemctl status k3s.service" and "journalctl -xeu k3s.service" for details. ``` The test script looks for `Starting k3s ` and always succeeds. In reality kmsg fails to mount and k3s does not start.

Xinayder commented

2023-12-02 16:20:39 +00:00

Member

This can be replaced by checking if the node is ready instead of the systemd service, as described on the k3s website:

# Check for Ready node, takes ~30 seconds 
sudo k3s kubectl get node

This can be replaced by checking if the node is ready instead of the systemd service, as described on the k3s website: ``` # Check for Ready node, takes ~30 seconds sudo k3s kubectl get node ```

👍 2

No labels

No milestone

No project

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference: forgejo/lxc-helpers#6

No description provided.