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
We observed that after upgrading a node to flatcar 3850.1.0 we're hitting this issue. The value that vmware-tools is pulling somehow from the node is like this:
Linux 6.6.16-flatcar Flatcar Container Linux by Kinvolk 3850.1.0 (Oklo) Flatcar Container Linux by Kinvolk 3850.1.0 2024-02-12-1854
which exceeds 128 characters. Previous releases did not include the date stamp at the end.
I understand this is not so much an issue of Flatcar but lies with VMware, however it might affect other Flatcar users.
The text was updated successfully, but these errors were encountered:
Hi, is this something that can be addressed/fixed to the old behaviour before the next release? At this point I'm not sure where this value is pulled from but this has recently changed in the flatcar code I suspect.
There was no change in Flatcar to explain it, so we don't know what to do about it. The best guess is that an update to open-vm-tools changed how this field is synthesized.
Description
We observed that after upgrading a node to flatcar 3850.1.0 we're hitting this issue. The value that vmware-tools is pulling somehow from the node is like this:
Linux 6.6.16-flatcar Flatcar Container Linux by Kinvolk 3850.1.0 (Oklo) Flatcar Container Linux by Kinvolk 3850.1.0 2024-02-12-1854
which exceeds 128 characters. Previous releases did not include the date stamp at the end.
I understand this is not so much an issue of Flatcar but lies with VMware, however it might affect other Flatcar users.
The text was updated successfully, but these errors were encountered: