Not able to ssh to amphora or curl the vip after rebooting
Bug #1517290 reported by
Banashankar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Expired
|
High
|
Unassigned |
Bug Description
Steps to reproduce
1. Create a Load balancer.
2. SSH to it ssh -i /etc/octavia/
3. Do a sudo reboot.
4. Once amphora comes back try to do ssh.
I was not able to ssh and did not see any errors. Security groups have ssh enabled. Some times I was able to ssh to it.
[update1]
What I observed is, amphora receives the syn but it's not sending back the syn ack
[update2]
Test environment: Vagrant, Ubuntu 14.04, local.conf : https:/
Works fine from the router namespace.
description: | updated |
description: | updated |
summary: |
- Not able to ssh to amphora after rebooting + Not able to ssh to amphora or curl the vip after rebooting |
description: | updated |
Changed in octavia: | |
importance: | Undecided → High |
Changed in octavia: | |
assignee: | Michael Johnson (johnsom) → nobody |
To post a comment you must log in.
My guess is the route table is not persisting across the reboot.