Project

General

Profile

Actions
Copy link

Bug #3524

closed

AutoPrefixPropagator: asymmetric log level

Added by Junxiao Shi over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Low
Assignee:
Yanbiao Li
Category:
RIB
Target version:
v0.5
Start date:
03/09/2016
Due date:
% Done:

100%

Estimated time:
0.50 h

Description

Steps to reproduce:

  1. set log level AutoPrefixPropagator=TRACE
  2. properly configure automatic prefix propagation with ndn:/my-identity certificate trusted by the HUB
  3. nfdc register /localhop/nfd tcp4://hobo
  4. ndnpingserver /my-identity/hello
  5. look at NFD logs
1457558803.878112 INFO: [AutoPrefixPropagator] this is a prefix registered by some hub: /localhop/nfd
1457558803.878515 INFO: [AutoPrefixPropagator] redo 0 propagations when new Hub connectivity is built.
1457558807.584872 INFO: [RibManager] Adding route /ndn/edu/arizona/cs/shijunxiao/hello/ping nexthop=265 origin=0 cost=0
1457558807.630564 TRACE: [AutoPrefixPropagator] start propagate /ndn/edu/arizona/cs/shijunxiao
1457558807.751975 TRACE: [AutoPrefixPropagator] success to propagate /ndn/edu/arizona/cs/shijunxiao
1457558822.254201 INFO: [RibManager] Removing route /ndn/edu/arizona/cs/shijunxiao/hello/ping nexthop=265 origin=0
1457558822.327040 INFO: [AutoPrefixPropagator] start revoke propagation of /ndn/edu/arizona/cs/shijunxiao
1457558822.683380 TRACE: [AutoPrefixPropagator] success to revoke propagation of /ndn/edu/arizona/cs/shijunxiao

Expected: start propagate and start revoke propagation of have the same log level

Actual: start propagate has TRACE level, but start revoke propagation of have INFO level

Actions
Copy link

Also available in: Atom PDF