I was able to reproduce this bug in the following manner:
0. in nova.conf: "network_manager = nova.network.manager.FlatManager" 1. `nova network-create --fixed-range-v6 2001:db8:dead:beef::/64 ipv6net` 2. `nova boot --image $IMAGE --flavor $FLAVOR --nic net-id=$NET-ID new-server` 3. a. `nova list`. Observe new-server in ERROR state. b. `nova show`. fault is "{u'message': u'NoValidHost', u'code': 500, u'created': u'2013-01-30T17:38:57Z'}" c. Observe error "NovaException: v4 subnets are required for legacy nw_info" in nova-compute logs.
I will begin working on a fix.
I was able to reproduce this bug in the following manner:
0. in nova.conf: "network_manager = nova.network. manager. FlatManager" dead:beef: :/64 ipv6net` 01-30T17: 38:57Z' }"
1. `nova network-create --fixed-range-v6 2001:db8:
2. `nova boot --image $IMAGE --flavor $FLAVOR --nic net-id=$NET-ID new-server`
3. a. `nova list`. Observe new-server in ERROR state.
b. `nova show`. fault is "{u'message': u'NoValidHost', u'code': 500, u'created': u'2013-
c. Observe error "NovaException: v4 subnets are required for legacy nw_info" in nova-compute logs.
I will begin working on a fix.