Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore leaves broken awx_task container #1962

Open
3 tasks done
gendergap opened this issue Sep 20, 2024 · 0 comments
Open
3 tasks done

Restore leaves broken awx_task container #1962

gendergap opened this issue Sep 20, 2024 · 0 comments

Comments

@gendergap
Copy link

gendergap commented Sep 20, 2024

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

Restoring an AWX backup spins up the web interface, but the task container does not work. It shows a database column error.

AWX Operator version

2.9.0

AWX version

23.5.1

Kubernetes platform

kubernetes

Kubernetes/Platform version

1.20.11

Modifications

no

Steps to reproduce

  • Restore a backup of AWX (previously created like described in the manual)
  • Wait until the manager stops spinning up resources and the database has been restored
  • Log in to the web interface
  • Launch any job

Expected results

The job should start and complete.

Actual results

The job stays pending for eternity. Inspecting the awx_task pod shows the error message:

[wait-for-migrations] Waiting for database migrations...
[wait-for-migrations] Attempt 1
Traceback (most recent call last):
File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/django/db/backends/utils.py", line 89, in _execute
return self.cursor.execute(sql, params)
File "/var/lib/awx/venv/awx/lib64/python3.9/site-packages/psycopg/cursor.py", line 723, in execute
raise ex.with_traceback(None)
psycopg.errors.UndefinedColumn: column "listener_port" of relation "main_instance" does not exist
LINE 1: ...city", "mem_capacity", "node_type", "node_state", "listener_...

Additional information

No response

Operator Logs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant