one of cinder units fails to deploy

Bug #2060836 reported by Marian Gasparovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Snap
New
Undecided
Unassigned

Bug Description

Six node deployment, cinder-2 did not deploy

cinder/2 error idle 10.1.126.132 crash loop backoff: back-off 5m0s restarting failed container=cinder-scheduler pod=cinder-2_openstack(dca83f5d-7493-4...

Logs from container show

2024-04-10T11:15:18.786Z [container-agent] 2024-04-10 11:15:18 ERROR juju.worker.uniter pebblenotices.go:108 container "cinder-scheduler": WaitNotices error, waiting 1s: cannot communicate with server: Get "http://localhost/v1/noti
ces?timeout=30s": dial unix /charm/containers/cinder-scheduler/pebble.socket: connect: connection refused
2024-04-10T11:15:19.777Z [container-agent] 2024-04-10 11:15:19 ERROR juju.worker.uniter pebblepoller.go:103 pebble poll failed for container "cinder-scheduler": failed to get pebble info: cannot obtain system details: cannot commun
icate with server: Get "http://localhost/v1/system-info": dial unix /charm/containers/cinder-scheduler/pebble.socket: connect: connection refused

Artifacts - https://oil-jenkins.canonical.com/artifacts/fa38464c-bf08-4bc5-9f48-5851aa7f1cf9/index.html

Tags: cdo-qa
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.