Bug 1450798 - OCP 3.6 Installation failed on Atomic Host platform
Summary: OCP 3.6 Installation failed on Atomic Host platform
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Giuseppe Scrivano
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-15 08:11 UTC by Weihua Meng
Modified: 2017-08-16 19:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-10 05:24:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1716 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 09:02:50 UTC

Description Weihua Meng 2017-05-15 08:11:45 UTC
Description of problem:
OCP 3.6 Installation failed on Atomic Host platform, 
TASK [openshift_version : Get available atomic-openshift version]

Version-Release number of selected component (if applicable):
openshift-ansible-3.6.68-1.git.0.9cbe2b7.el7.noarch.rpm

How reproducible:
always

Steps to Reproduce:
1. install OCP 3.6 on Atomic Host platform by latest openshift-ansible 
2.
3.

Actual results:
Installation failed.
TASK [openshift_version : Get available atomic-openshift version] **************
Monday 15 May 2017  01:39:08 +0000 (0:00:00.096)       0:02:15.876 ************ 
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: OSError: [Errno 2] No such file or directory
fatal: [host-8-174-75.host.centralci.eng.rdu2.redhat.com]: FAILED! => {
    "changed": false, 
    "failed": true, 
    "module_stderr": "Traceback (most recent call last):\n  File \"/tmp/ansible_MlRDGm/ansible_module_repoquery.py\", line 635, in <module>\n    main()\n  File \"/tmp/ansible_MlRDGm/ansible_module_repoquery.py\", line 626, in main\n    rval = Repoquery.run_ansible(module.params, module.check_mode)\n  File \"/tmp/ansible_MlRDGm/ansible_module_repoquery.py\", line 586, in run_ansible\n    results = repoquery.repoquery()\n  File \"/tmp/ansible_MlRDGm/ansible_module_repoquery.py\", line 545, in repoquery\n    rval = self._repoquery_cmd(repoquery_cmd, True, 'raw')\n  File \"/tmp/ansible_MlRDGm/ansible_module_repoquery.py\", line 383, in _repoquery_cmd\n    returncode, stdout, stderr = _run(cmds)\n  File \"/tmp/ansible_MlRDGm/ansible_module_repoquery.py\", line 354, in _run\n    stderr=subprocess.PIPE)\n  File \"/usr/lib64/python2.7/subprocess.py\", line 711, in __init__\n    errread, errwrite)\n  File \"/usr/lib64/python2.7/subprocess.py\", line 1327, in _execute_child\n    raise child_exception\nOSError: [Errno 2] No such file or directory\n", 
    "module_stdout": ""
}

MSG:

MODULE FAILURE


Expected results:
installation SUCCESS

Additional info:
Containerized installation on RHEL platform SUCCESS.
RPM installation SUCCESS

Comment 1 Scott Dodson 2017-05-15 13:11:03 UTC
https://github.com/openshift/openshift-ansible/pull/4189 I think addresses this?

Comment 2 Giuseppe Scrivano 2017-05-15 14:11:44 UTC
yes, https://github.com/openshift/openshift-ansible/pull/4189 addresses this

Comment 3 Giuseppe Scrivano 2017-05-17 09:51:33 UTC
https://github.com/openshift/openshift-ansible/pull/4189 merged

Comment 5 Weihua Meng 2017-05-24 00:52:40 UTC
Verified with openshift-ansible-3.6.80-1.git.0.807fc98.el7.noarch.rpm
Fixed.
<---snip--->
TASK [openshift_version : Get available atomic-openshift version] **************
Tuesday 23 May 2017  22:39:50 +0000 (0:00:00.220)       0:01:48.389 *********** 
skipping: [host-8-174-62.host.centralci.eng.rdu2.redhat.com] => {
    "changed": false, 
    "skip_reason": "Conditional check failed", 
    "skipped": true
}
<---snip--->
Finished: SUCCESS

Comment 7 errata-xmlrpc 2017-08-10 05:24:06 UTC
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/RHEA-2017:1716


Note You need to log in before you can comment on or make changes to this bug.