From 157afd773852948a0127128c0172c3f7b17a1532 Mon Sep 17 00:00:00 2001 From: Nicole Rappe Date: Thu, 26 Sep 2024 04:54:44 -0600 Subject: [PATCH] Update Docker & Kubernetes/Servers/AWX/AWX Operator/Upgrading Past 2.10.0.md --- .../Servers/AWX/AWX Operator/Upgrading Past 2.10.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Docker & Kubernetes/Servers/AWX/AWX Operator/Upgrading Past 2.10.0.md b/Docker & Kubernetes/Servers/AWX/AWX Operator/Upgrading Past 2.10.0.md index 6e2d289..0e69412 100644 --- a/Docker & Kubernetes/Servers/AWX/AWX Operator/Upgrading Past 2.10.0.md +++ b/Docker & Kubernetes/Servers/AWX/AWX Operator/Upgrading Past 2.10.0.md @@ -1,4 +1,4 @@ -## Upgrading from 2.10.0 to 2.19.1 +## Upgrading from 2.10.0 to 2.19.1+ There is a known issue with upgrading / install AWX Operator beyond version 2.10.0, because of how the PostgreSQL database upgrades from 13.0 to 15.0, and has changed permissions. The following workflow will help get past that and adjust the permissions in such a way that allows the upgrade to proceed successfully. If this is a clean installation, you can also perform this step if the fresh install of 2.19.1 is not working yet. (It wont work out of the box because of this bug). `The developers of AWX seem to just not care about this issue, and have not implemented an official fix themselves at this time). ### Create a Temporary Pod to Adjust Permissions