Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2021-08-05
13:53:34 opendevreview Balazs Gibizer proposed openstack/nova master: Block servers wit vGPU and device profile in heal_allocations https://review.opendev.org/c/openstack/nova/+/803603
13:53:42 gibi bauzas: thanks, and here is the doc and block ^^
13:57:01 bauzas gibi: looking
15:08:27 melwitt bauzas: I'm gonna respond on the review too but the "unknown" is not a default consumer type, it's a cosmetic-only label for friendliness to the user. (same with the "all" label as a query parameter). a consumer with no type has NULL in the column. the reproposal of the spec has removed mention of the original proposed "UNKNOWN" official default type. during review reviewers preferred to leave NULL to represent the absence of a consumer
15:08:29 melwitt type
15:08:46 bauzas melwitt: oh ok
15:08:58 bauzas I only looked at the train spec
15:09:08 bauzas when this was something as a gerrit spec :p
15:09:09 melwitt ah gotcha
15:09:25 bauzas melwitt: will then remove my -1
15:09:41 melwitt cool thanks :)
15:10:08 bauzas (and yeah sorry I cheated :p )
15:11:13 melwitt haha no worry
15:14:08 lyarwood https://review.opendev.org/c/openstack/nova/+/803585 btw gibi / stephenfin / melwitt ; moving the LM jobs to NV for the time being while someone looks at the underlying QEMU failure(s)
15:14:48 melwitt /sad trombone sound
15:18:41 melwitt kashyap: I see you have commented on https://launchpad.net/bugs/1912310 before ^ but no leads yet right?
15:18:54 kashyap melwitt: Hi, /me looks
15:19:13 kashyap (The bot doesn't seem to higlight the summary on IRC anymore)
15:20:29 melwitt hm yeah not sure what happened to the bot
15:20:51 kashyap melwitt: Yeah, no leads yet
15:22:07 kashyap melwitt: Is it hitting more often? Looks like so from gibi's #7 on 31Jul
15:22:46 melwitt kashyap: yeah, lyarwood is proposing above making the live migration job non-voting because of it
15:23:03 kashyap melwitt: Oh, yeah - just saw that
15:55:48 bauzas lyarwood: unfortunately +Wd the live-mig job be non-votign
15:56:02 lyarwood ack thanks
16:06:35 gibi about the bug resolver bot I asked infra they said that https://meetings.opendev.org/irclogs/%23opendev/%23opendev.2021-08-03.log.html#t2021-08-03T16:31:32
16:11:16 melwitt thanks gibi
16:14:20 gibi so probably we lost the both the topic handling and the bug resolving capability of the bot during that transformatin
16:43:02 gibi If I had time I would be happy working on those bots
18:11:55 opendevreview Merged openstack/nova master: zuul: Mark live migration jobs as non-voting due to bug #1912310 https://review.opendev.org/c/openstack/nova/+/803585
21:12:41 nurdie Hey OS nova! I had to evacuate a failed compute node (it's super dead) on shared storage (ceph). 3 instances are hanging in "nova migration-list" as "accepted" but are already on another compute node. Does anyone know what galera db.table I can edit real quick to clear that up?
23:23:58 opendevreview melanie witt proposed openstack/placement master: Add consumer_types migration, database and object changes https://review.opendev.org/c/openstack/placement/+/669170
23:24:06 opendevreview melanie witt proposed openstack/placement master: Microversion 1.38: API support for consumer types https://review.opendev.org/c/openstack/placement/+/679441
23:24:11 opendevreview melanie witt proposed openstack/placement master: Switch ConsumerType to use an AttributeCache https://review.opendev.org/c/openstack/placement/+/679486
23:24:35 melwitt bauzas: updated first patch per your comments ^
#openstack-nova - 2021-08-06
00:18:06 opendevreview Brin Zhang proposed openstack/nova master: Replace all_tenants with all_projects in List Server APIs https://review.opendev.org/c/openstack/nova/+/765311
01:45:00 opendevreview Qiu Fossen proposed openstack/nova master: Allow migrating PMEM's data https://review.opendev.org/c/openstack/nova/+/802225
03:06:33 opendevreview melanie witt proposed openstack/placement master: Switch ConsumerType to use an AttributeCache https://review.opendev.org/c/openstack/placement/+/679486
07:55:55 lyarwood gibi: Morning, https://bugs.launchpad.net/nova/+bug/1939108 but on the positive side, logsearch++
08:06:18 aarents bauzas: thanks for https://review.opendev.org/c/openstack/nova/+/764435 review, I applied the rephrasing.
08:13:22 gibi lyarwood: morning! could this be related to the guest blocking or delaying the detach attempt? I vaguly remember we discussed such option before
08:14:52 lyarwood gibi: yeah it's likely that, I need to push the tempest change ahead to rework detach so we actually dump the console to know either way
08:15:08 lyarwood iirc it was failing on something random the last time I rechecked
08:15:18 lyarwood https://review.opendev.org/c/openstack/tempest/+/794757
08:15:45 lyarwood yeah unrelated test_create_list_show_delete_interfaces_by_network_port ssh timeouts
08:15:48 lyarwood /o\
08:15:50 lyarwood rechecks again
08:16:17 lyarwood actually rebase as it has been that long
08:20:11 lyarwood gibi: https://github.com/gibizer/zuul-log-search-config/pull/1 btw, have a few ideas about the tool itself but I might not have time to hack on it until next week
08:29:56 gibi ohh, ok, lets hope the console log reveale something, other than that we can only increase timeout for the single detach attempt or increase the amount of retry we do
08:30:39 lyarwood indeed, 1 hit in the last 100 failures however suggests we are somewhere close to getting this right in CI finally
08:31:11 gibi lyarwood: if you have ideas about the feel free to note them in an github issue or directly in the TODO.md in the repo
08:31:53 lyarwood ack will do, it's mostly basic stuff like an argument for number of days back to search for etc and maybe a handler for logstash but that's it at the moment
08:31:56 gibi lyarwood: thanks for looking at that func faiure I had the intention to look at both func faiures but I had no time since and probablny not even today
08:40:49 bauzas aarents: thanks for the ping, just rechecked and +2d
08:43:53 aarents bauzas: thanks
09:08:16 opendevreview Pierre Libeau proposed openstack/nova master: Move file system freeze after end of mirroring https://review.opendev.org/c/openstack/nova/+/803713
09:08:59 opendevreview Lee Yarwood proposed openstack/nova master: func: Increase rpc_response_timeout in TestMultiCellMigrate tests https://review.opendev.org/c/openstack/nova/+/803714
09:09:52 lyarwood gibi / bauzas / stephenfin ; ^ okay I think that's a pretty trivial fix to the functional failures, I don't get why it's suddenly an issue but as this RPC call to the conductor then calls down to the source I'm assuming we've added some additional overhead somewhere and were not creeping over the 1 second timeout in the test.
09:10:10 lyarwood are now*
09:12:58 gibi lyarwood: will check soon
09:42:57 kashyap lyarwood: What's the "best" manual way to change the video model for an existing instance? (Asking for a friend.) Is the following painful approach the only way?
09:43:30 kashyap lyarwood: (1) Stop the instance. (2) snapshot it (what kind?). (3) Update the metadata on the snapshot image to use 'virtio' display dev. (4) Then rebuild the instance using the snapshot
09:43:34 kashyap Any better way than that?
09:43:54 kashyap (Besides the future goodness of 'nova-manage' command akin to machine_type update)
09:44:27 lyarwood if you want to persist the instance data then yeah I think that's the only way
09:44:42 lyarwood I don't think resize would change it
09:45:16 kashyap I see.
09:45:41 kashyap And for new instances, obviously start with: openstack image set --property hw_video_model=virtio [...]
09:46:54 lyarwood yeah
09:48:00 kashyap Or:
09:48:01 kashyap $ openstack server create --flavor m1.micro \
09:48:01 kashyap --image Fedora34 \
09:48:01 kashyap --property 'hw_video_model=virtio' vm1
09:48:05 kashyap Thanks!
09:52:10 lyarwood I don't think the second command is valid?
09:54:53 lyarwood oh it's metadata
09:55:07 lyarwood so yeah that isn't going to do anything kashyap
09:55:53 kashyap lyarwood: Oh, I see. So what's the way again to set the prop while creating the server?
09:56:35 lyarwood For new servers you would update the associated image
09:56:49 lyarwood for the existing server case you'd update the snapshot image
09:57:03 lyarwood and then in both create a new server from the image
09:57:36 opendevreview Merged openstack/nova master: compute: Avoid duplicate BDMs during reserve_block_device_name https://review.opendev.org/c/openstack/nova/+/801990
09:58:19 stephenfin kashyap: Echoing what lyarwood said, we don't expose this kind of knob via flavor extra specs. It's only possible via image metadata properties which rn require a rebuild to change
09:58:59 kashyap stephenfin: lyarwood: Thank you very much, both. I don't have this top off my head.
09:59:02 stephenfin kashyap: you can find a full list of all supported extra specs here https://docs.openstack.org/nova/latest/configuration/extra-specs.html
09:59:05 kashyap I'll correct my mistake on a bugzilla
10:01:51 opendevreview Lee Yarwood proposed openstack/nova stable/wallaby: Add functional test for bug 1937375 https://review.opendev.org/c/openstack/nova/+/803717
10:01:52 opendevreview Lee Yarwood proposed openstack/nova stable/wallaby: compute: Avoid duplicate BDMs during reserve_block_device_name https://review.opendev.org/c/openstack/nova/+/803718
10:02:04 pjakuszew kashyap: I wrote a script which modifes extra_specs on existing instances, though I consider it dangerous
10:02:38 kashyap pjakuszew: Heh, understood. The intersting question is - did it work reliably for you, without any nasty side-effects?
10:03:28 opendevreview Lee Yarwood proposed openstack/nova stable/victoria: Add functional test for bug 1937375 https://review.opendev.org/c/openstack/nova/+/803720
10:03:29 opendevreview Lee Yarwood proposed openstack/nova stable/victoria: compute: Avoid duplicate BDMs during reserve_block_device_name https://review.opendev.org/c/openstack/nova/+/803721
10:04:59 pjakuszew kashyap: In my case it was a case of adding a cpu_type key to a flavor, then syncing the flavor metadata to instance and reqspec extra_specs - in your case (hw_video_model=virtio) I guess you will have to do a hard reboot so the libvirt xmls will be regenerated
10:05:32 kashyap pjakuszew: Yep; in this case hard-reboot is unavoidable
10:06:44 pjakuszew let me check it, one sec
10:13:47 kashyap pjakuszew: Note, though: I don't have any environment to try this out. I'm just documenting some stuff due to a fallout downstream
10:13:53 kashyap But thank you! :)
10:15:22 pjakuszew kashyap: sure, I'm checking the differences between the xmls with and without properties right now
10:15:43 pjakuszew so I can check if the metadata change was properly propagated after hard reboot later

Earlier   Later