expand/awx-on-k3s
1
0
Fork 0
mirror of https://github.com/Expand-sys/awx-on-k3s synced 2025-12-15 21:42:15 +11:00
Code Issues Projects Releases Packages Wiki Activity Actions

feat: add guide to reveal censored logs

Browse source
This commit is contained in:
kurokobo 2022-06-25 17:14:46 +09:00
parent ea2ba2ce48
commit 6cbae08e4e
4 changed files with 35 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
backup/awxbackup.yaml
View file

@ -7,3 +7,6 @@ metadata:
spec:
deployment_name: awx
backup_pvc: awx-backup-claim
# Uncomment to reveal "censored" logs
#no_log: "false"

3
base/awx.yaml
View file

@ -30,3 +30,6 @@ spec:
web_resource_requirements: {}
task_resource_requirements: {}
ee_resource_requirements: {}
# Uncomment to reveal "censored" logs
#no_log: "false"

3
restore/awxrestore.yaml
View file

@ -15,3 +15,6 @@ spec:
#backup_pvc_namespace: awx
#backup_pvc: awx-backup-claim
#backup_dir: /backups/tower-openshift-backup-2021-06-06-10:51:49
# Uncomment to reveal "censored" logs
#no_log: "false"

26
tips/troubleshooting.md
View file

@ -10,6 +10,7 @@ Some hints and guides for when you got stuck during deployment and daily use of
- [First Step: Investigate your Situation](#first-step-investigate-your-situation)
- [Investigate Status and Events of the Pods](#investigate-status-and-events-of-the-pods)
- [Investigate Logs of the Containers inside the Pods](#investigate-logs-of-the-containers-inside-the-pods)
- [Reveal "censored" output in the AWX Operator's log](#reveal-censored-output-in-the-awx-operators-log)
- [The Pod is `ErrImagePull` with "429 Too Many Requests"](#the-pod-is-errimagepull-with-429-too-many-requests)
- [The Pod is `Pending` with "1 Insufficient cpu, 1 Insufficient memory." event](#the-pod-is-pending-with-1-insufficient-cpu-1-insufficient-memory-event)
- [The Pod is `Pending` with "1 pod has unbound immediate PersistentVolumeClaims." event](#the-pod-is-pending-with-1-pod-has-unbound-immediate-persistentvolumeclaims-event)
@ -102,6 +103,31 @@ For AWX Operator and AWX, specifically, the following commands are helpful.
- Logs of PostgreSQL
- `kubectl -n awx logs -f statefulset/awx-postgres`
### Reveal "censored" output in the AWX Operator's log
If you've found the `FAILED` tasks while investigating AWX Operator's log, sadly sometimes it's marked as `censored` and you can't get actual log.
```bash
$ kubectl -n awx logs -f deployments/awx-operator-controller-manager -c awx-manager
...
TASK [Restore database dump to the new postgresql container] ********************************
fatal: [localhost]: FAILED! => {"censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result", "changed": true}
...
```
AWX Operator 0.23.0 or later supports making this revealed.
To achieve this, you can uncomment `no_log: "false"` manually under `spec` for your `awx.yaml`, `awxbackup.yaml`, or `awxrestore.yaml`, and then re-run your deployment, backup, or restoration.
```yaml
...
spec:
...
# Uncomment to reveal "censored" logs
no_log: "false" 👈👈👈
...
```
### The Pod is `ErrImagePull` with "429 Too Many Requests"
If your Pod for PostgreSQL is in `ErrImagePull` and its `Events` shows following events, this is due to [the rate limit on Docker Hub](https://docs.docker.com/docker-hub/download-rate-limit/).