| Summary: | Issues within playbook while upgrade from 3.X to 3.Y version | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Vladislav Walek <vwalek> |
| Component: | Cluster Version Operator | Assignee: | Steve Milner <smilner> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3.0 | CC: | aos-bugs, bleanhar, jiajliu, jokerman, mmccomas, tdawson |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
tar was not listed as a dependency
Consequence:
On systems where tar is not part of the base system the installer could fail
Fix:
tar was added as a dependency
Result:
The installer is able to use tar during installation/upgrade
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-12 18:48:01 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: | |
https://github.com/ansible/ansible/pull/18205 opened upstream to add tar to the specfile requirements ensuring that tar is installed when ansible is installed into a container. There may be other issues at hand here. *** Bug 1387636 has been marked as a duplicate of this bug. *** It has the same issue when run installer on container.
Version:
imageopenshift3/installer latest
1. docker pull openshift3/installer image
2. trigger an installer on container
3. the install will fail becase no tar command in installer container
Play 17/29 (Additional master configuration)
.......................................................................................................fatal: [openshift-136.x.x.x -> localhost]: FAILED! => {"changed": false, "cmd": "tar -C /usr/share/ansible/openshift-ansible/roles/openshift_examples/files/examples/v1.3/ -cvf /tmp/openshift-ansible-MdF0qgU/openshift-examples.tar .", "failed": true, "msg": "[Errno 2] No such file or directory", "rc": 2}
localhost : ok=12 changed=9 unreachable=0 failed=0
openshift-136.lab.eng.nay.redhat.com : ok=296 changed=68 unreachable=0 failed=1
Troy, we're thinking we could workaround this by having openshift-ansible depend on tar. We'll make openshift-ansible depend on tar. Changes in PR https://github.com/openshift/openshift-ansible/pull/3124 https://github.com/openshift/openshift-ansible/pull/3124 has been merged. Waiting puddle for testing The tar packages was added as dependency package when install openshift-ansible in openshift-ansible-3.5.5 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-2017:0903 |
Description of problem: When running the containerized upgrade from 3.2 to 3.3 an error appears while running task openshift_examples from post.yml playbook: FAILED! => {"changed": false, "cmd": "tar -C /usr/share/ansible/openshift-ansible/roles/openshift_examples/files/examples/v1.3/ -cvf /tmp/openshift-ansible-bIBcjVF/openshift-examples.tar .", "failed": true, "msg": "[Errno 2] No such file or directory", "rc": 2} to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_3/upgrade.retry The ansible fails on running the examples. This tasks should not be critical and should not fail the entire installation. Could you please fix that? Also if running the upgrade from container itself, the ansible is not checking if tar is available or not. Could be there a check if tar is available? Version-Release number of selected component (if applicable): OpenShift Container Platform 3.3 Actual results: The upgrade fails on post.yml playbook on openshift_examples task. Expected results: The upgrade should skip the example tasks in order to finish the installation, but showing that upgrade was not able to upgrade the examples and this tasks should be executed manually. Additional info: Would be better if in docs could be information or known issue about containerized upgrade in container and openshift_examples. I got information that in order to skip it, the inventory file should contain openshift_install_examples=false.