No module named 'trove.common.single_tenant_remote'
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
kolla-ansible | Status tracked in Dalmatian | |||||
Antelope |
Fix Released
|
Undecided
|
Unassigned | |||
Bobcat |
Fix Released
|
Undecided
|
Unassigned | |||
Caracal |
Fix Released
|
Undecided
|
Unassigned | |||
Dalmatian |
Fix Released
|
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-
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/
2021-07-21 18:44:34.797 19 ERROR trove.common.wsgi result = super(Resource, self).execute_
2021-07-21 18:44:34.797 19 ERROR trove.common.wsgi File "/var/lib/
2021-07-21 18:44:34.797 19 ERROR trove.common.wsgi return self.dispatch(
2021-07-21 18:44:34.797 19 ERROR trove.common.wsgi File "/var/lib/
```
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.
I would suggest trying to fix it yourself, then propose the fix upstream.