# We verified latest rpm available is suitable, so just yum update.
- name: Upgrade packages
  action: "{{ ansible_pkg_mgr }} name={{ openshift.common.service_type }}-{{ component }}{{ openshift_pkg_version }} state=present"

- name: Ensure python-yaml present for config upgrade
  action: "{{ ansible_pkg_mgr }} name=PyYAML state=present"
  when: not openshift.common.is_atomic | bool

- name: Restart node service
  service: name="{{ openshift.common.service_type }}-node" state=restarted

# We verified latest rpm available is suitable, so just yum update.
- name: Upgrade packages
  action: "{{ ansible_pkg_mgr }} name={{ openshift.common.service_type }}-{{ component }}{{ openshift_pkg_version }} state=present"

- name: Ensure python-yaml present for config upgrade
  action: "{{ ansible_pkg_mgr }} name=PyYAML state=present"
  when: not openshift.common.is_atomic | bool

Stop restarting node after upgrading master rpms.
Stop restarting node after upgrading master rpms.

This looks to be causing a customer issue where some HA upgrades fail,
due to a missing EgressNetworkPolicy API. We update master rpms, we
don't restart services yet, but then restart node service which tries to
talk to an API that does not yet exist. (pending restart)

Restarting node here is very out of place and appears to not be
required.
