Conflicting info when creating configuration

[NilesDev]

I recently got this message when running "lm-cli configurations create ...":

╭─────────────────────────────────────────────────────────────────────────────────────────── REQUEST FAILED ────────────────────────────────────────────────────────────────────────────────────────────╮
│ Couldn't create configuration: Received an error response ({"message":"Configuration id 12 created."}).     

After the command, the configuration was indeed created and looked like any other configuration.

[NilesDev]

One possibility: I did not have permission to add any slurm license counters, that might have been the failure.

[julianaklulo]

Hi @NilesDev, thank you for reporting this.

I see that configuration 12 was created in the staging environment, so the command executed correctly.
I tried to reproduce the error and got the expected answer:

lm-cli configurations create --name test --product test --features '{"test": {"total": 123, "limit": 123}}' --license-servers test:123.123.123:123 --license-server-type test --grace-time 123 --client-id test

╭────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── Configuration creation succeeded. ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                                                                                                                                                                                                                                                                                                                                                               │
│   The configuration was created successfully.                                                                                                                                                                                                                                                                                                                                                                                 │
│                                                                                                                                                                                                                                                                                                                                                                                                                               │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

I'll investigate it further and let you know what I find.

[julianaklulo]

Do you remember when you ran the command?
The lm-cli in staging enviroment was updated to version 2.2.17 on Jan 25.
In this version, the response code for the create endpoint was changed from 200 (OK) to 201 (Created), which could trigger the error in the response code validation in lm-cli.

[NilesDev]

Sorry for late reply, but this was in production so probably the earlier version with the 201 response.