Public bug reported:
This issue occurs on a fresh OpenStack Kilo installation (Ubuntu 14.04
LTS) with a single non-HA network node:
In general public access via floating IPs works, I can ping, ssh and so
on my instances.
But if I associate a new floating IP to a new instance, all floating IPs
Public bug reported:
Using nova 1:2014.1.4-0ubuntu2 (Icehouse) on Ubuntu 14.04.2 LTS
After associating a floating IP address to an instance in Build/Spawning
state, 'nova list' and 'nova show' need - per default - a lot of time
(up to 40 minutes) to display that floating IP.
Steps to reproduce:
Public bug reported:
nova-compute.log on kvm:
2014-04-28 14:51:57.294 14659 ERROR nova.compute.manager
[req-e9768eff-116d-4681-9ff6-3ab51dbbdee0 c460eaefef634e4bab938915224a6201
e159f0e56ea545bd84529fc38063
ceee] [instance: 61a3e08f-b22f-47a8-a815-f586422860ef] Instance failed to spawn
3 matches
Mail list logo