You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 @
, while the stop function is using $CONTRAIL_VROUTER_AGENT_DPDK_CONTAINER_NAME which has a different value in my network-functions-vrouter-dpdk-env file , 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_NAME instead of the static one.
The text was updated successfully, but these errors were encountered:
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 thecontrail-vrouter-agent-dpdk
container, 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
@contrail-container-builder/containers/vrouter/base/network-functions-vrouter-dpdk
Line 113 in 7ba3017
$CONTRAIL_VROUTER_AGENT_DPDK_CONTAINER_NAME
which has a different value in mynetwork-functions-vrouter-dpdk-env
file , 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_NAME
instead of the static one.The text was updated successfully, but these errors were encountered: