Description of problem:
Nova Compute is trying to call brctl through nova-rootwrap but the command can not be found.

Version-Release number of selected component (if applicable):
openstack-nova-compute-2013.2-0.19.b3.el6.noarch

How reproducible:
Probably always, but haven't tested

Steps to Reproduce:
1. Install EL6.4
2. Make sure bridge-utils have not been installed already (e.g. minimal install)
3. Install OpenStack (FWIW: Havana-3, with Neutron, without Packstack)

Actual results:
[...]
2013-09-17 16:46:01.748 4457 TRACE nova.compute.manager [instance: a37b711f-e74e-4dfc-afb4-04d207f67074] ProcessExecutionError: Unexpected error while running command.
2013-09-17 16:46:01.748 4457 TRACE nova.compute.manager [instance: a37b711f-e74e-4dfc-afb4-04d207f67074] Command: sudo nova-rootwrap /etc/nova/rootwrap.conf brctl addbr qbr52facc6a-bb
2013-09-17 16:46:01.748 4457 TRACE nova.compute.manager [instance: a37b711f-e74e-4dfc-afb4-04d207f67074] Exit code: 96
2013-09-17 16:46:01.748 4457 TRACE nova.compute.manager [instance: a37b711f-e74e-4dfc-afb4-04d207f67074] Stdout: '/usr/bin/nova-rootwrap: Executable not found: brctl (filter match = brctl)\n'
2013-09-17 16:46:01.748 4457 TRACE nova.compute.manager [instance: a37b711f-e74e-4dfc-afb4-04d207f67074] Stderr: ''
[...]
2013-09-17 16:46:03.100 4457 TRACE nova.virt.libvirt.vif [instance: a37b711f-e74e-4dfc-afb4-04d207f67074] ProcessExecutionError: Unexpected error while running command.
2013-09-17 16:46:03.100 4457 TRACE nova.virt.libvirt.vif [instance: a37b711f-e74e-4dfc-afb4-04d207f67074] Command: sudo nova-rootwrap /etc/nova/rootwrap.conf brctl delif qbr52facc6a-bb qvb52facc6a-bb
2013-09-17 16:46:03.100 4457 TRACE nova.virt.libvirt.vif [instance: a37b711f-e74e-4dfc-afb4-04d207f67074] Exit code: 96
2013-09-17 16:46:03.100 4457 TRACE nova.virt.libvirt.vif [instance: a37b711f-e74e-4dfc-afb4-04d207f67074] Stdout: '/usr/bin/nova-rootwrap: Executable not found: brctl (filter match = brctl)\n'
2013-09-17 16:46:03.100 4457 TRACE nova.virt.libvirt.vif [instance: a37b711f-e74e-4dfc-afb4-04d207f67074] Stderr: ''
[...]

Expected results:
No errors :)

Additional info:
Manually installing bridge-utils on the compute nodes resolved the issue (as expected).