Comment 0 for bug 1641585

contrail-schema fails to start during fab setup_all using contrail-networking package on R3.0.2.x build11.

2016-11-14 16:44:04:689586: [root@10.204.217.172] out: ======= Starting the services ======
2016-11-14 16:44:04:689658: [root@10.204.217.172] out: + for svc in '$msg_svc' '$web_svc' memcached
2016-11-14 16:44:04:689731: [root@10.204.217.172] out: + service rabbitmq-server restart
2016-11-14 16:44:04:689803: [root@10.204.217.172] out: unix:///tmp/supervisord_support_service.sock no such file
2016-11-14 16:44:04:790741: [root@10.204.217.172] out: + for svc in '$msg_svc' '$web_svc' memcached
2016-11-14 16:44:04:790865: [root@10.204.217.172] out: + service apache2 restart
2016-11-14 16:44:04:790944: [root@10.204.217.172] out: apache2: unrecognized service
2016-11-14 16:44:04:791019: [root@10.204.217.172] out: + for svc in '$msg_svc' '$web_svc' memcached
2016-11-14 16:44:04:791093: [root@10.204.217.172] out: + service memcached restart
2016-11-14 16:44:04:791166: [root@10.204.217.172] out: memcached: unrecognized service
2016-11-14 16:44:04:791239: [root@10.204.217.172] out: + service neutron-server restart
2016-11-14 16:44:04:791312: [root@10.204.217.172] out: neutron-server stop/waiting
2016-11-14 16:44:04:807196: [root@10.204.217.172] out: neutron-server start/running, process 19891
2016-11-14 16:44:04:823986: [root@10.204.217.172] out:
2016-11-14 16:44:04:840031:
2016-11-14 16:44:04:844423: [root@10.204.217.172] Executing task 'verify_cfgm'
2016-11-14 16:44:04:844985: [root@10.204.217.172] sudo: service supervisor-config status
2016-11-14 16:44:04:845223: [root@10.204.217.172] out: supervisor-config start/running, process 19190
2016-11-14 16:44:04:911348: [root@10.204.217.172] out:
2016-11-14 16:44:04:911550:
2016-11-14 16:44:04:911848: [root@10.204.217.172] sudo: service contrail-api status
2016-11-14 16:44:04:912070: [root@10.204.217.172] out: contrail-api:0 RUNNING pid 19212, uptime 0:00:24
2016-11-14 16:44:05:053121: [root@10.204.217.172] out:
2016-11-14 16:44:05:060687:
2016-11-14 16:44:05:067685: [root@10.204.217.172] sudo: service contrail-discovery status
2016-11-14 16:44:05:067918: [root@10.204.217.172] out: contrail-discovery:0 RUNNING pid 19393, uptime 0:00:19
2016-11-14 16:44:05:209514: [root@10.204.217.172] out:
2016-11-14 16:44:05:217156:
2016-11-14 16:44:05:223585: [root@10.204.217.172] sudo: service contrail-schema status
2016-11-14 16:44:05:223833: [root@10.204.217.172] out: contrail-schema FATAL Exited too quickly (process log may have details)
2016-11-14 16:44:05:373042: [root@10.204.217.172] out:
2016-11-14 16:44:05:374673:
2016-11-14 16:44:05:378899: [root@10.204.217.172] sudo: service contrail-schema status
2016-11-14 16:44:25:399503: [root@10.204.217.172] out: contrail-schema FATAL Exited too quickly (process log may have details)
2016-11-14 16:44:25:513619: [root@10.204.217.172] out:
2016-11-14 16:44:25:521738:
2016-11-14 16:44:25:527213: [root@10.204.217.172] sudo: service contrail-schema status
2016-11-14 16:44:45:547971: [root@10.204.217.172] out: contrail-schema FATAL Exited too quickly (process log may have details)
2016-11-14 16:44:45:686330: [root@10.204.217.172] out:
2016-11-14 16:44:45:686563:
2016-11-14 16:44:45:686704: [root@10.204.217.172] sudo: service contrail-schema status
2016-11-14 16:45:05:704055: [root@10.204.217.172] out: contrail-schema FATAL Exited too quickly (process log may have details)
2016-11-14 16:45:05:825653: [root@10.204.217.172] out:
2016-11-14 16:45:05:825881:
2016-11-14 16:45:05:831655: [root@10.204.217.172] sudo: service contrail-schema status
2016-11-14 16:45:25:856442: [root@10.204.217.172] out: contrail-schema FATAL Exited too quickly (process log may have details)
2016-11-14 16:45:25:985384: [root@10.204.217.172] out:
2016-11-14 16:45:25:989995:
2016-11-14 16:45:26:001889: [root@10.204.217.172] sudo: service contrail-schema status
2016-11-14 16:45:46:013920: [root@10.204.217.172] out: contrail-schema FATAL Exited too quickly (process log may have details)
2016-11-14 16:45:46:128545: [root@10.204.217.172] out:
2016-11-14 16:45:46:136151:
2016-11-14 16:45:46:143273: [root@10.204.217.172] sudo: service contrail-schema status
2016-11-14 16:46:06:152227: [root@10.204.217.172] out: contrail-schema FATAL Exited too quickly (process log may have details)
2016-11-14 16:46:06:366040: [root@10.204.217.172] out:
2016-11-14 16:46:06:366266:
2016-11-14 16:46:06:366604: [root@10.204.217.172] sudo: service contrail-schema status
2016-11-14 16:46:26:385599: [root@10.204.217.172] out: contrail-schema FATAL Exited too quickly (process log may have details)
2016-11-14 16:46:26:522646: [root@10.204.217.172] out:
2016-11-14 16:46:26:522837:
2016-11-14 16:46:26:524469: [root@10.204.217.172] sudo: service contrail-schema status
2016-11-14 16:46:46:537179: [root@10.204.217.172] out: contrail-schema FATAL Exited too quickly (process log may have details)
2016-11-14 16:46:46:650346: [root@10.204.217.172] out:
2016-11-14 16:46:46:657828:
2016-11-14 16:46:46:664603: [root@10.204.217.172] sudo: service contrail-schema status
2016-11-14 16:47:06:677480: [root@10.204.217.172] out: contrail-schema FATAL Exited too quickly (process log may have details)
2016-11-14 16:47:06:813744: [root@10.204.217.172] out:
2016-11-14 16:47:06:813989:

The setup details are:
ontrol Nodes : [u'nodei13-vm2', u'nodei14-vm2']
Compute Nodes : [u'nodea12', u'nodea15', u'nodea17']
Openstack Node : [u'nodek7-vm2']
WebUI Node : nodei13-vm2
Analytics Nodes : [u'nodei13-vm2']
Database Nodes : [u'nodei14-vm2']
Physical Devices : [u'hooper', u"'hooper'"]

The ip-address of the VMs are
nodei13-vm2: 10.204.217.172
nodei14-vm2: 10.204.217.179
nodek7-vm2: 10.204.216.111