elections-messages

#2 Crash loops after merging #1
Closed by bcotton. Opened by bcotton.

Closed
Reopen Issue

After PR #1 was merged, I've been getting frequent emails like this

[FIRING:1] PodCrashLoop elections (elections https-main kube-state-metrics elections-13-pb7gt openshift-monitoring/k8s kube-state-metrics warning 8bfaf8d0-e8c6-4d55-912f-6592880a2a1a)
Labels
alertname = PodCrashLoop
container = elections
endpoint = https-main
job = kube-state-metrics
namespace = elections
pod = elections-13-pb7gt
prometheus = openshift-monitoring/k8s
service = kube-state-metrics
severity = warning
uid = 8bfaf8d0-e8c6-4d55-912f-6592880a2a1a
Annotations
description = Container elections in Pod elections/elections-13-pb7gt has restarted 4.29 in the last 15 minutes.
summary = Pod elections-13-pb7gt is in CrashLoop state.

I'm not sure if it's related, but it seems to be coincidental, so I figured I'd start here.

cc @jrichardson @nphilipp

Coincidence? I think so!

Kevin says "ok, elections in stg should be fixed. Somehow the password was wrong. Not at all sure why... but I fixed that and it's running now."

Metadata Update from @bcotton:
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.