Description of problem: Don't set OSE repo on master/nodes, atomic-openshift-installer upgrade to v3.1. the python exception for 'Error: No matching Packages to list' Version-Release number of selected component (if applicable): atomic-openshift-node-3.1.0.0-0.git.0.0e71938.el7aos.x86_64 How reproducible: always Steps to Reproduce: 1. Don't set OSE3.1 repo on master/nodes 2. atomic-openshift-installer upgrade Actual Result: TASK: [Determine available versions] ****************************************** changed: [192.168.1.48] TASK: [set_fact ] ************************************************************* fatal: [192.168.1.48] => Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ansible/runner/__init__.py", line 586, in _executor exec_rc = self._executor_internal(host, new_stdisummaryn) File "/usr/lib/python2.7/site-packages/ansible/runner/__init__.py", line 789, in _executor_internal return self._executor_internal_inner(host, self.module_name, self.module_args, inject, port, complex_args=complex_args) File "/usr/lib/python2.7/site-packages/ansible/runner/__init__.py", line 1013, in _executor_internal_inner complex_args = template.template(self.basedir, complex_args, inject, fail_on_undefined=self.error_on_undefined_vars) File "/usr/lib/python2.7/site-packages/ansible/utils/template.py", line 138, in template d[k] = template(basedir, v, templatevars, lookup_fatal, depth, expand_lists, convert_bare, fail_on_undefined, filter_fatal) File "/usr/lib/python2.7/site-packages/ansible/utils/template.py", line 122, in template varname = template_from_string(basedir, varname, templatevars, fail_on_undefined) File "/usr/lib/python2.7/site-packages/ansible/utils/template.py", line 371, in template_from_string res = jinja2.utils.concat(rf) File "<template>", line 9, in root File "/usr/lib64/python2.7/site-packages/yaml/__init__.py", line 93, in safe_load return load(stream, SafeLoader) File "/usr/lib64/python2.7/site-packages/yaml/__init__.py", line 71, in load return loader.get_single_data() File "/usr/lib64/python2.7/site-packages/yaml/constructor.py", line 37, in get_single_data node = self.get_single_node() File "/usr/lib64/python2.7/site-packages/yaml/composer.py", line 43, in get_single_node event.start_mark) ComposerError: expected a single document in the stream in "<string>", line 1, column 1: Error: No matching Packages to list ^ but found another document in "<string>", line 2, column 1: --- ^ Expected Result: atomic-openshift-installer should report error message and abort rather than exception. atomic-openshift-installer should report error messages such as "Can't found openshift 3.1 packages, please make sure your have subscript to openshift v3.1 " Additional info:
verified and pass TASK: [openshift_master_ca | Install the base package for admin tooling] ****** failed: [10.14.6.120] => {"changed": false, "failed": true, "rc": 0, "results": []} msg: No Package matching 'atomic-openshift' found available, installed or updated FATAL: all hosts have already failed -- aborting
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-2015:2492