I am seeing same - having just installed Tower for the first time and
trying to get up and running with the simplest of projects and playbooks.
Under 'Projects' I can start an SCM Update using the cloud/arrow icon and
it will complete (but ONLY if I select 'Delete on Update' but that seems to
be a side issue).
However, when I run the job related to my simple playbook, it fails with
Explanation: Previous Task Failed >> details; SCM Update failed for
{project} with ID 41.
But my jobs listed only go as far as 40 at present. 39 = SCM Update (the
one I ran from Projects tab). 40 = the failed playbook run.
On Wednesday, 15 March 2017 21:50:38 UTC+8, Nicholas Chrysandreas wrote:
>
> Hi,
>
> We are running ansible 2.2.1.0 and upgraded tower from 3.0.2 to 3.1.1
> After the tower upgrade, when we run a job template, the job fails because
> the with "SCM Update failed for Ops with ID 46720"
> The issue I realized is that the job is looking for a job ID that doesn't
> exist.
>
> Example, running the job template will spawn two jobs, 46718 is the ID of
> the play and 46719 the ID for the scm update, but the play job will fail
> with the above message looking for job ID 46720 (not 46719) which doesn't
> exits.
>
> Thanks for your help
>
> Regards
> Nik
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/e0e185e5-5b8e-48cc-857a-d0b067e62dc4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
