No module named 'trove.common.single_tenant_remote'

Bug #1937120 reported by Boris Lukashev
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla-ansible
In Progress
Undecided
Unassigned

Bug Description

Deploying current wallaby-based stack using Ubuntu containers on Ubuntu host systems with trove single tenant set to yes, attempting to access the Trove Horizon view results in:
```
8cca9655-6275-4924-9ff5-8ae772a0da11: No module named 'trove.common.single_tenant_remote': ModuleNotFoundError: No module named 'trove.common.single_tenant_remote'
2021-07-21 18:44:34.797 19 ERROR trove.common.wsgi Traceback (most recent call last):
2021-07-21 18:44:34.797 19 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib/python3.8/site-packages/trove/common/wsgi.py", line 248, in execute_action
2021-07-21 18:44:34.797 19 ERROR trove.common.wsgi result = super(Resource, self).execute_action(
2021-07-21 18:44:34.797 19 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib/python3.8/site-packages/trove/common/base_wsgi.py", line 393, in execute_action
2021-07-21 18:44:34.797 19 ERROR trove.common.wsgi return self.dispatch(self.controller, action, request, **action_args)
2021-07-21 18:44:34.797 19 ERROR trove.common.wsgi File "/var/lib/kolla/venv/lib/python3.8/site-packages/trove/common/base_wsgi.py", line 402, in dispatch
```
which i imagine is not the intended outcome of that operation.

Whats the proper way to hot-patch containers with dependencies while stuff is resolved upstream? I have a local repo docker repo as a proxy already.

Revision history for this message
Mark Goddard (mgoddard) wrote :

I would suggest trying to fix it yourself, then propose the fix upstream.

Revision history for this message
Boris Lukashev (rageltman) wrote :

I can add this to my backlog, but i'm booked out for months with client work and other Open Source commitments (also i'm not a Python developer, Ruby is my game for interpreted languages). If you could point me to the procedures i requested in terms of modifying the containers, i can take a quick stab at it next time i have some free time. Otherwise i'll need to allocate actual project time somewhere in Q4 in our project management system (Trove isn't required for us, but a neat function to have available).

Revision history for this message
Dai Dang Van (daikk115) wrote :

The default value have been change, you can overwrite by putting bellow configuration into /etc/kolla/config/trove.conf.

And of course, we should update this in kolla template as well

# Client to send Nova calls to. (string value)
#remote_nova_client = trove.common.clients_admin.nova_client_trove_admin

# Client to send Neutron calls to. (string value)
#remote_neutron_client = trove.common.clients_admin.neutron_client_trove_admin

# Client to send Cinder calls to. (string value)
#remote_cinder_client = trove.common.clients_admin.cinder_client_trove_admin

Changed in kolla-ansible:
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)
Changed in kolla-ansible:
status: Confirmed → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.