Hey Tracy. Have you tried to use the images from https://hub.docker.com/r/openshift/origin-ansible/ ? Best,
-- Mateus Caruccio / Master of Puppets GetupCloud.com We make the infrastructure invisible Gartner Cool Vendor 2017 2018-04-26 0:15 GMT-03:00 Tracy Reed <tr...@ultraviolet.org>: > > Is there really no version of ansible currently suitable for running > atomic-openshift-installer install? > > I keep plowing ahead trying to get openshift up and running and keep > running into weird obstacles. Possibly entirely my fault but I'm keen to > get this up and running! > > Most recently while running the openshift installer I ran into this: > > https://pastebin.com/35Ra7ZKH > > and googling turns up this: > > https://bugzilla.redhat.com/show_bug.cgi?id=1499627 > > so I uninstall my latest version ansible which is apparently not > compatible and install ansible-2.3.2.0-2.el7.noarch. I run the installer > again and I get this: > > https://pastebin.com/qJDFGbVT > > for which google turns up this: > > https://github.com/ansible/ansible/issues/14991 > > which says "you have an old version of the setup module and are trying > to run it with a new version of the module_utils." > > So the first version of ansible I tried, the most recent in the rhel > repo, is apparently too new. But the recommended version in that first > bug report is too old. So maybe I now need to find the sweet spot > version of ansible which works? The next version up is > ansible-2.4.0.0-5.el7.noarch so I try that. > > The installer says: > > athering information from hosts... > [DEPRECATION WARNING]: 'include' for playbook includes. You should use > 'import_playbook' instead. This feature will be removed in version 2.8. > Deprecation warnings can be disabled by setting > deprecation_warnings=False in ansible.cfg. > ERROR! Unexpected Exception, this is probably a bug: 'CallbackModule' > object has no attribute 'set_options' > There was a problem fetching the required information. Please see > /tmp/ansible.log for details. > > and the log contains: > > https://pastebin.com/QB7JVEf3 > > So the next version of ansible is 2.4.1.0-1.el7 so I do yum install > 2.4.1.0-1.el7 and try running the installer again: > > atomic-openshift-installer install > > which gets me: > > Gathering information from hosts... > [DEPRECATION WARNING]: 'include' for playbook includes. You should use > 'import_playbook' instead. This feature will be removed in version 2.8. > Deprecation warnings can be disabled by setting > deprecation_warnings=False in ansible.cfg. > [DEPRECATION WARNING]: default callback, does not support setting > 'options', it will work for now, but this will be required in the > future and should be updated, see the 2.4 porting guide for details.. > This feature will be removed in > version 2.9. Deprecation warnings can be disabled by setting > deprecation_warnings=False in ansible.cfg. > [WARNING]: Failure using method (v2_playbook_on_start) in callback > plugin (<ansible.plugins.callback.facts_callback.CallbackModule object > at 0x7fa589c60fd0>): playbook_on_start() takes exactly 1 argument (2 > given) > [WARNING]: Failure using method (v2_runner_on_ok) in callback plugin > (<ansible.plugins.callback.facts_callback.CallbackModule object at > 0x7fa589c60fd0>): runner_on_ok() takes exactly 3 arguments (2 given) > [WARNING]: Failure using method (v2_runner_on_failed) in callback > plugin (<ansible.plugins.callback.facts_callback.CallbackModule > object at 0x7fa589c60fd0>): runner_on_failed() takes at least 3 > arguments (3 given) > There was a problem fetching the required information. Please see > /tmp/ansible.log for details. > > https://pastebin.com/MuZXjA9g > > so I try the next version of ansible: > > yum install ansible-2.4.2.0-2.el7.noarch > > and run the installer again which results in: > > Gathering information from hosts... > [DEPRECATION WARNING]: 'include' for playbook includes. You should use > 'import_playbook' instead. This feature will be removed in version 2.8. > Deprecation warnings can be disabled by setting > deprecation_warnings=False in ansible.cfg. > [DEPRECATION WARNING]: default callback, does not support setting > 'options', it will work for now, but this will be required in the > future and should be updated, see the 2.4 porting guide for details.. > This feature will be removed in > version 2.9. Deprecation warnings can be disabled by setting > deprecation_warnings=False in ansible.cfg. > [WARNING]: Failure using method (v2_playbook_on_start) in callback > plugin (<ansible.plugins.callback.facts_callback.CallbackModule object > at 0x7f2527601b10>): playbook_on_start() takes exactly 1 argument (2 > given) > [WARNING]: Failure using method (v2_runner_on_ok) in callback plugin > (<ansible.plugins.callback.facts_callback.CallbackModule object at > 0x7f2527601b10>): runner_on_ok() takes exactly 3 arguments (2 given) > [WARNING]: Failure using method (v2_runner_on_failed) in callback > plugin (<ansible.plugins.callback.facts_callback.CallbackModule > object at 0x7f2527601b10>): runner_on_failed() takes at least 3 > arguments (3 given) > There was a problem fetching the required information. Please see > /tmp/ansible.log for details. > > https://pastebin.com/18AF1SJT > > And now the only remaining version is the latest which I tried > originally. Just for kicks I try it again: > > Gathering information from hosts... > [DEPRECATION WARNING]: 'include' for playbook includes. You should use > 'import_playbook' instead. This feature will be removed in version 2.8. > Deprecation warnings can be disabled by setting > deprecation_warnings=False in ansible.cfg. > [DEPRECATION WARNING]: default callback, does not support setting > 'options', it will work for now, but this will be required in the > future and should be updated, see the 2.4 porting guide for details.. > This feature will be removed in > version 2.9. Deprecation warnings can be disabled by setting > deprecation_warnings=False in ansible.cfg. > [WARNING]: Failure using method (v2_playbook_on_start) in callback > plugin (<ansible.plugins.callback.facts_callback.CallbackModule object > at 0x7fe224412a90>): playbook_on_start() takes exactly 1 argument (2 > given) > [WARNING]: Failure using method (v2_runner_on_ok) in callback plugin > (<ansible.plugins.callback.facts_callback.CallbackModule object at > 0x7fe224412a90>): runner_on_ok() takes exactly 3 arguments (2 given) > [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead > of using `result|version_compare` instead use `result is > version_compare`. This feature will be removed in version 2.9. > Deprecation warnings can be disabled by setting > deprecation_warnings=False in ansible.cfg. > [DEPRECATION WARNING]: Using tests as filters is deprecated. Instead > of using `result|version_compare` instead use `result is > version_compare`. This feature will be removed in version 2.9. > Deprecation warnings can be disabled by setting > deprecation_warnings=False in ansible.cfg. > [WARNING]: Failure using method (v2_runner_on_failed) in callback > plugin (<ansible.plugins.callback.facts_callback.CallbackModule > object at 0x7fe224412a90>): runner_on_failed() takes at least 3 > arguments (3 given) > There was a problem fetching the required information. Please see > /tmp/ansible.log for details. > > > https://pastebin.com/bNJPTExP > > Same error as the original error. So at least it's repeatable. > > Is there really no version of ansible currently suitable for > installing openshift? What am I doing wrong here? > > Any ideas are greatly appreciated! > > -- > Tracy Reed > http://tracyreed.org > Digital signature attached for your safety. > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
