ceph-radosgw wasn't running
Bug #1563467 reported by
Andreas Hasenack
This bug report is a duplicate of:
Bug #1577519: ceph-radosgw "Initialization timeout, failed to initialize".
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Server |
Incomplete
|
Undecided
|
Andreas Hasenack | ||
ceph-radosgw (Juju Charms Collection) |
New
|
Undecided
|
Unassigned |
Bug Description
The juju metadata job failed. Upon inspection, the ceph-radosgw service wasn't running. Logs attached.
Note: node sekine.scapestack was used and it's configured with bcache for /. Roles featureflag enabled, maas-1.9FF not.
UPDATE: this was happening again in another openstack installation via the autopilot, which was counting down the attempts and failing each time. We just logged in on the ceph-radosgw unit, started ceph-radosgw and the installation finished.
information type: | Proprietary → Public |
tags: | added: kanban-cross-team landscape |
description: | updated |
tags: | removed: kanban-cross-team |
To post a comment you must log in.
machine-0: 2016-03-29 13:08:57 DEBUG juju.apiserver apiserver.go:275 -> [6] user-admin@local 102.674us {"RequestId" :3,"Error" :"upgrade in progress - Juju functionality is limited" ,"Response" :"'body redacted'"} Block[""].List
How was this machine installed (what version of Autopilot/ Juju/OpenStack/ MAAS/?)
Did the Juju flag for not upgrading get setup properly?