Comment 3 for bug 1284002

1. L3 agent may not start on the second controller, as it is not strictly required, right after the deployment - this is expected behaviour
2. This is the expected behaviour of Neutron.
3. We need to see the logs and which action were taken to ensure the interfaces are not up
4. Q-dhcp namespace will be created only after dhcp-agent is started on the controller and by default Pacemaker will not migrate resources to the newer controller -

I am closing this bug as invalid - please pick only the 3rd case and provide all the required bug information.