Landscape Server

ceph-radosgw wasn't running

Bug #1563467 reported by Andreas Hasenack on 2016-03-29

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.

See original description

Tags:

Revision history for this message

Andreas Hasenack (ahasenack) wrote on 2016-03-29:

all-machines.log Edit (41.1 KiB, text/plain)
api.log Edit (596.1 KiB, text/plain)
appserver.log Edit (1.0 MiB, text/plain)
async-frontend.log Edit (151.6 KiB, text/plain)
distributed-lock.log Edit (270 bytes, text/plain)
job-handler.log Edit (232.8 KiB, text/plain)
juju-status.out Edit (46.6 KiB, text/plain)
juju-sync.log Edit (786.0 KiB, text/plain)
landscape-profiles.log Edit (23.5 KiB, text/plain)
message-server.log Edit (396.4 KiB, text/plain)
package-search.log Edit (661 bytes, text/plain)
package-upload.log Edit (583.0 KiB, text/plain)
pingserver.log Edit (886.6 KiB, text/plain)
process-alerts.log Edit (4.7 KiB, text/plain)
update-alerts.log Edit (22.2 KiB, text/plain)
usn-script.log Edit (2.4 KiB, text/plain)

Andreas Hasenack (ahasenack) on 2016-04-06

information type:	Proprietary → Public
tags:	added: kanban-cross-team landscape
description:	updated

🤖 Landscape Builder (landscape-builder) on 2016-04-06

tags:

removed: kanban-cross-team

Revision history for this message

Adam Collard (adam-collard) wrote on 2016-04-11:

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?