juju does not log warnings to console unless -v is set
Bug #1204388 reported by
Andrew Wilkins
This bug report is a duplicate of:
Bug #1223224: juju client should show warnings by default.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Triaged
|
High
|
Unassigned | ||
Bug Description
As the summary says, warnings are not shown unless -v is passed to juju. This makes problem diagnosis harder than it should be.
See: https:/
Related branches
| Changed in juju-core: | |
| assignee: | nobody → Andrew Wilkins (axwalk) |
Revision history for this message
| Andrew Wilkins (axwalk) wrote | #1 |
| Changed in juju-core: | |
| milestone: | none → dev-docs |
| status: | New → In Progress |
| Changed in juju-core: | |
| milestone: | dev-docs → none |
| Changed in juju-core: | |
| importance: | Undecided → High |
| Changed in juju-core: | |
| status: | In Progress → Triaged |
| assignee: | Andrew Wilkins (axwalk) → nobody |
| tags: | added: ui |
To post a comment you must log in.
This isn't all upside, I think. We're going to end up with extraneous error messages. Is this acceptable?
No juju environment configuration file exists.
Please create a configuration by running:
juju init -w
then edit the file to configure your juju environment.
You can then re-run bootstrap.
2013-07-24 08:17:28 ERROR juju supercommand.go:235 command failed: open /tmp/juju_
error: open /tmp/juju_