SM:R3.1.1 build38:centos: Multi interface provisioning stuck at zoo config

SM:R3.1.1 build38:centos: Multi interface provisioning stuck at zoo config errors

With build R3.1.1 centos build 38 liberty, Multi interface provisioning stuck at zoo config errors

1) Install SM build 3.1.1 build 38 Liberty
2) Reimage the target with centos 72 (multi interface setup). Reimage happens succesfully (After working around the bug 1640064 SM: R3.1.1 build 38 After reimage , nodes are unable to connect to the SM in multi interface setup)
3) Initiate Provision with centos liberty contrail package build 38
4) Observe that the provision stuck with database_completed with following error

Nov 8 06:01:09 nodec35 puppet-agent[16929]: (/Stage[config]/Contrail::Config_cassandra/Exec[cassandra-env-update]/returns) executed successfully
Nov 8 06:01:09 nodec35 puppet-agent[16929]: executed setup-quantum-server-setup
Nov 8 06:01:09 nodec35 puppet-agent[16929]: (/Stage[config]/Contrail::Config::Setup_quantum_server_setup/Notify[executed setup-quantum-server-setup]/message) defined 'message' as 'executed setup-quantum-server-setup'
Nov 8 06:01:10 nodec35 puppet-agent[16929]: Could not start Service[zookeeper]: Execution of '/usr/bin/systemctl start zookeeper' returned 6: Failed to start zookeeper.service: Unit zookeeper.service failed to load: No such file or directory.
Nov 8 06:01:10 nodec35 puppet-agent[16929]: Wrapped exception:
Nov 8 06:01:10 nodec35 puppet-agent[16929]: Execution of '/usr/bin/systemctl start zookeeper' returned 6: Failed to start zookeeper.service: Unit zookeeper.service failed to load: No such file or directory.
Nov 8 06:01:10 nodec35 puppet-agent[16929]: (/Stage[config]/Contrail::Config::Database_service/Service[zookeeper]/ensure) change from stopped to running failed: Could not start Service[zookeeper]: Execution of '/usr/bin/systemctl start zookeeper' returned 6: Failed to start zookeeper.service: Unit zookeeper.service failed to load: No such file or directory.

Notes :
------
1) Provisioning with build 38 centos in single node is completed and does not hit the above issue
2) With previous build (Build 37) , bug https://bugs.launchpad.net/juniperopenstack/r3.1/+bug/1638814 was seen

Setup

SM : 10.204.217.160
host1 = 'root@10.204.221.58'
host2 = 'root@10.204.221.59'
host3 = 'root@10.204.221.60'
host4 = 'root@10.204.221.61'

env.roledefs = {
    'all': [host1, host2, host3, host4],
    'cfgm': [host1],
    'openstack': [host1],
    'control': [host1,host2],
    'compute': [host3,host4],
    'collector': [host2],
    'webui': [host2],
    'database': [host2],
    'build': [host_build],
}

env.hostnames = {
    'all': [ 'nodec35', 'nodec33', 'nodea4', 'nodec57']
}