-
Getting Started (38)
-
Troubleshooting (19)
- Instance in error status: libvirt error
- Why does it take 4-5 seconds to SSH to my instance?
- Why can't I SSH to an instance, or ping it?
- Error: 'Server doesn't support microversions' When Running Nova Commands
- Cloud Foundry: Invalid Availability Zone Error
- Attempt to Create a Router is Failing
- How Many Simultaneous Connections can HAProxy Handle?
- When using any of the OpenStack CLIs on Windows, I get authentication failure errors
- Why are all the floating IPs that were assigned to me not available?
- Why can't I delete my project/tenant from the Horizon dashboard?
- Error: No valid host was found
- Why Can't I See My New vCPUs Listed in Horizon?
- Error: Failure prepping block device
- Why Can’t I Delete A Security Group?
- Troubleshooting FAQ
- Why Can't I Ping Across My Tenant Networks?
- Why can't I use L2pop when I want my vIP instances to failover?
- View More ( 10 )
-
Open Stack (15)
-
Horizon [GUI] (10)
-
Nova [Compute] (13)
-
Neutron [Networking] (22)
-
Glance [Images] (6)
-
Cinder [Block Storage] (13)
-
Keystone [Identity] (8)
-
Heat [Orchestration] (7)
-
Ceilometer [Telemetry] (1)
Why can't I use L2pop when I want my vIP instances to failover?
Why can’t I use L2pop when I want my vIP instances to failover?
L2 population presents some limitations for customers that want to implement vIP failover between instances, because it won’t work without making Neutron API calls.