# Upgrade with awx-operator 1.1.2 to 1.1.3 (or newer) fails **URL:** \ **Category:** AWX Project\ **Tags:** awx\ **Created:** [February 10, 2023, 2:41pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647 "2023-02-10T14:41:09Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![trippinnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trippinnik/32/4308_2.png) [@trippinnik](https://forum.ansible.com/u/trippinnik)\ **Post date:** [February 10, 2023, 2:41pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/1 "2023-02-10T14:41:09Z")
Upgrade with awx-operator 1.1.2 to 1.1.3 (or newer) fails the awx web instance never gets going as waiting for db migrations fails and repeats continuously. ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [February 10, 2023, 6:57pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/2 "2023-02-10T18:57:45Z")
Are you able to provide the pod logs for the awx-web container? _NOTE_ please inject your own pod and container names. kubectl logs $PODNAME -c $WEBCONTAINERNAME Thanks, AWX Team ---
**Author:** ![trippinnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trippinnik/32/4308_2.png) [@trippinnik](https://forum.ansible.com/u/trippinnik)\ **Post date:** [February 10, 2023, 7:04pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/3 "2023-02-10T19:04:47Z")
I’ve reverted so they are gone, but it was just the waiting for db migrations message. waiting 5 seconds, then x seconds then 30 seconds try number x. then after 30 tries failed. no reason given. I’ve seen those messages previously but after the final try it just moved on and web front end was available. I’ve done the upgrade a number of times, same process. I do not see any release notes that say my helm needs any changes. Used to have to delete awx-controller-operator but that was fixed. This happens on both my dev and prod instances ---
**Author:** ![sinnl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sinnl/32/1532_2.png) [@sinnl](https://forum.ansible.com/u/sinnl)\ **Post date:** [February 13, 2023, 9:34pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/4 "2023-02-13T21:34:10Z")
Hi, In my case, what has helped was deleting coredns pods. Once those got recreated migration started within few seconds. I am using external db which I’m guessing there was an issue resolving. Not sure if this is going to be of help but thought I share anyway 🙂 L. ---
**Author:** ![trippinnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trippinnik/32/4308_2.png) [@trippinnik](https://forum.ansible.com/u/trippinnik)\ **Post date:** [February 27, 2023, 7:04pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/5 "2023-02-27T19:04:36Z")
still can’t upgrade to anything newer than 1.1.2: [wait-for-migrations] Attempt 30 of 30 [wait-for-migrations] ERROR: Database migrations not applied Database is managed by awx-operator so @Sinnl suggestion n/a ---
**Author:** ![Purp-E](https://avatars.discourse-cdn.com/v4/letter/p/e19b73/32.png) [@Purp-E](https://forum.ansible.com/u/Purp-E)\ **Post date:** [February 28, 2023, 9:49am UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/6 "2023-02-28T09:49:25Z")
Hi, we also see this Error sometimes and to resolve it we usually access the web-container terminal and then put the command ‘awx-manage migrate’ in. Always resolved the problem and made the container working again. ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [March 1, 2023, 7:54pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/7 "2023-03-01T19:54:57Z")
Nicholas are you still experiencing trouble upgrading to 1.1.3? ---
**Author:** ![trippinnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trippinnik/32/4308_2.png) [@trippinnik](https://forum.ansible.com/u/trippinnik)\ **Post date:** [March 1, 2023, 9:01pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/8 "2023-03-01T21:01:35Z")
Yes, I created external rds I confirmed connectivity from awx-web with python to the instance but seems to not be connecting on its own as it should. Logging shows the migrating failure I suspect issue with getting creds in configuration yaml but have tried a number of different ways so far no joy ---
**Author:** ![AWX\_Project](https://avatars.discourse-cdn.com/v4/letter/a/eada6e/32.png) [@AWX\_Project](https://forum.ansible.com/u/AWX_Project)\ **Post date:** [March 3, 2023, 6:16pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/9 "2023-03-03T18:16:35Z")
can you provide logging from the external RDS postgres service? is it evident that the DB is trying to apply the migrations? which postgres version are you running? AWX Team ---
**Author:** ![trippinnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trippinnik/32/4308_2.png) [@trippinnik](https://forum.ansible.com/u/trippinnik)\ **Post date:** [March 3, 2023, 8:40pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/10 "2023-03-03T20:40:59Z")
Got external dB working ---
**Author:** ![trippinnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trippinnik/32/4308_2.png) [@trippinnik](https://forum.ansible.com/u/trippinnik)\ **Post date:** [March 7, 2023, 6:16pm UTC](https://forum.ansible.com/t/upgrade-with-awx-operator-1-1-2-to-1-1-3-or-newer-fails/37647/11 "2023-03-07T18:16:50Z")
So I am going through this process to make sure I can migrate my prod instance to external db and keep the data, but even setting up a new instance with managed db: 2023-03-07 18:10:04.698 UTC [270] ERROR: relation “django\_migrations” does not exist at character 124 2023-03-07 18:10:04.698 UTC [270] STATEMENT: SELECT “django\_migrations”.“id”, “django\_migrations”.“app”, “django\_migrations”.“name”, “django\_migrations”.“applied” FROM “django\_migrations” WHERE (“django\_migrations”.“app” = ‘main’ AND NOT (“django\_migrations”.“name”::text LIKE ‘%squashed%’)) ORDER BY “django\_migrations”.“id” DESC LIMIT 1 postgres logs show this. I initially tried 1.2.0 - it failed so rolled back to 1.1.2 and deleted all the persistent data etc so make sure fresh setup. but just see that error repeat while the awx\_web repeats the db migrations waiting messages