| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2026-04-22 | |||
| 19:29:45 | sean-k-mooney | you will also need to set it for the subvar | |
| 19:29:58 | melwitt | ack | |
| 19:30:18 | sean-k-mooney | we can proably fix this in the devstack defintion to be based on if you have selecte ipv4 or ipv6 for the serivce ip later | |
| 19:31:22 | sean-k-mooney | in the job defintion we are seting SERVICE_IP_VERSION: 6 so we have something to switch off | |
| 19:31:41 | sean-k-mooney | withthat said if i look at the job vriable for the compute | |
| 19:31:43 | sean-k-mooney | https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_dcc/openstack/dcc395a124c04f4fbc3368ddf97400d3/zuul-info/inventory.yaml | |
| 19:32:01 | sean-k-mooney | i see a lot of other ip v4 stuff there but we can revisti that if needed | |
| 19:32:43 | opendevreview | melanie witt proposed openstack/nova master: DNM test ceph ipv6 https://review.opendev.org/c/openstack/nova/+/984623 | |
| 19:33:22 | sean-k-mooney | melwitt: as an asside we started looking at this because we wanted to test a patch that was related to it | |
| 19:33:32 | sean-k-mooney | melwitt: do you recall if we you knwo merged that bug fix? | |
| 19:33:43 | sean-k-mooney | the libvirt migration one | |
| 19:34:06 | melwitt | right. no we did not merge it yet and I have been trying to make this work in order to verify it | |
| 19:34:13 | sean-k-mooney | ack | |
| 19:34:16 | melwitt | I'm not opposed to merging it without verification but it would be really great to be able to | |
| 19:34:43 | sean-k-mooney | oh ya i agree it would be good to have it | |
| 19:34:59 | sean-k-mooney | i just lost context on where we were at with the patch | |
| 19:35:06 | melwitt | after seeing that XML ipv6 brackets thing, I am feeling like I really want to see this work haha | |
| 19:35:16 | sean-k-mooney | yep | |
| 19:35:23 | sean-k-mooney | ok im going to wrap for today | |
| 19:36:09 | melwitt | it looks fine to me. just wanted to see if I could do this. if not, I'll just review it without | |
| 19:36:16 | sean-k-mooney | ill try and remember to check the resutls of tha trun but feel free to ping me to take another look | |
| 19:36:41 | melwitt | cool thanks for the help | |
| 19:37:19 | sean-k-mooney | melwitt: by the way i said this before but there is currently no ipv6 + ceph covage anywhere. i dont even think there is singel node | |
| 19:37:41 | sean-k-mooney | so defintly nice ot fix that at some point | |
| 19:37:57 | melwitt | ++ | |
| 19:39:16 | isaacvicente[m] | hi guys o/ i would like to start solving this bug: https://bugs.launchpad.net/nova/+bug/2035911 | |
| 19:39:16 | isaacvicente[m] | given the last time it was assigned to someone, its ok to assign to myself? i replied on the bug but got no reponse | |
| 19:40:38 | melwitt | isaacvicente[m]: yeah I would go ahead and assign it to yourself | |
| 19:48:10 | isaacvicente[m] | nice, i started looking into it, and i wonder where I would do the changes. Trying to understand better the bug and the code base itself I asked chatgpt-codex-5.3 where the changes would be. It said that drivers under nova/virt/libvirt/volumes has two functions: connect_volume and disconnect_volume. I would then add the os-brick context manager guard_connections on those functions. I'm not sure if this is the right | |
| 19:48:10 | isaacvicente[m] | direction. Does it make sense? | |
| 19:49:05 | isaacvicente[m] | * nice, i started looking into it, and i wonder where I would do the changes. Trying to understand better the bug and the code base itself I asked chatgpt-codex-5.3 where the changes would be. It said that drivers under nova/virt/libvirt/volumes has two functions: connect_volume and disconnect_volume. I would then add the os-brick context manager guard_connection on those functions. I'm not sure if this is the right | |
| 19:49:05 | isaacvicente[m] | direction. Does it make sense? | |
| #openstack-nova - 2026-04-23 | |||
| 00:58:55 | opendevreview | melanie witt proposed openstack/nova master: DNM test ceph ipv6 https://review.opendev.org/c/openstack/nova/+/984623 | |
| 02:09:31 | opendevreview | Takashi Kajinami proposed openstack/nova-specs master: libvirt: AMD SEV-SNP support https://review.opendev.org/c/openstack/nova-specs/+/983376 | |
| 09:01:53 | dougszu | sean-k-mooney - morning, the bug about ephemeral volume corruption during VM migration (https://bugs.launchpad.net/nova/+bug/2095173) has that been fixed in Nova by dropping the creation of a filesystem in the base image? | |
| 12:12:56 | lajoskatona | Uggla: Hi, today I have a topic for os-external-events vs Neutron notifier vs SDK (https://etherpad.opendev.org/p/nova-2026.2-ptg#L771), shall I ask to have it discussed before 1530UTC (1730 CEST) as I have to drop around that time ? | |
| 12:16:27 | Uggla | Hi lajoskatona, it should happen around 1400 / 1430UTC. So yes. | |
| 12:19:05 | lajoskatona | Uggla: thanks | |
| 12:53:05 | jkulik | How come n-api and n-scheduler require a cell DB? Is it just to be able to register as a compute service? | |
| 12:59:51 | sean-k-mooney | jkulik: its used for 2 thing | |
| 13:00:09 | sean-k-mooney | so cell 0 is where all the service entries for the global serviece live i..e the schdluer/api ecta | |
| 13:00:36 | jkulik | ah. cell0! thanks, I thought I'd have to use a productive cell | |
| 13:00:37 | sean-k-mooney | its also used to sotre instance that cannot be schduled ot "real" "comptue" cells | |
| 13:00:51 | sean-k-mooney | jkulik: ya no you put those in cell 0 | |
| 13:01:02 | jkulik | thank you. helped a lot | |
| 13:01:26 | sean-k-mooney | right os the api need a plce to stre the full instnace object for an instance that failed to go to a real cell so we just use that for the service records as well | |
| 13:01:53 | jkulik | yeah. makes sense. thanks again | |
| 13:02:46 | sean-k-mooney | i dont think it woudl breake anything to have the scuder use the cell1 db isntead but it buys you nothing either because you still need cell0 and the schduelr does not work per cell so we recommend cell0 because it alwasy extis and it shoudl be under less load | |
| 13:02:55 | sean-k-mooney | jkulik: no worries | |
| 13:47:29 | opendevreview | Lajos Katona proposed openstack/nova master: Use SDK for Neutron security-groups https://review.opendev.org/c/openstack/nova/+/981141 | |
| 13:55:58 | opendevreview | Takashi Kajinami proposed openstack/nova-specs master: libvirt: AMD SEV-SNP support https://review.opendev.org/c/openstack/nova-specs/+/983376 | |
| 14:35:40 | opendevreview | Anton Iacobaeus proposed openstack/nova-specs master: Intel TDX support in libvirt driver https://review.opendev.org/c/openstack/nova-specs/+/979608 | |
| 14:58:04 | bauzas | Uggla: planning any break after the current discussion ? I'm afraid to say I'm a little fried and I need coffee | |
| 14:58:56 | Uggla | Yes I'd like to have a short 5mn break if TheJulia and dansmith are ok. | |
| 15:01:45 | TheJulia | fine with me | |
| 15:06:45 | Uggla | TheJulia thx | |
| 15:07:07 | tkajinam | just in case someone can answer this question ... In case we remove a trait from a compute host RP, it does not care any existing instance requires that trait, right ? | |
| 15:09:33 | TheJulia | That is an interesting question and relates to the next topic :) | |
| 15:10:07 | dansmith | tkajinam: no, nothing will break | |
| 15:10:37 | dansmith | meaning, there's no checking like that, nor any implication that traits now mean traits in the future or past | |
| 15:10:46 | TheJulia | That is what I was thinking based upon what was in my recall of nova code, because its far past the use of scheduling | |
| 15:10:52 | tkajinam | ok | |
| 15:11:00 | tkajinam | and that's what I thought | |
| 16:23:49 | opendevreview | Stephen Finucane proposed openstack/os-vif master: pre-commit: Bump versions https://review.opendev.org/c/openstack/os-vif/+/976358 | |
| 16:23:50 | opendevreview | Stephen Finucane proposed openstack/os-vif master: Migrate setup configuration to pyproject.toml https://review.opendev.org/c/openstack/os-vif/+/976359 | |
| 16:23:51 | opendevreview | Stephen Finucane proposed openstack/os-vif master: tests: Remove errant parameters https://review.opendev.org/c/openstack/os-vif/+/976360 | |
| 16:23:52 | opendevreview | Stephen Finucane proposed openstack/os-vif master: trivial: Use bit shifting https://review.opendev.org/c/openstack/os-vif/+/976361 | |
| 16:23:54 | opendevreview | Stephen Finucane proposed openstack/os-vif master: typing: Add initial type annotations https://review.opendev.org/c/openstack/os-vif/+/745162 | |
| 16:23:56 | opendevreview | Stephen Finucane proposed openstack/os-vif master: typing: Add typing to vif_plug_noop module https://review.opendev.org/c/openstack/os-vif/+/976362 | |
| 16:23:58 | opendevreview | Stephen Finucane proposed openstack/os-vif master: WIP: typing: Add typing to vif_plug_ovs module https://review.opendev.org/c/openstack/os-vif/+/976363 | |
| 18:21:15 | opendevreview | Dan Smith proposed openstack/python-novaclient master: Remove deprecation warning workaround https://review.opendev.org/c/openstack/python-novaclient/+/985993 | |
| 19:25:39 | sean-k-mooney | melwitt: so picking up our conversation form yestereday https://zuul.opendev.org/t/openstack/build/a5324089fe45434ca8ed15a8de9e12a3 the failure in that job is weried. | |
| 19:26:26 | melwitt | yeah I have seen that before and I never understand how the thing doesn't have the 'openstack' command | |
| 19:26:49 | sean-k-mooney | if i look at the local.conf the SERVICE_HOST didnt make it to the local.conf https://zuul.opendev.org/t/openstack/build/a5324089fe45434ca8ed15a8de9e12a3/log/controller/logs/local_conf.txt | |
| 19:27:09 | melwitt | the last revision of the ipv6 devstack stuff I think messed up the expected format for an apache config for the listen address so I'm trying to figure that out | |
| 19:27:37 | melwitt | hm | |
| 19:27:46 | sean-k-mooney | that form world dbump if we fail really early i.e. beofre devstack has run and installed it | |
| 19:28:19 | sean-k-mooney | ack so looking at the logs we dont have a stack log | |
| 19:28:31 | sean-k-mooney | so we failed super early in the job | |
| 19:28:45 | melwitt | oh maybe it's expected it wouldn't be in local.conf bc it's under devstack_localrc not devstack_local_conf | |
| 19:29:17 | melwitt | it's been comical how difficult getting the f'ing ipv6 url format right for the different parts has been | |
| 19:29:32 | sean-k-mooney | its also not in https://zuul.opendev.org/t/openstack/build/a5324089fe45434ca8ed15a8de9e12a3/log/controller/logs/_.localrc_auto.txt | |
| 19:29:40 | melwitt | some need the brackets or it blows up, some have to not have the brackets or it blows up. I'm really not liking whoever invented brackets | |
| 19:30:46 | sean-k-mooney | lol you might be cursed. | |
| 19:30:51 | sean-k-mooney | https://zuul.opendev.org/t/openstack/build/a5324089fe45434ca8ed15a8de9e12a3/log/zuul-info/zuul-info.controller.txt | |
| 19:31:09 | melwitt | probably | |
| 19:31:10 | sean-k-mooney | i dont know if that will break it but that host does nto have a publicly reoutable ipv6 adresss | |
| 19:31:23 | sean-k-mooney | i guess link local ipv6 could work | |
| 19:31:38 | sean-k-mooney | but i dont know if that will show up in teh default ipv6 varibale | |
| 19:32:13 | sean-k-mooney | SERVICE_HOST: '[{{hostvars[''controller''][''ansible_default_ipv6''][''address'']}}]' | |
| 19:32:22 | melwitt | yeah ... I wonder is this a futile endeavor? how can we make sure our zuul nodes have routable ipv6 addresses? | |
| 19:32:43 | sean-k-mooney | although HOST_IP: '{{ hostvars[inventory_hostname][''nodepool''][''private_ipv4''] | |
| 19:32:45 | sean-k-mooney | }}' | |
| 19:32:55 | sean-k-mooney | is the host ip var so the double '' i guess is expected | |
| 19:33:17 | melwitt | ansible_default_ipv6: {} | |
| 19:33:32 | melwitt | in https://zuul.opendev.org/t/openstack/build/a5324089fe45434ca8ed15a8de9e12a3/log/zuul-info/host-info.controller.yaml | |
| 19:34:38 | sean-k-mooney | https://zuul.opendev.org/t/openstack/build/a5324089fe45434ca8ed15a8de9e12a3/log/zuul-info/host-info.controller.yaml#214 | |
| 19:34:50 | melwitt | I was just looking at that | |
| 19:34:54 | sean-k-mooney | so we could get the first ipv6 adress if we knw the interface name | |
| 19:35:01 | melwitt | and that shows up in ansible_all_ipv6_addresses | |