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

AWX task pod unable to initialize in Azure openshift cluster #1814

Open
3 tasks done
jaipal1983 opened this issue Apr 9, 2024 · 2 comments
Open
3 tasks done

AWX task pod unable to initialize in Azure openshift cluster #1814

jaipal1983 opened this issue Apr 9, 2024 · 2 comments

Comments

@jaipal1983
Copy link

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

Installing awx using helm, all the pods are running except task pod does not get initialize.

AWX Operator version

2.13.1

AWX version

24.0.0

Kubernetes platform

openshift

Kubernetes/Platform version

v1.26.7+0ef5eae

Modifications

no

Steps to reproduce

Execute the below command to install the AWX operator

  1. helm install ansible-awx-operator awx-operator/awx-operator --version 2.13.1c
  2. Run the below awx.yaml deployment file using command oc create -f awx.yml

Expected results

All the pods should run.

[root@SU02848 ~]# oc get pods
NAME READY STATUS RESTARTS AGE
awx-operator-controller-manager-66c686b575-bcn2l 2/2 Running 0 103m
awx-qa-postgres-15-0 1/1 Running 0 167m
awx-qa-task-6976894b96-pd8h4 0/4 Running 0 102m
awx-qa-web-68bc79f956-78fds 3/3 Running 0 166m
[root@SU02848 ~]#

Actual results

awx-qa-task-6976894b96-pd8h4 pod not get initialized.
[root@SU02848 ~]# oc get pods
NAME READY STATUS RESTARTS AGE
awx-operator-controller-manager-66c686b575-bcn2l 2/2 Running 0 103m
awx-qa-postgres-15-0 1/1 Running 0 167m
awx-qa-task-6976894b96-pd8h4 0/4 Init:0/2 0 102m
awx-qa-web-68bc79f956-78fds 3/3 Running 0 166m
[root@SU02848 ~]#

Additional information

For postgres db and project data volume is dynamically provision using the storage class managed csi and azurefile csi

[root@SU02848 ~]# oc get pvc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
awx-qa-projects-claim Bound pvc-81c0262d-e3f5-46b7-8523-34311eb65945 10Gi RWX azurefile-csi 179m
postgres-15-awx-qa-postgres-15-0 Bound pvc-73c123cb-fa9b-4c4e-b970-0584b53fdbed 50Gi RWO managed-csi 3h
[root@SU02848 ~]#

init-database: container is waiting for migration in pod awx-qa-task-6976894b96-pd8h4

Operator Logs

operator_log.txt

Attached operator log

@jaipal1983
Copy link
Author

Added describe output and awx.yml deployment file
awx.yml.txt
describe_output.txt

@fosterseth
Copy link
Member

fosterseth commented Apr 12, 2024

2.13.1 has this PR #1674 (comment)

which should run migrations in a separate awx-migration- pod, but I don't see any listed under your oc get pods results

the operator hit a fatal error when creating super user, but that might just mean your data did not migrate correctly

can you poke around and see that your database has migrated?

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

2 participants