[openstack-ansible] : libvirtd debug logs after Wallaby upgrade
Hi Team I have recently done Victoria to Wallaby upgrade on my openstack-ansible installation. After the upgrade we observe that /var/log/libvirt/ size on all the computes was growing due to libvirtd.log file. Further checking this file it can be seen that there are debug logs. 2025-01-19 11:15:20.817+0000: 2943565: *debug *: virNetlinkEventCallback:862 : dispatching to max 0 clients, called from event watch 7 2025-01-19 11:15:20.817+0000: 2943565:* debug* : virNetlinkEventCallback:876 : event not handled. 2025-01-19 11:15:20.821+0000: 2943605: *debug :* udevHandleOneDevice:1492 : udev action: 'add' ... libvirtd configuration file on compute shows log_level=1 cat libvirtd.conf # Ansible managed # enabling debug mode according to http://wiki.libvirt.org/page/DebugLogs log_level = 1 log_filters="3:remote 4:event 3:json 3:rpc" log_outputs="1:file:/var/log/libvirt/libvirtd.log" listen_tls = 0 listen_tcp = 0 unix_sock_group = "libvirt" unix_sock_ro_perms = "0777" unix_sock_rw_perms = "0770" auth_unix_ro = "none" auth_unix_rw = "none" auth_tcp = "sasl" No related parameter was changed/updated in user_variable file during the upgrade? Any information what could have enabled the debug logs for libvirtd on all the computes? Also how can I turn-off this using the openstack-ansible and what could be impact during the procedure? Regards
Hey, Debug logs are only enabled if `debug: True` is set in user_variables or somewhere in group_vars: https://opendev.org/openstack/openstack-ansible-os_nova/src/tag/wallaby-eom/... With that default value of `debug` should be set to False. You can try running smth like that to check value of the variable: cd /opt/openstack-ansible; ansible -m debug -a var=debug nova_compute On Sun, 19 Jan 2025, 12:33 Rambo Rambo, <ram.ramb2412@gmail.com> wrote:
Hi Team
I have recently done Victoria to Wallaby upgrade on my openstack-ansible installation. After the upgrade we observe that /var/log/libvirt/ size on all the computes was growing due to libvirtd.log file.
Further checking this file it can be seen that there are debug logs.
2025-01-19 11:15:20.817+0000: 2943565: *debug *: virNetlinkEventCallback:862 : dispatching to max 0 clients, called from event watch 7 2025-01-19 11:15:20.817+0000: 2943565:* debug* : virNetlinkEventCallback:876 : event not handled. 2025-01-19 11:15:20.821+0000: 2943605: *debug :* udevHandleOneDevice:1492 : udev action: 'add' ...
libvirtd configuration file on compute shows log_level=1
cat libvirtd.conf # Ansible managed
# enabling debug mode according to http://wiki.libvirt.org/page/DebugLogs log_level = 1 log_filters="3:remote 4:event 3:json 3:rpc" log_outputs="1:file:/var/log/libvirt/libvirtd.log" listen_tls = 0 listen_tcp = 0 unix_sock_group = "libvirt" unix_sock_ro_perms = "0777" unix_sock_rw_perms = "0770" auth_unix_ro = "none" auth_unix_rw = "none" auth_tcp = "sasl"
No related parameter was changed/updated in user_variable file during the upgrade? Any information what could have enabled the debug logs for libvirtd on all the computes? Also how can I turn-off this using the openstack-ansible and what could be impact during the procedure?
Regards
Hi Dmitriy Thanks for the feedback. I have identified that debug is true in user_variable file and that too since very long time. May be we have more debug logging in libvirtd after the wallaby upgrade. So now below can be applied? Change debug to False. openstack-ansible os-nova-install.yml --tags nova-config Regards On Sun, Jan 19, 2025 at 12:10 PM Dmitriy Rabotyagov <noonedeadpunk@gmail.com> wrote:
Hey,
Debug logs are only enabled if `debug: True` is set in user_variables or somewhere in group_vars:
https://opendev.org/openstack/openstack-ansible-os_nova/src/tag/wallaby-eom/...
With that default value of `debug` should be set to False. You can try running smth like that to check value of the variable: cd /opt/openstack-ansible; ansible -m debug -a var=debug nova_compute
On Sun, 19 Jan 2025, 12:33 Rambo Rambo, <ram.ramb2412@gmail.com> wrote:
Hi Team
I have recently done Victoria to Wallaby upgrade on my openstack-ansible installation. After the upgrade we observe that /var/log/libvirt/ size on all the computes was growing due to libvirtd.log file.
Further checking this file it can be seen that there are debug logs.
2025-01-19 11:15:20.817+0000: 2943565: *debug *: virNetlinkEventCallback:862 : dispatching to max 0 clients, called from event watch 7 2025-01-19 11:15:20.817+0000: 2943565:* debug* : virNetlinkEventCallback:876 : event not handled. 2025-01-19 11:15:20.821+0000: 2943605: *debug :* udevHandleOneDevice:1492 : udev action: 'add' ...
libvirtd configuration file on compute shows log_level=1
cat libvirtd.conf # Ansible managed
# enabling debug mode according to http://wiki.libvirt.org/page/DebugLogs log_level = 1 log_filters="3:remote 4:event 3:json 3:rpc" log_outputs="1:file:/var/log/libvirt/libvirtd.log" listen_tls = 0 listen_tcp = 0 unix_sock_group = "libvirt" unix_sock_ro_perms = "0777" unix_sock_rw_perms = "0770" auth_unix_ro = "none" auth_unix_rw = "none" auth_tcp = "sasl"
No related parameter was changed/updated in user_variable file during the upgrade? Any information what could have enabled the debug logs for libvirtd on all the computes? Also how can I turn-off this using the openstack-ansible and what could be impact during the procedure?
Regards
Yes, pretty much that should do the trick. I can't recall though if Wallaby had tags working properly or not, as we had some mess back then with tags, due to mis-use of include_tasks vs import_tasks. On Mon, 20 Jan 2025, 11:22 Rambo Rambo, <ram.ramb2412@gmail.com> wrote:
Hi Dmitriy
Thanks for the feedback. I have identified that debug is true in user_variable file and that too since very long time. May be we have more debug logging in libvirtd after the wallaby upgrade.
So now below can be applied? Change debug to False.
openstack-ansible os-nova-install.yml --tags nova-config
Regards
On Sun, Jan 19, 2025 at 12:10 PM Dmitriy Rabotyagov < noonedeadpunk@gmail.com> wrote:
Hey,
Debug logs are only enabled if `debug: True` is set in user_variables or somewhere in group_vars:
https://opendev.org/openstack/openstack-ansible-os_nova/src/tag/wallaby-eom/...
With that default value of `debug` should be set to False. You can try running smth like that to check value of the variable: cd /opt/openstack-ansible; ansible -m debug -a var=debug nova_compute
On Sun, 19 Jan 2025, 12:33 Rambo Rambo, <ram.ramb2412@gmail.com> wrote:
Hi Team
I have recently done Victoria to Wallaby upgrade on my openstack-ansible installation. After the upgrade we observe that /var/log/libvirt/ size on all the computes was growing due to libvirtd.log file.
Further checking this file it can be seen that there are debug logs.
2025-01-19 11:15:20.817+0000: 2943565: *debug *: virNetlinkEventCallback:862 : dispatching to max 0 clients, called from event watch 7 2025-01-19 11:15:20.817+0000: 2943565:* debug* : virNetlinkEventCallback:876 : event not handled. 2025-01-19 11:15:20.821+0000: 2943605: *debug :* udevHandleOneDevice:1492 : udev action: 'add' ...
libvirtd configuration file on compute shows log_level=1
cat libvirtd.conf # Ansible managed
# enabling debug mode according to http://wiki.libvirt.org/page/DebugLogs log_level = 1 log_filters="3:remote 4:event 3:json 3:rpc" log_outputs="1:file:/var/log/libvirt/libvirtd.log" listen_tls = 0 listen_tcp = 0 unix_sock_group = "libvirt" unix_sock_ro_perms = "0777" unix_sock_rw_perms = "0770" auth_unix_ro = "none" auth_unix_rw = "none" auth_tcp = "sasl"
No related parameter was changed/updated in user_variable file during the upgrade? Any information what could have enabled the debug logs for libvirtd on all the computes? Also how can I turn-off this using the openstack-ansible and what could be impact during the procedure?
Regards
participants (2)
-
Dmitriy Rabotyagov
-
Rambo Rambo