nova-common 2012.1~e2-0ubuntu2 installation fails

Bug #905464 reported by Adam Gandelman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nova (Ubuntu)
Fix Released
High
Chuck Short

Bug Description

nova-common 2012.1~e2-0ubuntu2 . The added --libvirt_use_virtio_for_bridges option was added with =True argument, but it is not valid syntax.

Adding new user `nova' (UID 105) with group `nova' ...
Not creating home directory `/var/lib/nova'.
Usage: nova-manage [options]
nova-manage: error: --libvirt_use_virtio_for_bridges option does not take a value

Dave Walker (davewalker)
Changed in nova (Ubuntu):
importance: Undecided → High
status: New → Triaged
milestone: none → precise-alpha-2
Revision history for this message
Adam Gandelman (gandelman-a) wrote :

Fixed in 2012.1~e2-0ubuntu2

Changed in nova (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
shake.chen (shake-chen) wrote :

hi

the bug seem not fix.

as my know, Nova have no openstackx.

I use ubuntu 12.04 alpha 2,

python2.7/dist-packages/migrate/versioning/util/__init__.py:162
Setting up nova-ajax-console-proxy (2012.1~e4~20120203.12454-0ubuntu1) ...
nova-ajax-console-proxy start/running, process 6629
Setting up nova-api (2012.1~e4~20120203.12454-0ubuntu1) ...
nova-api start/running, process 6659
Setting up nova-objectstore (2012.1~e4~20120203.12454-0ubuntu1) ...
nova-objectstore start/running, process 6693
Setting up nova-scheduler (2012.1~e4~20120203.12454-0ubuntu1) ...
nova-scheduler start/running, process 6723
Setting up nova-vncproxy (2012.1~e4~20120203.12454-0ubuntu1) ...
nova-vncproxy start/running, process 6757
Setting up openstackx (0.2+git20120120-0ubuntu1) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
nova-api stop/waiting
nova-api start/running, process 6817
Usage: nova-manage [options]

nova-manage: error: --force_dhcp_release option does not take a value
stop: Unknown instance:
nova-api start/running, process 6839
nova-scheduler stop/waiting
nova-scheduler start/running, process 6850
nova-objectstore stop/waiting
nova-objectstore start/running, process 6861
nova-vncproxy stop/waiting
nova-vncproxy start/running, process 6872
nova-ajax-console-proxy stop/waiting
nova-ajax-console-proxy start/running, process 6883
Usage: nova-manage [options]

nova-manage: error: --force_dhcp_release option does not take a value
Usage: nova-manage [options]

nova-manage: error: --force_dhcp_release option does not take a value
root@node34:~/openstack-setup# ./nova-

Revision history for this message
Adam Gandelman (gandelman-a) wrote :

@shake-chen,

Thanks for reporting. Are you hitting this on a new installation of packages or upgrading from a previous version? If an upgrade, does removing the '=True' from --force_dhcp_release in /etc/nova/nova.conf resolve the issue for you? The config file that is shipped with a the newest packages has been updated, but if you are upgrading from a previous version, you'll need to change this manually as apt will not overwrite your existing, custom config file with the current, packaged version unless instructed to do so.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.