So I think these are logged, they're just not where we expect them to be. I noticed that when running journalctl in devstack:
'sudo journalctl --unit <email address hidden>'
I was seeing haproxy lines, most likely since it's using systemd and haproxy is started as a child.
I also noticed it in other jobs as well:
http://logs.openstack.org/88/535488/1/check/barbican-simple-crypto-devstack-tempest/4a4b91a/logs/screen-q-l3.txt.gz#_Jan_18_22_10_24_019350
That doesn't mean there isn't work to do in TripleO to capture them as well.
So I think these are logged, they're just not where we expect them to be. I noticed that when running journalctl in devstack:
'sudo journalctl --unit <email address hidden>'
I was seeing haproxy lines, most likely since it's using systemd and haproxy is started as a child.
I also noticed it in other jobs as well:
http:// logs.openstack. org/88/ 535488/ 1/check/ barbican- simple- crypto- devstack- tempest/ 4a4b91a/ logs/screen- q-l3.txt. gz#_Jan_ 18_22_10_ 24_019350
That doesn't mean there isn't work to do in TripleO to capture them as well.