Bug 1504593
Summary: | Installer doesn't report the installer status correctly if openshift health checks failed | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Gan Huang <ghuang> |
Component: | Installer | Assignee: | Russell Teague <rteague> |
Status: | CLOSED ERRATA | QA Contact: | Gan Huang <ghuang> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3.7.0 | CC: | aos-bugs, jokerman, mmccomas, rteague |
Target Milestone: | --- | ||
Target Release: | 3.8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
The OpenShift Health Checker was not part of an Installer Phase and was not reported after playbook execution. The OpenShift Health Checker section of the primary installer path has been moved to its own section and an installer 'phase' has been added to report on installer status.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-28 22:18:47 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: |
Description
Gan Huang
2017-10-20 09:50:27 UTC
I already have a PR open to address this. Proposed: https://github.com/openshift/openshift-ansible/pull/5742 $ git tag --contains c66536bc27db98232ba1e231cfdee48a72936d5b openshift-ansible-3.7.0-0.184.0 openshift-ansible-3.7.0-0.185.0 openshift-ansible-3.7.0-0.186.0 openshift-ansible-3.7.0-0.187.0 openshift-ansible-3.7.0-0.188.0 Tested in openshift-ansible-3.7.0-0.188.0.git.0.aebb674.el7.noarch.rpm Installer aborted and reported the solution. INSTALLER STATUS *************************************************************** Initialization : Complete Health Check : In Progress This phase can be restarted by running: playbooks/byo/openshift-checks/pre-install.yml 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/RHSA-2017:3188 |