Thank you.
It worked with the new settings. Now the instances are correctly in
ERROR state of network is not functional.
To solve the performance problem and have 0 instances in ERROR state I
had to enable the neutron-rootwrap-daemon. Without it the dhcp agents
were not fast enough to consume the
With such settings nova is not waiting for info from neutron and that is why
Your instances starting without network ready.
If You will change this timeout to some value higher than 0 then instance will
be paused and nova will wait for info from neutron that port is active (You
should also
Hello,
thanks for the tip.
I checked on a compute node, in the nova.conf file I have the following:
vif_plugging_is_fatal=False
vif_plugging_timeout=0
both options are in the [DEFAULT] section.
I guess these settings were never changed since we were running Icehouse.
Should I change to the
Hello,
Do You have configured in nova-compute: vif_plugging_timeout and
vif_plugging_is_fatal options?
With those options nova should pause VM until port will be set to ACTIVE in
Neutron.
--
Slawek
> Wiadomość napisana przez Saverio Proto w dniu
> 09.08.2017, o
Hello,
I see this in Openstack Newton
I start 200 instances with a oneliner.
openstack server create \
--image "Ubuntu Xenial 16.04 (SWITCHengines)" \
--flavor c1.small \
--network demonetwork \
--user-data cloud-init.txt \
--key-name macsp \
--min 200 \
--max 200 test
When I do this I see a