Must start quantum-dhcp-agent by hand first time after devstack install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Critical
|
Aaron Rosen |
Bug Description
Steps to reproduce:
- Fresh install of Ubuntu 12.04 server (dual homed, eth0 is setup via DHCP, eth1 is configured with 192.168.4.0 net and has static IP 192.168.4.1)
- Download latest devstack
- Create the following localrc in the devstac directory:
HOST_IP=192.168.4.1
FLAT_INTERFACE=eth1
FIXED_RANGE=
FIXED_NETWORK_
FLOATING_
MULTI_HOST=True
Q_INTERFACE=eth1
LOGFILE=
ADMIN_PASSWORD=
MYSQL_PASSWORD=
RABBIT_
SERVICE_
SERVICE_
LIBVIRT_
ENABLED_
Q_PLUGIN=
- sudo ./stack.sh
Expected results:
dnsmasq and quantum-dhcp-agent are running
Observed results:
Neither is running. But they can be started by hand, e.g.,
$ sudo python /opt/stack/
Changed in devstack: | |
status: | New → Incomplete |
Changed in quantum: | |
status: | New → Incomplete |
no longer affects: | devstack |
Changed in quantum: | |
importance: | Undecided → Critical |
milestone: | none → folsom-rc1 |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | folsom-rc1 → 2012.2 |
Also, if I reboot the host, and re-run devstack, the services start without intervention, so this looks to be a start state sort of bug with respect to installation.