resetConfiguration API fails to reset Decimal type configurations at cluster scope

[RosiKyu]

problem

The resetConfiguration API returns success but fails to actually reset certain cluster-scoped configurations to their default values. Specifically observed with cpu.overprovisioning.factor (Decimal type).

versions

ACS 4.22 (probably exists on previous version as well)

The steps to reproduce the bug

1. Ensure a cluster exists with a modified cpu.overprovisioning.factor value (e.g., 2.0 instead of default 1.0)
2. Attempt to reset the configuration via CLI:

reset configuration name=cpu.overprovisioning.factor clusterid=<CLUSTER_ID>

3. Verify the value after reset:

list configurations clusterid=<CLUSTER_ID> name=cpu.overprovisioning.factor

Expected Behavior

• The resetConfiguration API should reset the value to the default (1.0)
• The returned response should show "value": "1.0"
• Subsequent list configurations should show "value": "1.0"

Actual Behavior

• The API returns a response indicating success with "value": "2" (truncated, should be 1.0)
• The actual value remains 2.0 (unchanged)
• The configuration is NOT reset to its default value

Evidence

(localcloud) 🐱 > list configurations clusterid=39ae3d32-8d5e-460e-a056-5004d5dbb908 name=cpu.overprovisioning.factor
{
  "configuration": [
    {
      "defaultvalue": "1.0",
      "name": "cpu.overprovisioning.factor",
      "scope": "cluster",
      "type": "Decimal",
      "value": "2.0"
    }
  ]
}

• attempt to reset config to default

(localcloud) 🐱 > reset configuration name=cpu.overprovisioning.factor clusterid=39ae3d32-8d5e-460e-a056-5004d5dbb908
{
  "configuration": {
    "defaultvalue": "1.0",
    "name": "cpu.overprovisioning.factor",
    "scope": "Cluster",
    "type": "Decimal",
    "value": "2"
  }
}

• list configuration

(localcloud) 🐱 > list configurations clusterid=39ae3d32-8d5e-460e-a056-5004d5dbb908 name=cpu.overprovisioning.factor
{
  "configuration": [
    {
      "defaultvalue": "1.0",
      "name": "cpu.overprovisioning.factor",
      "value": "2.0"   <-- NOT RESET
    }
  ]
}
Environment 2: 10.0.32.242 (without PR #11728)
(localcloud) 🐱 > list configurations clusterid=2347bf43-ab8e-4987-a62d-9588b622f647 name=cpu.overprovisioning.factor
{
  "configuration": [
    {
      "defaultvalue": "1.0",
      "name": "cpu.overprovisioning.factor",
      "scope": "cluster",
      "type": "Decimal",
      "value": "2.0" <-- NOT RESET
    }
  ]
}

• works on the Global settings level

What to do about it?

No response

[abh1sar]

@RosiKyu can you please check what was the config value at a zone or global scope when you did restore to default?

Is it possible that one of those values were 2 and the cluster scope config inherited the value(2) from its parent?

[DaanHoogland]

@abh1sar I discussed with @RosiKyu and this is indeed the case. I think we can close this issue, @RosiKyu ?