Bug 1753032 - vSphere UPI e2e add bootstrap gather
Summary: vSphere UPI e2e add bootstrap gather
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.2.0
Assignee: Joseph Callen
QA Contact: sheng.lao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-17 21:03 UTC by Joseph Callen
Modified: 2019-10-16 06:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:41:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift release pull 5060 0 None closed Bug 1753032: cluster-launch-installer-upi-e2e: vsphere upi: Add bootstrap gather 2020-08-19 21:16:30 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:41:41 UTC

Description Joseph Callen 2019-09-17 21:03:49 UTC
Description of problem:

Define GATHER_BOOTSTRAP_ARGS so if bootstrap fails `gather bootstrap` is executed via:
gather_bootstrap_and_fail()





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 2 sheng.lao 2019-09-20 06:48:15 UTC
This is a ci related bug and function `gather_bootstrap_and_fail` is called when bootstrap is failed, I can't reproduce it.
So I check the pr code and read logs of build: https://testgrid.k8s.io/redhat-openshift-release-informing#redhat-canary-openshift-ocp-installer-e2e-vsphere-upi-4.2.

So I move it to `verified`.

Comment 3 errata-xmlrpc 2019-10-16 06:41:28 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:2922


Note You need to log in before you can comment on or make changes to this bug.