Comment 4 for bug 1664670

TBH, I think there are two bugs here:

1. we have a situation where service dependencies drop a service that is required and, even if appropriate, it we may need a mitigation for that
2. the yum update is hanging because (FWICT) nova doesn't like the try-restart without access to rabbitmq. If yum was not hung, the puppet-apply that we would eventually get to would resolve the issue of the neutron-openvswitch-agent not running. AFAICT, since we still have connectivity on the control plane and also to external networks we would get "unstuck" if this didn't happen. Even so, we should look at (1.) just in case.

Additionally I think we need to add some cautionary notes on network configuration to our docs. This is mainly happening because the neutron-openvswitch-agent in the overcloud and the internal_api network are linked by way of bridge mappings. If they were not, then this particular scenario would not happen.