The resource foo is not there in Resource_List.*, and any jobs that are submitted to the reservation later will not have the resource foo.
I believe we should go ahead and document this behaviour.
@prakashcv13
Thanks for testing this. Did the resulting reservation queue have a resources_max.foo? If it doesn’t, I’m somewhat surprised. If I were to submit pbs_rsub -lfoo=5, the resulting reservation queue should have resources_max.foo = 5. We are creating a reservation based on the job resources. At the time we query the resources, the job has Resource_List.foo. It isn’t until after we create the reservation and move the job that it loses it. If a queue has a resources_max, a job should pick it up as a default.