gflag --pidfile isn't working
Bug #712681 reported by
Christian Berendt
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Christian Berendt |
Bug Description
We're starting the all nova processes like nova-compute --pidfile=
--pidfile: pidfile to use for this service
32459 pts/6 S 0:03 /usr/bin/python /usr/bin/
drwxrwxrwx 2 nova root 4096 Feb 3 14:26 nova
Related branches
lp://staging/~berendt/nova/lp712681
- Todd Willey (community): Approve
- Devin Carlen (community): Approve
- Thierry Carrez (community): Approve
-
Diff: 2496 lines (+0/-2320)32 files modifiedcontrib/puppet/files/etc/default/nova-compute (+0/-1)
contrib/puppet/files/etc/default/nova-volume (+0/-1)
contrib/puppet/files/etc/issue (+0/-5)
contrib/puppet/files/etc/libvirt/qemu.conf (+0/-170)
contrib/puppet/files/etc/lvm/lvm.conf (+0/-463)
contrib/puppet/files/etc/nova.conf (+0/-28)
contrib/puppet/files/production/boto.cfg (+0/-3)
contrib/puppet/files/production/genvpn.sh (+0/-35)
contrib/puppet/files/production/libvirt.qemu.xml.template (+0/-35)
contrib/puppet/files/production/my.cnf (+0/-137)
contrib/puppet/files/production/nova-iptables (+0/-187)
contrib/puppet/files/production/nova-iscsi-dev.sh (+0/-19)
contrib/puppet/files/production/setup_data.sh (+0/-6)
contrib/puppet/files/production/slap.sh (+0/-261)
contrib/puppet/fileserver.conf (+0/-8)
contrib/puppet/manifests/classes/apt.pp (+0/-1)
contrib/puppet/manifests/classes/issue.pp (+0/-14)
contrib/puppet/manifests/classes/kern_module.pp (+0/-34)
contrib/puppet/manifests/classes/loopback.pp (+0/-6)
contrib/puppet/manifests/classes/lvm.pp (+0/-8)
contrib/puppet/manifests/classes/lvmconf.pp (+0/-8)
contrib/puppet/manifests/classes/nova.pp (+0/-464)
contrib/puppet/manifests/classes/swift.pp (+0/-7)
contrib/puppet/manifests/site.pp (+0/-120)
contrib/puppet/manifests/templates.pp (+0/-21)
contrib/puppet/puppet.conf (+0/-11)
contrib/puppet/templates/haproxy.cfg.erb (+0/-39)
contrib/puppet/templates/monitrc-nova-api.erb (+0/-138)
contrib/puppet/templates/nova-iptables.erb (+0/-10)
contrib/puppet/templates/production/nova-common.conf.erb (+0/-55)
contrib/puppet/templates/production/nova-nova.conf.erb (+0/-21)
nova/service.py (+0/-4)
Changed in nova: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in nova: | |
assignee: | nobody → Christian Berendt (berendt) |
status: | Confirmed → In Progress |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → 2011.2 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
--pidfile is no longer a supported flag in Bexar Nova. Ever since paste.deploy was introduced, although FLAGS.pidfile exists, it doesn't do anything anymore for the bin/* programs.
Two bugs are evident:
* FLAGS.pidfile should be removed. It is obselete and confusing for users who see it on the --help output
* No documentation exists for using the configuration file examples in etc/ (for instance, the etc/nova-api.conf file).
You can control the pidfile used in startup by using paster. Since Nova is now using paste.deploy, you can refer to this documentation on starting/ stopping/ reloading server daemons with paste.script:
http:// pythonpaste. org/script/
Cheers,
jay