See the referenced bug report. ENABLED_SERVICES is one I copied from an earlier post you made on this thread, and from the devstack logs (attached to the bug), it sure looks like it is trying to start it.
+ screen -S stack -p q-agt -X stuff 'sudo python /opt/stack/quantum/quantum/plugins/openvswitch/agent/ovs_quantum_agent.py --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini^M'
+ screen_it q-dhcp 'sudo python /opt/stack/quantum/bin/quantum-dhcp-agent --config-file /etc/quantum/quantum.conf --config-file=/etc/quantum/dhcp_agent.ini'
++ echo -ne '\015'
+ NL=$'\r'
+ is_service_enabled q-dhcp
+ services=q-dhcp
+ for service in '${services}'
+ [[ ,g-api,g-reg,key,n-api,n-cpu,n-sch,n-vnc,mysql,rabbit,openstackx,q-svc,quantum,q-agt,n-cpu,q-dhcp, =~ ,q-dhcp, ]]
+ return 0
+ screen_rc q-dhcp 'sudo python /opt/stack/quantum/bin/quantum-dhcp-agent --config-file /etc/quantum/quantum.conf --config-file=/etc/quantum/dhcp_agent.ini'
+ SCREENRC=/opt/stack/devstack/stack-screenrc
+ [[ ! -e /opt/stack/devstack/stack-screenrc ]]
+ grep q-dhcp /opt/stack/devstack/stack-screenrc
+ screen -S stack -X screen -t q-dhcp
+ sleep 1.5
+ [[ -n '' ]]
+ screen -S stack -p q-dhcp -X stuff 'sudo python /opt/stack/quantum/bin/quantum-dhcp-agent --config-file /etc/quantum/quantum.conf --config-file=/etc/quantum/dhcp_agent.ini^M'
+ NOVA_CONF_DIR=/etc/nova
+ [[ ! -d /etc/nova ]]
++ whoami
↧