cs_tools fails after cluster upgraded to v10.10.0.cl-73

[bmofkn]

Our cluster was upgraded from 10.9 to 10.10 overnight. Since the upgrade, many cs_tools commands are failing. Is this related to Enable to enter PROD environment?

Most cs_tools commands that connect to our cluster have the same errors:
[DEBUG - 2025-07-02T05:38:50-0600] [cs_tools.api.client - client.__after_response__ 163] <<< HTTP 403 <- /api/rest/2.0/roles/search
{"error":{"message":{"debug":{"debug":"Roles feature is disabled"}}}}

The above has been in our logs for several itterations, so I suspect it's benign. However, the message that follows the above is new this morning:
[DEBUG - 2025-07-02T05:38:50-0600] [cs_tools.cli.commands.main - main.run 110] whoopsie, something went wrong!

... and all commands end with something similar to the following:
Library/Application Support/cs_tools/.cs_tools/lib/python3.13/site-packages/pydantic/main.py", line 253, in __init__ validated_self = self.__pydantic_validator__.validate_python(data, self_instance=self)

pydantic_core._pydantic_core.ValidationError: 1 validation error for SessionContext thoughtspot.version Value error, not enough values to unpack (expected at least 3, got 1) [type=value_error, input_value='tsswint', input_type=str]

For further information visit https://errors.pydantic.dev/2.11/v/value_error

Anyone have any suggestions on a workaround? Thanks!

[saurabhsingh2974]

Hi @bmofkn ,this will be fixed by this week

[bmofkn]

Thanks @saurabhsingh2974! We use cs_tools every morning to download the TML for all objects. In the interim, any known workarounds to get some of the scripts to execute while waiting for the official fix?

[bmofkn]

As of Monday, July 7, 2025, even though a new version of cs_tools was not released, this appears to be fixed. I re-ran several scriptability commands and they worked as expected 👍

[DevinMcPherson-TS]

The issue was a server side bug that was fixed over the weekend. Thank you for bringing this to our attention.