The UI is always assuming that the serial console log feature is on for an individual VM regardless of the cluster wide default

More info with screenshots in the first comment.

4.15

100%

1. set the cluster wide default for the serial console log to off
2. try to create a VM from an instance type from the catalog
3. check the status of the serial console logs know in the VM configuration

The feature is off as for its cluster wide default.
the know on the UI assumes that it's on.
The console logs area in the diagnostic section is active even if the feature is off on the backend.

The UI considers the serial log feature to be on at VM level if and only if really on for the specific VM.

More info with screenshots in the first comment.