Skip to content

Upgrade to operator 2.13.0 fail when postgres_extra_args is present #1760

@woodbb

Description

@woodbb

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that the AWX Operator is open source software provided for free and that I might not receive a timely response.

Bug Summary

When doing an upgrade of AWX from older version using postgres-13 to the 2.13.0 operator with postgres-15, a new postgres PV is created (empty) and the old PV is removed.

AWX Operator version

2.13.0

AWX version

24.0.0

Kubernetes platform

openshift

Kubernetes/Platform version

4.13

Modifications

no

Steps to reproduce

Install latest AWX operator (2.13.0) into namespace with old operator running (named the same as old instance).

Expected results

I would expect the same PV to be used and the database migrations to happen - or steps to migrate data from old PV to new PV

Actual results

new PV created, old PV removed .. resulting in loss of data

Additional information

If we are not upgrading properly, and there is documentation on the proper way to upgrade, please point me in that direction.

Or if we should be leveraging labels on the PV for postgres in a customized manner, please let me know what parameters should be in our awx instance.

Any guidance is appreciated.

Operator Logs

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions