Closed elisabettai closed 1 year ago
@GitHK, could you please have a look (see error above)? on osparc.io. the sidecar of service 5af4ae77-52ff-4036-addb-61f985bdcce0
is still there and the study has unlocked itself, as predicted.
@elisabettai we are trying to figure out what is wrong with this issue. Currently we don't know so we have a PR to make storage provide some more meaningful logs https://github.com/ITISFoundation/osparc-simcore/pull/4867
@elisabettai while I did try to figure out what was happening, could not reproduce the same error. Imperonating the user I could the node in question started and I manage to save it
Probably related to Closing new style services behaves slightly differently
@elisabettai this should be fixed by this PR https://github.com/ITISFoundation/osparc-simcore/pull/4924
fix in staging will be delivered to production soon
Long Story Short I am trying to close a study on osparc.io where I'm the owner (study uuid:
a4628a32-3419-11ed-9a85-02420a0b01c2
). One of the node fails while uploading the outputs. The study is current locked because I'm closing it. I suspect that at some point it will unlock, but the service will fail to start.Additional context The node uuid of the failing node is
5af4ae77-52ff-4036-addb-61f985bdcce0
This are the errors in the dy-sidecar: