locked
NodeGroup not changed if other JobTemplate choosen RRS feed

  • Question

  • The following actions show an unexpected and unwanted behaviour, at least in my opinion:

    1. Assign a job-Template (Template0) which requires a NodeGroup. Lets say TestGroup0.
    2. Assign another Template (Template1) which requires another NodeGroup. Lets say TestGroup1.
    3. Create a job with Template0 and save it to an xml-file.
    4. Create a job from this xml-file and change the job template to Template1.

    Bug symptoms:
    You can't submit the job because of error:
    "Job template validation failed: The value of property NodeGroups
    is out of range. Update the job an try again."

    Bug symptoms continuing:
    You have a look at Resource Selection where you will find NodeGroup0
    in the selected node groups window.

    Bug:
    The userinterface is actualised, but the data in the job-files is not.

    Work around in this case:
    5.: Add another nodegroup to the selected nodes,
    and remove it again in the job properties.

    6.: The job can be submitted.


    In my opinion this is a bug.  I want to have different queues implemented by job templates. So e.g. a user tests the job properties with a quick run on my short runtime queue and the resubmits the same job on the long running queue with the intended setup.

    Regards,

    Johannes
    JH
    Monday, November 23, 2009 6:41 AM

Answers

  • Hi Johannes,

    Thanks for reporting this issue to us. We reproduced the problem and filed a bug. Thanks for the help.

    Liwei
    Tuesday, December 8, 2009 3:30 AM