The org admin is able to create a job template using an execution environment from other organization

[yagomarques]

ISSUE TYPE

• Bug Report

SUMMARY

• associate an execution_environment in a job template in which the Execution Environment is no longer global and has been linked to an other organization than the organization related to the job template.

STEPS TO REPRODUCE

reproducing by API

1. create an organization A
2. create an organization B
3. create a global execution environment A
4. create a project A related to organization A
5. associate execution environment A with the organization B
6. create an user with the org admin role and associate with the organization A
7. create a job_template associating with project A and selecting execution_environment A.
8. check that Job Template was associated an organization A and the project A. But the Job Template is using an execution environment associated an organization B

EXPECTED RESULTS

• should to return an error, because the Execution Environment is no longer available to the organization

ACTUAL RESULTS

• the job template was successfully registered

ADDITIONAL INFORMATION

we try to reproduce that behave with different users(sys_admin, org_admin and the ee_org_admin).

• sys_admin - is able too to exec the same behave.
• ee_org_admin - don't have access to create a new job_template.

[jbradberry]

@yagomarques you should distinguish between the cases of 1) trying to create a JT with the EE already attached, and 2) creating a JT then after creation trying to attach the EE.

[masbahnana]

all tests are passing.

[masbahnana]

all tests are passing.

[tiagodread]

Looks like this was reopened accidentally with the comment