machristie commented on pull request #69: URL: https://github.com/apache/airavata-django-portal/pull/69#issuecomment-1061214399
@dinukadesilva The problem is that not all queues have cpuPerNode configured. For a queue that doesn't have cpuPerNode configured (default value of 0) there is no way to calculated cpus or nodes based on the other. So if the lock button is there but cpuPerNode isn't configured, users may expect that the cpus or nodes will be automatically calculated, however, that won't happen. Does that help explain the situation? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
