This was hit together with bug 1275986 and the cause and the fix could be similar or the same for these two bugs, but we're not sure of that yet, so we agreed to report this separately for now. We hit this issue on two environments. os-collect-config journal: lis 10 09:32:32 overcloud-controller-0.localdomain os-collect-config[1259]: Error: /Stage[main]/Nova::Consoleauth/Nova::Generic_service[consoleauth]/Service[nova-consoleauth]: Failed to call refresh: Could not restart Service[nova-consoleauth]: Execution of '/usr/bin/systemctl restart openstack-nova-consoleauth' returned 1: Job for openstack-nova-consoleauth.service canceled. lis 10 09:32:32 overcloud-controller-0.localdomain os-collect-config[1259]: Error: /Stage[main]/Nova::Consoleauth/Nova::Generic_service[consoleauth]/Service[nova-consoleauth]: Could not restart Service[nova-consoleauth]: Execution of '/usr/bin/systemctl restart openstack-nova-consoleauth' returned 1: Job for openstack-nova-consoleauth.service canceled. lis 10 09:32:32 overcloud-controller-0.localdomain os-collect-config[1259]: Wrapped exception: lis 10 09:32:32 overcloud-controller-0.localdomain os-collect-config[1259]: Execution of '/usr/bin/systemctl restart openstack-nova-consoleauth' returned 1: Job for openstack-nova-consoleauth.service canceled. lis 10 09:32:32 overcloud-controller-0.localdomain os-collect-config[1259]: Error: /Stage[main]/Apache::Service/Service[httpd]: Failed to call refresh: Could not restart Service[httpd]: Execution of '/usr/bin/systemctl restart httpd' returned 1: Job for httpd.service canceled. lis 10 09:32:32 overcloud-controller-0.localdomain os-collect-config[1259]: Error: /Stage[main]/Apache::Service/Service[httpd]: Could not restart Service[httpd]: Execution of '/usr/bin/systemctl restart httpd' returned 1: Job for httpd.service canceled. lis 10 09:32:32 overcloud-controller-0.localdomain os-collect-config[1259]: Wrapped exception: lis 10 09:32:32 overcloud-controller-0.localdomain os-collect-config[1259]: Execution of '/usr/bin/systemctl restart httpd' returned 1: Job for httpd.service canceled. nova-consoleauth journal: [root@overcloud-controller-0 ~]# journalctl -u openstack-nova-consoleauth -- Logs begin at Út 2015-11-10 07:17:50 EST, end at Út 2015-11-10 12:11:16 EST. -- lis 10 07:31:02 overcloud-controller-0.localdomain systemd[1]: Starting Cluster Controlled openstack-nova-consoleauth... lis 10 07:31:09 overcloud-controller-0.localdomain systemd[1]: Started Cluster Controlled openstack-nova-consoleauth. lis 10 09:09:50 overcloud-controller-0.localdomain systemd[1]: Stopping OpenStack Nova VNC console auth Server... lis 10 09:09:51 overcloud-controller-0.localdomain systemd[1]: Stopped OpenStack Nova VNC console auth Server. lis 10 09:24:36 overcloud-controller-0.localdomain systemd[1]: Starting Cluster Controlled openstack-nova-consoleauth... lis 10 09:24:38 overcloud-controller-0.localdomain systemd[1]: Started Cluster Controlled openstack-nova-consoleauth. lis 10 09:31:52 overcloud-controller-0.localdomain systemd[1]: Stopping Cluster Controlled openstack-nova-consoleauth... lis 10 09:31:53 overcloud-controller-0.localdomain systemd[1]: Starting Cluster Controlled openstack-nova-consoleauth... lis 10 09:31:55 overcloud-controller-0.localdomain systemd[1]: Stopping Cluster Controlled openstack-nova-consoleauth... lis 10 09:31:55 overcloud-controller-0.localdomain systemd[1]: Stopped Cluster Controlled openstack-nova-consoleauth. lis 10 09:31:57 overcloud-controller-0.localdomain systemd[1]: Starting Cluster Controlled openstack-nova-consoleauth... lis 10 09:31:59 overcloud-controller-0.localdomain systemd[1]: Started Cluster Controlled openstack-nova-consoleauth.
jistr, assigning this one to you as I think it will be fixed under the larger umbrella of fixing pacemaker/puppet service restart issues
I did several updates for both 7.0 -> 7.2 and 7.1 -> 7.2 and I didn't hit the issue reported here so I will move this to verified.
This bug is almost same issue as bug 1275986. The use case has been already covered by Marius (see Comment 3).
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. https://access.redhat.com/errata/RHBA-2015:2651