I’m migrating our internal AWX from v2.0.1 to v5.0.0 following the recommended data migration procedure (tower-cli receive/send).
So far I was able to import inventories, organization, users and projects.
But I’m stuck at importing job_templates. The 5.0.0 server returns this error: “Option credential is not a valid option for job_template <job_template_name>”
Effectively, if I try to replicate a simple job_template in 5.0.0 and export it using tower-cli, I see no “credential” field.
I guess there was some change in the way a machine credential is linked to a job_template. But I can’t see where that information is stored.
Any help with locating the relation between machine credential and job_templates in the latest version of AWX?
I every job_template definition in the json file generated with tower-cli receive, deleting the “credentials” key.
After importing the JSON with tower-cli send into the new AWX instance I had all job_templates created with the SSH credential field empty (cloud credentials were imported correctly).
Now, I tried to update every job template with the corresponding SSH credential, but:
using tower-cli job_template associate_credential the server says:
Response: {“error”:“Extra credentials must be network or cloud.”}
using tower-cli job_template modify --credential <credential_name> <job_template_id> results in the resource being changed according to the CLI and the API logs, but the SSH credential is not associated to the job template.
In the end, I had to manually associate the SSH credential for every job_template in the web UI.
I understand this is due to some change in the way credentials are associated to job_templates, but it bothers me how the API just accepts the PATCH operation with no errors.
My tower-cli version:
Tower CLI 3.3.4
API v2
GET http:///api/v2/config/
Params: {}