Friday, 2023-10-06

opendevreviewsean mooney proposed openstack/nova master: add initial healthcheck support  https://review.opendev.org/c/openstack/nova/+/82501500:20
opendevreviewsean mooney proposed openstack/nova master: add healthcheck manager to manager base  https://review.opendev.org/c/openstack/nova/+/82784401:38
opendevreviewAmit Uniyal proposed openstack/nova master: Adds server show in helpers  https://review.opendev.org/c/openstack/nova/+/89358406:03
opendevreviewAmit Uniyal proposed openstack/nova master: Refactor volumeAttachment for regressions  https://review.opendev.org/c/openstack/nova/+/89358506:03
opendevreviewAmit Uniyal proposed openstack/nova master: Refactor vol attachment api call for rest of the tests  https://review.opendev.org/c/openstack/nova/+/89358706:03
zigoHi there!07:07
zigoQuick Alembic question, not sure if this channel is the best place to ask, but asking anyways. Where is Alembic storing the current revision of the db, and where's the ordered list of db-migration stored?07:07
zigoAh no, I'm searching the info about sqlalchemy-migrate in fact...07:25
zigo(we're trying to upgrade from Victoria to Bobcat...)07:26
fricklerif you see doc build failures please check https://bugs.launchpad.net/nova/+bug/202634507:37
bauzaszigo: with alembic, that's a bit different but you can find them08:14
zigoYeah, I found the version in the db, but can't find the version in the code ...08:15
auniyalfrickler, I am seeing this today, even though my change do not have any doc update, thanks for sharing bug.08:17
fricklerzigo: there was a big cleanup in https://review.opendev.org/c/openstack/nova/+/872428 which might affect you?08:21
fricklerare you trying to go in one big step from V to B?08:22
zigofrickler: No, we're currently designing our upgrade script to script it all...08:37
zigoAnd we'd like to add db version checks on each step.08:38
zigoSo we need this check for both alembic and sqla-migrate...08:40
zigoSo far, I have:08:41
zigoSELECT version_num FROM alembic_version;08:41
zigoto get the current version in the *db* for alembic, and:08:41
zigopython3 manage.py version08:41
zigoto get the *code* version of sqla-migrate. I need to find out how to fetch:08:42
zigoThe *code* version for Alembic and the *db* version for sqla-migrate ...08:42
bauzaswe recently packed the versions08:56
bauzashttps://github.com/openstack/nova/tree/master/nova/db/main/migrations/versions08:56
bauzasfor the cell DB08:56
bauzasand https://github.com/openstack/nova/tree/master/nova/db/api/migrations/versions for the API DB one08:57
bauzasHTH08:57
bauzas(if I understood correctly your question)08:57
zigoI'm not explaining what I need correctly I guess. My question is:09:02
zigo- for alembic: how to find out what's the latest revision ID in /usr/lib/python3/dist-packges/nova/db ?09:02
zigo- for sqla-migrate: how to find out the currently installed revision of the db in /var/lib/mysql ?09:02
bauzasah I see09:04
bauzaswell, I don't think we have some file saying in some variable exactly which version is the last, it's automatically calculed by alembic09:04
bauzasbut when you look at the files in github, you can find the last commit date09:05
bauzasthen, if you open one of the version (like the last committed one), you find its version + the parent one09:05
bauzashttps://github.com/openstack/nova/blob/master/nova/db/main/migrations/versions/1acf2c98e646_add_compute_id_to_instance.py#L25-L2609:07
bauzasthat's the last revision09:07
fricklerzigo: does https://alembic.sqlalchemy.org/en/latest/tutorial.html#getting-information help?09:08
bauzasbut I guess the simpliest is calling the alembic command in the repo09:08
bauzasyeah, "alembic current" will give you this09:08
zigoOh, I just found out for migrate ... :)09:09
zigoroot@controller-1 /usr/lib/python3/dist-packages/nova/db/sqlalchemy/migrate_repo # python3 manage.py db_version --url="mysql+pymysql://nova:<password>@<ip>/novadb?charset=utf8"09:10
zigoroot@C1-cl1-controller-1>_ /usr/lib/python3/dist-packages/nova/db/main # alembic -c alembic2.ini current09:15
zigoINFO  [alembic.runtime.migration] Context impl MySQLImpl.09:15
zigoINFO  [alembic.runtime.migration] Will assume non-transactional DDL.09:15
zigoERROR [alembic.util.messaging] Can't locate revision identified by 'cdeec0c85668'09:15
zigo  FAILED: Can't locate revision identified by 'cdeec0c85668'09:15
zigo(I replaced sqlalchemy.url= in this alembic2.ini, as the original one doesn't contain the connection info as per nova.conf...)09:16
zigoOh, my bad.09:16
zigonovapidb vs novadb ...09:16
zigoThanks a lot !09:17
*** gryf is now known as Guest236010:12
*** Guest2360 is now known as _gryf10:13
opendevreviewPavlo Shchelokovskyy proposed openstack/nova master: Do not store InstanceInvalidState as instance_fault  https://review.opendev.org/c/openstack/nova/+/86070211:41
noonedeadpunkhey everyone. I have weird issues with castellan when attaching encrypted volumes. So it fails on nova-compute on attach attempt with smth like this: https://paste.openstack.org/show/bLY6qE339z2dD5eZntFM/12:15
noonedeadpunkWe've start catching that right after upgrade to 2023.112:15
noonedeadpunkI'm just not sure really where to start looking into - if it's smth related to nova or keystone or castellan itself... So just checking if you might heard about smth like that before12:16
fricklernoonedeadpunk: which version of castellan are you using? there were some last-minute reverts for 2023.2 because of compatibility issues https://review.opendev.org/q/topic:revert-castellan-bobcat12:19
fricklernot sure though whether it is really the same issue you are seeing12:19
noonedeadpunklet me see....12:22
noonedeadpunkAs I was looking into secret users already but not sure that's it12:23
fricklerhmm, the errors in https://review.opendev.org/c/openstack/requirements/+/883141 look different, but that's for func tests only12:24
noonedeadpunk4.1.012:27
noonedeadpunkso it shouldn't have any of these I assume12:28
noonedeadpunk(some win from u-c usage at least12:28
noonedeadpunkI have some feeling it is related to service tokens... But visually everything is in place...12:33
noonedeadpunkas it fails in self.service_auth.get_token12:33
noonedeadpunk(for keystoneauth1)12:33
noonedeadpunk`service_user` section is in place, with all auth and `send_service_user_token = True`, service_token_roles_required = True in keystone_authtoken...12:42
zigoFYI, as an operator, we are SUPER HAPPY about the BDM sync feature of Bobcat, thanks to whoever worked on that, it's going to make our lives a way less miserable !!! :)13:06
zigoWe had so many issues with the attachments in nova/cinder not being in sync ...13:07
zigoSo: thanks... !13:07
* zigo is looking forward the upgrade13:07
*** blarnath is now known as d34dh0r5313:11
sahido/13:13
noonedeadpunkOk, my issue was related to missing barbican_service_user section...13:13
sahidhey bauzas thanks for your comment on https://review.opendev.org/c/openstack/nova/+/89651213:14
sahidI will create a launchpad bp and update the change13:14
bauzas++13:14
bauzassorry for the paperwork but I wanted to have it tracked correctly for the operators13:14
bauzaslooks to me more a feature than a bugfix13:15
bauzas(but I could be wrong)13:15
sahidI don't know, it's an improvment I guess13:15
sahidthat fixes a bug reported13:16
sahids/bug/limitation13:16
bauzasyup, hence my point13:17
bauzasanyway, we'll see what others say13:17
bauzassahid: if you create a blueprint, could you please be in a next nova meeting for discussing it ?13:18
bauzas(Tuesdays 16UTC)13:18
*** haleyb is now known as haleyb|away13:27
dansmithbauzas: I think you owe me a response on my alias spec about mdevs? specifically about mdevs not yet being attachable at runtime (like ports and disks)?13:39
bauzasdid I forget anything ? shit if so13:40
* bauzas goes looking at your spec13:40
bauzas-ETOOMANYGERRITEMAILS13:40
dansmithbauzas: well you left it as "yeah then we can do mdevs too" and I said "I want to do all attachable devices, but I think that's just disks and ports" and then we had a private convo about it13:41
dansmithand I think we decided that it was probably just ports and disks in that category, but you said you'd circle back13:41
dansmithunrelated, gibi I wrote up this patch we discussed, can you have a look? https://review.opendev.org/c/openstack/nova/+/89707613:42
dansmithgibi: there's another assertion patch above that that came from a real-world situation and I think it'd probably be good to have that in a scenario where you're moving cell databases around :)13:42
bauzasdansmith: okidoki, so I'll add a comment and review it again13:43
* bauzas wonders why he missed it13:43
dansmithbauzas: well, I just want to close the loop so it doesn't look like it's waiting for a change :)13:43
bauzasdansmith: correct, hence my new comment needed :)13:45
bauzasyou explained me that it would only be for attach/detach calls13:45
bauzasthat mdevs don't do 13:45
bauzasthat said I said I should look at other devices, if we do this13:45
bauzasbut I think I found none of them13:45
dansmithyep, cool :)13:46
dansmithbauzas: thanks for that14:12
gibidansmith: thanks I will take a look14:13
dansmithgibi: thanks14:13
sahidbauzas: sure I will do14:24
opendevreviewsean mooney proposed openstack/nova master: add initial healthcheck support  https://review.opendev.org/c/openstack/nova/+/82501517:23
opendevreviewsean mooney proposed openstack/nova master: add healthcheck manager to manager base  https://review.opendev.org/c/openstack/nova/+/82784417:23

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!