Bug 1628977

Description of problem:
When doing one OCP upgrade version (3.9 -> 3.10 for example) if we add the "openshift_hosted_manage_router" variable to inventory, as specified in the documentation it still upgrade and restart routers. when it should not manage or touch them:

https://docs.openshift.com/container-platform/3.4/install_config/install/advanced_install.html#configuring-dedicated-infrastructure-nodes

"If you do not intend to use OpenShift Container Platform to manage the registry and router, configure the following Ansible settings:

openshift_hosted_manage_registry=false
openshift_hosted_manage_router=false
"

It should not manage and perform the router upgrade version (and hence doing one router restart).

Version-Release number of the following components:
$ rpm -q openshift-ansible
openshift-ansible-3.9.33-1.git.56.19ba16e.el7.noarch

$ rpm -q ansible
ansible-2.4.4.0-1.el7ae.noarch

$ ansible --version
ansible 2.4.4.0
  config file = /home/jd07552/openshift-install/ansible.cfg
  configured module search path = [u'/home/jd07552/openshift-install/openshift-ansible/roles/lib_openshift/library', u'/home/jd07552/openshift-install/openshift-ansible/roles/lib_utils/library', u'/usr/share/ansible']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, May 31 2018, 09:41:32) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]

How reproducible:
In OCP 3.9 and higer
Steps to Reproduce:
1. Configure the "openshift_hosted_manage_router=false" variable in the inventory
2. Execute the ansible upgrade playbook
3. Existing running routers are upgraded to the new version and restarted 

Expected results:
Existing running routers should not be upgraded or managed in any way