Bug 1672782

Summary: [Hackfest] Error in ovn_migration.sh validation wont let you use $HOME/ovn-extras.yaml
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, joea, lhh, lmarsh, lmartins, majopela, slinaber, twilson
Target Milestone: ---Keywords: TestOnly, Triaged, ZStream
Target Release: 14.0 (Rocky)   
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, 1700302, 1717144    
Bug Blocks:    

Description Miguel Angel Ajo 2019-02-05 22:02:12 UTC 
Description of problem:

ovn_migration doesn't properly detect/check the configured environment files for overcloud deploy.


(overcloud) [stack@undercloud ovn_migration]$ ovn_migration.sh setup-mtu-t1
ovn-extras.yaml file is missing in /home/stack/overcloud-deploy-ovn.sh. Please add it as " -e /home/stack/ovn-extras.yaml"

We had -e $HOME/ovn-extras.yaml (as documentation says), but that wasn’t properly detected
Comment 1 Joe Antkowiak 2019-02-07 15:55:00 UTC 
*** Bug 1673611 has been marked as a duplicate of this bug. ***
Comment 9 Jason Joyce 2019-06-07 18:02:32 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 10 Eran Kuris 2019-06-11 08:26:15 UTC 
Can't verify before getting the fix of https://bugzilla.redhat.com/show_bug.cgi?id=1700302
Comment 13 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