Job was not working after migration postgres data from 17.1.0 to 19.0.0

[Niko Wang]

 Hello AWX,

I was trying to migrate the postgres dump file from 17.1.0 to 19.0.0, restore was successful but the sync and scheduled jobs like project and template are not working, it's always running without any output.

Is this caused by EE integration so any key/value was changed in DB?

Any way we can migrate the data from old version?

Thanks.

[Niko Wang]

It's from docker compose to k8s.

[Mathias Homann]

Am Donnerstag, 27. Mai 2021, 09:18:41 CEST schrieb Niko Wang:
> It's from docker compose to k8s.
>
> On Thursday, May 27, 2021 at 2:54:56 PM UTC+8 Niko Wang wrote:
> > Hello AWX,
> >
> > I was trying to migrate the postgres dump file from 17.1.0 to 19.0.0,
> > restore was successful but the sync and scheduled jobs like project and
> > template are not working, it's always running without any output.

I'm having a very similar problem here. I deployed AWX 19.1 with an import of
my database from my working AWx 17.1, and for about a week that new AWX 19 was
usable - and then out of the blue project syncs stopped working. Whenever AWX
is supposed to pull from git the job sits there in "running" but nothing is
actually happening - and there's nothign suspicious in the logs of the awx-
task or awx-ee pods either.

So far noone has come up with any usable idea on how to fix this - even
deleting the AWXS object in kubernetes and deploying again didn't fix it.

i guess I'll eventually have to wipe the whole namespace off my kubernetes and
deploy completely from scratch, and then see how long that instance is usable.

cheers
MH

--
Mathias Homann
Mathias...@openSUSE.org
OBS: lemmy04
Jabber (XMPP): le...@tuxonline.tech
IRC: [Lemmy] on freenode and ircnet (bouncer active)
telegram: https://telegram.me/lemmy98
keybase: https://keybase.io/lemmy
gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102

[Niko Wang]

But I don't think it will be working even deleting the name space if still import the database from 17, I strongly suspect the issue is the items changed in database with new version, because I can run a job with success which is created in new version.

[Justin Verweel | deployable.nl]

Maybe related: https://github.com/ansible/awx/issues/10489

Did your AWX setup have 10k+ jobs?

Our setup suddenly stopped working too, and I found out that it was after running 9999 jobs, number 10k and up have this "running but nothing is happening" behavior.

Using a fresh databases fixes this, until you reach job ID 10000 again.

[Sam]

Hello 

I found in AWX document a procedure to migrate docker-compose setup into local docker, but I couldn't find anything on how to migrate from AWX 17 --> 19, can you please share any guidelines/hints on how to do it ?