inconsistent logging between different providers
Bug #893379 reported by
Mark Mims
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
lxc instances have no /var/lib/
ec2 instances still have the charm.log separate from the unit-agent log.
description: | updated |
Changed in juju: | |
milestone: | none → florence |
Changed in juju: | |
milestone: | florence → galapagos |
Changed in juju: | |
milestone: | galapagos → honolulu |
Changed in juju: | |
milestone: | 0.6 → none |
Changed in juju: | |
status: | Confirmed → Triaged |
Changed in juju: | |
importance: | Medium → Low |
To post a comment you must log in.
I was quite confused by this as well at first. Seems like a by-product of the 1 machine -> multiple units paradigm that only exists in the local provider right now. Maybe if LXC is used everywhere (sans networking?) then the logging will end up consistent?