Bug 1819136

Summary: Custom Ansible modules not supported for the downstream documentation
Product: OpenShift Container Platform Reporter: Maysa Macedo <mdemaced>
Component: InstallerAssignee: Maysa Macedo <mdemaced>
Installer sub component: OpenShift on OpenStack QA Contact: weiwei jiang <wjiang>
Status: CLOSED ERRATA Docs Contact:
Severity: low    
Priority: urgent CC: dsanzmor, ltomasbo
Version: 4.5   
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1819132 Environment:
Last Closed: 2020-05-04 11:47:45 UTC Type: ---
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: 1819132    
Bug Blocks:    

Description Maysa Macedo 2020-03-31 09:55:05 UTC 
+++ This bug was initially created as a clone of Bug #1819132 +++

Description of problem:

The current OpenStack UPI support is relying on custom Ansible modules to perform operations not supported by Ansible.
However, the downstream documentation of this work would needed to link the Github repository containing those custom modules,
which is not permitted by support.
As there's no more time to rely on building RPM, a conversion of those modules to openstackcli for the playbooks is needed.

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag
Comment 3 weiwei jiang 2020-04-14 09:20:08 UTC 
Checked with 4.4.0-0.nightly-2020-04-13-113747, and work well, so moved to verified.
Comment 5 errata-xmlrpc 2020-05-04 11:47:45 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-2020:0581