It affects every other job run in my setup. I run template X it fails because of prior job (even though I am not doing "update on launch") then i run it again and it goes through fine.
Only testing it at the moment so not end of the world. I was thinking of just doing a stunnel wrapper maybe. I dont think this forum supports Tower however, so you would likely have to put a support ticket in with Red Hat to get more info/help. https://access.redhat.com/ On Thursday, March 16, 2017 at 5:07:36 AM UTC-4, Nicholas Chrysandreas wrote: > > My SCM (using mercurial) is indeed on a non-standard port (8000) but when > the I run an SCM update on the project it completes fine. > Also when running a template the SCM update job that spawns completes > successfully but the play job fails because it is checking the wrong job ID. > I'm wondering if this was caused when updating. Maybe a member of the team > tried to run a play while I was updating tower and something got messed up > in the Tower DB? > > On Thursday, 16 March 2017 04:25:33 UTC+2, cupcake wrote: >> >> does your SCM use a non-standard port? might relate to: >> https://github.com/ansible/ansible/issues/20653 >> >> I had a similar issue with SCM after the 3.0==>3.1 and my SCM uses port >> 2222 instead of 80 or 443 >> >> -- 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/38cb5554-f3ae-4ef3-9d9b-b5999d00d8a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
