Hi,
Indeed, the remaining info messages were coming from the nova-compute resource tracker. Adding nova=WARN in the list did remove these messages. Thank you very much for your help.
Best regards,
Jean-Philippe Méthot Openstack system administrator Administrateur système Openstack PlanetHoster inc.
Le 8 mai 2019 à 09:35, Jay Pipes jaypipes@gmail.com a écrit :
Sorry for delayed response... comments inline.
On 05/07/2019 05:31 PM, Jean-Philippe Méthot wrote:
Indeed, this is what was written in your original response as well as in the documentation. As a result, it was fairly difficult to miss and I did comment it out before restarting the service. Additionally, as per the configuration I had set up, had the log-config-append option be set, I wouldn’t have any INFO level log in my logs. Hence why I believe it is strange that I have info level logs, when I’ve set default_log_levels like this: default_log_levels = amqp=WARN,amqplib=WARN,boto=WARN,qpid=WARN,sqlalchemy=WARN,suds=WARN,oslo.messaging=WARN,iso8601=WARN,requests.packages.urllib3.connectionpool=WARN,urllib3.connectionpool=WARN,websocket=WARN,requests.packages.urllib3.util.retry=WARN,urllib3.util.retry=WARN,keystonemiddleware=WARN,routes.middleware=WARN,stevedore=WARN,taskflow=WARN,keystoneauth=WARN,oslo.cache=WARN
Do you see any of the above modules logging with INFO level, though? Or are you just seeing other modules (e.g. nova.*) logging at INFO level?
If you are only seeing nova modules logging at INFO level, try adding:
,nova=WARN
to the default_log_levels CONF option.
Let us know if this works :)
Best, -jay