Comment 3 for bug 1664650

So I tried this on a fairly recent ocata env.
We start the overcloud deploy against an existing overcloud at the following time:
2017-02-14 18:25:45Z [Networks]: UPDATE_IN_PROGRESS state changed

In the attached "services-being-restarted" file I grepped for any service that was restarted on overcloud-controller-0.

So looking at http I see the following in the puppet debug logs:
2017-02-14 18:32:26 +0000 Puppet (info): Computing checksum on file /etc/httpd/conf/ports.conf
2017-02-14 18:32:26 +0000 Puppet (info): FileBucket got a duplicate file {md5}8c87b9f11b8696570777c0f491819160
2017-02-14 18:32:26 +0000 /Stage[main]/Apache/Concat[/etc/httpd/conf/ports.conf]/File[/etc/httpd/conf/ports.conf] (info): Filebucketed /etc/httpd/conf/ports.conf to puppet with sum 8c87b9f11
b8696570777c0f491819160
2017-02-14 18:32:26 +0000 /Stage[main]/Apache/Concat[/etc/httpd/conf/ports.conf]/File[/etc/httpd/conf/ports.conf]/content (notice): content changed '{md5}8c87b9f11b8696570777c0f491819160' to
 '{md5}737e2fe64473f2781e3c99022a27b6ff'
2017-02-14 18:32:26 +0000 /Stage[main]/Apache/Concat[/etc/httpd/conf/ports.conf]/File[/etc/httpd/conf/ports.conf] (debug): The container Concat[/etc/httpd/conf/ports.conf] will propagate my
refresh event
2017-02-14 18:32:26 +0000 /Stage[main]/Apache/Concat[/etc/httpd/conf/ports.conf]/File[/etc/httpd/conf/ports.conf] (debug): The container /etc/httpd/conf/ports.conf will propagate my refresh
event
2017-02-14 18:32:26 +0000 /etc/httpd/conf/ports.conf (debug): The container Concat[/etc/httpd/conf/ports.conf] will propagate my refresh event
2017-02-14 18:32:26 +0000 Concat[/etc/httpd/conf/ports.conf] (debug): The container Class[Apache] will propagate my refresh event
2017-02-14 18:32:26 +0000 Concat[/etc/httpd/conf/ports.conf] (info): Scheduling refresh of Class[Apache::Service]
2017-02-14 18:32:26 +0000 Class[Apache] (debug): The container Stage[main] will propagate my refresh event
2017-02-14 18:32:26 +0000 Class[Apache::Service] (info): Scheduling refresh of Service[httpd]
2017-02-14 18:32:26 +0000 Puppet (debug): Executing: '/usr/bin/systemctl is-active httpd'
2017-02-14 18:32:26 +0000 Puppet (debug): Executing: '/usr/bin/systemctl is-enabled httpd'
2017-02-14 18:32:26 +0000 Puppet (debug): Executing: '/usr/bin/systemctl is-active httpd'
2017-02-14 18:32:26 +0000 Puppet (debug): Executing: '/usr/bin/systemctl restart httpd'
2017-02-14 18:32:46 +0000 /Stage[main]/Apache::Service/Service[httpd] (notice): Triggered 'refresh' from 1 events
2017-02-14 18:32:46 +0000 /Stage[main]/Apache::Service/Service[httpd] (debug): The container Class[Apache::Service] will propagate my refresh event
2017-02-14 18:32:46 +0000 Class[Apache::Service] (debug): The container Stage[main] will propagate my refresh event
2017-02-14 18:32:46 +0000 /Stage[main]/Keystone::Deps/Anchor[keystone::service::end] (notice): Triggered 'refresh' from 7 events
2017-02-14 18:32:46 +0000 /Stage[main]/Keystone::Deps/Anchor[keystone::service::end] (debug): The container Class[Keystone::Deps] will propagate my refresh event
2017-02-14 18:32:46 +0000 Class[Keystone::Deps] (debug): The container Stage[main] will propagate my refresh event

At least for httpd it seems we are hitting this:
https://bugs.launchpad.net/puppet-horizon/+bug/1191647

But it seems a few services are affected and we will need to look at all of them