You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: add DependenciesNotReady troubleshooting and fix make target (#450)
## Summary
- Add troubleshooting section for packages stuck in
`DependenciesNotReady` status, explaining how to find missing
dependencies in operator logs and fix them
- Fix outdated `make image-cozystack` → `make image-packages` in the
packages management development guide
Normally all of them should be `Ready` and `Release reconciliation succeeded`
107
107
108
+
## Packages stuck in DependenciesNotReady
109
+
110
+
If some packages show `DependenciesNotReady` status:
111
+
112
+
```console
113
+
$ kubectl get pkg -A | grep -v True
114
+
NAME VARIANT READY STATUS
115
+
cozystack.cozystack-basics default False One or more dependencies are not ready
116
+
cozystack.tenant-application default False One or more dependencies are not ready
117
+
cozystack.monitoring-application default False One or more dependencies are not ready
118
+
```
119
+
120
+
This usually means a package in the dependency chain is missing or disabled. To diagnose:
121
+
122
+
1.**Find the root cause** — check the operator logs for `"dependency not found"` messages:
123
+
124
+
```bash
125
+
kubectl logs -n cozy-system deploy/cozystack-operator | grep "dependency not found"
126
+
```
127
+
128
+
This will show which dependency is missing, for example:
129
+
130
+
```
131
+
dependency not found, marking as not ready package=cozystack.monitoring-application dependency=cozystack.postgres-operator
132
+
```
133
+
134
+
2.**Check if you disabled a required package** — some packages have dependencies on other packages. If you disabled a package (e.g. `cozystack.postgres-operator`) that other packages depend on, the entire dependency chain will be blocked.
135
+
136
+
3.**Fix the issue** — either re-enable the disabled package, or if you intentionally want to keep it disabled, add it to `ignoreDependencies` on the affected package:
0 commit comments