Bug #47969: cephadm: output migration of alertmanager is confusing - Orchestrator - Ceph

Actions

Copy link

Bug #47969

open

cephadm: output migration of alertmanager is confusing

Added by Patrick Seidensal over 3 years ago. Updated almost 2 years ago.

Status:

New

Priority:

Low

Assignee:

Category:

cephadm/monitoring

Target version:

% Done:

Source:

Tags:

Backport:

octopus

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

Though the migration process runs through successfully, the displayed output is probably confusing:

Pulling container image registry.suse.com/caasp/v4.5/prometheus-alertmanager:0.16.2...
Non-zero exit code 1 from /usr/bin/podman run --rm --ipc=host --net=host --entrypoint stat -e CONTAINER_IMAGE=registry.suse.com/caasp/v4.5/prometheus-alertmanager:0.16.2 -e NODE_NAME=master registry.suse.com/caasp/v4.5/prometheus-alertmanager:0.16.2 -c %u %g /etc/alertmanager
stat:stderr stat: cannot stat '/etc/alertmanager': No such file or directory
Non-zero exit code 1 from /usr/bin/podman run --rm --ipc=host --net=host --entrypoint stat -e CONTAINER_IMAGE=registry.suse.com/caasp/v4.5/prometheus-alertmanager:0.16.2 -e NODE_NAME=master registry.suse.com/caasp/v4.5/prometheus-alertmanager:0.16.2 -c %u %g /etc/alertmanager
stat:stderr stat: cannot stat '/etc/alertmanager': No such file or directory

This is due to cephadm checking for two paths for the configuration file of the alertmanager because containers might have different places for them (like the SUSE container differs from the upstream prometheus alertmanager container).

The prometheus upstream container is not affected by this as the first try to determine the directory succeeds.