| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-10-03 | |||
| 17:26:05 | atmark | should I remove entry or just update the deleted field ? | |
| 17:26:48 | dansmith | atmark: you can just set the deleted field to id if you want (that's what service delete does) but really they should go away.. but fine to just mark as deleted to test if you want | |
| 17:40:25 | opendevreview | Dan Smith proposed openstack/nova master: WIP: Warn if we find compute services in cell0 https://review.opendev.org/c/openstack/nova/+/897246 | |
| 17:47:20 | atmark | dansmith: For compute25 - I didn't have to do anything. compute01 - I deleted the RP, restarted nova-compute and then ran heal so issue is now resolved. I learned something new. Thanks a lot. | |
| 17:47:48 | dansmith | atmark: awesome, glad to hear it.. so you cleaned up the service *and* node records from cell0 right? | |
| 17:47:49 | atmark | If I unset alloactions instead of alloactions, will I face the same issue? https://docs.openstack.org/nova/latest/admin/troubleshooting/orphaned-allocations.html#solution | |
| 17:48:25 | atmark | dansmith: yes, I decided to remove the records instead of updating deleted field. | |
| 17:48:29 | dansmith | cool | |
| 17:48:52 | dansmith | atmark: not sure what you're asking about. unset .. "allocations instead of allocations" | |
| 17:49:31 | atmark | "allocation unset instead of allocation remove" | |
| 17:50:49 | dansmith | atmark: no I think it would have ended up the same way | |
| 17:56:38 | atmark | is it safe to remove these records in instances table in nova_cell0? https://paste.openstack.org/show/bP2VO4c7Gh6Tb4SIm5Wi/ | |
| 17:59:19 | dansmith | yes on the compute nodes.. the instances were all deleted in the last dump, so they belong there and will be cleaned after an archive | |
| 17:59:29 | dansmith | instances *do* belong in cell0, if they failed the schedule | |
| 18:10:18 | atmark | got it. thanks again | |
| 18:19:58 | opendevreview | Merged openstack/nova stable/zed: Fix failed count for anti-affinity check https://review.opendev.org/c/openstack/nova/+/885344 | |
| 19:30:23 | opendevreview | Dan Smith proposed openstack/nova master: WIP: Warn if we find compute services in cell0 https://review.opendev.org/c/openstack/nova/+/897246 | |
| #openstack-nova - 2023-10-04 | |||
| 10:03:38 | auniyal | Hi sean-k-mooney, reminder ping for https://review.opendev.org/q/topic:bug%252F1996732 | |
| 10:05:24 | auniyal | can you also please quick lookon https://review.opendev.org/q/topic:bug%252F2008102 only 2 patches are pending to merge | |
| 10:16:55 | auniyal | thanks sean-k-mooney | |
| 11:58:17 | opendevreview | Merged openstack/nova stable/xena: Have host look for CPU controller of cgroupsv2 location. https://review.opendev.org/c/openstack/nova/+/882921 | |
| 15:24:20 | opendevreview | Dan Smith proposed openstack/nova master: WIP: Warn if we find compute services in cell0 https://review.opendev.org/c/openstack/nova/+/897246 | |
| 15:24:34 | opendevreview | Dan Smith proposed openstack/nova master: Warn if we find compute services in cell0 https://review.opendev.org/c/openstack/nova/+/897246 | |
| 17:09:49 | frickler | anyone willing tp push a small status check URL fix over the edge? https://review.opendev.org/c/openstack/nova/+/895770 | |
| 17:09:55 | frickler | *to | |
| 17:11:14 | dansmith | frickler: the new one gives me a 404 | |
| 17:11:18 | dansmith | https://docs.openstack.org/nova/latest/admin/hw_machine_type.html | |
| 17:11:40 | dansmith | second new one seems right tho | |
| 17:15:58 | frickler | humm, I admit I only checked the second one because that's what I stumbled about and then just duplicated the change for the other URL | |
| 17:16:07 | frickler | let me try to find a proper URL | |
| 17:17:11 | frickler | ah, dashes instead of underscores, will amend, thx for noticing this | |
| 17:18:26 | opendevreview | Dr. Jens Harbott proposed openstack/nova master: Fix URLs in status check results https://review.opendev.org/c/openstack/nova/+/895770 | |
| 17:19:07 | frickler | dansmith: ^^ | |
| 17:19:53 | dansmith | frickler: got it | |
| 22:46:31 | opendevreview | Merged openstack/nova master: Fix URLs in status check results https://review.opendev.org/c/openstack/nova/+/895770 | |
| 23:16:34 | opendevreview | melanie witt proposed openstack/nova master: testing: Detect log message string formatting bugs https://review.opendev.org/c/openstack/nova/+/897370 | |
| #openstack-nova - 2023-10-05 | |||
| 02:36:45 | opendevreview | Dr. Jens Harbott proposed openstack/nova stable/2023.2: Fix URLs in status check results https://review.opendev.org/c/openstack/nova/+/897297 | |
| 13:29:21 | opendevreview | sean mooney proposed openstack/nova stable/wallaby: fix sr-iov support on Cavium ThunderX hosts. https://review.opendev.org/c/openstack/nova/+/897300 | |
| 13:44:03 | opendevreview | Dan Smith proposed openstack/nova master: Warn if we find compute services in cell0 https://review.opendev.org/c/openstack/nova/+/897246 | |
| 13:48:06 | opendevreview | Merged openstack/nova stable/yoga: Fix failed count for anti-affinity check https://review.opendev.org/c/openstack/nova/+/885345 | |
| 14:14:11 | bauzas | fwiw, live OIL session on Youtube about Bobcat now https://www.youtube.com/watch?v=q7WDncK3YuM | |
| 18:11:55 | auniyal | Hi dansmith, can you please review this https://review.opendev.org/c/openstack/nova/+/857339, its pending from quite sometime, I do have few comments from bauzas already. | |
| 18:54:16 | opendevreview | sean mooney proposed openstack/nova master: [WIP] add initial healthcheck support https://review.opendev.org/c/openstack/nova/+/825015 | |
| 23:19:03 | opendevreview | melanie witt proposed openstack/nova master: libvirt: Configure and teardown ephemeral encryption secrets https://review.opendev.org/c/openstack/nova/+/826754 | |
| 23:19:03 | opendevreview | melanie witt proposed openstack/nova master: imagebackend: Add support to libvirt_info for LUKS based encryption https://review.opendev.org/c/openstack/nova/+/826755 | |
| 23:50:01 | opendevreview | melanie witt proposed openstack/nova-specs master: Re-propose spec for ephemeral storage encryption https://review.opendev.org/c/openstack/nova-specs/+/897502 | |
| 23:52:42 | opendevreview | melanie witt proposed openstack/nova-specs master: iRe-propose spec for ephemeral encryption for libvirt https://review.opendev.org/c/openstack/nova-specs/+/897503 | |
| 23:53:24 | opendevreview | melanie witt proposed openstack/nova-specs master: Re-propose spec for ephemeral encryption for libvirt https://review.opendev.org/c/openstack/nova-specs/+/897503 | |
| #openstack-nova - 2023-10-06 | |||
| 00:20:00 | opendevreview | sean mooney proposed openstack/nova master: add initial healthcheck support https://review.opendev.org/c/openstack/nova/+/825015 | |
| 01:38:38 | opendevreview | sean mooney proposed openstack/nova master: add healthcheck manager to manager base https://review.opendev.org/c/openstack/nova/+/827844 | |
| 06:03:11 | opendevreview | Amit Uniyal proposed openstack/nova master: Adds server show in helpers https://review.opendev.org/c/openstack/nova/+/893584 | |
| 06:03:12 | opendevreview | Amit Uniyal proposed openstack/nova master: Refactor volumeAttachment for regressions https://review.opendev.org/c/openstack/nova/+/893585 | |
| 06:03:12 | opendevreview | Amit Uniyal proposed openstack/nova master: Refactor vol attachment api call for rest of the tests https://review.opendev.org/c/openstack/nova/+/893587 | |
| 07:07:36 | zigo | Hi there! | |
| 07:07:36 | zigo | Quick 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:25:55 | zigo | Ah no, I'm searching the info about sqlalchemy-migrate in fact... | |
| 07:26:07 | zigo | (we're trying to upgrade from Victoria to Bobcat...) | |
| 07:37:38 | frickler | if you see doc build failures please check https://bugs.launchpad.net/nova/+bug/2026345 | |
| 08:14:38 | bauzas | zigo: with alembic, that's a bit different but you can find them | |
| 08:15:04 | zigo | Yeah, I found the version in the db, but can't find the version in the code ... | |
| 08:17:56 | auniyal | frickler, I am seeing this today, even though my change do not have any doc update, thanks for sharing bug. | |
| 08:21:01 | frickler | zigo: there was a big cleanup in https://review.opendev.org/c/openstack/nova/+/872428 which might affect you? | |
| 08:22:29 | frickler | are you trying to go in one big step from V to B? | |
| 08:37:55 | zigo | frickler: No, we're currently designing our upgrade script to script it all... | |
| 08:38:09 | zigo | And we'd like to add db version checks on each step. | |
| 08:40:13 | zigo | So we need this check for both alembic and sqla-migrate... | |
| 08:41:59 | zigo | So far, I have: | |
| 08:41:59 | zigo | SELECT version_num FROM alembic_version; | |
| 08:41:59 | zigo | to get the current version in the *db* for alembic, and: | |
| 08:41:59 | zigo | python3 manage.py version | |
| 08:42:00 | zigo | to get the *code* version of sqla-migrate. I need to find out how to fetch: | |
| 08:42:02 | zigo | The *code* version for Alembic and the *db* version for sqla-migrate ... | |
| 08:56:48 | bauzas | we recently packed the versions | |
| 08:56:53 | bauzas | https://github.com/openstack/nova/tree/master/nova/db/main/migrations/versions | |
| 08:56:58 | bauzas | for the cell DB | |
| 08:57:12 | bauzas | and https://github.com/openstack/nova/tree/master/nova/db/api/migrations/versions for the API DB one | |
| 08:57:33 | bauzas | HTH | |
| 08:57:41 | bauzas | (if I understood correctly your question) | |
| 09:02:34 | zigo | I'm not explaining what I need correctly I guess. My question is: | |
| 09:02:34 | zigo | - for alembic: how to find out what's the latest revision ID in /usr/lib/python3/dist-packges/nova/db ? | |
| 09:02:34 | zigo | - for sqla-migrate: how to find out the currently installed revision of the db in /var/lib/mysql ? | |
| 09:04:04 | bauzas | ah I see | |
| 09:04:49 | bauzas | well, I don't think we have some file saying in some variable exactly which version is the last, it's automatically calculed by alembic | |
| 09:05:06 | bauzas | but when you look at the files in github, you can find the last commit date | |
| 09:05:32 | bauzas | then, if you open one of the version (like the last committed one), you find its version + the parent one | |
| 09:07:06 | bauzas | https://github.com/openstack/nova/blob/master/nova/db/main/migrations/versions/1acf2c98e646_add_compute_id_to_instance.py#L25-L26 | |
| 09:07:13 | bauzas | that's the last revision | |
| 09:08:11 | frickler | zigo: does https://alembic.sqlalchemy.org/en/latest/tutorial.html#getting-information help? | |
| 09:08:14 | bauzas | but I guess the simpliest is calling the alembic command in the repo | |
| 09:08:51 | bauzas | yeah, "alembic current" will give you this | |
| 09:09:43 | zigo | Oh, I just found out for migrate ... :) | |
| 09:10:39 | zigo | root@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:15:32 | zigo | root@C1-cl1-controller-1>_ /usr/lib/python3/dist-packages/nova/db/main # alembic -c alembic2.ini current | |
| 09:15:33 | zigo | INFO [alembic.runtime.migration] Context impl MySQLImpl. | |
| 09:15:33 | zigo | INFO [alembic.runtime.migration] Will assume non-transactional DDL. | |
| 09:15:33 | zigo | ERROR [alembic.util.messaging] Can't locate revision identified by 'cdeec0c85668' | |
| 09:15:33 | zigo | FAILED: Can't locate revision identified by 'cdeec0c85668' | |
| 09:16:12 | 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:21 | zigo | Oh, my bad. | |
| 09:16:27 | zigo | novapidb vs novadb ... | |