Closed anjannath closed 2 years ago
JSON deserializer issue.
I can not reproduce this with the current tray and a previous version of the backend. (avoiding config calls).
On start we use the /api/pull-secret
to determine if this is set. This is not a JSON response.
We specifically expect a 200 OK
with an empty result:
https://github.com/code-ready/tray-windows/blob/482f4dafec482add25cbdbd92567521426807745/Communication/DaemonCommander.cs#L85-L109
And this got changed here: https://github.com/code-ready/crc/commit/4c786d0865e5d6f1fa3a5492b49a024295422e2a#diff-bcb95a56a8b0d6310d991246364f360be183560450d8b59a318c317cbaf23888R62 to return 200 OK
with a message: pull secret exists
. This will fail the JSON deserialization, as the message is NOT empty anymore.
If the pull-secret file set, then clicking on Start from the tray throws an exception.
Exception details