Multiple Subnets Per Network

I have configured a flat provider network and subnets that map to our colo network:
quantum net-create net1 \
       --shared \
       --provider:network_type flat \
       --provider:physical_network physnet1 \
       --router:external=True
quantum subnet-create --name subnet10 net1 192.168.10.1/24 \
       --gateway_ip 192.169.10.1 \
       --enable_dhcp=True \
       --host_routes type=dict list=true destination=192.168.0.0/16,nexthop=192.168.10.1 \
       --dns_nameservers list=true 192.168.10.2 \
       --allocation_pools type=dict list=true start=192.168.10.100,end=192.168.10.199
quantum subnet-create --name subnet11 net1 192.168.11.1/24 \
       --gateway_ip 192.169.11.1 \
       --enable_dhcp=True \
       --host_routes type=dict list=true destination=192.168.0.0/16,nexthop=192.168.11.1 \
       --dns_nameservers list=true 192.168.11.2 \
       --allocation_pools type=dict list=true start=192.168.11.100,end=192.168.11.199

My controller node is on the 192.168.10.1/24 subnet --> 192.168.10.3
I have 2 compute nodes:
ComputeNode10 on the 192.168.10.1/24 subnet --> 192.168.10.4
ComputeNode11 on the 192.168.11.1/24 subnet --> 192.168.11.4

The Problem:
when I launch a new VM on ComputeNode10 the VM is able to get network configuration during boot and is accessible on the network(ping, ssh, etc...).
However, when I launch a VM on ComputeNode11, nova is able to schedule and launch the VM on ComputeNode11 but the VM cannot get network configuration during boot and it is not accessible on the network. I can see in horizon that Quantum assigned an IP address from the wrong subnet (192.168.10.1/24 --> 192.168.10.101)

Is it possible to tell quantum/nova to launch a VM on a specific subnet and only assign an IP address from that subnet?

P.S
I did try to create a port with a fixed IP on the 192.168.11.1/24 subnet but got the following error:
quantum --debug port-create --fixed-ip subnet_id=subnet11,ip_address=192.168.11.102 net1
QuantumClientException: Invalid input for operation: IP address 192.168.11.102 is not a valid IP for the defined subnet.
* I tried to create a port on the 192.168.10.1/24 subnet and got the same error