Bug 1494461
| Summary: | installer is trying to start cri-o service on nfs host | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
| Component: | Installer | Assignee: | Giuseppe Scrivano <gscrivan> |
| Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.7.0 | CC: | aos-bugs, jokerman, mmccomas, sdodson, smilner |
| Target Milestone: | --- | ||
| Target Release: | 3.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-11-28 22:12:28 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: | |||
Proposed fix: https://github.com/openshift/openshift-ansible/pull/5501 Verified this bug with openshift-ansible-3.7.0-0.134.0.git.0.6f43fc3.el7.noarch, and PASS.
TASK [docker : Start the CRI-O service] ****************************************
Friday 29 September 2017 06:55:22 +0000 (0:00:00.984) 0:04:45.688 ******
skipping: [ec2-34-207-180-112.compute-1.amazonaws.com] => {"changed": false, "skip_reason": "Conditional result was False", "skipped": true}
ec2-34-207-180-112.compute-1.amazonaws.com is the nfs host, it is skipped now.
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 |
Description of problem: See the following details. Version-Release number of the following components: openshift-ansible-3.7.0-0.127.0.git.0.b9941e4.el7.noarch How reproducible: Always Steps to Reproduce: 1. prepare inventory host file, enable cri-o, and define a standalone nfs host 2. trigger installation 3. Actual results: Installation failed due to installer is trying run cri-o on a nfs host. fatal: [ec2-54-86-209-24.compute-1.amazonaws.com]: FAILED! => { "changed": true, "cmd": "lsmod | grep overlay", "delta": "0:00:00.006780", "end": "2017-09-22 04:16:35.417998", "failed": true, "rc": 1, "start": "2017-09-22 04:16:35.411218" } MSG: non-zero return code <--snip--> fatal: [ec2-54-86-209-24.compute-1.amazonaws.com]: FAILED! => { "changed": false, "failed": true } MSG: Unable to start service cri-o: Job for cri-o.service failed because the control process exited with error code. See "systemctl status cri-o.service" and "journalctl -xe" for details. <--snip--> Failure summary: 1. Hosts: ec2-54-86-209-24.compute-1.amazonaws.com Play: Set openshift_version for all hosts Task: Start the CRI-O service Message: Unable to start service cri-o: Job for cri-o.service failed because the control process exited with error code. See "systemctl status cri-o.service" and "journalctl -xe" for details. Expected results: Installer should never install cri-o service on a nfs host. Additional info: docker rpm never is installed on a nfs host, cri-o service also should never installed on a nfs host, should only installed on a node host.