ansible / ansible/awx-operator
Current devel branch doesn't deploy due to image name
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 1.5k
- Forks
- 714
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 3
Description
ISSUE TYPE
- Bug Report
SUMMARY
if you try to follow the instructions for the current devel branch, you get an imageerrbackoff because the TAG it's looking for is latest, and that doesn't exist. it needs to be devel or 0.14.0 ...
ENVIRONMENT
- AWX version: 0.14.0
- Operator version: devel
- Kubernetes version: 1.22 (k3s)
- AWX install method: k3s
STEPS TO REPRODUCE
Download current branch (devel)
make deploy
... wait
kubectl get pods -n awx
EXPECTED RESULTS
I should see the operator deployed
ACTUAL RESULTS
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 23s default-scheduler Successfully assigned awx/awx-operator-controller-manager-7c6c695c8d-l7rz8 to iicl00149
Normal Pulled 23s kubelet Container image "gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0" already present on machine
Normal Created 23s kubelet Created container kube-rbac-proxy
Normal Started 23s kubelet Started container kube-rbac-proxy
Warning Failed 21s (x2 over 22s) kubelet Error: ImagePullBackOff
Normal BackOff 21s (x2 over 22s) kubelet Back-off pulling image "quay.io/ansible/awx-operator:latest"
Normal Pulling 10s (x2 over 23s) kubelet Pulling image "quay.io/ansible/awx-operator:latest"
Warning Failed 10s (x2 over 22s) kubelet Failed to pull image "quay.io/ansible/awx-operator:latest": rpc error: code = NotFound desc = failed to pull and unpack image "quay.io/ansible/awx-operator:latest": failed to resolve reference "quay.io/ansible/awx-operator:latest": quay.io/ansible/awx-operator:latest: not found
Warning Failed 10s (x2 over 22s) kubelet Error: ErrImagePull
ADDITIONAL INFORMATION
If you update the Makefile to have a different version listed, it works fine
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 21s default-scheduler Successfully assigned awx/awx-operator-controller-manager-7f86988565-sk8w5 to iicl00149
Normal Pulled 20s kubelet Container image "gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0" already present on machine
Normal Created 20s kubelet Created container kube-rbac-proxy
Normal Started 20s kubelet Started container kube-rbac-proxy
Normal Pulling 20s kubelet Pulling image "quay.io/ansible/awx-operator:devel"
Normal Pulled 17s kubelet Successfully pulled image "quay.io/ansible/awx-operator:devel" in 2.8943327s
Normal Created 17s kubelet Created container manager
Normal Started 17s kubelet Started container manager
AWX-OPERATOR LOGS
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Makefile and trace the image tag used by make deploy. Reproduce with make deploy, then inspect the operator pod with kubectl get pods -n awx and its events. Done means the deployment uses an available image tag and the operator pod starts without ImagePullBackOff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100