Ceilometer-agent-compute service not running due to start-limit-hit
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Ceilometer Agent Charm |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Nova Compute Charm |
Fix Released
|
High
|
Unassigned | ||
Train |
Fix Committed
|
Undecided
|
Unassigned | ||
Ussuri |
Fix Committed
|
Undecided
|
Unassigned | ||
Victoria |
Fix Committed
|
Undecided
|
Unassigned | ||
Wallaby |
Fix Committed
|
Undecided
|
Unassigned | ||
Xena |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
This is a spin-off of lp:1927277. On a fresh deployment, some ceilometer-agent units end up blocked due to the ceilometer-
The ceilometer-
`systemctl status ceilometer-
Oct 18 10:14:25 solqa-lab1-
Oct 18 10:14:25 solqa-lab1-
Oct 18 10:14:25 solqa-lab1-
I suspect ceilometer-
Workaround: systemctl restart ceilometer-
tags: | added: cdo-qa foundations-engine |
tags: | added: aubergine |
Changed in charm-nova-compute: | |
milestone: | none → 22.04 |
Changed in charm-nova-compute: | |
status: | Fix Committed → Fix Released |
Changed in charm-nova-compute: | |
status: | Fix Released → In Progress |
assignee: | Aurelien Lourot (aurelien-lourot) → Liam Young (gnuoy) |
Changed in charm-nova-compute: | |
status: | In Progress → Fix Released |
assignee: | Liam Young (gnuoy) → nobody |
Changed in charm-nova-compute: | |
status: | Fix Released → In Progress |
Changed in charm-nova-compute: | |
status: | In Progress → Triaged |
Changed in charm-nova-compute: | |
status: | Triaged → Fix Released |
+1, have also seen this on a fresh focal/ussuri deployment.