Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

operations-guide: SSH access to amphorae #608

Merged
merged 1 commit into from
Jun 13, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 17 additions & 1 deletion docs/guides/operations-guide/openstack/octavia.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,27 @@ sidebar_label: Octavia

# Octavia

## Cleanup of amphora missing from the DB
## Cleanup of amphorae missing from the DB

```none title="/var/log/kolla/octavia/octavia-health-manager.log"
2023-10-25 16:43:52.547 22 WARNING octavia.amphorae.drivers.health.heartbeat_udp [-]
The amphora 2a33a889-4f9a-4340-84a5-e58a7a8af17e with IP 10.1.0.79 is missing from the
DB, so it cannot be automatically deleted (the compute_id is unknown). An operator must
manually delete it from the compute service.
```

## SSH access to amphorae

1. Get the local IP address (`lb_network_ip`) of the amphora you want to access via
`openstack --os-cloud admin loadbalancer amphora list`.

2. Connect to one of the nodes that you use for Octavia. Normally the control-
or network nodes.

3. You can now use SSH to access the amphora. The use of sudo is required here because
you cannot access `/etc/kolla/octavia-worker/octavia_ssh_key` with the operator user
account. Replace `lb_network_ip` with the local IP address of the amphora.

```
sudo ssh -i /etc/kolla/octavia-worker/octavia_ssh_key ubuntu@lb_network_ip
```
Loading