Investigate KOTS Preflight Check Warning - Kernel Version Showing "No matching files" Message

[jimmybrancaccio]

Bug description

I have just recently noticed the preflight check for kernel version seems to not be working correctly. I am not positive what system it is checking the kernel of or the files for, but here is the uname -a output of my master node and two worker nodes:

jimmy@kubemaster.mydomain.com:~$ uname -a
Linux kubemaster.mydomain.com 5.4.0-109-generic #123-Ubuntu SMP Fri Apr 8 09:10:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

jimmy@kubenode1.mydomain.com:~$ uname -a
Linux kubenode1.mydomain.com 5.4.0-109-generic #123-Ubuntu SMP Fri Apr 8 09:10:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

jimmy@kubenode2.mydomain.com:~$ uname -a
Linux kubenode2.mydomain.com 5.4.0-109-generic #123-Ubuntu SMP Fri Apr 8 09:10:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

They are above the pre-requisite of 5.4.0 however I am not sure what files its complaining about missing.

Steps to reproduce

1. Spin up a new instance of Gitpod using the KOTS installer. My instance is using gitpod/unstable if that makes any difference. During the initial install, I do not believe it reported the kernel version as being an issue, but I am not 100%. Ensure you're installing to a Kubernetes cluster where the kernel version is at least 5.4.0.
2. Await a new version to be released and for KOTS to "see" it.
3. Observe the kernel version preflight check showing as failed.

Workspace affected

No response

Expected behavior

I would expect this check to show more information about why it's not passing and what needs to be done in order for it to pass.

Example repository

No response

Anything else?

No response

[lucasvaltl]

from @mrsimonemms - there is likely nothing we can do on this. This is an issue with replicated and we should raise it with them. @lucasvaltl to raise with replicated.

[mrsimonemms]

This seems to be caught when the underlying collector fails. Because the preflight checks are (to the best of my knowledge) impossible to debug, I don't know what information we can give to make this better or help resolve the issue.

In my experience, this usually clears itself up by hitting "re-run". However, if this is a constant failure, it may be a specific problem that we've found - @jimmybrancaccio does this happen every time, or is it intermittent?

[jimmybrancaccio]

@mrsimonemms It looks like it's intermittent (which is no fun).

main.3397:

main.3398:

And then failed again in main.3400, didn't fail in main.3401 but did fail in main.3402. 😵‍💫

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.