Canonical Juju

juju.centralhub does not give useful debug messages

  1. Series 2.3
  2. Bug #1763397
Bug #1763397 reported by John A Meinel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Medium
Unassigned
2.3
Won't Fix
Medium
Tim Penhey

Bug Description

In 2.3.5 I'm seeing this when running "juju bootstrap --debug":
2018-04-12 14:30:18 DEBUG juju.centralhub subscriber.go:41 created subscriber 0xc42022ce60 for 0xbf1650
2018-04-12 14:30:18 DEBUG juju.worker.pubsub subscriber.go:96 subscribing to details topic
2018-04-12 14:30:18 DEBUG juju.centralhub subscriber.go:41 created subscriber 0xc42022cf50 for 0xbf4f00

It doesn't help me at all that it created Hex Pointer for Hex Pointer.

John A Meinel (jameinel)
tags: added: logging observability
removed: obser
Revision history for this message
Anastasia (anastasia-macmood) wrote :

Marking as Won't Fix for 2.3 series since we are not planning to make any further releases in this series at this stage.

Revision history for this message
Jon Seager (jnsgruk) wrote :

This doesn't appear to be an issue any more:

❯ grep -R "created subscriber" 2>/dev/null

Yields nothing for me, and I had a scrub through the code and couldn't find anywhere this might still come from.

Changed in juju:
status: Triaged → 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.