Bug 1652282
| Summary: | [3.10] installer checks for images with 'docker images -q' | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Russell Teague <rteague> |
| Component: | Installer | Assignee: | Russell Teague <rteague> |
| Installer sub component: | openshift-ansible | QA Contact: | Weihua Meng <wmeng> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | unspecified | CC: | aos-bugs, gpei, jialiu, jokerman, mmccomas, nick |
| Version: | 3.10.0 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Target Release: | 3.10.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Installer tasks used 'docker' command to check for container images which would fail if docker was not installed. Docker may not be installed if cri-o runtime is specified.
Consequence: Installer tasks would fail when checking container images.
Fix: Updated installer code to use the container image management tool based on the container runtime selected.
Result: Installer uses the correct container image management tool based on the selected container runtime and installs successfully.
|
Story Points: | --- |
| Clone Of: | 1618969 | Environment: | |
| Last Closed: | 2018-12-13 17:09:08 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: | 1618969 | ||
| Bug Blocks: | |||
|
Comment 1
Russell Teague
2018-11-21 19:27:19 UTC
Fixed in openshift-ansible-3.10.80-1 Fixed. openshift-ansible-3.10.82-1.git.0.fcfab8f.el7.noarch when using openshift_use_crio=true openshift_use_crio_only=true crictl used rather than docker 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-2018:3750 |