Add juju logging settings to troubleshooting for container/kvm creation #216

Merged
merged 2 commits into from Jan 6, 2015

Conversation

Projects
None yet
3 participants
Collaborator

chuckbutler commented Jan 6, 2015

It's often handy to understand why container/vm creation on a unit fails, and presently there is no way to capture that output that's very apparent to the user. By tweaking the juju logging environment settings
we can capture the TRACE of those commands yielding in more meaningful debugging sessions.

It's often handy to understand why container/vm creation on a unit
fails, and presently there is no way to capture that output that's very
apparent to the user. By tweaking the juju logging environment settings
we can capture the TRACE of those commands yielding in more meaningful
debugging sessions.
Owner

howbazaar commented Jan 6, 2015

👍

Owner

marcoceppi commented Jan 6, 2015

I think logging should exist elsewhere possibly its own section. This is a good start though.

Collaborator

chuckbutler commented Jan 6, 2015

I agree, I thought about starting the logging section - but its a fairly significant topic and the possibility of me writing all that tonight was close to nil, so I figured this was the best bet. Get it in troubleshooting and move it later. I'll file a bug for that.

Collaborator

chuckbutler commented Jan 6, 2015

See issue #217

marcoceppi added a commit that referenced this pull request Jan 6, 2015

Merge pull request #216 from chuckbutler/add-logging-trace-to-trouble…
…shooting

Add juju logging settings to troubleshooting for container/kvm creation

@marcoceppi marcoceppi merged commit 5682f21 into juju:master Jan 6, 2015

@chuckbutler chuckbutler deleted the chuckbutler:add-logging-trace-to-troubleshooting branch Jun 28, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment