Heat Caracal: log file full of oslo_messaging._drivers.amqpdriver Expecting reply to msg/Received RPC response
Hi, On our cloud where Caracal Magnum/Heat is deployed, heat_engine log file is filled with many occurences of the following pair of messages (IDs change for every pair) when there is a cluster creation (and probably deletion) : 2024-08-20 09:21:54.458 78230 INFO oslo_messaging._drivers.amqpdriver [None req-bd38bf98-d978-482a-8758-62b1af72fa43 jouvin - - - - -] Expecting reply to msg 699a920fddb940 8a81fd799125835996 in queue reply_2d4fccf5059340818bbfa72887989a6e 2024-08-20 09:21:54.468 78230 INFO oslo_messaging._drivers.amqpdriver [-] Received RPC response for msg 699a920fddb9408a81fd799125835996 Why these INFO messages from oslo that are polluting the logs? we have debug=false in Heat configuration. It doesn't seem to happen in Antelope that we run on another cloud. Any way to disable these messages? Best regards, Michel
Answering to myself... It seems possible to disable these messages by adding the following parameter in Heat configuration file: default_log_levels = 'oslo.messaging=WARN' According to https://docs.openstack.org/oslo.log/latest/configuration/, the default is INFO but it seems it was already the case in Antelope and it doesn't seem to affect Magnum. Is it a change done in Heat when initializing oslo? What is the potential impact (useful messages lost) on setting it to WARN? Michel Le 20/08/2024 à 09:40, Michel Jouvin a écrit :
Hi,
On our cloud where Caracal Magnum/Heat is deployed, heat_engine log file is filled with many occurences of the following pair of messages (IDs change for every pair) when there is a cluster creation (and probably deletion) :
2024-08-20 09:21:54.458 78230 INFO oslo_messaging._drivers.amqpdriver [None req-bd38bf98-d978-482a-8758-62b1af72fa43 jouvin - - - - -] Expecting reply to msg 699a920fddb940 8a81fd799125835996 in queue reply_2d4fccf5059340818bbfa72887989a6e 2024-08-20 09:21:54.468 78230 INFO oslo_messaging._drivers.amqpdriver [-] Received RPC response for msg 699a920fddb9408a81fd799125835996
Why these INFO messages from oslo that are polluting the logs? we have debug=false in Heat configuration. It doesn't seem to happen in Antelope that we run on another cloud. Any way to disable these messages?
Best regards,
Michel
That logging was introduced by this change [1]. We might want to propose changing that/those to DEBUG. [1] https://review.opendev.org/c/openstack/oslo.messaging/+/889425
On 20 Aug 2024, at 10:13, Michel Jouvin <michel.jouvin@ijclab.in2p3.fr> wrote:
Answering to myself... It seems possible to disable these messages by adding the following parameter in Heat configuration file:
default_log_levels = 'oslo.messaging=WARN'
According to https://docs.openstack.org/oslo.log/latest/configuration/, the default is INFO but it seems it was already the case in Antelope and it doesn't seem to affect Magnum. Is it a change done in Heat when initializing oslo? What is the potential impact (useful messages lost) on setting it to WARN?
Michel
Le 20/08/2024 à 09:40, Michel Jouvin a écrit :
Hi,
On our cloud where Caracal Magnum/Heat is deployed, heat_engine log file is filled with many occurences of the following pair of messages (IDs change for every pair) when there is a cluster creation (and probably deletion) :
2024-08-20 09:21:54.458 78230 INFO oslo_messaging._drivers.amqpdriver [None req-bd38bf98-d978-482a-8758-62b1af72fa43 jouvin - - - - -] Expecting reply to msg 699a920fddb940 8a81fd799125835996 in queue reply_2d4fccf5059340818bbfa72887989a6e 2024-08-20 09:21:54.468 78230 INFO oslo_messaging._drivers.amqpdriver [-] Received RPC response for msg 699a920fddb9408a81fd799125835996
Why these INFO messages from oslo that are polluting the logs? we have debug=false in Heat configuration. It doesn't seem to happen in Antelope that we run on another cloud. Any way to disable these messages?
Best regards,
Michel
Tibias, Thanks. Should I open an issue on launchpad about it? Or is it already on some sort of todo list? Michel Sent from my mobile Le 20 août 2024 10:17:50 Tobias Urdin <tobias.urdin@binero.com> a écrit :
That logging was introduced by this change [1]. We might want to propose changing that/those to DEBUG.
[1] https://review.opendev.org/c/openstack/oslo.messaging/+/889425
On 20 Aug 2024, at 10:13, Michel Jouvin <michel.jouvin@ijclab.in2p3.fr> wrote:
Answering to myself... It seems possible to disable these messages by adding the following parameter in Heat configuration file:
default_log_levels = 'oslo.messaging=WARN'
According to https://docs.openstack.org/oslo.log/latest/configuration/, the default is INFO but it seems it was already the case in Antelope and it doesn't seem to affect Magnum. Is it a change done in Heat when initializing oslo? What is the potential impact (useful messages lost) on setting it to WARN?
Michel
Le 20/08/2024 à 09:40, Michel Jouvin a écrit :
Hi,
On our cloud where Caracal Magnum/Heat is deployed, heat_engine log file is filled with many occurences of the following pair of messages (IDs change for every pair) when there is a cluster creation (and probably deletion) :
2024-08-20 09:21:54.458 78230 INFO oslo_messaging._drivers.amqpdriver [None req-bd38bf98-d978-482a-8758-62b1af72fa43 jouvin - - - - -] Expecting reply to msg 699a920fddb940 8a81fd799125835996 in queue reply_2d4fccf5059340818bbfa72887989a6e 2024-08-20 09:21:54.468 78230 INFO oslo_messaging._drivers.amqpdriver [-] Received RPC response for msg 699a920fddb9408a81fd799125835996
Why these INFO messages from oslo that are polluting the logs? we have debug=false in Heat configuration. It doesn't seem to happen in Antelope that we run on another cloud. Any way to disable these messages?
Best regards,
Michel
Hello, Here is a proposed change https://review.opendev.org/c/openstack/oslo.messaging/+/926704 Best regards
On 20 Aug 2024, at 22:03, Michel Jouvin <michel.jouvin@ijclab.in2p3.fr> wrote:
Tibias,
Thanks. Should I open an issue on launchpad about it? Or is it already on some sort of todo list?
Michel Sent from my mobile
Le 20 août 2024 10:17:50 Tobias Urdin <tobias.urdin@binero.com> a écrit :
That logging was introduced by this change [1]. We might want to propose changing that/those to DEBUG.
[1] https://review.opendev.org/c/openstack/oslo.messaging/+/889425
On 20 Aug 2024, at 10:13, Michel Jouvin <michel.jouvin@ijclab.in2p3.fr> wrote:
Answering to myself... It seems possible to disable these messages by adding the following parameter in Heat configuration file:
default_log_levels = 'oslo.messaging=WARN'
According to https://docs.openstack.org/oslo.log/latest/configuration/, the default is INFO but it seems it was already the case in Antelope and it doesn't seem to affect Magnum. Is it a change done in Heat when initializing oslo? What is the potential impact (useful messages lost) on setting it to WARN?
Michel
Le 20/08/2024 à 09:40, Michel Jouvin a écrit :
Hi,
On our cloud where Caracal Magnum/Heat is deployed, heat_engine log file is filled with many occurences of the following pair of messages (IDs change for every pair) when there is a cluster creation (and probably deletion) :
2024-08-20 09:21:54.458 78230 INFO oslo_messaging._drivers.amqpdriver [None req-bd38bf98-d978-482a-8758-62b1af72fa43 jouvin - - - - -] Expecting reply to msg 699a920fddb940 8a81fd799125835996 in queue reply_2d4fccf5059340818bbfa72887989a6e 2024-08-20 09:21:54.468 78230 INFO oslo_messaging._drivers.amqpdriver [-] Received RPC response for msg 699a920fddb9408a81fd799125835996
Why these INFO messages from oslo that are polluting the logs? we have debug=false in Heat configuration. It doesn't seem to happen in Antelope that we run on another cloud. Any way to disable these messages?
Best regards,
Michel
participants (2)
-
Michel Jouvin
-
Tobias Urdin