During a minor version update process in RHOSP13 + Contrail 5.1.0 environment, the RHOSP update hangs indefinitely. It was found that the /etc/sysconfig/network-scripts/ifdown-vhost is trying to unbind the NIC while it is still being used by the contrail-vrouter-agent-dpdk container, hence it is hanging until someone manually stop and remove the container.
So I think, since we wanted to use custom docker name , it is better to update the docker startup function to name the container $CONTRAIL_VROUTER_AGENT_DPDK_CONTAINER_NAME instead of the static one.
During a minor version update process in RHOSP13 + Contrail 5.1.0 environment, the RHOSP update hangs indefinitely. It was found that the
/etc/sysconfig/network-scripts/ifdown-vhostis trying to unbind the NIC while it is still being used by thecontrail-vrouter-agent-dpdkcontainer, hence it is hanging until someone manually stop and remove the container.While examining the network-function-vrouter-* and ifdown-vhost scripts it was found that the container is started with a static name
contrail-vrouter-agent-dpdk@ https://github.com/Juniper/contrail-container-builder/blob/7ba3017d20a39f206082c5b96450c79f36241b44/containers/vrouter/base/network-functions-vrouter-dpdk#L113, while the stop function is using$CONTRAIL_VROUTER_AGENT_DPDK_CONTAINER_NAMEwhich has a different value in mynetwork-functions-vrouter-dpdk-envfile , which is some how derived from my container location vars that points to an internal satellite server.So I think, since we wanted to use custom docker name , it is better to update the docker startup function to name the container
$CONTRAIL_VROUTER_AGENT_DPDK_CONTAINER_NAMEinstead of the static one.