Comment 13 for bug 1854981

Revision history for this message
Eric Desrochers (slashd) wrote :

I have restart the autopkgtest and they all passes BUT the disco cinder ones.

Looking at the failure, it's not related to this current SRU, and it seems to be a recurrent failing pattern:

autopkgtest [04:07:34]: test cinder-daemons: [-----------------------
2019-12-06 04:07:37.800 12844 WARNING oslo_db.sqlalchemy.engines [-] URL mysql://cinder:***@localhost/cinder does not contain a '+drivername' portion, and will make use of a default driver. A full dbname+drivername:// protocol is recommended. For MySQL, it is strongly recommended that mysql+pymysql:// be specified for maximum service compatibility
2019-12-06 04:07:37.803 12844 CRITICAL cinder [-] Unhandled error: ModuleNotFoundError: No module named 'MySQLdb'
2019-12-06 04:07:37.803 12844 ERROR cinder Traceback (most recent call last):
......
2019-12-06 04:07:37.803 12844 ERROR cinder File "/usr/lib/python3/dist-packages/sqlalchemy/dialects/mysql/mysqldb.py", line 102, in dbapi
2019-12-06 04:07:37.803 12844 ERROR cinder return __import__('MySQLdb')
2019-12-06 04:07:37.803 12844 ERROR cinder ModuleNotFoundError: No module named 'MySQLdb'
2019-12-06 04:07:37.803 12844 ERROR cinder 
autopkgtest [04:07:38]: test cinder-daemons: -----------------------]
autopkgtest [04:07:39]: test cinder-daemons: - - - - - - - - - - results - - - - - - - - - -
cinder-daemons FAIL non-zero exit status 1

Please ignore the following disco failures:

Regression in autopkgtest for cinder (ppc64el): test log
Regression in autopkgtest for cinder (s390x): test log
Regression in autopkgtest for cinder (amd64): test log
Regression in autopkgtest for cinder (arm64): test log
Regression in autopkgtest for cinder (i386): test log
Regression in autopkgtest for cinder (armhf): test log

Its failing because it can't find the MySQLdb module which is unrelated to the current LVM2 SRU.