openstack team mailing list archive
Mailing list archive
Re: No NIC attached/exists on newly created instances
you don't have to create networks in nova too - the ones you created with
quantum should be enough.
First, it might perhpaps good to exclude possible issues with your image.
If you're using KVM you could go and check the libvirt XML which is
generated for your instance. If you see a populated 'interfaces' section
there, then the VIFs have been correctly created, and perhaps for some
reason your image is not loading them.
If the 'interfaces' section is not populated, then the issues I can think
- quantum ports not created, in which case this might mean nova-compute is
not using the quantum network API driver
- quantum ports created but interfaces not attached, in which case this
might mean nova-compute is not using the appropriate VIF driver.
On 23 July 2013 03:09, Jake G. <dj_dark_junglist@xxxxxxxxx> wrote:
> Hi all,
> New issue here. I have two networks that I created through the OS
> dashboard, Private and public.
> These seem to be quantum networks because they are listed when using the
> cmd quantum net-list
> I deploy a new instance on the private network, then associate a floating
> ip. I login to the console and notice that there is no NIC attached to the
> instance (no NIC exists).
> What could be the cause of this? Do I need to create matching networks for
> nova as well? or should the quantum networks be enough?
> or is there a different issue here?
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp