ovn-controller container looses connection to openvswitch when openvswitch service is restarted

[Numan Siddique]

Presently ovn-controller container is started with "-v /run/openvswitch:/run/openvswitch".
The openvswitch systemd script deletes the /run/openvswitch folder when stopping it in the host.

/run/openvswitch path inside the ovn-controller container becomes a stale directory.
And when the service is started again, it creates the folder again. In order for ovn-controller
to access again, the folder has to be remounted or the ovn-controller container should be restarted.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/561945

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/561945
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=49963bc180139300afc1a968bfab3f2904f2c09d
Submitter: Zuul
Branch: master

commit 49963bc180139300afc1a968bfab3f2904f2c09d
Author: Numan Siddique <email address hidden>
Date: Tue Apr 17 18:53:08 2018 +0530

    ovn: Mount /run instead of /run/openvswitch when starting ovn-controller container

    Presently ovn-controller container is started with "-v /run/openvswitch:/run/openvswitch".
    The openvswitch systemd script deletes the /run/openvswitch folder when stopping it in the host.
    /run/openvswitch path inside the ovn-controller container becomes a stale directory.
    And when the service is started again, it creates the folder again. In order for ovn-controller
    to access again, the folder has to be remounted or the ovn-controller container should be
    restarted.

    As a temporary fix, this patch mounts /run so that when /run/openvswitch is created again, it will
    get reflected inside the ovn-controller container. The proper fix has to come from openvswitch
    systemd script to not delete /run/openvswitch when stopping the service. This is presently
    discusses in OVS mailing list [1], but no proper solution has been arrived yet.

    [1] - https://mail.openvswitch.org/pipermail/ovs-dev/2018-March/345589.html
    Closes-bug: #1764745
    Change-Id: I032571cec49537cac972ebbbb44733ea17c299fa

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/562538

[Brent Eagles (beagles)]

Won't this affect any neutron agent that mounts /run/openvswitch?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/562538
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=d0219817174c78ea2a66a77511ba582c17278281
Submitter: Zuul
Branch: stable/queens

commit d0219817174c78ea2a66a77511ba582c17278281
Author: Numan Siddique <email address hidden>
Date: Tue Apr 17 18:53:08 2018 +0530

    ovn: Mount /run instead of /run/openvswitch when starting ovn-controller container

    Presently ovn-controller container is started with "-v /run/openvswitch:/run/openvswitch".
    The openvswitch systemd script deletes the /run/openvswitch folder when stopping it in the host.
    /run/openvswitch path inside the ovn-controller container becomes a stale directory.
    And when the service is started again, it creates the folder again. In order for ovn-controller
    to access again, the folder has to be remounted or the ovn-controller container should be
    restarted.

    As a temporary fix, this patch mounts /run so that when /run/openvswitch is created again, it will
    get reflected inside the ovn-controller container. The proper fix has to come from openvswitch
    systemd script to not delete /run/openvswitch when stopping the service. This is presently
    discusses in OVS mailing list [1], but no proper solution has been arrived yet.

    [1] - https://mail.openvswitch.org/pipermail/ovs-dev/2018-March/345589.html
    Closes-bug: #1764745
    Change-Id: I032571cec49537cac972ebbbb44733ea17c299fa
    (cherry picked from commit - 49963bc180139300afc1a968bfab3f2904f2c09d)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 8.0.3 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 9.0.0.0b3 development milestone.