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

Bug 1605160

Summary: [Ansible-2.6.1] Create VPC failed where ansible module "ec2_vpc_net" raise exception of "does not exist: vpc_exists"
Product: OpenShift Container Platform Reporter: sheng.lao <shlao>
Component: InstallerAssignee: Chris Callegari <ccallega>
Status: CLOSED ERRATA QA Contact: sheng.lao <shlao>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.11.0CC: aos-bugs, jokerman, mmccomas, wmeng, xtian
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-10 09:03:57 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: 1627652    
Bug Blocks:    

Comment 3 sheng.lao 2018-08-09 13:47:35 UTC 
According to the upstream of ansible: https://github.com/ansible/ansible/issues/42427

I upgrade the rpm of python2-botocore >= 1.6.0, then play with master branch of openshift-ansible. 

The problem is gone.

I will change the state until the OCP channel update the rpm of python2-botocore
Comment 4 sheng.lao 2018-09-04 02:10:30 UTC 
Waiting the release rpm of python2-botocore
Comment 7 sheng.lao 2018-09-17 07:35:56 UTC 
The workaround of this problem is done by following:
    pip install --upgrade botocore==1.7.0
Comment 8 sheng.lao 2018-10-14 06:21:50 UTC 
As bz-1627652 is in the state "1627652", so I close this bug.
Comment 9 sheng.lao 2018-10-14 07:48:51 UTC 
Bz-1627652 is in the state "CLOSED WONTFIX"
Comment 11 errata-xmlrpc 2019-01-10 09:03:57 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:0024