March 2022 - openstack-discuss - lists.openstack.org

[yoga][horizon] Broken Horizon plugins UT: murano-dashboard, magnum-ui, heat-dashboard
by Thomas Goirand 31 Mar '22

31 Mar '22

Hi, Building Horizon plugins for yoga after upgrading to Horizon 22.1.0 lead me to broken unit tests. I haven't filed separate bugs yet, as I'd like to have the opinion of upstream about what's going on first. I've pushed the build logs over here: http://shade.infomaniak.ch/yoga-dashboard-plugins-build-logs/ So, what's going on? :) Cheers, Thomas Goirand (zigo) P.S: These are the last remaining failed to build issues I have for Yoga, everything else has been uploaded already.

2 2

[Ironic]After deleting server on bare metal node, baremetal node clean failed because pxe dhcp no reply
by 韩光宇 31 Mar '22

31 Mar '22

Hi all, I have a OpenStack Victoria All-in-One environment, and I can deploy os to bare metal by Ironic. I use `openstack server create --flavor my-baremetal-flavor --nic net-id=$PROVISION_UUID --image $whiole-disk-image BM-server-01` to get a server successfully. But if I delete server by "openstack server delete BM-server-01", baremetal node will be clean. When baremetal node performs the clean process, it enters the PXE phase, but its DHCP request cannot be replied. The log of ironic-conductor: 2022-03-31 11:40:42.572 63976 INFO ironic.conductor.task_manager [req-9e92ea87-d48c-42ed-83fd-2f7f14a20984 8763be6de0434240803f305c895fced5 a1758405f9c24ae191543248ad65a447 - default default] Node 4b243894-d651-4700-9a69-28ca3c60446f moved to provision state "clean wait" from state "cleaning"; target provision state is "available" 2022-03-31 12:11:06.694 63976 ERROR ironic.conductor.task_manager [req-3ff5cebf-0895-4e85-bf75-4ac1d20b30f4 - - - - -] Node 4b243894-d651-4700-9a69-28ca3c60446f moved to provision state "clean failed" from state "clean wait"; target provision state is "available" 2022-03-31 12:11:07.676 63976 INFO ironic.drivers.modules.network.flat [-] Removing ports from cleaning network for node 4b243894-d651-4700-9a69-28ca3c60446f 2022-03-31 12:11:08.218 63976 INFO ironic.common.neutron [-] Successfully removed node 4b243894-d651-4700-9a69-28ca3c60446f neutron ports. 2022-03-31 12:11:08.222 63976 ERROR ironic.conductor.utils [-] Timeout reached while cleaning the node. Please check if the ramdisk responsible for the cleaning is running on the node. Failed on step {}. The log of tcpdump in openstack: # tcpdump -n -S -i br-ex port 67 or port 68 or port 69 11:44:43.358657 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:46.550963 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:51.558266 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:57.374583 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:57.375096 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:57.691646 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:57.807714 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:57.907428 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 11:44:58.027351 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 18:9b:a5:81:46:b7, length 300 The log of /var/log/neutron/dhcp-agent.log: 2022-03-31 11:40:18.373 47489 INFO neutron.agent.dhcp.agent [-] Trigger reload_allocations for port admin_state_up=True, allowed_address_pairs=[], binding:host_id=, binding:profile=, binding:vif_details=, binding:vif_type=unbound, binding:vnic_type=baremetal, created_at=2022-03-31T03:40:18Z, description=, device_id=4b243894-d651-4700-9a69-28ca3c60446f, device_owner=, extra_dhcp_opts=[], fixed_ips=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d29aeeb8>], id=20e8d806-f976-4415-85f5-ed2df55978dc, mac_address=fa:16:3e:f1:b3:aa, name=, network=admin_state_up=True, availability_zone_hints=[], availability_zones=['nova'], created_at=2022-03-28T08:39:24Z, description=, id=faa2b805-7898-4fb2-ad51-49251da6e35e, ipv4_address_scope=None, ipv6_address_scope=None, is_default=False, mtu=1500, name=provider1, port_security_enabled=True, project_id=a1758405f9c24ae191543248ad65a447, provider:network_type=flat, provider:physical_network=provider, provider:segmentation_id=None, revision_number=2, router:external=True, shared=True, status=ACTIVE, subnets=['2d5d4c2c-8c8c-44ef-92b4-a124ed52030f'], tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-28T08:39:29Z, vlan_transparent=None, network_id=faa2b805-7898-4fb2-ad51-49251da6e35e, port_security_enabled=True, project_id=a1758405f9c24ae191543248ad65a447, revision_number=1, security_groups=['f574b5d0-8308-40f4-a8e5-81126b920e8f'], status=DOWN, tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-31T03:40:18Z on network _ns_name=qdhcp-faa2b805-7898-4fb2-ad51-49251da6e35e, admin_state_up=True, availability_zone_hints=[], availability_zones=['nova'], created_at=2022-03-28T08:39:24Z, description=, id=faa2b805-7898-4fb2-ad51-49251da6e35e, ipv4_address_scope=None, ipv6_address_scope=None, is_default=False, mtu=1500, name=provider1, non_local_subnets=[], port_security_enabled=True, ports=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a16a98>], project_id=a1758405f9c24ae191543248ad65a447, provider:network_type=flat, provider:physical_network=provider, provider:segmentation_id=None, revision_number=2, router:external=True, shared=True, status=ACTIVE, subnets=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a169d8>], tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-28T08:39:29Z, vlan_transparent=None 2022-03-31 11:40:18.516 47489 INFO neutron.agent.dhcp.agent [req-9b1713fa-1082-4ccf-8c8b-e953beaf5e5d - - - - -] DHCP configuration for ports {'20e8d806-f976-4415-85f5-ed2df55978dc'} is completed 2022-03-31 11:40:19.517 47489 INFO neutron.agent.dhcp.agent [-] Trigger reload_allocations for port admin_state_up=True, allowed_address_pairs=[], binding:host_id=4b243894-d651-4700-9a69-28ca3c60446f, binding:profile=local_link_information=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d29aeb28>], binding:vif_details=, binding:vif_type=unbound, binding:vnic_type=baremetal, created_at=2022-03-31T03:40:18Z, description=, device_id=4b243894-d651-4700-9a69-28ca3c60446f, device_owner=baremetal:none, extra_dhcp_opts=[], fixed_ips=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d29aefa8>], id=20e8d806-f976-4415-85f5-ed2df55978dc, mac_address=18:9b:a5:81:46:b7, name=, network_id=faa2b805-7898-4fb2-ad51-49251da6e35e, port_security_enabled=True, project_id=a1758405f9c24ae191543248ad65a447, revision_number=2, security_groups=['f574b5d0-8308-40f4-a8e5-81126b920e8f'], status=DOWN, tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-31T03:40:19Z on network _ns_name=qdhcp-faa2b805-7898-4fb2-ad51-49251da6e35e, admin_state_up=True, availability_zone_hints=[], availability_zones=['nova'], created_at=2022-03-28T08:39:24Z, description=, id=faa2b805-7898-4fb2-ad51-49251da6e35e, ipv4_address_scope=None, ipv6_address_scope=None, is_default=False, mtu=1500, name=provider1, non_local_subnets=[], port_security_enabled=True, ports=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a16a98>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d29aeaf8>], project_id=a1758405f9c24ae191543248ad65a447, provider:network_type=flat, provider:physical_network=provider, provider:segmentation_id=None, revision_number=2, router:external=True, shared=True, status=ACTIVE, subnets=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a169d8>], tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-28T08:39:29Z, vlan_transparent=None 2022-03-31 11:40:19.649 47489 INFO neutron.agent.dhcp.agent [req-7b9253ec-0a60-4309-ac66-8e3ea167cbba - - - - -] DHCP configuration for ports {'20e8d806-f976-4415-85f5-ed2df55978dc'} is completed 2022-03-31 11:40:19.678 47489 INFO neutron.agent.dhcp.agent [-] Trigger reload_allocations for port admin_state_up=True, allowed_address_pairs=[], binding:host_id=4b243894-d651-4700-9a69-28ca3c60446f, binding:profile=local_link_information=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d29c88e8>], binding:vif_details=, binding:vif_type=binding_failed, binding:vnic_type=baremetal, created_at=2022-03-31T03:40:18Z, description=, device_id=4b243894-d651-4700-9a69-28ca3c60446f, device_owner=baremetal:none, extra_dhcp_opts=[], fixed_ips=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d29c8558>], id=20e8d806-f976-4415-85f5-ed2df55978dc, mac_address=18:9b:a5:81:46:b7, name=, network_id=faa2b805-7898-4fb2-ad51-49251da6e35e, port_security_enabled=True, project_id=a1758405f9c24ae191543248ad65a447, revision_number=3, security_groups=['f574b5d0-8308-40f4-a8e5-81126b920e8f'], status=DOWN, tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-31T03:40:19Z on network _ns_name=qdhcp-faa2b805-7898-4fb2-ad51-49251da6e35e, admin_state_up=True, availability_zone_hints=[], availability_zones=['nova'], created_at=2022-03-28T08:39:24Z, description=, id=faa2b805-7898-4fb2-ad51-49251da6e35e, ipv4_address_scope=None, ipv6_address_scope=None, is_default=False, mtu=1500, name=provider1, non_local_subnets=[], port_security_enabled=True, ports=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a16a98>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d28b53d8>], project_id=a1758405f9c24ae191543248ad65a447, provider:network_type=flat, provider:physical_network=provider, provider:segmentation_id=None, revision_number=2, router:external=True, shared=True, status=ACTIVE, subnets=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a169d8>], tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-28T08:39:29Z, vlan_transparent=None 2022-03-31 11:40:19.776 47489 INFO neutron.agent.dhcp.agent [req-99eb793a-230c-490a-b126-ee9b595ed1bf - - - - -] DHCP configuration for ports {'20e8d806-f976-4415-85f5-ed2df55978dc'} is completed 2022-03-31 11:40:21.082 47489 INFO neutron.agent.dhcp.agent [-] Trigger reload_allocations for port admin_state_up=True, allowed_address_pairs=[], binding:host_id=4b243894-d651-4700-9a69-28ca3c60446f, binding:profile=local_link_information=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d288ea68>], binding:vif_details=, binding:vif_type=binding_failed, binding:vnic_type=baremetal, created_at=2022-03-31T03:40:18Z, description=, device_id=4b243894-d651-4700-9a69-28ca3c60446f, device_owner=baremetal:none, extra_dhcp_opts=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d288e9a8>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d288ed38>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d288e4f8>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d288e528>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d288e948>], fixed_ips=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d288e0a8>], id=20e8d806-f976-4415-85f5-ed2df55978dc, mac_address=18:9b:a5:81:46:b7, name=, network_id=faa2b805-7898-4fb2-ad51-49251da6e35e, port_security_enabled=True, project_id=a1758405f9c24ae191543248ad65a447, revision_number=4, security_groups=['f574b5d0-8308-40f4-a8e5-81126b920e8f'], status=DOWN, tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-31T03:40:21Z on network _ns_name=qdhcp-faa2b805-7898-4fb2-ad51-49251da6e35e, admin_state_up=True, availability_zone_hints=[], availability_zones=['nova'], created_at=2022-03-28T08:39:24Z, description=, id=faa2b805-7898-4fb2-ad51-49251da6e35e, ipv4_address_scope=None, ipv6_address_scope=None, is_default=False, mtu=1500, name=provider1, non_local_subnets=[], port_security_enabled=True, ports=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a16a98>, <neutron.agent.linux.dhcp.DictModel object at 0x7f56d29c8eb8>], project_id=a1758405f9c24ae191543248ad65a447, provider:network_type=flat, provider:physical_network=provider, provider:segmentation_id=None, revision_number=2, router:external=True, shared=True, status=ACTIVE, subnets=[<neutron.agent.linux.dhcp.DictModel object at 0x7f56d3a169d8>], tags=[], tenant_id=a1758405f9c24ae191543248ad65a447, updated_at=2022-03-28T08:39:29Z, vlan_transparent=None 2022-03-31 11:40:21.207 47489 INFO neutron.agent.dhcp.agent [req-d7cb57c1-4cda-4ceb-99ca-18ca650db61b - - - - -] DHCP configuration for ports {'20e8d806-f976-4415-85f5-ed2df55978dc'} is completed I would very appreciate any kind of guidance or help. Thank you, Han Guangyu

2 1

[neutron] bug deputy report of week 2022-03-21
by Bence Romsics 31 Mar '22

31 Mar '22

Hi Team, Once again sorry for the late report. Needs attention: ovn-octavia-provider maintainers please have a look at the the two ovn-octavia-provider bugs below. Critical: * https://bugs.launchpad.net/neutron/+bug/1966394 Functional tests hits oom-killer which is causing job failures gate failure, fix proposed: https://review.opendev.org/c/openstack/neutron/+/835179 * https://bugs.launchpad.net/neutron/+bug/1966035 neutron.tests.functional.agent.test_dhcp_agent.DHCPAgentOVSTestCase.test_good_address_allocation is failing intermittently One-off gate failure that we cannot reproduce, may need to be looked at again if it recurs. Medium: * https://bugs.launchpad.net/neutron/+bug/1965819 list object has no attribute 'acked' fix in ovdbapp merged and backported to wallaby: https://review.opendev.org/q/Iad0d7472a7adce4a79111f94a2f33fc5b1a5c530 proposed fix in neutron waiting for ovsdbapp release: https://review.opendev.org/c/openstack/neutron/+/834613 ovn-octavia-provider: * https://bugs.launchpad.net/neutron/+bug/1965772 ovn-octavia-provider does not report status correctly to octavia * https://bugs.launchpad.net/neutron/+bug/1966052 ovn-octavia-provider associates to wrong logical router when LogicalRouterPortEvent is fired and network has multiple routers Incomplete: * https://bugs.launchpad.net/neutron/+bug/1966383 ovs-agent: value -1 is not a valid port number when _set_port_filters * https://bugs.launchpad.net/neutron/+bug/1966121 [neutron-tempest-plugin] Test fails with AttributeError: type object 'DNSIntegrationTests' has no attribute 'query_client' Probably not a bug in code, but a dependency error in the reporter's environment. Invalid: * https://bugs.launchpad.net/neutron/+bug/1966403 Cres_Ubuntu 20.04,CI,Checkbox TPM test failed Cheers, Bence

1 0

[largescale-sig] Next meeting: Mar 30th, 15utc
by Thierry Carrez 31 Mar '22

31 Mar '22

Hi everyone, The Large Scale SIG will be meeting this Wednesday in #openstack-operators on OFTC IRC, at 15UTC. With recent DST changes, you should doublecheck how that time translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220330T15 Feel free to add topics to the agenda: https://etherpad.openstack.org/p/large-scale-sig-meeting Regards, -- Thierry Carrez

1 1

[kolla] Zed PTG Schedule && cancel weekly meeting 6th April
by Michał Nasiadka 31 Mar '22

31 Mar '22

Hello Koalas, The PTG is going to take place next week (April 4th to 8th). Kolla sessions are planned Mon/Tue 13-17UTC (Kolla/Kolla-Ansible) and Wed 13-15 UTC (Kayobe slot) in Havana room. NOTE: The weekly team meeting on 6th April is cancelled - since we’ll all be discussing Kayobe on the PTG then. If you haven't registered yet, there's still time! Please register here [2]. [1] https://etherpad.opendev.org/p/ <https://etherpad.opendev.org/p/>kolla-zed-ptg [2] https://openinfra-ptg.eventbrite.com/ <https://openinfra-ptg.eventbrite.com/>

1 0

Volume attached to removed instance
by Derek O keeffe 31 Mar '22

31 Mar '22

Hi all, We are having an issue with a volume. The volume was created and attached to an instance that was then deleted. We now need to attach the volume to another instance to rescue the data on it but it still thinks it's attached to the deleted instance and we can't "manage attachments" or view the details of the volume. We have tried forcing it from the cli to detach but with no luck. We were thinking of doing it through the DB but said we'd askhere first in case anyone has experienced the same and has a better way of approaching the issue. Thanks in advance. Regards,Derek

3 3

[edge] Edge sessions at the PTG
by Ildiko Vancsa 30 Mar '22

30 Mar '22

Hi, I’m reaching out to you to draw your attention to the edge related sessions at the PTG next week. As part of the event the OpenInfra Edge Computing Group[1] is meeting on three consecutive days, where we will talk about the challenges and steps to deploy and operate end-to-end edge infrastructures in production. Please join us if you have relevant experience, expertise or challenges to discuss requirements and solutions. The time slots of the edge sessions are the following: * Monday (April 4) at 1300 UTC - 1500 UTC * Tuesday (April 5) at 1500 UTC - 1700 UTC * Wednesday (April 6) at 1400 UTC - 1700 UTC For further details about the session and agenda please check out this article: https://superuser.openstack.org/articles/edge-in-production-at-the-upcoming… Please let me know if you have any questions. Thanks and Best Regards, Ildikó Váncsa [1] https://wiki.openstack.org/wiki/Edge_Computing_Group

1 0

[TripleO] TripleO Zed PTG topics Etherpad
by James Slagle 30 Mar '22

30 Mar '22

TripleO, Please add your proposed topics for the PTG to this etherad: https://etherpad.opendev.org/p/tripleo-zed-ptg-topics I will reserve time allocation for TripleO based on the number of proposed topics. Thanks! -- -- James Slagle --

2 3

[manila] Zed PTG schedule
by Carlos Silva 30 Mar '22

30 Mar '22

Hello fellow Zorillas and interested stackers, The PTG is going to take place next week (April 4th to 8th). Our agenda starts at 16 UTC with the Yoga cycle retrospective, as usual. On the following days, we will proceed with the proposed topics. The topics in the official Manila PTG etherpad [1] now have a proposed time slot assigned to them. Please check the etherpad and if you would like to have a topic moved around, please let me know. If you haven't registered yet, there's still time! Please register here [2]. [1] https://etherpad.opendev.org/p/zorilla-ptg-manila [2] https://openinfra-ptg.eventbrite.com/ See you soon! Thanks! carloss

1 0

[magnum] kube_cluster_deploy timing out
by Chris DiLorenzo 30 Mar '22

30 Mar '22

Hello, I'm trying to deploy a kubernetes cluster using CoreOS 33. I have also tried with CoreOS 35/. 1 master, 1 worker. Ths VMs are deploying without issue. However, the stack is timing out on kube_cluster_deploy. It appears the kubernetes API isn't running: [root@tes-001-pkjawhk66slm-master-0 log]# podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a08cbea59a57 docker.io/openstackmagnum/heat-container-agent:wallaby-stable-1 /usr/bin/start-he... 21 minutes ago Up 21 minutes ago heat-container-agent [root@tes-001-pkjawhk66slm-master-0 log]# ss -ln | grep 8080 -> nothing [root@tes-001-pkjawhk66slm-master-0 heat-config-script]# tail -f 8d8fa128-bca4-485e-946f-90732ebb4cf0-tes-001-pkjawhk66slm-kube_cluster_config-bwkfqwjxzk36.log + sleep 5 ++ kubectl get --raw=/healthz The connection to the server localhost:8080 was refused - did you specify the right host or port? + '[' ok = '' ']' + sleep 5 ++ kubectl get --raw=/healthz The connection to the server localhost:8080 was refused - did you specify the right host or port? + '[' ok = '' ']' + sleep 5 ++ kubectl get --raw=/healthz Not sure where else to look. Thanks Chris

2 1