Sqlalchemy errors with subnet and group snapshot models
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
High
|
Goutham Pacha Ravi |
Bug Description
Some manila or python-manilaclient jobs are broken, since some share network subnet and share group tests are constantly failing. In both cases, the issue seems database related.
All the failing tests have something in common in the exception, which is a database lazy loaded entity, as shown in the below example exception.
Captured traceback:
~~~~~~~~~~~~~~~~~~~
Traceback (most recent call last):
File "/home/
result = self.controller
File "/home/
return func.func(self, *args, **kwargs)
File "/home/
return f(self, req, *args, **kwargs)
File "/home/
req, share_network.
File "/home/
for share_network_
File "/home/
for share_network_
File "/home/
File "/home/
return self.impl.
File "/home/
value = self.callable_
File "/home/
% (orm_util.
sqlalchemy
Changed in manila: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → ussuri-2 |
description: | updated |
tags: | added: db |
summary: |
- Some manila jobs are failing due to unit test issues + Sqlalchemy errors with subnet and group snapshot models |
Changed in manila: | |
assignee: | nobody → Goutham Pacha Ravi (gouthamr) |
status: | Confirmed → In Progress |
Earlier in this morning, we've started searching for possible changes in SQLAlchemy, which is used by manila and is a requirement while running the tests.
We suspect that the problem may have started after the SQLAlchemy 1.3.13 release. I have tested in an environment which uses SQLAlchemy in a older version (1.3.10) and it worked just fine.
[1] https:/ /docs.sqlalchem y.org/en/ 13/changelog/ changelog_ 13.html# change- 1.3.13