Strange message when setting preset

[jeffmaury]

General information

• OS: Linux
• Hypervisor: KVM
• Did you run crc setup before starting it (Yes/No)?No
• Running CRC on: VM

CRC version

CRC version: 2.25.0+97705a
OpenShift version: 4.13.6
Podman version: 4.4.4

CRC status

crc does not seem to be setup correctly, have you run 'crc setup'?

CRC config

- consent-telemetry                     : no
- preset                                : microshift

Host Operating System

NAME="Fedora Linux"
VERSION="38 (Workstation Edition)"
ID=fedora
VERSION_ID=38
VERSION_CODENAME=""
PLATFORM_ID="platform:f38"
PRETTY_NAME="Fedora Linux 38 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:38"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f38/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=38
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=38
SUPPORT_END=2024-05-14
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Steps to reproduce

1. crc config set present microshift

Expected

Changes to configuration property 'preset' are only applied when the CRC instance is created.
If you already have a running CRC instance with different preset, then for this configuration change to take effect, delete the CRC instance with 'crc delete', setup it with `crc setup` and start it with 'crc start'.

Actual

WARN Value for config setting 'memory' is invalid, resetting it to its default value 
Changes to configuration property 'preset' are only applied when the CRC instance is created.
If you already have a running CRC instance with different preset, then for this configuration change to take effect, delete the CRC instance with 'crc delete', setup it with `crc setup` and start it with 'crc start'.

Logs

Before gather the logs try following if that fix your issue

$ crc delete -f
$ crc cleanup
$ crc setup
$ crc start --log-level debug

Please consider posting the output of crc start --log-level debug on http://gist.github.com/ and post the link in the issue.

[anjannath]

WARN Value for config setting 'memory' is invalid, resetting it to its default value

this is expected, when swiching from a preset that had cpus, memory values configured lower then the default cpus and memory for the second preset.

e.g

PS C:\Users\anath\go\bin> .\crc.exe config get memory
Configuration property 'memory' is not set. Default value '2048' is used


PS C:\Users\anath\go\bin> .\crc.exe config set memory 2100
Changes to configuration property 'memory' are only applied when the CRC instance is started.
If you already have a running CRC instance, then for this configuration change to take effect, stop the CRC instance with 'crc stop' and restart it with 'crc start'.


PS C:\Users\anath\go\bin> .\crc.exe config view
- consent-telemetry                     : no
- memory                                : 2100
- preset                                : podman


PS C:\Users\anath\go\bin> .\crc.exe config set preset microshift
WARN Value for config setting 'memory' is invalid, resetting it to its default value
Changes to configuration property 'preset' are only applied when the CRC instance is created.
If you already have a running CRC instance with different preset, then for this configuration change to take effect, delete the CRC instance with 'crc delete', setup it with `crc setup` and start it with 'crc start'.

do you remember before switching to microshift what was the preset and what was the value for memory?

(initial PR adding this was https://github.com/crc-org/crc/pull/3636#issue-1699461233)

[jeffmaury]

That look strange to me because I had not set memory in config. So I'm setting preset and got a message about memory, looks weird

[praveenkumar]

I highly doubt that without a lower value of memory which preset need not present in the config then WARN Value for config setting 'memory' is invalid, resetting it to its default value now shown. May be you set something from the PD and then tried to switch with crc cli? If you hit again can you check before crc config view ?

[jeffmaury]

I highly doubt that without a lower value of memory which preset need not present in the config then WARN Value for config setting 'memory' is invalid, resetting it to its default value now shown. May be you set something from the PD and then tried to switch with crc cli? If you hit again can you check before crc config view ?

There is no Podman Desktop involved in this case and the content of the config is given. Please note that seems to be Linux only

[praveenkumar]

There is no Podman Desktop involved in this case

Got it.

and the content of the config is given. Please note that seems to be Linux only

Content of the config which is mention on the issue is I think after executing the crc config set present microshift which automatic remove the memory config which was there before. Are you able to reproduce it?

[jeffmaury]

There is no Podman Desktop involved in this case

Got it.

and the content of the config is given. Please note that seems to be Linux only

Content of the config which is mention on the issue is I think after executing the crc config set present microshift which automatic remove the memory config which was there before. Are you able to reproduce it?

Yes each time I run crc config set preset microshift I can see the warning message