juju-core

cmd/jujud: bootstrap logs are no longer captured on failure

Bug #1366650 reported by Andrew Wilkins
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Andrew Wilkins
juju-core 1.21-alpha1

Bug Description

If bootstrap fails, we are no longer displaying the bootstrap logs to the user. Most likely related to the recent changes to use lumberjack.

Revision history for this message
Andrew Wilkins (axwalk) wrote :

Hmm nope, not the lumberjack change. Maybe rsyslog changes? Will bisect...

Revision history for this message
Andrew Wilkins (axwalk) wrote :

First guess was right, I just tested badly.

Changed in juju-core:
status: Triaged → In Progress
assignee: nobody → Andrew Wilkins (axwalk)
Revision history for this message
Andrew Wilkins (axwalk) wrote :

Also, there's no stack trace emitted when panics occur now, so the log message you get is practically useless.

Andrew Wilkins (axwalk)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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