Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1543655

Summary: delete exit-on-validation-errors option in os-net-config unit tests [11.z]
Product: Red Hat OpenStack Reporter: zenghui.shi <zshi>
Component: os-net-configAssignee: zenghui.shi <zshi>
Status: CLOSED ERRATA QA Contact: Shai Revivo <srevivo>
Severity: medium Docs Contact:
Priority: high    
Version: 11.0 (Ocata)CC: aschultz, bfournie, fbaudin, hbrock, jslagle, mburns, rhel-osp-director-maint, srevivo
Target Milestone: z5Keywords: Triaged, ZStream
Target Release: 11.0 (Ocata)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: os-net-config-6.1.4-1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1543653 Environment:
Last Closed: 2018-05-18 17:08:29 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: 1543653    
Bug Blocks:    

Description zenghui.shi 2018-02-08 23:39:31 UTC
+++ This bug was initially created as a clone of Bug #1543653 +++

Description of problem:

fix unit test error caused by backporting NIC Mapping report feature on 11.z

exit-on-validation-errors is not supported in 11, but two unit tests introduced by backporting NIC Mapping Reporting Feature with commit d692c62a are failing because of using this option. This patch is going to fix the unit test issue by deleting this option.

Note: this is downstream only patch.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

the NIC Mapping Report bz number is bz1532140

Comment 2 zenghui.shi 2018-05-10 06:51:35 UTC
pep8 and py27 test passed with this fix applied, moving to Verified status.

Comment 5 errata-xmlrpc 2018-05-18 17:08:29 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-2018:1622