---
# System prepended metadata

title: standalone 10 kvm octavia

---

# standalone 10 kvm octavia


Bug:

octavia_tempest_plugin.tests.scenario.v2.test_traffic_ops.TrafficOperationsScenarioTest.test_basic_http_traffic on centos stream 9 times out as it asks for password while connecting to the vm.

This should not be the proper behavior. On tempest tests, the ssh should be injected in the vm, and this should be accessed without the user interact.

The test is hanging exactly because of this, if you run the tempest manually, at some point, after the vm is on ACTIVE status, and the test tries to ssh to the vm, it ask for the password.

We tried to add into tempest.conf the image_ssh_password to see if we can workaround this, but no success.

We are pretty sure this is related to octavia test itself, because we teste the test_network_basic_ops, that do exactly the same (create a vm, and ssh using ssh key) and it works.

Bellow is the tempest.conf section for octavia that is being used:

```
[load_balancer]
test_server_path = "/usr/lib/python3.9/site-packages/octavia_tempest_plugin/contrib/test_server/test_server.bin"
test_with_ipv6 = False
enable_security_groups = True
admin_role = admin
RBAC_test_type = owner_or_admin
member_role = member
region = regionOne
enabled_provider_drivers = amphora:The Octavia Amphora driver.,octavia:Deprecated alias of the Octavia Amphora driver.,ovn:Octavia OVN driver.
```

Right now, we are not sure if this requires other configuration on load_balancer section or in the code of the test itself.

We were able to access the cirros VM manually, and we can confirm that the authorized_key is there on .ssh/authorized_keys

We also notice adding a different ssh key in the authorized_keys did not work. so it seems to be how the vm is being created (again, the basic_network_scenario_ops worked fine).





Looks like a problem with how the VM boots up in octavia.

