<div dir="ltr"><div>Hello:</div><div><br></div><div>This seems to be a problem in Neutron. Please provide what backend you are using, and the Neutron server logs. If the ML2 driver has agents (DHCP, ML2 agent), provide the agents logs too.</div><div><br></div><div>Regards.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 9, 2022 at 1:53 PM <<a href="mailto:tim%2Bopenstack.org@coote.org">tim+openstack.org@coote.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
On 9 Jun 2022, at 09:58, <a href="mailto:tim%2Bopenstack.org@coote.org" target="_blank">tim+openstack.org@coote.org</a> wrote:<br>
<br>
Hullo<br>
<br>
I’m trying to spin up a simple OS environment in a single vm and think that I’m making some silly mistake, but cannot spot it. Any hints would be greatly expected. I’ve tried this on a couple of laptops, with the same result, so I suspect that it’s something to do with how I’ve set up my vm, but I cannot identify it. (I think that there may be a few other devstack issues, but I’ve got to get it working to log any bugs).<br>
<br>
I’m using a vagrant box and VirtualBox on x86 Macs (Monterey), and the devstack install/build process. Everything seems to install, but when I try:<br>
<br>
`openstack server create --flavor 42 --image cirros-0.5.2-x86_64-disk --nic net-id=2a1a4a3a-a47b-48bd-a7df-c90fc75a1c63 --security-group default wibble`<br>
<br>
The network id is identified from this:<br>
“”"<br>
[vagrant@localhost devstack]$ openstack network list<br>
+--------------------------------------+---------+----------------------------------------------------------------------------+<br>
| ID | Name | Subnets |<br>
+--------------------------------------+---------+----------------------------------------------------------------------------+<br>
| 205fa7d7-7067-4f63-b3d9-6a9b37b4f11f | public | 1bbbfa3c-8e0a-483f-a084-4e38241b3315, eecfc603-c057-4b28-90bd-950a47345410 |<br>
| 2a1a4a3a-a47b-48bd-a7df-c90fc75a1c63 | private | e7377bed-3e22-4e8d-9c2d-ea7ba740fcfd, f915b88c-9988-4e1f-9060-a6295465699a |<br>
| fab3fb15-cbd2-45fe-8451-3f0063d59454 | shared | 97e6d8e6-0f57-48bc-8f1d-e30587086153 |<br>
+--------------------------------------+---------+——————————————————————————————————————+<br>
“””<br>
<br>
Using a public network fails with an error that this isn’t allowed.<br>
<br>
With the private network above, the failure throws out the following errors.<br>
“”"<br>
[vagrant@localhost devstack]$ sudo journalctl -f |grep ERROR<br>
Jun 08 15:33:52 localhost.localdomain nova-compute[87555]: ERROR nova.compute.manager [None req-01294678-b54a-4e40-964c-488ccf03d66c demo demo] [instance: 20e1b5bf-130a-48f9-af4e-9b4c7a475315] Instance failed to spawn: nova.exception.VirtualInterfaceCreateException: Virtual Interface creation failed<br>
Jun 08 15:33:52 localhost.localdomain nova-compute[87555]: ERROR nova.compute.manager [instance: 20e1b5bf-130a-48f9-af4e-9b4c7a475315] Traceback (most recent call last):<br>
<br>
[snip]<br>
“”"<br>
<br>
The Vagrantfile (commented out lines relate to trying this with Ubunutu, which failed the same way, and attempts to use multiple vms):<br>
“”"<br>
# -*- mode: ruby -*-<br>
# vi: set ft=ruby :<br>
<br>
[snip]<br>
Vagrant.configure(2) do |config|<br>
<br>
config.vm.box = "eurolinux-vagrant/centos-stream-9"<br>
#config.vm.box = "hashicorp/bionic64"<br>
<br>
<br>
config.hostmanager.enabled = true<br>
config.hostmanager.manage_host = true<br>
config.hostmanager.manage_guest = true<br>
config.hostmanager.ignore_private_ip = false<br>
config.hostmanager.include_offline = true<br>
<br>
config.ssh.pty = true<br>
<br>
config.vm.provision "shell", inline: $script<br>
<br>
config.vm.network "forwarded_port", guest: 80, host: 8080<br>
<br>
config.vm.provider "virtualbox" do | v |<br>
v.memory = "9216"<br>
v.cpus = "2"<br>
end<br>
<br>
end<br>
“””<br>
<br>
I think that the vm has enough RAM, although there is minimal swap being used, but I think that this is not significant as there is much more RAM used for caching files.<br>
<br>
Any obvious hints as to why the spin up fails to create the NIC - or somewhere to look for further and better details?<br>
<br>
Tim<br>
<br>
<br>
</blockquote></div>