Comment 6 for bug 2013189

Reviewed: https://review.opendev.org/c/openstack/openstack-ansible-os_neutron/+/878911
Committed: https://opendev.org/openstack/openstack-ansible-os_neutron/commit/f1a8c358531bdf86d8aeda725bc0b1c347d325c1
Submitter: "Zuul (22348)"
Branch: master

commit f1a8c358531bdf86d8aeda725bc0b1c347d325c1
Author: Dmitriy Rabotyagov <email address hidden>
Date: Wed Mar 29 16:24:34 2023 +0200

    Workaround ovs bug that resets hostname with add command

    After RDO bumped OVS version to 3.1 from 2.17 CentOS/Rocky fails
    tempest testing due to systemd unit calling adding hostname [1]
    while ovs-vsctl add in 3.1 actually behaves exactly as `set` which
    simply resets defined hostname on each service restart. To avoid that
    we're adding `--no-record-hostname` flag that will prevent such
    behaviour.

    [1] https://github.com/openvswitch/ovs/blob/branch-3.1/utilities/ovs-ctl.in#L51

    Change-Id: I8bee1850e3a120f7b76f586909e6d74361696e32
    Related-Bug: #2013189