Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning that probably should be info #521

Open
yaneti opened this issue Oct 1, 2018 · 3 comments
Open

Warning that probably should be info #521

yaneti opened this issue Oct 1, 2018 · 3 comments

Comments

@yaneti
Copy link

yaneti commented Oct 1, 2018

_log.warning('No routing policy defined for "{t}" but routing_nitpicky is '

I am using the simplest form of tail message with the default fedmsg config

config = fedmsg.config.load_config()
for name, endpoint, topic, msg in fedmsg.tail_messages(topic='org.fedoraproject.prod.buildsys.build.state.change', mute=True, **config):

and my log is filled with:
No routing policy defined for "org.fedoraproject.prod.buildsys.build.state.change" but routing_nitpicky is False so the message is being treated as authorized. on each koji message

which is quite useless imho. The default config is not to be nitpicky..

@TomasTomecek
Copy link

Yes, this is really annoying.

@sidpremkumar
Copy link

Does anyone know how to disable this WARNING?

@vojtechsokol
Copy link

@sidpremkumar I was able to disable this by editing the default config /etc/fedmsg.d/ssl.py and setting the value of validate_signatures to False.
And to disable the warning from code that calls tail_messages you have to slightly abuse fedmsg:

import fedmsg

fedmsg.destroy()                                                                                           
fedmsg.init(validate_signatures=False)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants