I've tried again in the dev env I have available right now with me, which is not queens, but pre-rocky with exabgp 4.0.6, and the feature works as designed in this context.
Just to make sure: are you aware that '-d' is not sufficient to have all the logging of all components, because some components (and exabgp is part of them) have their logging level controlled differently:
To override these settings and enable debug for exabgp, you'll have to use the --log-config-append option. This behavior is not specific to bagpipe-bgp, but common to many openstack components.
If you do this and still don't have exabgp debug, then this means we'll need to reproduce and dig on a queens environment.
I've tried again in the dev env I have available right now with me, which is not queens, but pre-rocky with exabgp 4.0.6, and the feature works as designed in this context.
Just to make sure: are you aware that '-d' is not sufficient to have all the logging of all components, because some components (and exabgp is part of them) have their logging level controlled differently:
https:/ /github. com/openstack/ networking- bagpipe/ blob/stable/ queens/ networking_ bagpipe/ bagpipe_ bgp/bgp_ daemon. py#L51- L60
To override these settings and enable debug for exabgp, you'll have to use the --log-config-append option. This behavior is not specific to bagpipe-bgp, but common to many openstack components.
If you do this and still don't have exabgp debug, then this means we'll need to reproduce and dig on a queens environment.