Bug 2418617
| Summary: | [9.0] promtail container being listed under cephadm list-images | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vinayak Papnoi <vpapnoi> |
| Component: | Cephadm | Assignee: | Redouane Kachach Elhichou <rkachach> |
| Status: | CLOSED UPSTREAM | QA Contact: | Vinayak Papnoi <vpapnoi> |
| Severity: | medium | Docs Contact: | Rivka Pollack <rpollack> |
| Priority: | unspecified | ||
| Version: | 9.0 | CC: | adking, akane, cephqe-warriors, rkachach, rpollack |
| Target Milestone: | --- | ||
| Target Release: | 9.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
.Promtail image remains visible after migration to Alloy
During the transition from Promtail to Alloy, cephadm continues to register the Promtail container image to maintain backward compatibility and ensure a smooth migration path. As a result, Promtail still appears in the cephadm `list-images` output after upgrading, even though Alloy is the new default. The behavior is intentional to prevent breaking log collection on clusters that have not fully migrated.
No workaround is required. Ignore the Promtail image entry during the supported transition phase. If log collection has fully migrated to Alloy and is verified, you can optionally remove legacy Promtail daemons and images manually. This cleanup is not required for cluster operation.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2026-03-04 09:57:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2388233 | ||
|
Description
Vinayak Papnoi
2025-12-03 16:14:11 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days or the product is inactive and locked |