Barbican/Heat Xena: strange error with barbican-manage (and heat-manage)
Hi,
I'm trying to update our Wallaby cloud to Xena. Doing this for Barbican and Heat, I have a problem when trying to upgrade the database. Here is the log for Barbican:
----------
[root@os-77023 ~]# barbican-manage db upgrade head [root@os-77023 ~]# barbican-manage db current ERROR: 'int' object is not iterable [root@os-77023 ~]# barbican-manage db upgrade ERROR: 'int' object is not iterable
----------
I can find a similar error in log files of Heat services, for example in heat-engine.log:
---------
2024-03-05 12:16:27.978 1638283 INFO heat.engine.worker [-] Starting engine_worker (1.4) in engine 686dc841-d595-49cd-bf5e-04a4de876dc1. 2024-03-05 12:16:28.109 1638283 ERROR oslo_service.service [req-b991252a-f4c1-4955-a2ed-b20db59a161c - - - - -] Error starting thread.: TypeError: 'int' object is not iterable ---------
My DB connection information, working well with Wallaby, is:
----------
sql_connection=mysql+pymysql://barbican:very_secret_pwd@os-sql-admin.lal.in2p3.fr/barbican
----------
I cannot find any other useful information. Anything trivial I missed?
Thanks in advance for any help. Best regards,
Michel
Answering to myself, I managed to identify that due to a problem in our DNF configuration, the python3-sqlalchemy installed was the version provided by the OS instead of the version provided by OpenStack Xena and this OS version is too old.
Michel
Le 05/03/2024 à 12:21, Michel Jouvin a écrit :
Hi,
I'm trying to update our Wallaby cloud to Xena. Doing this for Barbican and Heat, I have a problem when trying to upgrade the database. Here is the log for Barbican:
[root@os-77023 ~]# barbican-manage db upgrade head [root@os-77023 ~]# barbican-manage db current ERROR: 'int' object is not iterable [root@os-77023 ~]# barbican-manage db upgrade ERROR: 'int' object is not iterable
I can find a similar error in log files of Heat services, for example in heat-engine.log:
2024-03-05 12:16:27.978 1638283 INFO heat.engine.worker [-] Starting engine_worker (1.4) in engine 686dc841-d595-49cd-bf5e-04a4de876dc1. 2024-03-05 12:16:28.109 1638283 ERROR oslo_service.service [req-b991252a-f4c1-4955-a2ed-b20db59a161c - - - - -] Error starting thread.: TypeError: 'int' object is not iterable
My DB connection information, working well with Wallaby, is:
sql_connection=mysql+pymysql://barbican:very_secret_pwd@os-sql-admin.lal.in2p3.fr/barbican
I cannot find any other useful information. Anything trivial I missed?
Thanks in advance for any help. Best regards,
Michel
Hi,
Upgrading our cloud to Xena/Yoga, using CentOS Stream 8, I'm facing a strange problem with the package python3-sqlalchemy that led to my previous email yesterday... The reason the version provided/required by Xena/Yoga (1.4.x) was not installed, causing my problem, is that the package is not listed in repository metadata, even if I rebuilt them with createrepo. I even tried to create a new repo with just this RPM only (the version from Xena or Yoga has the same problem, despite being slightly different versions) and the repo appears (with dnf repoquery --all) as empty.
I don't understand what may be going wrong, we are using a lot of Yum repositories and never saw such an issue...
Is it something that has been seen by others? Any suggestion on how to fix it? It is an important issue as it needs to be deployed on all computes...
Best regards,
Michel
Le 05/03/2024 à 16:24, Michel Jouvin a écrit :
Answering to myself, I managed to identify that due to a problem in our DNF configuration, the python3-sqlalchemy installed was the version provided by the OS instead of the version provided by OpenStack Xena and this OS version is too old.
Michel
Le 05/03/2024 à 12:21, Michel Jouvin a écrit :
Hi,
I'm trying to update our Wallaby cloud to Xena. Doing this for Barbican and Heat, I have a problem when trying to upgrade the database. Here is the log for Barbican:
[root@os-77023 ~]# barbican-manage db upgrade head [root@os-77023 ~]# barbican-manage db current ERROR: 'int' object is not iterable [root@os-77023 ~]# barbican-manage db upgrade ERROR: 'int' object is not iterable
I can find a similar error in log files of Heat services, for example in heat-engine.log:
2024-03-05 12:16:27.978 1638283 INFO heat.engine.worker [-] Starting engine_worker (1.4) in engine 686dc841-d595-49cd-bf5e-04a4de876dc1. 2024-03-05 12:16:28.109 1638283 ERROR oslo_service.service [req-b991252a-f4c1-4955-a2ed-b20db59a161c - - - - -] Error starting thread.: TypeError: 'int' object is not iterable
My DB connection information, working well with Wallaby, is:
sql_connection=mysql+pymysql://barbican:very_secret_pwd@os-sql-admin.lal.in2p3.fr/barbican
I cannot find any other useful information. Anything trivial I missed?
Thanks in advance for any help. Best regards,
Michel
participants (1)
-
Michel Jouvin