#251 Stale TSS id

closed-postponed
3
2009-10-07
2009-09-03
No

Assume that I crated an atomic job and sent it to a TSS. Now I destroy the TSS, create the new one (by double clicking TSF) and finally send the opened job again. There is an error that TSS resource can't be found, seems that URC tries to submit the job to the old TSS.

Discussion

  • Bastian Demuth

    Bastian Demuth - 2009-09-04

    This is very hard to fix. If you do this, you actually select a TSS to submit the job to. Then you destroy it and expect the client to automatically change the choice that you have made. I don't think that automatically changing the user's choices helps in obtaining a transparent system. Remember that different target systems could potentially (int the future) have different properties. Furthermore, the problem can be easily circumvented by selecting the TSF for job creation, not the TSS. One solution one could think about is disallowing job creation on the TSS (as well as selection of a TSS in the resources panel of the job), but this would take away some control from the user. Maybe we should disallow this for the beginner mode?

     
  • Bastian Demuth

    Bastian Demuth - 2009-09-04
    • status: open --> pending-postponed
     
  • Krzysztof Benedyczak

    • status: pending-postponed --> open-postponed
     
  • Krzysztof Benedyczak

    +1 for hiding TSS (and leaving only TSF) in begginer mode.

    Regarding the general issue, after a consideration, I can agree. However it clearly shows that we need a better (more user friendly) error handling. At least some most common errors should be recognized by the client, and presented in more descriptive form then "Can't submit a job". Examples include bad_cert from server, bad cert from client, unknown resource and more. The hints what to do to recover should be provided too.

    If this is acceptable, I can move it as an FR.

     
  • Bernd Schuller

    Bernd Schuller - 2009-10-07

    I think better error handling / reporting is a general "wish" or feature request. Therefore I close this bug. Maybe a feature request regarding error reporting on the URC can be created.

    Best regards,
    Bernd.

     
  • Bernd Schuller

    Bernd Schuller - 2009-10-07
    • status: open-postponed --> closed-postponed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks