Fix functional issues after nosdn deployment 71/55071/3
authorTim Rozet <trozet@redhat.com>
Fri, 6 Apr 2018 17:44:27 +0000 (13:44 -0400)
committerTim Rozet <trozet@redhat.com>
Mon, 9 Apr 2018 17:43:13 +0000 (13:43 -0400)
After deploying with nosdn, it looks like there is some out of state
issue between the services.  First guess looks like something is going
on with the services and timing of registering to each other through
rabbit.  Simply restarting the services seems to sync them back up
correctly.

Change-Id: I417911067c841725ee12eb9354e5759054724e01
Signed-off-by: Tim Rozet <trozet@redhat.com>
lib/ansible/playbooks/post_deploy_overcloud.yml

index af1c648..13623f2 100644 (file)
         owner: root
         group: tacker
       become: yes
+    - name: Restart Controller Neutron/Nova Services (Pike Workaround)
+      shell: "systemctl restart {{ item }}"
+      become: yes
+      when:
+        - "'controller' in ansible_hostname"
+        - os_version == 'pike'
+      with_items:
+        - neutron-server
+        - openstack-nova-api
+        - openstack-nova-scheduler
+        - openstack-nova-conductor
+    - name: Restart Compute Nova Compute (Pike Workaround)
+      shell: "systemctl restart openstack-nova-compute"
+      become: yes
+      when:
+        - "'compute' in ansible_hostname"
+        - os_version == 'pike'