Bug 1672785

Summary: [Hackfest] networking-ovn-migration-mtu output is confusing during ovn_migration.sh reduce-mtu call
Product: Red Hat OpenStack Reporter: Miguel Angel Ajo <majopela>
Component: python-networking-ovnAssignee: Miguel Angel Ajo <majopela>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: apevec, lhh, lmarsh, lmartins, majopela, slinaber, twilson
Target Milestone: ---Keywords: TestOnly, Triaged, ZStream
Target Release: 14.0 (Rocky)Flags: majopela: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-networking-ovn-5.0.2-0.20190307204430.6a774a0.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-02 19:47:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1694572, 1717144    
Bug Blocks:    

Description Miguel Angel Ajo 2019-02-05 22:05:26 UTC 
See the arrow, that makes the admin believe that it needs to run that command manually, while in fact ovn_migration.sh will handle it for himself.

(overcloud) [stack@undercloud ovn_migration]$ ovn_migration.sh reduce-mtu
Verifying the tenant network mtu's
adapted_mtu tag is not set for the Network [HA network tenant 5445e312e3804c30aa4bdd6851339aa2]
adapted_mtu tag is not set for the Network [net1]

Please run : "/usr/bin/networking-ovn-migration-mtu update mtu" before starting the migration migration to OVN <------

Updating the tenant network mtu
Updating the mtu and the tag 'adapted_mtu of the network - HA network tenant 5445e312e3804c30aa4bdd6851339aa2
Updating the mtu and the tag 'adapted_mtu of the network - net1
Comment 9 Jason Joyce 2019-06-07 18:02:34 UTC 
According to our records, this should be resolved by python-networking-ovn-5.0.2-0.20190307204430.6a774a0.el7ost.  This build is available now.
Comment 12 errata-xmlrpc 2019-07-02 19:47:40 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1680