juju-core

local provider all-machines.log has only machine-0

Bug #1396796 reported by Tim Penhey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Menno Finlay-Smits
juju-core 1.22-beta1
1.21
Fix Released
High
Menno Finlay-Smits
juju-core 1.21-beta4

Bug Description

Summary says it all.

Revision history for this message
Menno Finlay-Smits (menno.smits) wrote :

I've confirmed that this appears to be a local provider only issue.

Revision history for this message
Menno Finlay-Smits (menno.smits) wrote :

The issue is that when the local provider is used the rsyslogd daemon on the state server expects namespaced syslog tags on the messages coming from machines and units in the environment (e.g. "juju-menno-local-machine-1") but the machine and unit agents are just using "juju-". It looks like this was missed when we stopped using rsyslogd on the client machines.

I have a fix. Adding unit tests and then backporting.

Changed in juju-core:
assignee: nobody → Menno Smits (menno.smits)
status: Triaged → In Progress
milestone: 1.21-beta4 → 1.22
Menno Finlay-Smits (menno.smits)
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.