New commit detected on ManageIQ/manageiq/fine:
Author: Nick Carboni <firstname.lastname@example.org>
AuthorDate: Mon Sep 25 09:49:53 2017 -0400
Commit: Satoe Imaishi <email@example.com>
CommitDate: Fri Sep 29 09:21:47 2017 -0400
Merge pull request #15762 from ailisp/proxy-not-work
Proxy support for cloning ansible repo and add provider
(cherry picked from commit 2526eb7300ee8e0ac0c44e4cb6950f095241fe53)
config/settings.yml | 8 ++++++++
lib/embedded_ansible.rb | 17 +++++++++++++++++
spec/lib/embedded_ansible_spec.rb | 31 +++++++++++++++++++++++++++++++
3 files changed, 56 insertions(+)
With a new environment I was able to verify the fix using the following steps:
1. Deploy appliance
2. Configure hostname + additional networking (IPv6 specific), configure database
3. Created SSH tunnels for proxy
4. Configure cfme http proxy
5. Enable, Disable, Enable Embedded Ansible
6. Add repo (successfully).
The enable, disable, enable dance was needed because of a chicken/egg problem with the settings file that we need to add the proxy information to.
/etc/tower/settings.yml doesn't exist until the tower installation is up and running. This is the file we need to edit. Tower also requires a restart for the changes in the file to take effect. So the following timeline should explain why we need a restart:
1. Enable Embedded Ansible
- This starts embedded ansible which creates the settings.yml file for the first time.
2. Restart Embedded Ansible (disable/enable)
- Before start we see that settings.yml is present, so we set the proxy settings
- Start embedded ansible
Given this, I think that the solution could use some improvement, but this should not hold up the release. Ideally I would like it if we could set the proxy settings in the inventory file when we first configure embedded ansible. That way there would be no need for the restart. Unfortunately I was not able to find any documentation on the tower side to indicate that this is possible.
I have created bug 1500034 to track improving this fix.
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.