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 operation does not overwrite secrets as claimed by documentation #1961

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

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

The orderly restore operation fails to overwrite the secrets, which have to manually removed for the time being.

AWX Operator version

2.9.0

AWX version

23.5.1

Kubernetes platform

kubernetes

Kubernetes/Platform version

1.20.11

Modifications

yes

Steps to reproduce

We had a running AWX that got broken during the update to a more recent release. Thus, we wanted to restore the backup from before the update (taken through the procedure described in the manual).

For the restore, we again used the manual and followed these steps in an empty cluster:

  • Install the Operator
  • Install a fresh empty AWX
  • Delete the AWX CR (which, as we found out, does not mean "certificate request", but "custom resource", something that could be better explained in the restore manual)
  • Delete the Postgres PVC
  • Apply the backup spec

Expected results

We expected the backup to be restored and AWX to be up and healthy afterwards.

Actual results

The restore failed because it could not apply the secrets from the backup.

When we deleted the two secrets "awx-admin-password" and "awx-secret-key" the restore procedure continued onwards. I feel it should be mentioned in documentation that these steps are required.

Also, finding out that there actually is a spec option "no_log" (from the codebase) was hard. Neither the restore nor the backup manual have a complete reference of available configuration options.

Additional information

No response

Operator Logs

awx-operator-controller-manager-6677bc895d-kb5x4_awx-manager.log

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