** Impact **
Trying to assoicate a second network/vlanc to a tennant results in the
following traceback:
2012-03-11 12:23:31 CRITICAL nova [-] 'bool' object has no attribute 'decode'
(nova): TRACE: Traceback (most recent call last):
(nova): TRACE: File "/usr/bin/nova-manage", line 2201, in <module>
(nova): TRACE: main()
(nova): TRACE: File "/usr/bin/nova-manage", line 2182, in main
(nova): TRACE: fn_kwargs[k] = v.decode('utf-8')
(nova): TRACE: AttributeError: 'bool' object has no attribute 'decode'
This can be worked around by modifying the mysql database directly.
** Development Fix **
This has been addressed in https://review.openstack.org/6358 and fixed
in quantal.
** Stable Fix **
This has been addressed in https://review.openstack.org/7298.
** Test Case **
(As above)
I want to start an instance with two NICs:
NIC1: eth0 connected to network1 (10.10.1.0/24 vlan1)
NIC2: eth1 connected to network2 (10.10.2.0/24 vlan2)
Let's say that network1/vlan1 was already associated automatically to my
tenant.
nova-manage network modify --network 10.10.2.0/24 --project 10 --host
node1
** Regression Impact **
Minimal this is a corner case usage of Openstack.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/952176
Title:
[SRU] Cannot associate a second network/vlan to a tenant with "nova-
manage network modify"
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/952176/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
