hook context id overly verbose

Bug #1705404 reported by John A Meinel
This bug report is a duplicate of:  Bug #1705405: hook context id overly verbose. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
John A Meinel

Bug Description

Every time a charm invokes a hook tool, we drop cruft at DEBUG level:
unit-easyrsa-0: 12:16:36 DEBUG worker.uniter.jujuc hook context id "easyrsa/0-update-status-9028046492320369901"; dir "/var/lib/juju/agents/unit-easyrsa-0/charm"
unit-easyrsa-0: 12:16:36 DEBUG worker.uniter.jujuc hook context id "easyrsa/0-update-status-9028046492320369901"; dir "/var/lib/juju/agents/unit-easyrsa-0/charm"
unit-easyrsa-0: 12:16:36 DEBUG worker.uniter.jujuc hook context id "easyrsa/0-update-status-9028046492320369901"; dir "/var/lib/juju/agents/unit-easyrsa-0/charm"
unit-easyrsa-0: 12:16:36 DEBUG worker.uniter.jujuc hook context id "easyrsa/0-update-status-9028046492320369901"; dir "/var/lib/juju/agents/unit-easyrsa-0/charm"
unit-easyrsa-0: 12:16:37 DEBUG worker.uniter.jujuc hook context id "easyrsa/0-update-status-9028046492320369901"; dir "/var/lib/juju/agents/unit-easyrsa-0/charm"

Note that this isn't the interesting bit at all.
    logger.Tracef("running hook tool %q %q", req.CommandName, req.Args)
    logger.Tracef("running hook tool %q", req.CommandName)
    logger.Debugf("hook context id %q; dir %q", req.ContextId, req.Dir)

It seems we dropped the interesting ones to Trace, but then left the uninteresting one at Debug.

Tags: logging
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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