Incus version 1:6.7-debian12-202411151750 from zabbly
Issue description
When limits.cpu.nodes: balanced is set in a config, Incus can set the value of volatile.cpu.nodes to "0" when creating an instance. However, this triggers a validation error when later attempting to edit an instance's config. Might be related to 676ba92cfceff9c71b3dee70eb983a14540e890f; I don't remember seeing this prior to the Incus 6.7 release.
Steps to reproduce
Add limits.cpu.nodes: balanced to a profile:
$ incus profile show default
config:
limits.cpu.nodes: balanced
description: Default Incus profile
devices:
eth0:
name: eth0
network: incusbr0
type: nic
root:
path: /
pool: default
type: disk
name: default
Create and start a new VM:
$ incus create --vm images:ubuntu/24.04
Creating the instance
Instance name is: dynamic-yak
$ incus start dynamic-yak
Open the config in an editor, and close without making any changes:
$ incus config edit dynamic-yak
Config parsing error: Invalid config: Invalid cpuset value: 0
Press enter to open the editor again or ctrl+c to abort change
^C
Required information
Issue description
When
limits.cpu.nodes: balanced
is set in a config, Incus can set the value ofvolatile.cpu.nodes
to "0" when creating an instance. However, this triggers a validation error when later attempting to edit an instance's config. Might be related to 676ba92cfceff9c71b3dee70eb983a14540e890f; I don't remember seeing this prior to the Incus 6.7 release.Steps to reproduce
Add
limits.cpu.nodes: balanced
to a profile:Create and start a new VM:
View the config for this pristine VM:
Open the config in an editor, and close without making any changes: