I reverted the latest snapshot and we can see the following on the node with separate keystone service:
root@node-3:/etc/fuel/plugins/detach-keystone-1.0# md5sum keystone-controller.pp 5035319a2ecd00d5f0aba1fafed83a8a keystone-controller.pp
and we can see that we have another version of this puppet manifest in http://jenkins-product.srt.mirantis.net:8080/job/build-fuel-plugins/lastSuccessfulBuild/artifact/built_plugins/:
xwizard@DFldslr:~/detach-keystone-1.0/deployment_scripts$ md5sum keystone-controller.pp ee0eda41c3538e1c5e82c128b2bd1842 keystone-controller.pp
but on master node: [root@nailgun deployment_scripts]# md5sum keystone-controller.pp 5035319a2ecd00d5f0aba1fafed83a8a keystone-controller.pp
I reverted the latest snapshot and we can see the following on the node with separate keystone service:
root@node- 3:/etc/ fuel/plugins/ detach- keystone- 1.0# md5sum keystone- controller. pp 5f0aba1fafed83a 8a keystone- controller. pp
5035319a2ecd00d
and we can see that we have another version of this puppet manifest in http:// jenkins- product. srt.mirantis. net:8080/ job/build- fuel-plugins/ lastSuccessfulB uild/artifact/ built_plugins/:
xwizard@ DFldslr: ~/detach- keystone- 1.0/deployment_ scripts$ md5sum keystone- controller. pp c5e82c128b2bd18 42 keystone- controller. pp
ee0eda41c3538e1
but on master node: scripts] # md5sum keystone- controller. pp 5f0aba1fafed83a 8a keystone- controller. pp
[root@nailgun deployment_
5035319a2ecd00d