Bug 1420393
| Summary: | [3.4] conntrack executable not found on $PATH during cluster horizontal run | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> |
| Component: | Installer | Assignee: | Giuseppe Scrivano <gscrivan> |
| Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4.1 | CC: | aos-bugs, gscrivan, jialiu, jokerman, mifiedle, mmccomas |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 3.4.z | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
OCP 3.4 and 3.3 introduced a requirement on the conntrack executable but this dependency was not enforced at install time so service proxy management may have failed post installation. The installer now ensures that conntrack is installed.
|
Story Points: | --- |
| Clone Of: | 1420182 | Environment: | |
| Last Closed: | 2017-03-06 16:38:35 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: | 1420182, 1420395 | ||
| Bug Blocks: | |||
|
Comment 1
Scott Dodson
2017-02-08 14:53:02 UTC
openshift-ansible change: https://github.com/openshift/openshift-ansible/pull/3385 For containerized install: # docker run --rm -ti --entrypoint rpm openshift3/node:v3.4.1.8 -q conntrack-tools conntrack-tools-1.4.3-1.el7.x86_64 For rpm install, test this bug with openshift-ansible-3.4.64-1.git.0.7bb288c.el7.noarch, and PASS. The following step is shown in node install. TASK [openshift_node : Install conntrack-tools package] ************************ After installation, check rpm package. # rpm -q conntrack-tools conntrack-tools-1.4.3-1.el7.x86_64 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:0448 |