Wednesday, 2026-02-25

opendevreviewmelanie witt proposed openstack/tempest master: Add tests for vTPM live migration  https://review.opendev.org/c/openstack/tempest/+/95747501:37
opendevreviewmelanie witt proposed openstack/tempest master: Add more tests for vTPM live migration  https://review.opendev.org/c/openstack/tempest/+/97790301:37
opendevreviewmelanie witt proposed openstack/whitebox-tempest-plugin master: Test vTPM live migration  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/95596901:53
opendevreviewmelanie witt proposed openstack/whitebox-tempest-plugin master: Test vTPM live migration 'deployment' mode  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/97790401:53
opendevreviewmelanie witt proposed openstack/whitebox-tempest-plugin master: Test vTPM live migration  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/95596902:01
opendevreviewmelanie witt proposed openstack/whitebox-tempest-plugin master: Test vTPM live migration 'deployment' mode  https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/97790402:01
opendevreviewMerged openstack/tempest master: Test create VM with unaddressed port  https://review.opendev.org/c/openstack/tempest/+/95918703:24
opendevreviewMerged openstack/tempest master: Replace skip with skipTest  https://review.opendev.org/c/openstack/tempest/+/97761606:09
opendevreviewBalazs Gibizer proposed openstack/tempest master: Revert "Test create VM with unaddressed port"  https://review.opendev.org/c/openstack/tempest/+/97792208:49
gibifolks ^^ needed to unblock nova-next. the original test landed during the night08:53
opendevreviewMerged openstack/tempest master: Revert "Test create VM with unaddressed port"  https://review.opendev.org/c/openstack/tempest/+/97792208:57
opendevreviewBalazs Gibizer proposed openstack/tempest master: DNM: Reapply "Test create VM with unaddressed port"  https://review.opendev.org/c/openstack/tempest/+/97793009:19
gibifolks we reverted the new tempest test blocking nova-next and now I proposed the reapply patch ^^ with an addition of nova-next job trigger to show the issue ^^09:22
opendevreviewPranali Deore proposed openstack/tempest master: Add tests for new add location api of glance  https://review.opendev.org/c/openstack/tempest/+/89102612:06
opendevreviewJohannes Kulik proposed openstack/tempest master: Test Nova API 2.101 async volume attachments  https://review.opendev.org/c/openstack/tempest/+/97795212:07
opendevreviewPranali Deore proposed openstack/tempest master: Add tests for new add location api of glance  https://review.opendev.org/c/openstack/tempest/+/89102612:11
stephenfingmaan: Care to review https://review.opendev.org/c/openstack/releases/+/977953 ? It just gets a release with the testtools skip fix out the door12:29
opendevreviewDouglas Viroel proposed openstack/devstack-plugin-prometheus master: Fix exporter URL to support multinode deployments  https://review.opendev.org/c/openstack/devstack-plugin-prometheus/+/97795613:14
fricklergmaan: sean-k-mooney: do you have some context on https://review.opendev.org/c/openstack/tempest/+/977930 ? like could it be that this is only possible with certain neutron backends? I also totally don't understand the use case for it, it seems to be very much contrary to how I expect neutron to work13:16
sean-k-mooneyfrickler: it requires specific neutron extentions to be enabled13:22
sean-k-mooneyhowever its possibel to have neutron report the extnsion to be avialable but not have ti funcitonal13:22
sean-k-mooneythe curernt patch is checkign for ip_allocation13:23
sean-k-mooneyand skiping based on that13:23
sean-k-mooneyhttps://github.com/openstack/neutron-lib/blob/master/neutron_lib/api/definitions/ip_allocation.py13:24
sean-k-mooneyi suspect that this si a bug in the ml2/ovn extion reporting13:24
sean-k-mooneythe simplest fix for now is to just add a feature flag for this to the tempest config13:25
sean-k-mooneyuntil folks have time to figure out why this is not working13:25
opendevreviewJohannes Kulik proposed openstack/tempest master: Test Nova API 2.101 async volume attachments  https://review.opendev.org/c/openstack/tempest/+/97795213:26
sean-k-mooneyfrickler: i dont see the ip_allocation exteion listed here https://github.com/openstack/neutron/blob/master/neutron/common/ovn/extensions.py#L14613:26
sean-k-mooneyso it should not be reported in ovn based jobs and it should have skiped13:27
sean-k-mooneyso i dont know why this wedged the nova-next job13:27
sean-k-mooneyis it possibel that temepst is not using the api respoce in the skip check https://review.opendev.org/c/openstack/tempest/+/977930/1/tempest/api/compute/servers/test_create_server.py#16413:30
sean-k-mooneyand relyingon its config or something?13:30
sean-k-mooneyralonsoh: ^ any idea why that is not enough or who would be able to help debug that13:33
sean-k-mooneyoh wait... nova-next is using ml2/ovs13:35
ralonsohsean-k-mooney, let me read first13:36
sean-k-mooneyreally i tought we chagne that years ago and only tested that in the nova-alt-config (formally nova-hybrid-plug) job13:36
ralonsohsean-k-mooney, in any case, that's a bug for OVN if we are missing this extension there13:37
ralonsohI'll create a bug and a patch13:37
sean-k-mooneyso nova-next is still using ml2/ovs but it is testign the ovs firewall driver13:38
sean-k-mooneyi forgot about that we wanted to test all 3 ml2/ovn ml2/ovs with ovs firewall and ml2/ovs with iptables13:39
ralonsohjust to confirm, this is failing with ovs+native FW13:39
sean-k-mooneyif i recally corectly when you added the extention filtering fature i think that was only done for ml2/ovn or started with it13:39
sean-k-mooneyralonsoh: its failling in a job that is cofnigure for that yes13:40
sean-k-mooneybut i don tknow if we have enabled that fucnctionality correctly13:40
sean-k-mooneyi think the problem might be htat ml2/ovs is reporting supprot fro it without use properly configurign it? 13:40
ralonsohlet me check the neutron API logs13:41
sean-k-mooneyi need ot check how this is ment to be enabled13:41
sean-k-mooneyack13:41
ralonsohFeb 25 09:36:20.335534 np9ec2ce0d381a4 devstack@neutron-api.service[76980]: DEBUG neutron.api.extensions [None req-ef5af19a-c63e-4033-bd14-1c11688de118 None None] Ext name="IP Allocation" alias="ip_allocation" description="IP allocation extension." updated="2016-06-10T23:00:00-00:00" {{(pid=76980) _check_extension /opt/stack/neutron/neutron/api/extensions.py:415}}13:41
ralonsohFeb 25 09:36:20.335804 np9ec2ce0d381a4 devstack@neutron-api.service[76980]: INFO neutron.api.extensions [None req-ef5af19a-c63e-4033-bd14-1c11688de118 None None] Extension ip_allocation not supported by any of loaded plugins13:41
ralonsohso no, it is discarded13:41
sean-k-mooneyright so ^ 13:41
sean-k-mooneyis the issue i was refering too13:41
sean-k-mooneythe tempest check is checkign if the extenion is reported and skiping if its not13:42
sean-k-mooneybut for ml2/ovs13:42
sean-k-mooneyit will report the extions as aviable13:42
sean-k-mooneyeven if its not properly configured13:42
sean-k-mooneyso we either need to work around that in tepemsest, fix that in neutorn with the saem filtering work you did for ovn13:42
sean-k-mooneyor fix the nova-next job to cofnigure the extion properly13:43
sean-k-mooneyor any combintion of those 313:43
ralonsohfor ovn is a matter of adding it to the static list13:44
ralonsohand for ovs, should be configured as extension13:44
sean-k-mooneydoes ovn supprot adressles ports properly? not l3 routed network but l2 networks with only a mac and no ip13:44
sean-k-mooneyit should just asking13:45
ralonsohI think it does but must be tested13:45
sean-k-mooneylike openfow can match only on the mac/ingress prot no problem13:45
sean-k-mooneywell that what the tempest test is trying to do :)13:45
sean-k-mooneywe can just use depens on to verify it13:45
ralonsohone sec13:46
ralonsohsean-k-mooney, https://review.opendev.org/c/openstack/neutron/+/97796113:51
sean-k-mooneythere is a minor ux issue by the way13:52
sean-k-mooneyto enable the ipallcoation exteion to work in neutron 13:52
sean-k-mooneyyou actully have to enabel the entirty of the segments plugin13:53
sean-k-mooneyhttps://github.com/openstack/neutron/blob/master/neutron/services/segments/plugin.py#L6713:53
sean-k-mooneyeven if you dont plan to suprpot l3 routed networks at all just unadressed ports13:53
sean-k-mooneyits unfortunet that that is requried becuase the 2 feature are mutally exclisive13:53
sean-k-mooneyyou cant use unadressed prot on l3 routed network so having to enable both via one plugin is not ideal13:54
ralonsohright, this is what is missing13:54
sean-k-mooneyanyway i think that is what we need to do in the nova next job. but the other thing that is missign is for ml2/ovs neutron shoudl add the same extension filterign feature that was implmented for ml2/ovn13:55
sean-k-mooneyso that neutron will not report it in the extenion list if no plugin that is enabeld reports supprot13:55
ralonsohbut for ovs is just a matter of adding it to the extension list in the config 13:55
ralonsohand enabling segments13:56
sean-k-mooneyright but nova and tempest but cvheck teh exention list api to knwo if the cloud supprots it13:56
sean-k-mooneyso its an api bug that a cloud that cant supprot this becuase the plugin is not enbaled reports the extions as aviabel to use13:56
sean-k-mooneythe test was passignon the other tempest jobs because ovn didnt reprot it and it was filtered out of the list13:56
sean-k-mooneyso the test woudl skip13:57
ralonsohcan you point me to this check?13:58
sean-k-mooneyhttps://review.opendev.org/c/openstack/tempest/+/977930/1/tempest/api/compute/servers/test_create_server.py#16413:58
ralonsohare we retrieving the extension list from the API or reading the config13:58
sean-k-mooneythe api13:59
sean-k-mooneywe also check the api in nova13:59
sean-k-mooneyill get that link now13:59
sean-k-mooneyso the fact that you saw that log in the neutron api server means both checks passed13:59
ralonsohlet me check how are we retrieving the extension list14:01
sean-k-mooneyok actully in nova we are just chking if the port value is populated rahter then for the exteion14:02
sean-k-mooneyso we are just passign thout the tempest requst14:02
sean-k-mooneywe coudl add a check14:02
sean-k-mooneybut that woudl nto fix this14:02
sean-k-mooneywe do check and reject request for many exteions https://github.com/openstack/nova/blob/master/nova/network/neutron.py#L1417-L151114:02
sean-k-mooneybut today we are just checkign https://github.com/openstack/nova/blob/master/nova/network/neutron.py#L2563-L256414:03
sean-k-mooneyit will be set to "imediat" for all normal ports defered is for l3 routned neworks and  the string "none" rather then python none is adress less ports14:04
ralonsohSo I can confirm that the "extension list --network" command will return only the loaded extensions14:07
sean-k-mooneydid you check that with ml2 ovs14:07
sean-k-mooneybecause the behvior is diffent unless ye fix that recently14:07
ralonsohif the extension has been discarded (for example, if you don't use service_plugin=segments), the extension won't be in the list14:07
ralonsohno, I didn't test that for ovs14:08
sean-k-mooneyok becuase when ye added the filtering it was intially only done for ml2/ovn if i recall14:08
ralonsohbut the behaviour is (should be) the same: if the extension is discarded, is not reported in the extension list14:08
ralonsohI'll try to spawn an env with ml2/ovs14:08
sean-k-mooneyand before you added the filtering feature the api reported all exteions it new about14:08
sean-k-mooneyrather then were enabled14:08
ralonsohslawek added a filtering for the extensions14:09
ralonsohso if the extensions are not required by any plugin (actually all plugins), they are discarded14:09
sean-k-mooneysorry you i ment neutron14:09
ralonsohlet me create a VM with devstack and ml2/ovs14:09
sean-k-mooneyrather then you sepcificly14:09
sean-k-mooneyi shoudl have type ye :) or neutron ot make that clear14:09
ralonsohthat could be me, probably!14:10
sean-k-mooneyFeb 25 09:36:20.334332 np9ec2ce0d381a4 devstack@neutron-api.service[76980]: DEBUG neutron.api.extensions [None req-ef5af19a-c63e-4033-bd14-1c11688de118 None None] Loading extension file: ip_allocation.py {{(pid=76980) _load_all_extensions_from_path /opt/stack/neutron/neutron/api/extensions.py:449}}14:12
sean-k-mooneyFeb 25 09:36:20.335534 np9ec2ce0d381a4 devstack@neutron-api.service[76980]: DEBUG neutron.api.extensions [None req-ef5af19a-c63e-4033-bd14-1c11688de118 None None] Ext name="IP Allocation" alias="ip_allocation" description="IP allocation extension." updated="2016-06-10T23:00:00-00:00" {{(pid=76980) _check_extension /opt/stack/neutron/neutron/api/extensions.py:415}}14:12
sean-k-mooneyFeb 25 09:36:20.335804 np9ec2ce0d381a4 devstack@neutron-api.service[76980]: INFO neutron.api.extensions [None req-ef5af19a-c63e-4033-bd14-1c11688de118 None None] Extension ip_allocation not supported by any of loaded plugins14:12
sean-k-mooneyso i see that14:12
sean-k-mooneybut i dont see anywhere in the logs wehere we do a neutron extions list14:12
sean-k-mooneythat might be nice ot add to devstack ro world dump or similar14:12
sean-k-mooneyso that we have that for debugging14:12
ralonsohthat would be helpful, yes, a debug log in tempest14:13
sean-k-mooneyralonsoh: https://paste.opendev.org/show/bUzT6XpEgq1nmzKN07tL/14:36
sean-k-mooneyralonsoh: so as i mentioned the fitlering was only implented for ovn explcityly the other ml2 drier just rely on the base implemetion 14:40
sean-k-mooneyhttps://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/plugin.py#L21714:40
sean-k-mooneywith that said the ip_alloctions one is not in the defualt list14:40
opendevreviewTakashi Kajinami proposed openstack/devstack master: Drop installation of tox  https://review.opendev.org/c/openstack/devstack/+/97797014:40
sean-k-mooneyso it should only get reported if the segments plugin is enabled14:41
sean-k-mooneyso im not really sure why the test is failing14:42
ralonsohsean-k-mooney, but this method `supported_extensions` is the only different thing between ML2/OVN and OVS14:52
ralonsohthe `_filter_extensions_by_mech_driver` is executed too and the extension discarding14:52
sean-k-mooneyyep so it shoudl work on master14:53
ralonsohso if service_plugin=segment is not loaded in any mech driver, the ip_allocation extension won't never be present14:53
sean-k-mooneyright14:53
sean-k-mooneythere is only 1 mechahim driver enabeld in this job ovs14:54
sean-k-mooneywe have ervice_plugins = router,neutron.services.metering.metering_plugin.MeteringPlugin,placement,trunk,qos14:56
sean-k-mooneyhttps://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_c82/openstack/c82065804d7e4297a6882fde834ce558/controller/logs/etc/neutron/neutron_conf.txt14:56
sean-k-mooneyso segments is not enabeld and tempest should have skipped14:57
opendevreviewTanvi Nautiyal proposed openstack/tempest master: Add TempURL prefix-based access test  https://review.opendev.org/c/openstack/tempest/+/97797615:39
fricklerif someone has a moment for this bionic cleanup that'd be nice https://review.opendev.org/c/openstack/devstack/+/977191 + 97719219:02
gmaandone19:35
gmaangibi: frickler thanks for reverting and merging the broken test. it was passing neutron plugin but need to check why it failed in nova-next19:35
fricklergmaan: see the backlog, seems neutron isn't handling the extension reporting correctly20:20
gmaank, will read it20:20
sean-k-mooneywe can make it pass by enableing the segments service plugin in nova-next but it shoudl have been skiped without that and it was not21:42
sean-k-mooneyso ya we need to get to the bottom of that21:42
opendevreviewMerged openstack/devstack master: Drop installation of tox  https://review.opendev.org/c/openstack/devstack/+/97797022:53

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